> Found a solution: not ideal and probably temporary. but switched to construct 3 and so far the lagging and freezing on my larger game has stopped (the saving takes forever though)
>
Yeah a workaround for some, but no solution for others. But it is a great quick fix (I ended doing this for one of my projects recently that was on a tight timeline and could not wait for the bug fix any longer).
zenbynature, (and — and —)
Can you try this?
shutdown with command line using
> C:\Windows\System32\shutdown.exe /s /t 0
When I shut down this way, I seem to have better response times. But it could be coincidental. also worth noting, even after this test the response time is still at unacceptable levels.
I should have said this sooner but I restart my PC every ~30 mins ever since I've encountered this problem as a workaround. As time passes, C2 becomes more and more sluggish. After a reboot, the 5 to 10 seconds delay becomes only 3 seconds every time I restart or shutdown, not sure if it has the same effects when logging out my PC though.
Also, I have tried to convert my project to C3 before but in order for me to have done that, I had to delete my incompatible plugins.
Because of the fact that C3 isn't cross compatible with C2, it's only a one way conversion. I would say this is an impractical solution for
C3 isn't fully equipped with essential 3rd party extensions yet. It's way too soon to permanently move especially with the limited SDK of C3.