We're working on exposing jolt's vehicle API + build question!

[bryanedds]

Hi Amer!

I don't think we have your direct discord contact, so we're just making this issue to let you know that we're working on exposing the vehicle API for your Jolt wrapper! This is for our upcoming racing gaming project we started working on very recently -

As for the Jolt API, these are the types we're planning to expose -

Wheel
WheelSettings
VehicleController
VehicleControllerSettings
VehicleConstraint
VehicleConstraint::CombineFunction (optional)
VehicleConstraint::StepCallback (optional)
VehicleConstraintSettings
VehicleAntiRollBars
VehicleCollisionTester with
 | VehicleCollisionTesterRay
 | VehicleCollisionTesterCastSphere
 | VehicleCollisionTesterCastCylinder

Please let us know if we've missed any!

These are our forks that we're going to make our pull requests to you here -

https://github.com/bryanedds/joltc

https://github.com/bryanedds/JoltPhysicsSharp

We'll update you as progress is made - shouldn't take us more than a day or two to have a PR ready for you!

Our big question is around building the joltc library for non-Windows platforms, such as Linux and Android for testing. We are hoping you'll be able to make the builds for all the platforms once you uptake our PR, but we'd at least like to build and test on Linux before submitting said PR. We'd like to be able to augment our organizational knowledge on how to build for these varying platforms.

[amerkoleci]

Hey Bryan,
Thanks for brilliant work, waiting for PR.

Yeah, I build joltc for windows (x64. arm64), linux (x64), macos (x64/arm64), android

Keep me updated,
Amer

[bryanedds]

After starting implementation, it appears the implementation effort was underestimated, so we're only able to provide a partial implementation on the first pass. The first thing we need to see is if a Jolt vehicle will be suitable for our type of racing game to begin with!

[bryanedds]

Progress appears to have been steadily made, tho it's been a bit more work than I had previous calculated :D

However, it looks like we'll be able to do the integration part of the new wrapper API by tomorrow evening and should hopefully having at least a vehicle accelerating in a Nu scene then!

Will post you a screenshot once we have something to show!

[bryanedds]

Yes, we finally have vehicle movement via user input in our .NET engine! No screenshot until likely tomorrow tho, sorry!

[amerkoleci]

Yes, we finally have vehicle movement via user input in our .NET engine! No screenshot until likely tomorrow tho, sorry!

Nice, waiting for screenshot and PR, good job!

[bryanedds]

Pile-up on the highway!

[bryanedds]

A driving is taking place!

[bryanedds]

Currently, the mostly out-of-box driving model seems quite fun and skill-based, but it does seem too stiff. I'm trying to adjust vehicle settings to get more of a Ridge Racer 'Grip Style', but so far, none of my adjustments have had the intended effect. Beyond just reading this document (https://www.asawicki.info/Mirror/Car%20Physics%20for%20Games/Car%20Physics%20for%20Games.html), I'll have to find a way to get a better understanding of the various settings that I could tune to enable this.

[bryanedds]

An x64 Windows build of the above Project Race Prototype Sample v0.1.0 is available here! - https://github.com/bryanedds/Nu/releases/tag/v18.16.0. As you'll see, the vehicle is still a bit too stiff to control but is surprisingly playable given that most of the vehicle settings are straight out of the box.

Amer, we'll have to discuss just how fine-grained you'll want the exposed vehicle API. In order to get things up and testable, I skipped implementing quite a bit of the overall API. There's just a lot there we didn't need to get up and running and much that we probably won't ever need.

[bryanedds]

Okay, so I was planning on trying to add more features before issuing the PRs, but for the last two weeks I've just kept getting pulled into other things. So even tho I feel like I could at least round out what parts of the API is exposed with further work, I'll go ahead and issue the PRs since I'm apparently not able to predict when I'll be able to work on it more.

Pull Requests here -

amerkoleci/joltc#38

#127

Thank you for your patience and attention so far, Amer!

[amerkoleci]

Okay, so I was planning on trying to add more features before issuing the PRs, but for the last two weeks I've just kept getting pulled into other things. So even tho I feel like I could at least round out what parts of the API is exposed with further work, I'll go ahead and issue the PRs since I'm apparently not able to predict when I'll be able to work on it more.

Pull Requests here -

amerkoleci/joltc#38

#127

Thank you for your patience and attention so far, Amer!

Hi
Merged both PR, thanks!

Monday I'll revisit code and do changes if required
Thanks again
Amer

[amerkoleci]

Hi,
I managed to visit the changes, not really happy and will improve it when possible, just little bit busy these days

Thanks for PR,
Amer

[bryanedds]

Yes, it definitely needs work as this really is just a first pass. We are planning to do additional passes as well once we can return to the project's development. Let us know when you've done your pass and we'll continue from there.