Live data from Hacker News

AI Can't Recreate the Thrust Game (But It Can Help You Understand It)

jamesdrandall.com

31–40 of 40 posts

Re: AI Can't Recreate the Thrust Game (But It Can Help You Understand It)

#31
post #10

Funny. I had claude recreate Thrust based on wiki article alone - and it nailed it. I then spent a week trying to implement a perfect autopilot for it. And then a solveable level generator. I have this running as a screen saver in one of my apps.

It might not have been to the exacting taste of someone who wanted the exact BBC micro version however...

Re: AI Can't Recreate the Thrust Game (But It Can Help You Understand It)

#32
post #10

Funny. I had claude recreate Thrust based on wiki article alone - and it nailed it. I then spent a week trying to implement a perfect autopilot for it. And then a solveable level generator. I have this running as a screen saver in one of my apps.

I’ve had this pretty frequent experience with AI where someone says, “AI can’t do X,” then someone a little more experienced with the tools or maybe a little luckier gets some prompts together with the solution in a few hours.

I think I’ve been on both sides of this.

Re: AI Can't Recreate the Thrust Game (But It Can Help You Understand It)

#33

I feel like a lot of the success of an AI project currently still comes down to the skills of the operator. I don't think it is possible to say "AI can't create this because I told AI to create it and it failed" any more than you can say "You can't write this in Rust because I tried and failed." There is still a TON of skill involved in guiding an AI to create something, and how good it turns out has a lot to do with…

This is often people invoking chesterton's fence, where the quickest way to have something corrected on the internet is just to say something wrong.

Re: AI Can't Recreate the Thrust Game (But It Can Help You Understand It)

#34

Earlier quoted context omitted.

No one, ever, uses centiseconds in this context.

It's actually in the commented original disassembly and used in some of the original BBC documentation / writing. Which is how it ended up here - the article is a mix of things I wrote and things I asked an AI to write for me from the notes / findings from the archaeolgy.

Ok, that makes sense. I was commenting from a modern gamedev context.

Re: AI Can't Recreate the Thrust Game (But It Can Help You Understand It)

#35

Earlier quoted context omitted.

It's actually in the commented original disassembly and used in some of the original BBC documentation / writing. Which is how it ended up here - the article is a mix of things I wrote and things I asked an AI to write for me from the notes / findings from the archaeolgy.

Ok, that makes sense. I was commenting from a modern gamedev context.

The weird world of retro game archaeology - it's genuinely fascinating.

Re: AI Can't Recreate the Thrust Game (But It Can Help You Understand It)

#37
post #32
post #10

Funny. I had claude recreate Thrust based on wiki article alone - and it nailed it. I then spent a week trying to implement a perfect autopilot for it. And then a solveable level generator. I have this running as a screen saver in one of my apps.

I’ve had this pretty frequent experience with AI where someone says, “AI can’t do X,” then someone a little more experienced with the tools or maybe a little luckier gets some prompts together with the solution in a few hours. I think I’ve been on both sides of this.

Those “AI can’t do x” articles/videos are not aging well.

I’m not sure why people keep thinking like that after seeing Will Smith eating pasta.

Also, not for nothing but every one of those “AI got it wrong, it’s really ___” are… training AI how to get it right.

Re: AI Can't Recreate the Thrust Game (But It Can Help You Understand It)

#38
post #32
post #10

Funny. I had claude recreate Thrust based on wiki article alone - and it nailed it. I then spent a week trying to implement a perfect autopilot for it. And then a solveable level generator. I have this running as a screen saver in one of my apps.

I’ve had this pretty frequent experience with AI where someone says, “AI can’t do X,” then someone a little more experienced with the tools or maybe a little luckier gets some prompts together with the solution in a few hours. I think I’ve been on both sides of this.

To be fair, designing an autopilot was an ordeal. Opus stuck to the principle of a mix of waypoint based routing plus a PD regulator - which made playing perfect levels hard. I wanted it to use the fact that the game mechanics is perfectly deterministic so theoretically it should be able to compute a perfect walkthrough before starting a level. It very reluctantly tried a monte carlo approach which ultimately kept failing. I have given up and went back to a smarter version of the waypoints + PD + softening the transition between waypoints. It is producing good, fast paced playthroughs but I've seen better speedruns by human players. Need to find time to see if Fable does a better job.

Re: AI Can't Recreate the Thrust Game (But It Can Help You Understand It)

#39
post #31
post #10

Funny. I had claude recreate Thrust based on wiki article alone - and it nailed it. I then spent a week trying to implement a perfect autopilot for it. And then a solveable level generator. I have this running as a screen saver in one of my apps.

It might not have been to the exacting taste of someone who wanted the exact BBC micro version however...

For sure. What it gave me was I think similar to the Amstrad version of Thrust and since I originally played it on a Commodore PLUS/4 I had to tweak it a bit. The fist version also had wrong gravity and rotation speed constants. But those were easy tweaks. Whenever I am bored or waiting for something more serious to complete I recreate games I used to play as a kid. I am currently working on Mercenary.
Post reply on HN