"Ayles told The Register that he'd planned to release the third in the series at Christmas, but performance refused to get above slideshow levels. "Then last week, I had to fix OpenSCAD rendering for another project and discovered the npm openscad-wasm package was from 2022 and silently ignoring the Manifold flag," he said. "The fix took renders from 2 minutes to 2 seconds. Rolled that back to OpenSCAD-Doom and suddenly it was playable.""
"As for how it works, Ayles said: "It's a custom Python engine that reads WAD files and outputs OpenSCAD code. Pygame handles input and runs a parallel software renderer. The OpenSCAD side uses Animation mode to bypass the file watcher's 200ms debounce." Performance-wise, the game runs at 10-20 FPS and renders well enough for the player to work out what is happening. It is, however, blocks of color."
OpenSCAD-Doom runs the 1990s shooter Doom inside the OpenSCAD CAD modeler. A custom Python engine reads WAD files and outputs OpenSCAD code while Pygame handles input and a parallel software renderer. OpenSCAD's Animation mode is used to bypass the file watcher's 200ms debounce. A prior performance issue was fixed by updating openscad-wasm handling of the Manifold flag, reducing render time from two minutes to two seconds. The resulting experience runs at roughly 10–20 FPS and renders block-colored frames that are recognizable but crude.
Read at Theregister
Unable to calculate read time
Collection
[
|
...
]