Game-destroying update !

HELLO,

WHEN I AM PAYING AN ANNUAL SUBSCRIPTION FOR A PRODUCT AND THE DEVELOPER TELLS ME THAT AN UPDATE IS STABLE, THE VERY LEAST I EXPECT IS FOR IT TO WORK CORRECTLY.

IF THE SOLUTION TO THE PROBLEMS CAUSED BY A "STABLE" RELEASE IS FOR USERS TO ACCEPT THE FRUSTRATION OR GO BACK TO WORKING WITH PREVIOUS VERSIONS, THEN SOMETHING IS CLEARLY NOT WORKING AS IT SHOULD.

THANK YOU.

I FULLY UNDERSTAND THAT NO SOFTWARE IS PERFECT AND THAT ISSUES CAN OCCASIONALLY ARISE. HOWEVER, WHEN PROBLEMS OCCUR ON A REGULAR BASIS, IT IS ONLY REASONABLE FOR USERS TO BEGIN QUESTIONING THE CURRENT VERSION RELEASE PROCESS.

We just released r487.3 to correct a few more regressions. Hopefully that resolves any remaining compatibility issues since the previous stable release.

No software is perfect and also no testing system is perfect either - there is always going to be the risk of a couple of issues that slip through the net and end up in a stable release. We are usually very responsive when people file issues, and if you follow all the guidelines, often an issue can be fixed within minutes. The main cause of delays in fixing issues is nobody filing an issue. I'm afraid it's usually impossible to investigate issues when people just write that something doesn't work in a forum post or comment - we're not telepathic! And if we haven't been able to identify the issue ourselves, then we have nothing to go on. So I would ask for your patience and co-operation if any issues come up - please file an issue, and with a good report, often we can have it fixed very quickly.

Hi Ashley,

I didn't file the issue because i'm almost done with my game, and as someone kindly pointed out that i could still launch the previous release where i had no problems with, it seemed simpler for me to just do that and move forward. I realize my message was very blunt, it came from the frustration i felt when i thought i was taking a step big back on the final stretch, but the solution of finishing it with the previous release of construct was fine by me.

I just wanted to let you know the last update completely fixed my issue, so thanks for your kind help.

Cheers !