Mame not holding onto joysick controller port mappings

Please refer to this forum post: https://forums.launchbox-app.com/topic/38881-installing-update-version-of-launchbox-clears-mame-controller-settings/

And this one too ... https://forums.launchbox-app.com/topic/40084-after-1-year-still-cant-get-mame-to-hold-onto-joystick-port-mappings/

EDIT: I am now convinced mame and launchbox are not properly passing joystick mappings... known issue with Mame... can Launchbox team work with mame devs to get this attention to fix??? Launchbox is not picking up the mappings properly... i get them when i run mameui64 executable directly but in launchbox they are wiped. Mame often switches the joypad numbers randomly...... http://forum.arcadecontrols.com/index.php/topic,151710.msg1586917.html#msg1586917

the default.cfg file in Mame keeps getting erased to defaults when the wireless controller port mappings change, or when the wireless controller or pc turns off. I assume I am in a small niche here using Xbox one wireless controllers combined with Mame and Launchbox???.... I've experienced this same behavior on 3 different PC's, and Mame seems to behave the same way for me on all 3 test boxes.... no joy here. Retroarch doesnt seem to be effected much by this as badly as Mame... I personally think its just how window 10 is dynamically mapping wireless controllers and how Mame and launch-box picks them up. I also tested this with the Xbox 360 adapter and 360 wireless controllers and had the same exact issue as with the xbox one wireless controllers.. Tomorrow I will purchase an Xbox one S wireless controller and test with that since it uses Bluetooth instead of these wireless adapters.... what i am trying to figure out is if wireless Bluetooth holds onto the same controller ports when it syncs each time in windows... maybe Bluetooth controllers do not experience this issue and it only occurs with the Microsoft Wireless adapters? (Edit...tested today, Bluetooth controllers make no difference.)

Is there anything here that can be addressed within Launchbox to tame this sort of behavior with Mame? basically Mame is un-usable with Launchbox when using wireless controllers in a 10 foot interface HTPC environment?

Can the fundamentals of the controllerremapGui utility be incorporated into launchbox to ease this matter? https://www.reddit.com/r/MAME/comments/46wayj/joypad_number_changing_every_restart_hellpp/

my own opinion...I'd personally prefer improvements like this made to the core features of the app rather than new features being added.

Thanks, Mazjohn AKA - Mr Arcade

Comments (11)