Post #3434660

2025-09-02 02:35 UTC

More small steps towards input remapping: mappings can now be loaded from home. So technically it already works, even tho there's no UI yet. The paths can be: - per-game, e.g.: ~/.var/app/app.drey.Highscore.Devel/data/highscore/mappings/nes-f4095791987351be68674a9355b266bc/nes.mapping (overriding nes controller for NES TLoZ) - global per-controller, e.g.: ~/.var/app/app.drey.Highscore.Devel/data/highscore/mappings/global/nes.mapping (overriding it for all games using nes controller)

Replies (1)

@alice@mk.nyaa.place 2025-09-05 03:07

Alright, so - I just added a toggle for switching between ParaLLEl-RDP+ParaLLEl+RSP and GLideN64+HLE RSP (or LLE/HLE modes internally, or Accurate/Fast in the UI). One thing that this required was moving compatibility checks from ParaLLEl-RDP itself to highscore. Not even to the mupen64plus port. This way we can know if it works or doesn't work in advance, and grey out the preference + lock it out into fast mode. Meanwhile, the core stopped doing automatic fallback and just selects whatever the frontend tells it too, and parallel-rdp plugin no longer has custom highscore-specific API for doing this check. So, it's nicer overall. Though it did require me to write way more Vulkan code than I'd like. Anyway, devices like @luna@lunar.place's laptop can now switch to the fast mode and run Conker's Bad Fur Day with less lag :3 It will still default to accurate, though it should be possible to try to determine a default based on the GPU in theory. For example, default to fast on older models of intel and amd iGPUs. I also need to adjust the wording, e.g. it may imply that changing the mode requires a game reset or an app restart. It doesn’t, just that if a game is running, it needs to be closed and reopened, nothing else

Open ##3434659