mupen64plus
M64Py not recognizing Pokopom v2.1 input plugin
Using M64Py v0.2.5 and Mupen64Plus v2.5.9
Unsure if this is an M64Py or Pokopom issue, but seeing as there seem to be significant problems with M64Py input configuration in general, figured it best to start here. Attempting to use a Steam Controller with M64Py, and as far as I've been able to find, Pokopom is the only N64 input plugin that can support Steam Controllers. The default Mupen64Plus input plugin that comes included with M64Py refuses to recognize inputs from the track pads (both clicking the pads as well as control stick emulation), making D pad and C button inputs impossible. Pokopom claims to work with many N64 emulators, and I imagine dropping the .dll into the plugins directory is all it should really take to get it show up in the plugins drop down selection. However, it doesn't.
I'm not particularly technically inclined, so troubleshooting this entirely on my own isn't feasible. If there are certain logs or whatever else I should be looking at for diagnosing the issue here, I'll need someone to walk me through it.
M64Py, for now, works only with mupen64plus-input-sdl plugin, there is an issue about that here https://github.com/mupen64plus/mupen64plus-ui-python/issues/123. If you need different plugin you can use it in mupen64plus, but not in UI.
Is implementing other input plugins in the works? I read #123 and that was 2 years ago. The reason I would like it is due to the fact that I have the Raphnet N64 to USB adapter (dual) and with the Mupen64Plus Raphnet RAW plugin, it allows for the direct communication from a N64 controller to the emulator and as such has full compatibility with N64 controller peripherals (also extremely low latency). It also would not require a configuration menu to be set up for it. Would love to use M64Py (and did set it up), however not being able to use this plugin was a deal breaker.
So I'm very much hoping this one day gets implemented :).
The goal is to implement one input plugin, that will work for them all. The same is currently for all other plugin types. The reason why m64py is still usable after all these years is because of that, e.g. GLideN64 didn't exist back then, but you could change settings from m64py as soon as it was out (options are not grouped or sorted but it works). That needs to be done also for the input plugin, and it is the highest priority for me, I just don't have the time, but eventually, I will get to it. Any help is welcomed.