Game-destroying update !

There's a relatively small set of changes in that release which potentially narrows it down a lot, but I'm afraid from your description alone it's not clear what change could be responsible. Perhaps there is an accidental side-effect from an unrelated change. I think we will need a smaller project demonstrating the issue to be able to resolve it. The bug report guidelines includes advice on stripping down a full project to a smaller reproduction project for a bug report.

I've narrowed it down to a very specific set of circumstances and raised it here:

github.com/Scirra/Construct-bugs/issues/9125

I do have a simple workaround so don't mind if it's fixed or not, but I'm certain there's been a change in behaviour that the sample project demonstrates. Maybe there's a more serious bug behind this?

I may have found what is causing the "Failed to open project" message and most of the new issues in my game: I've removed every 3d models in my project and now it seems to work with the latest C3 build.

68kStudios - can you reproduce the issue by adding a 3D model to a new empty project? If so, please file an issue with that project.

pumacap - we're not aware of anyone else reporting such issues, and it could also be something else on your system using up a lot of memory. If you want us to investigate further, please file an issue and be as detailed as possible, including testing every beta release since the last stable release to identify which specific release it changed in, along with a sample project file, steps to follow, and measurements of memory usage (preferably from Chrome's task manager as it is probably most accurate - press Shift + Escape to open).

Whenever I run the project, my boolean variables don't change when the event is supposed to make them change, and when I close the preview, it says it cannot read null: Ie. It seems to be some sort of issue with boolean variables.

Hello,

Want to start by saying that I think Construct 3 is a good software. However, with this most recent update the program demands considerably higher performance. With 16 GB ram I can barely make the program open a window in the event sheet to add new events or actions. Before the update it worked alright.

Best regards,

My PC has 16GB of RAM and I never had such an issue, so I don't think the problem is with Construct 3.

EpicNoobDudePro888 - please file an issue so we can look in to that - I'm afraid it's virtually impossible to help from just a forum post.

Always stick to the version that works now. That's an industry-wide approach to making games.

All engines are bound to break your project sooner or later with new updates.

Always stick to the version that works now. That's an industry-wide approach to making games.

You will have to update sooner or later if you want to publish your game. And the more versions behind you are, the more likely you'll run into issues.

JULIUS 😘🖤

**HELLO,**

GIVEN THE GROWING NUMBER OF COMPLAINTS FROM CONSTRUCT 3 USERS, MYSELF INCLUDED, I BELIEVE IT IS TIME FOR YOU TO SERIOUSLY RECONSIDER THE FREQUENCY OF THE SOFTWARE'S UPDATES.

RATHER THAN HELPING, the constant stream of updates has become a real headache for many developers. Every new release brings changes, adjustments, or unexpected issues that force us to spend time testing and adapting our projects instead of focusing on what truly matters: developing our games.

IT OFTEN FEELS LIKE WE SPEND MORE TIME KEEPING UP WITH UPDATES THAN ACTUALLY CREATING.

WOULDN'T IT MAKE MORE SENSE TO REDUCE THE FREQUENCY OF RELEASES AND PUBLISH ONE OR TWO MAJOR UPDATES PER YEAR, thoroughly tested, stable, and optimized?

Many users would greatly value stability and reliability over a constant flow of changes that, in many cases, end up slowing down or disrupting our work.

PLEASE LET US DEVELOP AND FINISH OUR PROJECTS IN PEACE.

**LET US LIVE!**

THANK YOU. 😈🎮🖤

JULIUS 😘🖤

**HELLO,**

GIVEN THE GROWING NUMBER OF COMPLAINTS FROM CONSTRUCT 3 USERS, MYSELF INCLUDED, I BELIEVE IT IS TIME FOR YOU TO SERIOUSLY RECONSIDER THE FREQUENCY OF THE SOFTWARE'S UPDATES.

RATHER THAN HELPING, the constant stream of updates has become a real headache for many developers. Every new release brings changes, adjustments, or unexpected issues that force us to spend time testing and adapting our projects instead of focusing on what truly matters: developing our games.

IT OFTEN FEELS LIKE WE SPEND MORE TIME KEEPING UP WITH UPDATES THAN ACTUALLY CREATING.

WOULDN'T IT MAKE MORE SENSE TO REDUCE THE FREQUENCY OF RELEASES AND PUBLISH ONE OR TWO MAJOR UPDATES PER YEAR, thoroughly tested, stable, and optimized?

Many users would greatly value stability and reliability over a constant flow of changes that, in many cases, end up slowing down or disrupting our work.

PLEASE LET US DEVELOP AND FINISH OUR PROJECTS IN PEACE.

**LET US LIVE!**

THANK YOU. 😈🎮🖤

Dramatic