VF2 has three sound output modes: HDMI/PWMDAC/Bluetooth. Will changing the sound output mode improve it? 
I’ve noticed the projects over at Harbour Masters · GitHub now support building with a USE_OPENGLES option.
It took me some while to figure these out, it turned out I needed an 8 GB swapfile to compile any of them. I tried two, Mario Kart and Zelda OOT, with mixed results.
Mario Kart 64 runs slow no matter what you do to graphics settings. Surprisingly, the emulated version is quicker once it compiles its shaders. Must be the huge tracks it is loading, or something?
Zelda on the other hand is very playable. Fullscreen 1920x1080 you only experience dips to 14 fps at the biggest of areas - since the game is designed to run at 20, I call that a win. The only issue is that parts of the graphics are simply missing. Half of Epona is gone, as is half of Hyrule Castle from distance, next to several other random things. I swapped around the OTR files with a fully working concurrent amd64 copy with no effect, so I guess it’s the shaders or something.
I’m surprised to see Ocarina working so well, even with half of it gone. Might try to compile Majora in the future and report how it goes.
2 Likes
… so I’ve tested Star Fox 64 (“Starship”) and Majora’s Mask (“2ship2harkinian”) from HarbourMasters.
Star Fox 64 does not run well, not even the title screen does. I blame the shadows and move on.
Majora’s Mask is surprisingly playable. Much like Ocarina it will have an occasional framerate dip, here they happen on scene flyovers when entering a place, and, similar to Ocarina, whenever particles take up a portion of the screen, either as floaty semitransparent pixels, or whenever Tatl or Navi get closeups. I expect Termina Field to chug more (particles, semitransparent slime enemies, large draw distance) … but I did not play far enough to get to Termina Field because frankly I find this game spiteful and annoying. The big take is that all textures are working fine. So they should be working in Ocarina, too, and I should first try building a “Release” version, then, provided they still don’t show, probably file a bug report over at Shipwright 
Majora’s Mask is not a game I like. Its native build is also not something I was ever expecting to be able to play on this device, though.
Edit: what a ride this machine has been. To think I was once happy to get Abiword and DosBox working.
Almost forgot, this is a clock I use in SwayWM to ditch swaybar/waybar/GUI info bars entirely. Bound it to appear as a floating, 10% transparent app on (Win)+c. (Win)+f then makes it a (100% opaque) screensaver. Same button combo to get back to desktop. (Win)+D to get rid of it.
Just a tip, you can adjust the colors before compilation. (I inverted them to turn my Wayland machines into nice dark desktop/wall clocks whenever their screen isn’t being used.)
2 Likes
I haven’t used Sway for a few years. Since I learned to use Labwc on ArchLinux-CTW, I’ve been using Labwc with xfce4-panel in Starfive_Debian. It continues the habits of Openbox and XFce4. 