Built using seizer and implementing the same addictive variant of solitaire found in Last Call BBS; seizer solitaire gives you a way to pass the time on any x86_64 or aarch64 machine that has a Wayland compositor.
You can even run it on little gaming handhelds running ROCKNIX:
To run on a ROCKNIX device you’ll want to put the
aarch64-linux-none build in
roms/ports, and then (so emulation station will pick it up) add
seizer-solitaire.sh to the same folder:
#!/bin/sh
/storage/games-internal/roms/ports/seizer-solitaire
14 Likes
This is sweet!
By the way it runs at 100% CPU for me - not sure if you’re aware of that. I’ll file an issue if you like.
geemili
3
I suspect you’re running into performance issues with the multi-threaded rendering I recently added, but I don’t have a tracking issue for that anyway. What (physical) resolution are you running it at?
If it is the multi-threaded rendering you’re running into, then I need to do one or more of the following to fix it:
- Profile the multi-threaded renderer and optimize hot spots
- Render at a lower resolution and let the compositor upscale it (the assets aren’t high resolution anyway)
- Implement a different rendering backend that relies more heavily on the compositor using the subcompositor protocol
So uh, feel free to open an issue, or I’ll make one later.
1 Like
I didn’t resize the window:
btw it crashed when I pressed the print screen button!
It doesn’t seem slow, are you sure it’s not a vsync issue? Maybe it’s rendering frames at an unlimited speed with no sleep()?
Oh! Never mind, the backtrace made me see the issue actually.
It’s this kde bug which will be fixed with the next update.
1 Like
geemili
6
Ah, okay. I’ll have to fix that bug with print screen, but I’ll hold off on doing performance optimization. Thanks for the follow up!
geemili
7
New release! See the link for details.
1 Like
What Zig version is the project using?
Narven
9
Its being built on the pipeline using 0.12.0
geemili
10
Sorry, that script is outdated ( I do need to get CI set up at some point). I mentioned it in a issue here, version 0.14.0-dev.3188+34644511b, with plans to target 0.14.0 stable when it releases.