Hi,

 

If things go according to plan, we will release the first version (including suspensions) in the next weeks in March - but I cannot guarantee the date. We plan to release it with the source code, so that you can adapt and extend it as required in your game.

The constraint car is not the ideal method for car simulation. It primarily acts as a test/demo for our constraint classes - and that is one reason why we use motor constraints ;-).
Applying forces feels indeed more natural and is a possible solution. On the other hand, constraints have the advantage that they are more stable in the simulation than force effects.
Our car physics is currently under development and we are still evaluating and comparing solutions. I can give you more information, when our implementation is finished.

I don't want to look impatient but... any news on that?

Hope it's not been abandoned, I'm holding on my purchase for it :)

Awesome, thanks!!

Ok, I've been playing around with the vehicle sample. It's cool! I was initially worried about performance on the 360, since adding 3 or 4 more cars would bring the framerate down, but it turns out that the culprit was the scenery - removing all debris, bridges etc. leaves enough fps for 8 cars or more. Would need to investigate a bit more to determine whether it is the rendering or the simulation that is expensive, but anyway. The incoming blog article will probably clarify a few more things for me.

So, I'm definitely sold now - you can count on my purchase :)

Thanks

When you say "let the simulation run parallel to the Draw() method" you mean that by default the car simulation is not multithreaded?

Fantastic article BTW!