3 ms·
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...
by jedberg 4mo ago
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...
- jonplackett 4mo agoI think you’re missing the point
- poisonfountain 4mo agoThis engine is not optimised for performance. It's using CSS, after all.
- Insanity 4mo agoYeah this is a case of “not the right tool for the job”. It is awesome though.
- jedberg 4mo agoOf 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.
- culi 4mo agoDecades of optimizing a toaster to make better toast will not make the toaster any better at making meatloaf
- deleted 4mo ago[deleted]
- rustystump 4mo agoI 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.
- harrall 4mo agoCSS 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?”
- Akronymus 4mo agoId assume "a fun challenge" could be enough of a reason
- libria 4mo agoIs 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.
- matt_kantor 4mo agoIt'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.)
- culi 4mo agoI 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.
- billfor 4mo agoWe haven't had a toaster that makes better toast since 1997 (Sunbeam radiant control).
- culi 4mo agoIs this you? https://www.timstoasters.com/ https://www.timstoasters.com/
- qmr 4mo agoToaster you say? https://philip.greenspun.com/humor/eecs-difference-explained https://philip.greenspun.com/humor/eecs-difference-explained
- DanielHB 4mo agoWait, 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.
- lightedman 4mo agoQuake ran on a P75 with 8MB RAM in DOS mode. Not the best but it worked at 320x200.
- jedberg 4mo agoIt must have, because that's what I had in 1996 and I played it.
- iamphilrae 4mo agoIf 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.
- UltraSane 4mo agoQuake ran well on my 100Mhz Pentium.
- bluedino 4mo agoBare minimum for it being playable was a 486DX4 100MHz or similar, but with the floating point Quake really wanted a Pentium
- to11mtm 4mo agoEither 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.
- jamal-kumar 4mo agoFor what it's worth it works like smooth butter under Chrome on an M2, on Safari it's clunky and seems to clip alot
- jeroenhd 4mo agoZero issues on Firefox + Linux. Gnome Web is stuttery and weird, though. Must be a WebKit/Safari thing.
- jedberg 4mo agoPossibly, I did it on Safari. Trying it now on Chrome and it's fine.
- api 4mo agoQuake compiled in C will run insanely fast at 8K full resolution on an M1.
- jedberg 4mo agoYou wouldn’t happen to have a pointer on where to get this version would you?
- amatecha 4mo agoErr, 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)
- itvision 4mo agoRuns 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.
- arendtio 4mo agoMaybe 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.