Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

jamesdrandall.com

Post reply on HN
Print view View original

11–20 of 40 posts

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

#11

Post by linsomniac »

iambenm wrote: post #5

Hmm - the article isn't dated and it doesn't mention which models were used for the initial slop version. The initial commit in the git repo is from Feb 15, 2026. I wonder how the initial pass would fare now with Fable 5 or 5.6 Sol?

I've been saying for months that any time you say something about the capabilities of the AI tooling you should say what exact model, agent, and effort level you're using. Because I've taken a few of those "AI can't do X" and had AI do a fine job at them.

I have Sol 5.6 ultra working on Thrust right now.

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

#12

Post by jamesrandall »

iambenm wrote: post #5

Hmm - the article isn't dated and it doesn't mention which models were used for the initial slop version. The initial commit in the git repo is from Feb 15, 2026. I wonder how the initial pass would fare now with Fable 5 or 5.6 Sol?

I think it was Opus but can't remember the version. Would have been whatever was available in Claude Code in February.

Managed to find some screenshots. It did work but gravity wasn't really gravity - things fell at a constant rate. Turrets were floating in mid-air. It was missing the shields and you couldn't pick up the ball from the pedestal.

https://www.jamesdrandall.com/old-thrust/1.png

https://www.jamesdrandall.com/old-thrust/2.png

https://www.jamesdrandall.com/old-thrust/3.png

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

#13

Post by jamesrandall »

acbart wrote: post #2

I'd be interested in seeing the "slop" version for comparison.

Managed to find some screenshots.

https://www.jamesdrandall.com/old-thrust/1.png

https://www.jamesdrandall.com/old-thrust/2.png

https://www.jamesdrandall.com/old-thrust/3.png

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

#14

Post by SamBam »

not-a-llm wrote: post #9
abtinf wrote: post #3

> This is where things got interesting. Not because AI wrote the code — the code itself isn’t complicated, it’s a 1986 game that ran in 32K of RAM — but because Claude turned out to be an extraordinary tool for interrogating 6502 assembly. Complaining about slop with slop.

> The tick loop waits at least 3 centiseconds per frame, giving an effective rate of about 33.33 Hz 3 centiseconds instead of 30 miliseconds, totally not a robot

Why would AI say that, when nearly every piece of training data is ever been fed would use milliseconds? I think much more likely that this is how the author thinks of it.

3 hundreds of a second == 33 Hz is very clean in my human brain.

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

#15

Post by jamesrandall »

spudlyo wrote: post #4
abtinf wrote: post #3

> This is where things got interesting. Not because AI wrote the code — the code itself isn’t complicated, it’s a 1986 game that ran in 32K of RAM — but because Claude turned out to be an extraordinary tool for interrogating 6502 assembly. Complaining about slop with slop.

I was about to complain at you for jumping to conclusions, but your cited example contains two emdashes and a nested "it's not X it's Y". It certainly looks like slop. In my own writing I'm increasingly conscious of trying to avoid the appearance of slop, I would like to think I would have caught this.

For what its worth the article was a mix of things I wrote and things I asked an AI to generate from the notes I'd accumulated from the archaeology.

My focus was on the recreation - and getting it accurate was a lot of work (and a lot of fun). It's pretty easy to get an approximation (particularly if you just go with a standard physics model) but one that feels "off" if you played the original a lot.

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

#16

Post by nnevatie »

SamBam wrote: post #14
not-a-llm wrote: post #9

Earlier quoted context omitted.

> The tick loop waits at least 3 centiseconds per frame, giving an effective rate of about 33.33 Hz 3 centiseconds instead of 30 miliseconds, totally not a robot

Why would AI say that, when nearly every piece of training data is ever been fed would use milliseconds? I think much more likely that this is how the author thinks of it. 3 hundreds of a second == 33 Hz is very clean in my human brain.

No one, ever, uses centiseconds in this context.

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

#17

Post by [deleted] »

not-a-llm wrote: post #9
abtinf wrote: post #3

> This is where things got interesting. Not because AI wrote the code — the code itself isn’t complicated, it’s a 1986 game that ran in 32K of RAM — but because Claude turned out to be an extraordinary tool for interrogating 6502 assembly. Complaining about slop with slop.

> The tick loop waits at least 3 centiseconds per frame, giving an effective rate of about 33.33 Hz 3 centiseconds instead of 30 miliseconds, totally not a robot

[deleted]

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

#18

Post by tom_ »

nnevatie wrote: post #16
SamBam wrote: post #14

Earlier quoted context omitted.

Why would AI say that, when nearly every piece of training data is ever been fed would use milliseconds? I think much more likely that this is how the author thinks of it. 3 hundreds of a second == 33 Hz is very clean in my human brain.

No one, ever, uses centiseconds in this context.

Centiseconds was one of the ways time was measured on the BBC Micro. Your convenient options for accurately measuring the passage of time were vsyncs (50/sec), centiseconds (100/sec), microseconds (1,000,000/sec), or cycles (2,000,000/sec).

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

#19

Post by jamesrandall »

nnevatie wrote: post #16
SamBam wrote: post #14

Earlier quoted context omitted.

Why would AI say that, when nearly every piece of training data is ever been fed would use milliseconds? I think much more likely that this is how the author thinks of it. 3 hundreds of a second == 33 Hz is very clean in my human brain.

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.

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

#20

Post by iainmerrick »

Your reconstruction is so close, I'm a little surprised you didn't stick with the original controls! Even though the BBC had a rather weird layout for all the non-alphanumeric keys.

It's been a very long time since I played Thrust, and I've played plenty of WASD games in the meantime, but it still felt really strange to control it that way rather than the classic BBC Z/X/*/? for left/right/up/down.

Pretty sure it was return to fire, space for shield/tractor; and maybe * for thrust? Edit to add: ah, no, shift to thrust. Works very well on modern keyboards too.

Post reply on HN