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.
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.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot post attachments in this forum