Joe35car

When it opens it has the tool bar on top. When I launch outside LB it's totally fullscreen without the tool bar on top. I have to hit f11 for it to work in LB. Also once in a blue moon it works properly. Then close and launch the game again and has the toolbar on top. When I open a game it blinks like it wants to go fullscreen then shows the toolbar

I also only us the canary builds

Yes I tried it with the --fullscreen=true and also already is set to true in the toml. I use the xenia manager and inside there is a emulation folder where my xenia is. I have my LB pointing to the xenia exe. IT works but not in fullscree. xenia-canary.config.toml

OK I did a clean install on Xenia emulator and all my games launch in full-screen outside of Launchbox. But inside LB it's not showing in full-screen. I tried adding -fullscreen

So I see changes were made on importing Teknoparot games. I use to be able to just add a new game when released. Now it wants to import all with xml? I have to delete all the games except the one I want. Why is it doing this?

OK I think I have it working and keeping fingers crossed. Rebooted MAME several times and its remembering the ID's. If it wasn't for the 2 of you it wouldn't be much fun using the light guns. Thanks again. Wish you guys lived near me to go out and have a couple of beers.

This shows his putting a ID number for the lightgun. Video is really old so but sure if mame changed since.

Well after rebooting pc and starting MAME it doesn't work. IDs changed again. I'm at my wits end. MAME makes it so hard to do this. We have to be missing something. I think we need to assign the stick to a number. If player 1 is gun 3 for example we need to set it to 3.

Awesome that worked. Now a few more questions. Sorry I'm a noob when it comes to writing cfgs. Do I need to change the guncode_1 or leave them as number 1 for both player 1 and 2? Also still a little confused on how to add the button support for these guns. There would be at least 3 buttons for each gun. Also these guns have a up down let right mini joystick. Do I need to add anything to remember the buttons on the guns? I'll test and get abck to you if the IDS remain the same in MAME. Thanks again to the both of you.

I just wanted to say thank you to both of you for helping me out. I'm still getting that fatal error. I copied it from MAME cmd and also put the = sign in. Here's a copy of whats in my mapdevice cfg which is placed in the Mame ctrlr folder. Changed the MAME ini part to ctrlr and added mapdevice. Now player 1 light gun is gun2. Player 2 is gun3. I would prefer to keep this way and get the cfg working. I know this question has nothing to do with the cfg but should I have multimouse at 0 or 1? Also do I change the controller=GUNCODE 1 to GUNCODE 2 since that's what player 1 is. And player 2 would be GUNCODE 3? <?xml version="1.0"?> <mameconfig version="10"> <system name="default"> <input> <mapdevice device="VID_0483&PID_5750&MI_00&Col01#8&38255be8&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}" controller="GUNCODE_1" /> <mapdevice device="VID_0483&PID_5751&MI_00&Col01#9&23770f6c&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}" controller="GUNCODE_1" /> </input> </system> </mameconfig> I'm sure it's something simple to fix. Thanks again guys for the help. This is from my current mame -v PS F:\LaunchBox\Emulators\MAME> .\mame -v Attempting load of mame.ini Parsing mame.ini Attempting load of mame.ini Parsing mame.ini Loading translation file language\English\strings.mo Reading translation file: 1 strings, original table at word offset 7, translated table at word offset 9 Loaded 0 translated string from file Starting plugin data... Starting plugin hiscore... Starting plugin layout... Attempting load of mame.ini Parsing mame.ini Attempting load of mame.ini Parsing mame.ini Attempting load of source\empty.ini Attempting load of ___empty.ini Video: Monitor 65537 = "\\.\DISPLAY1" (primary) Physical width 3840, height 2160 Initializing BGFX library DirectSound: Primary buffer: 48000 Hz, 16 bits, 2 channels Input: Adding keyboard #1: HID Keyboard Device (device id: \\?\HID#VID_093A&PID_2533&MI_01&Col02#7&38334002&0&0001#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding keyboard #2: HID Keyboard Device (device id: \\?\HID#VID_1C4F&PID_5C44&MI_00#7&1005db58&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding keyboard #3: HID Keyboard Device (device id: \\?\HID#INTC816&Col01#3&10839a5c&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding keyboard #4: HID Keyboard Device (device id: \\?\HID#ConvertedDevice&Col01#5&36801e08&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding keyboard #5: HID Keyboard Device (device id: \\?\HID#VID_1C4F&PID_5C44&MI_01&Col04#7&13d1626a&0&0003#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding keyboard #6: HID Keyboard Device (device id: \\?\HID#VID_1C4F&PID_5C44&MI_01&Col05#7&13d1626a&0&0004#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding keyboard #7: HID Keyboard Device (device id: \\?\HID#VID_1C4F&PID_5C44&MI_01&Col06#7&13d1626a&0&0005#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding keyboard #8: HID Keyboard Device (device id: \\?\HID#VID_0483&PID_5750&MI_00&Col02#8&38255be8&0&0001#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding keyboard #9: HID Keyboard Device (device id: \\?\HID#VID_0483&PID_5751&MI_00&Col02#9&23770f6c&0&0001#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding keyboard #10: HID Keyboard Device (device id: \\?\HID#VID_D209&PID_0301#8&33dcf051&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding keyboard #11: HID Keyboard Device (device id: \\?\HID#VID_D209&PID_2001#8&4b683d&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding mouse #1: HID-compliant mouse (device id: \\?\HID#VID_093A&PID_2533&MI_00#7&250323c4&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding mouse #2: HID-compliant mouse (device id: \\?\HID#VID_0483&PID_5750&MI_00&Col01#8&38255be8&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding mouse #3: HID-compliant mouse (device id: \\?\HID#VID_0483&PID_5751&MI_00&Col01#9&23770f6c&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding mouse #4: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_1582&MI_01#9&c2ed3e1&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding mouse #5: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_1582&MI_02#9&2160e07&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding mouse #6: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_0501&MI_01#9&263a1a66&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding lightgun #1: HID-compliant mouse (device id: \\?\HID#VID_093A&PID_2533&MI_00#7&250323c4&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding lightgun #2: HID-compliant mouse (device id: \\?\HID#VID_0483&PID_5750&MI_00&Col01#8&38255be8&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding lightgun #3: HID-compliant mouse (device id: \\?\HID#VID_0483&PID_5751&MI_00&Col01#9&23770f6c&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding lightgun #4: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_1582&MI_01#9&c2ed3e1&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding lightgun #5: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_1582&MI_02#9&2160e07&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding lightgun #6: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_0501&MI_01#9&263a1a66&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding joystick #1: 3A-3H Retro Shooter 1 (device id: 3A-3H Retro Shooter 1 product_57500483-0000-0000-0000-504944564944 instance_d13114f0-de41-11ef-8001-444553540000) DirectInput: Device type=0x14 subtype=0x01 HID=yes Input: Adding joystick #2: Ultimarc Ultra-Stik Player 1 (device id: Ultimarc Ultra-Stik Player 1 product_0501d209-0000-0000-0000-504944564944 instance_b39ed840-cf5b-11ef-8003-444553540000) DirectInput: Device type=0x14 subtype=0x01 HID=yes Input: Adding joystick #3: 3A-3H Retro Shooter 2 (device id: 3A-3H Retro Shooter 2 product_57510483-0000-0000-0000-504944564944 instance_9fffae80-e0b9-11ef-8001-444553540000) DirectInput: Device type=0x14 subtype=0x01 HID=yes Optional memory region ':screen' not found Starting No Driver Loaded ':' (missing dependencies; rescheduling) Starting Video Screen ':screen' Starting No Driver Loaded ':' Checking for icons in directory icons No candidate icons found for machines Attempting to parse: default.cfg Attempting to parse: ___empty.cfg Starting No Driver Loaded No more renderers - shutting down BGFX library PS F:\LaunchBox\Emulators\MAME> mame.ini mapdevice.cfg

OK I tried this for now: <?xml version="1.0"?> <mameconfig version="10"> <system name="default"> <input> <mapdevice device"VID_0483&PID_5750&MI_00&Col01#8&38255be8&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}" controller="GUNCODE_1" /> <mapdevice device"VID_0483&PID_5751&MI_00&Col01#9&23770f6c&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd " controller="GUNCODE_1" /> </input> </system> </mameconfig> I get that fatal error as above in my post.

from MAME command. I have a lot on my control panel lol

This is what I get when in MAME and copy. Player 1 Gun6 \\?\HID#VID_0483&PID_5750&MI_00&Col01#8&38255be8&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd} Player 2 Gun2 \\?\HID#VID_0483&PID_5751&MI_00&Col01#9&23770f6c&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd} What should I copy in my custom cfg? These are Retroshooter reaper guns When I reboot pc or MAME the gun# will change for them. Trying to get stable IDs. Also want to save the trigger IDs for them

OK so after rebooting the pc MAME didn't remember the IDs of the guns. They changed again the IDs. I need to find out what the proper format for the cfg. Do I need to set to read only for the default cfg for mame? https://docs.mamedev.org/advanced/devicemap.html