Of course, but you'd think after 30 years the compute power should be enough to overcome any lack of optimization. It's a testament to the engineering that went into the original Quake engine.
Both a toaster and an oven might benefit from improved electronics but in the end—whether its a toaster from the 60s or a toaster from 3008—you are still using a toaster to make a meatloaf.
CSS is not remotely comparable to a game engine. It's not even a programming language.
CSS is a general rendering solution, not something built for rendering 3D games.
And no one has spent any time optimizing 3D transforms to make a game workable because no one would be able to justify the use of their time like that. It wouldn’t even give you brownie points ‘cause most people would just ask “why?”
Err, strange, what browser? I'm using Firefox on a ThinkPad from 2018 running Linux, and cssquake was running at a smooth 60fps just now (and at 1080p resolution vs the 320x240 or 320x200 someone would likely be running on a P133)
Most of the time, things seem to be optimized for Chrome, but with this, I actually had the impression that Firefox ran a bit smoother, but I tested it on Linux.
Comments
This is an awesome achievement, but I can't help but notice that Quake ran smoother on my Pentium-133 PC in the 90s than it runs on my Mac M1 Pro...
This engine is not optimised for performance. It's using CSS, after all.
Yeah this is a case of “not the right tool for the job”.
It is awesome though.
Of course, but you'd think after 30 years the compute power should be enough to overcome any lack of optimization. It's a testament to the engineering that went into the original Quake engine.
Decades of optimizing a toaster to make better toast will not make the toaster any better at making meatloaf
We haven't had a toaster that makes better toast since 1997 (Sunbeam radiant control).
Is this you? https://www.timstoasters.com/
Toaster you say?
https://philip.greenspun.com/humor/eecs-difference-explained
Is this the right analogy? The product is the same, the appliance is different.
It should be "Decades of inventions from toasters to IOT AI Smart Air Fryers will not make better toast than the original"
But I'd argue the IOT AI Smart Air Fryer should make really good toast. Which is what GP is saying.
It'd be like if the IOT AI Smart Air Fryer had a constraint of only being allowed to use friction to create heat.
CSSQuake uses an intentionally-absurd rendering pipeline. It's not surprising that the result is sub-optimal.
(Though I agree that the meatloaf analogy is not very good.)
I stand by my analogy.
Both a toaster and an oven might benefit from improved electronics but in the end—whether its a toaster from the 60s or a toaster from 3008—you are still using a toaster to make a meatloaf.
CSS is not remotely comparable to a game engine. It's not even a programming language.
I am on the ground. This is great.
Still, why css is as slow as it is given what tech like imgui can do is a little wild.
CSS is a general rendering solution, not something built for rendering 3D games.
And no one has spent any time optimizing 3D transforms to make a game workable because no one would be able to justify the use of their time like that. It wouldn’t even give you brownie points ‘cause most people would just ask “why?”
Id assume "a fun challenge" could be enough of a reason
Err, strange, what browser? I'm using Firefox on a ThinkPad from 2018 running Linux, and cssquake was running at a smooth 60fps just now (and at 1080p resolution vs the 320x240 or 320x200 someone would likely be running on a P133)
For what it's worth it works like smooth butter under Chrome on an M2, on Safari it's clunky and seems to clip alot
Zero issues on Firefox + Linux. Gnome Web is stuttery and weird, though. Must be a WebKit/Safari thing.
Possibly, I did it on Safari. Trying it now on Chrome and it's fine.
Quake compiled in C will run insanely fast at 8K full resolution on an M1.
You wouldn’t happen to have a pointer on where to get this version would you?
Maybe try Firefox.
Most of the time, things seem to be optimized for Chrome, but with this, I actually had the impression that Firefox ran a bit smoother, but I tested it on Linux.
Runs perfectly fine at over 60fps on my Intel Core 358H at roughly 2560x1600.
Perhaps there's something wrong with your web browser. Try Firefox - it works beautifully there.
Wait, did Quack run on Pentium-133? I had a Pentium MMX 233mhz and I always assumed it didn't ran well so I never bother to get it.
If you had a 3dfx card it would run silky smooth on a Pentium-120 (what I had at the time)! Quake 2 ran pretty well too if I recall.
Yep 3dfx was a game changer. Was night and day on my 486 DX4 100 with and without
Yeah I didn't have a 3dfx so I assumed the software renderer required a more powerful CPU
Quake ran on a P75 with 8MB RAM in DOS mode. Not the best but it worked at 320x200.
Bare minimum for it being playable was a 486DX4 100MHz or similar, but with the floating point Quake really wanted a Pentium
I played it on a Pentium with 60mhz - it was allright
I played quake in 486dx100.
It must have, because that's what I had in 1996 and I played it.
I ran it on a Pentium 60. If you stuck to 320x200 it ran fine.
Ran fine on my Pentium 90 with 16MB RAM
Quake ran well on my 100Mhz Pentium.
Either you had a Voodoo on your P133 or whatever the M1 is doing is having a bad time...
On my 7945HX this is plenty fast.
I think you’re missing the point