MAME no longer saving PID's

[Joe35car]

OK I havn't played MAME in a while but this has worked for years until now. I'm using MAME 287. Here is what is in my cfg in the ctrlr folder. file named mapdevice. Inside my MAME ini is this 

#
# CORE INPUT OPTIONS
#
coin_lockout              1
ctrlr                     mapdevice

and below is the cfg I use for the ID's

 

<?xml version="1.0"?>
<mameconfig version="10">
    <system name="default">
        <input>
            <mapdevice device="VID_0483&amp;PID_5750&amp;MI_00&amp;Col01#8&amp;38255be8&amp;0&amp;0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}" controller="GUNCODE_6" /> 
            <mapdevice device="VID_0483&amp;PID_5751&amp;MI_00&amp;Col01#9&amp;23770f6c&amp;0&amp;0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}" controller="GUNCODE_7" />
            <mapdevice device="3A-3H Retro Shooter 1 product_57500483-0000-0000-0000-594944564944 instance_d13114f0-de41-11ef-8001-4445535400000" controller="GUNCODE_6" />
            <mapdevice device="3A-3H Retro Shooter 2 product_57510483-0000-0000-0000-504944564944 instance_9fffae80-e0b9-11ef-8001-4445535400000" controller="GUNCODE_7" />
            <mapdevice device="Xinput Player 1" controller="JOYCODE_4" />
            <mapdevice device="Xinput Player 2" controller="JOYCODE_5" />
        </input>
    </system>
</mameconfig>

 

Now everytime I shutdown MAME it keeps changing my gun ID's. MAME must of changed something in the past releases.

Edited yesterday at 12:02 AM by Joe35car

[JoeViking245]

From the Windows Command Prompt, run the command "mame.exe -v" and read through the verbose output.

It should show the devices is whatever order, then later indicate it's loading your mapdevice.cfg file and (re)setting the order.

[Joe35car]

OK but why is it changing? I have been having no issues for over 2 years and all of a sudden it keeps resetting?

 

[Joe35car]

Here's the results. I'm kind of a noob when reading this. Can you tell me what I should set my retroshooter light gun 1 and 2 for?

New Text Document.txt

[Joe35car]

Well I'm going to try again. My guns seemed to be revered. I changed the inputs for lightgun settings in mame. Swithed the numbers in the cfg devicemapping.

 

[Joe35car]

Well seems to be working now. Closed MAME several times and pc. Gun 1 is now 7 and gun is is 6. It use to be different. Not sure why it changed when it worked for a few years with no issues. I even make sure I plug in all the usbs in the same port when I work on my panel. 

[JoeViking245]

21 minutes ago, Joe35car said:

Well seems to be working now. Closed MAME several times and pc. Gun 1 is now 7 and gun is is 6. It use to be different. Not sure why it changed when it worked for a few years with no issues. I even make sure I plug in all the usbs in the same port when I work on my panel. 

With your mapdevice.cfg file, it shouldn't matter which USB port they're plugged into because you're referencing the device by its ID.

If you wish (works either way, but doesn't explain why it was, then wasn't and is now working), you can truncate your 2 lightgun ID's in your cfg file.  e.g.

<mapdevice device="VID_0483&amp;PID_5750 controller="GUNCODE_6" />
<mapdevice device="VID_0483&amp;PID_5751 controller="GUNCODE_7" />

 

For the other 2 GUNCODE_6 and 7, between your Log and your cfg file, there's an extra 0 (zero) at the end of the instance in the cfg file.  Not sure if it makes a difference or not.

cfg file
4445535400000
Log file
444553540000

 

Regardless, glad it's working now.

[Joe35car]

Thanks for the catch with extra 0. I'll check on my backup cfg if it was always had that extra 0.