Join the discussion
Write your take first — we'll ask for email only when you're ready to publish.
- Hacker News
- Just in time for the 30th anniversary. This looks great, well done!by ckeck
- Very cool. I wonder what the limitations are? I see the dog I shot is floating in the air. Is that maybe a CSS thing or is it fixable?by sgt
- Damn, always gotta deal with these accursed z-index issues with CSS ;)by amatecha
- .dog { display: float; }by freakynit
- Is this a rip from https://github.com/NielsLeenheer/cssDOOMby edwinjm
- The source appears to be <https://github.com/LayoutitStudio/cssQuake>by degamad
- Separate projects. Niels Leenheer who made CSS Doom has seen Agustin Capeletto's CSS Quake.by OuterVale
- Source code: https://github.com/LayoutitStudio/cssQuakeby itvision
- As someone who passionately and ardiently hates prolifiration of this set of _hacks on top of hacks_ called CSS (and CSS/JS/HTML aka Web-stack), I must say this is good and valid use case for CSS. :)by divan
- Show HN: from the dev (who's also in here, maybe a title update) https://news.ycombinator.com/item?id=48571117
- Really cool experiment. A lot of jank. It would sometimes rubber band me back, movement was grid aligned in a way that made accessing the secret room challenging, and the whole tab unexpectedly crashed with no error. 5 star would play againby criley2
- It seems like this CSS Quake needs JS to run…by remix2000
- Maybe possible with https://lyra.horse/x86css/ ?by rikschennink
- CSS does the rendering, the game logic is TypeScript.by zamadatix
- Impressive. I guess this isn't only the renderer made to use CSS but also a full recreation of the engine and logic right? My guess is because a bunch of things do not behave like the original game, e.g. some buttons need to be shot instead of touched to activate, some secret doors open by touching them instead of being shot, etc.
- No it’s just the renderer. The game itself is Typescript.by slopinthebag
- Hi there! Thanks for the report, buttons should work properly now.
Regarding the game logic, the build step has a small JS extractor over QuakeC/progs.dat to generate JSON source facts: states, models, attacks, sounds, etc. The browser runtime is TypeScript and consumes those for Quake-ish gameplay.
by rofko - Awesome! Harder to exit than vim.by AzzieElbab
- how did you exit? because nothing seems to be working.by deskamess
- In case you want to view the menu, press Tab. Click outside menu items to resume game.by pgt
- This is the first thing I've seen on the intertubes for a /long/ time which genuinely makes me smile, thank you op.
Checked out https://cssdoom.wtf/ and loved it too, both are far lighter than current affairs. \o/
by jojogeo - 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
- 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.by DanielHB
- 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.
by itvision - 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.
by arendtio - Quake compiled in C will run insanely fast at 8K full resolution on an M1.by api
- Zero issues on Firefox + Linux. Gnome Web is stuttery and weird, though. Must be a WebKit/Safari thing.by jeroenhd
- For what it's worth it works like smooth butter under Chrome on an M2, on Safari it's clunky and seems to clip alotby jamal-kumar
- 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)by amatecha
- This engine is not optimised for performance. It's using CSS, after all.