Sometimes vsync is not desired when testing WebGL and other animations in Chrome. This is how to launch chrome without vsync in OSX, from the command line.
open -a "Google Chrome" --args --disable-gpu-vsyncHappy coding.
Sometimes vsync is not desired when testing WebGL and other animations in Chrome. This is how to launch chrome without vsync in OSX, from the command line.
open -a "Google Chrome" --args --disable-gpu-vsyncHappy coding.
I am experiencing strange (not so strange) bug in chrome, when you return to the tab with launched engine, the timestep gets broken. Reproduced on softWheel example at jsFiddle: perform any action in “js” panel (drive back and forth), switch to another tab for 10 seconds and return back – watch the execution is faster than normal. It becomes okay after some random time.
Obviously, it is caused by resources distribution system, but can you suggest a quick solution for that. I am reading sources now and without “world step setup” cannot invent any.
The solution is to not add to the deltaTime while the user is away. See https://github.com/schteppe/p2.js/issues/229
Thank you