Search the Community
Showing results for tags 'port mappings'.
Found 1 result
Hi all, been having this issue for over 1 year now. Mame isn't holding onto joystick port mappings on re-boot with Xbox one wireless controllers.... since v .170 all the way up to the current release of 0.187, I've tried everything imaginable without success.... Without a reliable Mame, my launch-box build is severely lacking. Windows 10 and the wireless adapter seem to randomly assign different joystick ports everytime the system is powered off and back on. Mame resets the port mappings back to default every single time my machine is turned off and back on. If the wireless controllers are not powered on, mame also wipes the controller mappings... wondering if I Am i the only one with these issues? im using xbox one wireless controllers with Launch-box connected to an HTPC over a 10 ft interface on the couch... wired controllers are not an option here. I cant seem to emulate the older mame32 stuff with mame .187 using retroarch cores otherwise i would dump mame completely. I Appreciate any help , feedback or thoughts ... also are there other types of wireless controllers that i could switch over to to prevent this? anyone have success ? apologies for the rant....lol