If you for whatever reason used the "Define joystick buttons" of MiSTer and and pressed something on your cab - you now have a virtual gamepad, which will cause issues with things that consume keyboard input, like arcade cores. Most cores support this, and most cores use the standard MAME mapping. To avoid the complexities of the MiSTer input system, arcade cores can also consume keyboard input where there is no artificial player1/player2/cabinet limitations. ![]() ![]() There is a hack to get around this, but I will not get into that. To complicate matters further, MiSTer can take input from a physical USB keyboard and present it to a core as ONE gamepad, not two. Since gamepads are not equal, you will also have to remap your gamepad. This is all strongly tied to low-level USB workings, so input from one USB device is constrained to one player. It's not obvious where an arcade core should look for things like TEST, SERVICE, TILT etc, so naturally, it's either not implemented or varies from core to core.įor a console/computer core, one physical USB device will be player 1, another physical device can be player 2. MiSTer cores can consume gamepad and/or keyboard input from the Linux subsystem, which makes sense from a console/retro-computer perspective, but no so much for arcade, where you have one cabinet. ![]() The input system of MiSTer is a bit of a mess when it comes to arcade cores. The reason of my ask about supporting default Mame keyboard input (An it work fine with a lot of arcade cores): Thanks taking the time answering :) Not sure if was really cleat and I actually forgot to put on more link:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |