I would be highly interested in a good library for vehicles - I spent tons of time back in the day trying to get nice car physics in jME, but they never really felt the way that I would’ve liked them to. For me, the absolute (wish) focus of this project would be a good API for the physics, with tons of tweakable values. Stuff like GUI, maps, horn sounds, break marks on the ground sure are nice-to-have, but I see this more as an additional feature, that is nowhere near as important as the actual physics.
I most likely won’t have time to support this topic code-wise, but my suggestion would be to maybe split the library into two parts:
- a core library, offering vehicle physics with all the parameters, car loading, etc.
- a samples library (based on core), that offers sample cars, a playground map, GUI, horns, break marks, maybe even a demo app and all the other fancy stuff that people might want to use when setting up a project without wanting to go the whole way of implementing it customized for their game
… with the focus obviously being to provide a good extensible core. I saw Jay doing quite a bit of research on this topic (math and physics wise) and it makes sense, that his implementation might be better than the one we had in the past. I think with his work as a base, there is a high chance to come up with a great addition to jME, so it would be unfortunate if all this fresh motivation was spent on fancy demo stuff that isn’t correlated to the actual physics, which in my opinion is worth way more. But don’t get me wrong, any addition is great, I just wanted to highlight where my personal interest in this library would be.
In any case, however you decide and on whatever you work in this project - Good luck!