There's basically 2 ways to do input: you map once to an abstraction and cores tie into that abstraction by some (changeable) default, or you map nothing by default and a person needs to come in and map each thing separately/manually. At that point I decided to play VC on my Wii instead. And my display would keep turning off during gameplay (which is OK until the display turns off and Retroarch freezes). except the audio would be interspersed with bursts of noise, and fiddling with audio buffer length/etc. m64py is also hard to configure in ways.Įventually I got OOT running mostly fine in Retroarch on Ubuntu 18.04. If I recall, m64py also uses autogenerated graphics plugin GUIs based on config files.
#NESTOPIA CONTROLLER MAPPING HOW TO#
I'm not entirely sure how to edit N64 video plugin settings. It's like the worst of a text editor dump (no ctrl+F) and the worst of a GUI (no organization) and a non-native console-style interface (tedious and slow to use: scroll 1 line at a time, can't click to jump to line). Retroarch ParaLLel has an option, but it's confusingly organized because.Īutogenerated GUI based on per-core metadata? Retroarch Mupen64Plus has no option to bind C buttons separately. IIRC, Retroarch only lets you bind L/R and U/D to controller axes.
Some N64 games use C buttons individually. I feel that a "global controller abstraction" causes problems with consoles with controllers that don't fit the mold. You have to manually map your controller to retroarch's Retropad abstraction (ABXY, L1L2元, etc.) then read the docs to find how the RetroPad abstraction is mapped to the per-console buttons. One config interface for every console under the sun: I don't understand the difference between global, per-console, per-game config. Different config options available from the menu, vs. I wish I could search the entire options hierarchy, like Jetbrains IDE setttings. Main menu is designed for game controller use, not keyboard/mouse. I have some theories about Retroarch's interface (mostly N64):
0 kommentar(er)
