Can not access https://editor.construct.net/r293-3/

I join. I support 2 games in Play Store. And they are spoiled by the new version of r302. There are problems with rendering 3D and transparency of objects.

The new version brought new cool features, but it is not compatible with r293.3

I was thinking about this yesterday. It's always good to have new features, but almost every time there's a stable release, someone (or sometimes everyone) has issues.

This is not a bash against Scirra at all. This is the nature of software development, and for that reason, nearly every piece of software on my PC has settings to request doing an update before it does so. People should be allowed to update their software when it suits them. I'd rather put up with a "there's an update available!" message every time I open Construct than be forced to use versions which could introduce bugs into my development process.

When I click "not now", that should mean "leave me alone until I'm ready to deal with this", and not "okay just do it next time".

And yes, there are workarounds, like using the browser and specifying a url, but that completely defeats the purpose of installing C3 and using it like a traditional application.

The solution would be to not auto-update C3 unless I tell it to by checking a box.

Solved the access problem...

* press the small "i" next to adress bar.

* click cookies

* select construct cookie

* press delete

* reload page

I am now trying to "install as app".

Tried to uninstall construct using uninstall button, the icon is gone but no option to "install as app" appears and the "open in construct" context menu is still available, currently I can not find anywhere how to uninstall construct 3 to make the "install as app" appear in r293.3

Loading r293.3 works fine for me. I don't know why there would be a problem loading it - it's loading the same version as you would have previously been using.

We work hard to make sure changes don't break anything. By the time of a stable release most of the changes have also had several weeks of public testing in beta releases, but sometimes things slip through the net. I apologise for any inconvenience with changes in updates, but it's impossible to make any changes to software without some risk of breaking existing things; sometimes mistakes are made and not caught by beta testing. The best thing to do is to report any problems by filing an issue following all the guidelines. It's also very helpful if regular users can at least occasionally try their projects in the latest beta release, and let us know if anything isn't working, so we can make sure any accidental breakages are fixed before the stable release.

I'd add we also have fixed loads of other bugs between r293.3 and r302, so the overall reliability of Construct has definitely improved, and will continue to improve. The longer you stick to an old release the more likely you are to end up stuck on some other issue that we already fixed, so it's best to regard that as a temporary measure and focus on getting your project working in the latest release.