PatKerr

Hi. Just spotting this comment now.

It was probably just due to some parameter tweaks that were made during "tuning", especially when the game designers started making adjustments.

I'll maybe see if I can reproduce such changes eventually, but I'm going to be busy travelling from the next little while, so don't hold your breath! Sorry.

Just use "view source" from inside Motion Lab.

I deliberately kept it as plain JavaScript with no aggressive obfuscation.

There are even some comments! ;-)

I actually use that word quite a lot in normal writing, and find that my general tone is quite bot-similar.

I am nevertheless unworried by this. ;-)

#replicant

Partial AI use, yes, on the diagrams -- somewhat as an experiment to see whether it was any good. I thought it was better than nothing.

But the core text was hand-written, and the code faithfully represents the logic of the hand-crafted original from 30 years ago.

The original was very similar, but with minimum UI (no "Settings" panel), and it was just black on white line drawings, although I did add skid trails etc. after I'd got the core of it working.

It's probably not a realistic enough simulation to be a viable learning aid, but that's a funny idea.

I might build something else on top of this though, and will try to keep parking in mind!

That's an interesting problem, and I can't immediately see why you would keep getting a side-effect like that.

Good luck with figuring it out!

There isn't much "air resistance" (or general velocity dampening) on these things, and the velocities carry over when you change the body's "shell".

So, it's sort of intended, but also not very significant one way or the other.

LOL!

I am the author of this thing, and I find your comment very amusing. ;-)

Just the little bits of text glueing the (yes, machine generated) diagrams together as I recall, when I was indeed trying to finish the thing off in a bit of a hurry.

I wrote the rest of it "by hand" though.

Thanks. I'm glad you liked it.

Correction, it was some mildly ChatGPT-assisted PatSlop.

I speak with some authority on the matter. ;-)

What in particular would you like to know?

As I said in the summary article, the core is a "textbook" 2D rigid body simulation (the "Brick" layer), and the Car bit is mostly a matter of deciding what forces are applied to the tyres.

In short, the tires "like" to go back and forward, but resist going sideways (relative to the direction they are pointing in).

The forces which are applied at the tyres are roughly equivalent to friction, but not quite (friction is stranger than many people think, and is not actually very velocity dependent). In some ways my tyre forces actually behave more like a form of "viscous drag" actually. I knew this was a bit dodgy at the time, and it was a sort of conscious "hack" that was chosen to produce "playable" behaviour as simply as I could.

Thanks. I'm glad you got something out of it.