Ray tracing made possible on 42-year-old ZX Spectrum: 'reasonably fast, if you consider 17 hours per frame to be reasonably fast'
Ray tracing made possible on 42-year-old ZX Spectrum: 'reasonably fast, if you consider 17 hours per frame to be reasonably fast'
i once took 12+ hours to raytrace on an 8mhz Amiga only to realize that it didn't have any light sources and so was pitch black.
I share that memory. At least twice
It's not that the bear dances well, it's that the bear dances at all.
60 frames per 42.5 days, playable.
You could get a totally playable fps if you play in geological time scale
Edit. Not really fpS as s stands for second, but ...
Frames Per Stratum
Nice, hitting that sweetspot at 42 fpm (frame per month)
I mean that's pretty fucking impressive imo. I figured a RT frame would take days to render on hardware that old
And back when that computer was contemporary, it would have. We've learned a hell of a lot since Nvidia announced they had cracked real-time ray tracing all those years ago.
Now write it in Z80 assembly instead of basic and see how much faster you can get it to run.
So true.
When I switched from basic to assembler on a Trash 80 Model 1, it was truly night and day
It’s like playing chess by mail, but with Doom.
My brain initially assumed 17 fps and I was like dayamnnnn
700 years worth of compute to do about an hour of gaming that I just did on my pc at home in realtime ... damn.
Did I math it right? I was averaging about 100 fps in hogwarts for about an hour.
Say you generated 86'400'000 frames. 17h a frame that's roughly 16'767 years.
tbf that’s probably on par with the performance Cyberpunk 2077 was doing on release
Still remember loading games from cassette tapes on this thing and the Z80.
"is it still loading or did it fail?"
ah, plus ça change...
Since my dedicated hybrid graphics card was broken, my gaming experience is almost the same as with this one.
What resolution? I'm guessing 64x48?
The strain of going from a 32 x 22 image to a 256 x 176 one is evident in how much longer this secondary image took to render. From 879.75 seconds (nearly 15 minutes) to 61,529.88 seconds (over 17 hours). Luckily, some optimisations and time-saving tweaks meant this could be brought down to 8,089.52, or near-ish two and a half hours.
Those are really reasonable values. I guess my laptop would take that long to render a 4k image as well.
Back in the day we had to just use VU-3D.
Here is an alternative Piped link(s):
https://piped.video/6Em-CWYZhG8?feature=shared
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I'm open-source; check me out at GitHub.
This is what it was like using 3D programs on an Amiga in the late 80s or early 90s. One image took hours and hours to render. 5-6 hours would be a short one, usually it was more like 12.
How many btc per decade is that?
I can't help to think that all that amount of effort could be better spent.
But where’s the fun in that?
Ray tracing in MySQL instead? https://demozoo.org/productions/268459/
I was thinking the same sort of thing. What'd I'd kill for the time to spend on useless shit heh.
The human eye can only see 1 frame per 18 hours so I consider this reasonably fast.
Are you a tree
Nah, just The Lorax.
You may need to consult a doctor.