Game-destroying update !

Hi everyone.

I wanted to work on my game today, so i launched Construct, which went through a quick update. Then, i wanted to play it a bit to debug some stuff, and i was stunned to see that things that worked perfectly fine until now don't work anymore. The game stopped registering some collisions between the player and some of the stuff. Apparently, when two sprites are on different layers, they can't interact with each other anymore. That's infuriating because i don't get why the developers made that change, and i would have to make extremely time consuming changes to my code to compensate for that modification in Construct. Does anyone know how i can easily fix this, or am i completely screwed ?

Thanks

Uuuuuurgh ! It drives me crazy ! There's so many things that have been broken by the last update ! And of course you can't go back to a previous version of Construct. The game was almost done, and now i need to go back and fix it all. That's just a huge drawback. Thanks a lot, Construct !

you can go back to an earlier version here. Scroll down to the bottom of the page.

construct.net/en/make-games/releases

This update broke my project. I keep getting message "failed to open project". How can this be fixed? I've been working on this game for a long time. I can roll back to a prior build but then what happens going forward? Construct needs to fix this so existing projects continue to work

the same is happening with me =/ i hope it gets fixed soon

actually, when i tried firefox it worked just fine, its just laggy to work on firefox (idk why)

In general, if you run in to a problem, please file an issue following all the guidelines. If you are able to provide all that information, frequently issues can be resolved within minutes. Otherwise it is significantly harder and can take weeks or months to establish the problem.

It is also particularly helpful if you can test every beta release from the previous stable release to the latest stable release, and determine which specific release something stopped working in. That usually narrows down the scope of potential changes from months of work to just a week's work.

you can go back to an earlier version here. Scroll down to the bottom of the page.

https://www.construct.net/en/make-games/releases

Thanks ! I didn't realise i could use a previous version. That's a relief !

Folks - we're happy to help but unfortunately there is just nothing we can do if you only write a forum post saying something's broken. Please file an issue if you can. If you really can't figure out the problem from a new project, you can send your full project to supportdnd@construct.net where we will do our best, but it is often impossible to work out what is wrong from a large and complex project, which is why our bug report guidelines ask for a minimal project.

68kStudios

If the problem is opening the project, it can be useful, even if it's massive. If you don't want to share it in the public tracker, you can send it to support.

Could anyone's issue be related to creating objects at run time?

I have a project that works perfectly in 476.4 but not in 487.

Essentially, I have a JSON array that lists some images stored in local storage. I loop through the array and create a sprite for each entry and assign an incrementing instance var to the sprite. Once they're all created, I request the first image from local storage and load it into the first sprite, then increment the var and repeat until all are loaded.

But in 487, the first sprite didn't load on local storage get.

What I've found I need to do to fix is insert a wait 0 seconds after I've created the sprites otherwise the on local storage get doesn't trigger because it can't find the sprite.

I can't replicate in a simple minimal project I just created from scratch and I can't upload my project as it is as it uses a private back end so I'd have to deconstruct it which might take a while.

But the wait 0 workaround works for me, so I'm not too concerned - but just thought my findings might help others.

I have a project that works perfectly in 476.4 but not in 487.

As I said before, one of the most helpful things you can do is test every beta release in between those release numbers, and identify the specific release number the problem first started in. That can narrow it down from hundreds of potential changes to maybe a dozen.

You can also speed things up by testing the half-way point - e.g. test r481, if it works then test half way between that and r487, if it doesn't then test half way between that and r476.4, etc. So you split the range in half each time.

First breaking release is r485