Turning off VSync with 0.8 SDK

I don't think there is an option to disable V-Sync any longer.

But does your simulation really need to run at 150fps? Can you make it framerate independent?

You could just skip all rendering every other frame, or X number of fixed time simulation steps per render loop to match a desired number of steps per second. Having your simulation timestep be framerate dependent is never a good idea unless you really dont care about stability. People with slower computers will see different behavior, or behavior will change depending on what is visible on screen.

"cybereality" wrote:
I don't think there is an option to disable V-Sync any longer.

But does your simulation really need to run at 150fps? Can you make it framerate independent?

Yes unfortunately for many simualtions like smooth particle hydrodynamics, fluid dynamics or fur for example you need a pretty small time step so the simulation doesn't blow up, and ideally the time step should not fluctuate or at least have a minimal ( stable ) rate. I'm guessing turning of V-Sync isn't the ideal solution anyway so I'll try to find a work around like running the simulation multiple times per frame as owenwp suggested, I just think this will result in hitching if I want or need a simulation rate that is not a perfect multiple of 75hz. For 150 I'd just run the simulation twice per rendered frame, but if I wanted 120, I'd have to double up simulation steps every 5 of 8 frames which I can see causing a problem since the steps need to be the same length.

Same problem I'm guessing will happen if I multi-threaded.

"owenwp" wrote:
You could just skip all rendering every other frame, or X number of fixed time simulation steps per render loop to match a desired number of steps per second. Having your simulation timestep be framerate dependent is never a good idea unless you really dont care about stability. People with slower computers will see different behavior, or behavior will change depending on what is visible on screen.

Thanks, I'm going to try this when I have some time. As mentioned above it might have to be a perfect multiple, like doubling up simulation steps per frame to achieve 150 or else I'd be doing 2 simulation steps one frame, and maybe not the next, but my simulation steps need to be the same length for consistent simulation.

Would be better if the VSync didn't stall the engine or thread, but I guess that's how it's designed to work and I probably need some tricky multi-threading support.

I don't think there should be any issue with iterating multiple times per frame with a fixed timestep. This is ideal, since you should not rely on the framerate being anything is particular (as this can be variable based on so many factors). See this article. http://gafferongames.com/game-physics/f ... -timestep/