Rendering and physics thread repartition

[Marcus]

[Kzinti]

[refractor]

For some (relatively esoteric) handheld systems (notably the GP2X) it is worth partitioning the game code into two because they do have multiple CPUs. It's also worth considering if you're targeting the game at current/future PCs.

However, I agree with kzinti and would target a single-cored machine with a traditional single-threaded one. There's no point messing about with the extra thread synchronisation overhead if you're not gaining anything anyway.

[Marcus]

[Kzinti]

[Marcus]

[Marcus]

[jaguard]

[warmi]

[Kak]

in a single loop, you can just render once and run the physics thread as many times as you need, depending on the time spent so far.

I suppose somebody'd have said it in those long messages though ;)

[Kzinti]

What Kak said... You don't want to run your physics with a variable timestep. Just run the physics at the rate you need (say 30/sec) with a fixed time step.

[Marcus]

[Kak]