It still feels great to play! I love the history too, it's actually a great example of why prototyping "toys" is so important in product development. It allows you to play with isolated concepts without baggage or the expectation to make things production grade. Just getting straight to the point.
Interesting that he namechecks Thrust from 1986, an absolutely amazing game for the BBC Model B, and I guess the first 'physics' game I ever encountered. The 'towing' physics were amazing.
If you accelerate the Car, then switch the configuration from Car to Brick, the brick won't slow down.
Not sure whether is it intended but it feels wrong.
>One weekend in late August 1996, I wrote a 2D physics simulation which later became the basis of the vehicle system in the eventually popular game "Grand Theft Auto" aka "GTA".
I don't mean to be... judgemental, but if you had the talent to go something like this, why devolve on the remake? One could think that a person with your level of skill would be one of the main vanguard for hand coding. Again, I don't want to be too judgemental, as I am not a great programmer and use assisted tools when planning and designing personal apps, but I am just curious.
Why needlessly do extra work when it's easier than ever before to modernize what is already made? Why would he want to be a vanguard for "hand coding"?
I've been a developer for not nearly as long as the author but long enough that at some point it felt like I was writing the same code and same abstractions over and over again and sometimes a new novel problem would reinvigorate my love of programming but today I'm happy to let an LLM write the tedious code while I give the more fun high level architectural direction and when reviewing the code sometimes I'll give it a nudge in a different direction. I suspect the author has written code like the 2d car physics many times over. Just my 2 cents.
I'd say you're fully off the mark here. That page contains serious architectural insight on how to make a "designed" car feeling work within a "physically correct" collision engine. Getting the balance right is super hard and he explains how to do it. I'm confident no AI could do that architecture, so this is most likely hours of hard work with a thin layer of LLM gloss on top.
No, I don't want to see the prompt. Yes it has some llm tics, but it's clear that he went back and forth before arriving at this. Why would I be interested in the transcript?
yes and? someone sharing the details of an extremely popular project is super cool. comments like this will not encourage more people to share more cool things.
I'd be ecstatic if more people used AI to share more cool things they've done. that'd be awesome. more of this blog post please.
Great story, programming and mechanics.
And shortly after I learned how expensive tyres were, I stopped doing handbrake turns.
And shortly afterwards, in addition to all the different physics-in-action experience, I learned about how car insurance excess works.
https://youtu.be/Dt44PEIWBRg?is=CbVTRyDfo8Nt56fH
Thrust was by Jeremy C. Smith who went on to work on Exile with Peter Irvin
It'd be amazing to hook is up with the engine sound simulator: https://github.com/ange-yaghi/engine-sim
http://truckslop.joshu.dev/
I don't mean to be... judgemental, but if you had the talent to go something like this, why devolve on the remake? One could think that a person with your level of skill would be one of the main vanguard for hand coding. Again, I don't want to be too judgemental, as I am not a great programmer and use assisted tools when planning and designing personal apps, but I am just curious.
Seems the author chose option 2 and focused on the article instead.
Ran out of steam, I guess...
I'd be ecstatic if more people used AI to share more cool things they've done. that'd be awesome. more of this blog post please.