Okay, everything has started with Chrome lagging for my game at 60 fps. I’ve tried some approaches, but nothing worked except of Variable Dt (but variable Dt causes some other messy stuff).
I’ve tried bundle HTML5 with release mode on. But the result was the same. If I understand everything right release mode must turn off all the debug stuff like
msg.post("@system:", "toggle_profile")
Or not? At 30 fps with release mode on, profiler is not showing. But at 60 fps with toggled profiler and release mode on I am able to see all the profiler’s info on screen. This pushes me to the idea of release mode is not working properly at 60 fps.
Once more:
30 fps, release mode on: I have no lags in Chrome, profiler’s info is not displaying.
30 fps, release mode off: I have lags in Chrome, profiler’s info is displaying.
60 fps, release mode off: I have lags in Chrome, profiler is displaying.
60 fps, release mode on: I have lags in Chrome, profiler is displaying.
One more thing why I think there is something wrong with release mode. Referring to Ragnar_Svensson: “The thing that differs in release mode is that we throw away all the reverse-hash info to save memory. If you ever do things like local s = str(my_hash), that won’t work in release mode.”
I have local s = str(my_hash) stuff working (it actually shouldn’t) in 60 fps with release mode. But this doesn’t work in 30 fps with release mode, like it should.