Ultimarc Aimtrak - single gun recognised as GUN 2

[DaveJ-UK]

I have a single Ultimarc AimTrak recoil gun in black.

I got it working in MAME last week although off-screen reload remained problematic. Now I have come back to it, I couldn't get it to work and I realised that MAME is seeing it as GUN 2 even though I only have a single gun.

In the AimTrak utility it is on DEVICE 1 and has the latest firmware (9.19)

I'm running Windows 10 x64 and in Game Controllers there is a single Controller named AMTRAK Device #1.

In MAME Plus! 0.159 I have "Enable lightgun input" checked and I have set "Lightgun device" to Lightgun.

I am struggling to think of what else to check?

Is there a utility or setting within MAME that allows me to correct the way it is enumerating through DirectInput controllers? (I guess this is what is causing the problem?)

Also, should it be starting at GUN 0 or is GUN 1 the first lightgun?

Thanks

[Titchgamer]

Dont worry about which gun number it is.
But the device ID can change if you have several USB devices which can cause mame problems

[Scotty_C]

in the later versions of MAME ( I think 180+) you can take advantage of mapdevice so that the specific USB device id is always mapped to the same MAME controller ID (Gun1 2 3 etc..)

More details here:
http://docs.mamedev.org/advanced/devicemap.html

[DaveJ-UK]

Thank you for the prompt replies.

So I have got my lightgun device IDs from the mame -v console output. When I have my (single) AimTrak connected it sees 2 lightguns and when I unplug it then it sees 1. Hmmm.

I see the ctrlr directory and I understand how to write the XML but which file do I put it in? The article you linked to doesn't say.

[Titchgamer]

The Aim traks have 2 listings in windows.
I think it is one for the sender and one for the receiver.

[DaveJ-UK]

OK, that would make more sense. But it's still a pain that my only gun is detected as GUN 2. If it was GUN 1 then the defaults would work fine.

Here is the console output with one AimTrak connected:

Video: Monitor 26806613 = "\\.\DISPLAY1" (primary)
Direct3D: Using Direct3D 9
Physical width 2560, height 1600
Direct3D: Initialize
Direct3D: Configuring adapter #0 = NVIDIA GeForce GTX 560 Ti
Direct3D: Using dynamic textures
Direct3D: YUV format = RGB
Direct3D: Max texture size = 16384x16384
Direct3D: Device created at 2560x1600
Direct3D: Initialize HLSL
RawInput: APIs detected
RawInput: APIs detected
RawInput: APIs detected
DirectSound: Primary buffer: 48000 Hz, 16 bits, 2 channels
Input: Adding keyboard #0: HID Keyboard Device (device id: \\?\HID#VID_046D&PID_C52B&MI_00#8&1b971193&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding mouse #0: HID-compliant mouse (device id: \\?\HID#VID_046D&PID_C52B&MI_01&Col01#8&335a9dd8&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding mouse #1: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_1601&MI_02#8&253a70e3&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding lightgun #0: HID-compliant mouse (device id: \\?\HID#VID_046D&PID_C52B&MI_01&Col01#8&335a9dd8&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding lightgun #1: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_1601&MI_02#8&253a70e3&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding joystick #0: ATRAK Device #1 (device id: ATRAK Device #1 product_1601d209-0000-0000-0000-504944564944 instance_287539b0-eaff-11e6-8002-444553540000)
Region ':user1' created
Starting No Driver Loaded ':'
  (missing dependencies; rescheduling)
Starting Video Screen ':screen'
Optional device ':screen:finder_dummy_tag' not found
Starting No Driver Loaded ':

However I still don't understand where I am meant to be adding the XML for the device mapping. Does it go in cfg/default.cfg? MAME just  overwrites it.

Or does it go in the ctrlr? If so, how do I load it?

[Scotty_C]

Okay so go ahead and create a default.cfg and place it in your ctrlr folder  (you might have to play around with the device id's n such but this is a start)

Try this example default.cfg

Code: [Select]

<mameconfig version="10">
<system name="default">
<input>
<mapdevice device="ATRAK Device #1" controller="JOYCODE_0" />
<mapdevice device="VID_D209&amp;PID_1601" controller="GUNCODE_0" />
</input>
</system>
</mameconfig>

Then you can either launch mame.exe as : mame.exe -v ctrlr default. Or you can add default to your mame.ini so that it loads the default.cfg file everytime so you can then just launch mame.exe -v

Code: [Select]

#
# CORE INPUT OPTIONS
#
ctrlr                     default


[DaveJ-UK]

Thanks for the detailed reply.

If I run mame0182b with that configuration file it loads but then the GUI freezes and it crashes after a few seconds.

If I strip out the first mapdevice line then it loads, I can navigate the GUI but then it closes without error the moment I try and load a game.

If I strip out the second mapdevice line then the GUI freezes and crashes after a few seconds, same as it does with both lines present.

I get the same behaviour with mapdevice device="VID_046D&PID_C52B"

Any other suggestions?

[Titchgamer]

I use something called Tur Game Controller Order to keep my AT ID's the same and its easy to use/set up

[Scotty_C]

Do you see the remapping happening in the verbose output? Might be something else going on with mame version compared to rom version 

I just tried the attached ctrlr file (I got rid of the & stuff on this example) on my arcade and launched maxforce just fine   (mame version 0182b maxforce 0171 romset version)

Code: [Select]

C:\Users\BlueButt\Desktop\mame0182>mame64.exe -v maxforce
Video: Monitor 65537 = "\\.\DISPLAY1" (primary)
Direct3D: Using Direct3D 9
Physical width 1920, height 1080
Direct3D: Initialize
Direct3D: Configuring adapter #0 = AMD Radeon HD 8570
Direct3D: Using dynamic textures
Direct3D: YUV format = RGB
Direct3D: Max texture size = 16384x16384
Direct3D: Device created at 1920x1080
Direct3D: Initialize HLSL
Direct3D: First store options
Direct3D: HLSL initialized
RawInput: APIs detected
RawInput: APIs detected
RawInput: APIs detected
DirectSound: Primary buffer: 48000 Hz, 16 bits, 2 channels
Input: Adding keyboard #0: HID Keyboard Device (device id: \\?\HID#VID_413C&PID_2501&MI_00#7&b3e6d2c&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding keyboard #1: HID Keyboard Device (device id: \\?\HID#VID_D209&PID_0411&MI_01#8&304b5c5b&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding keyboard #2: HID Keyboard Device (device id: \\?\HID#VID_D209&PID_0410&MI_01#8&38fc2244&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding mouse #0: HID-compliant mouse (device id: \\?\HID#VID_413C&PID_2501&MI_02#7&1b21cb50&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding mouse #1: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_1601&MI_02#8&253a70e3&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding mouse #2: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_1603&MI_02#8&1544c414&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding mouse #3: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_0411&MI_02#8&19944f94&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding mouse #4: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_0410&MI_02#8&213895ff&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding lightgun #0: HID-compliant mouse (device id: \\?\HID#VID_413C&PID_2501&MI_02#7&1b21cb50&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding lightgun #1: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_1601&MI_02#8&253a70e3&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding lightgun #2: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_1603&MI_02#8&1544c414&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding lightgun #3: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_0411&MI_02#8&19944f94&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding lightgun #4: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_0410&MI_02#8&213895ff&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding joystick #0: I-PAC Ultimate (device id: I-PAC Ultimate product_0410d209-0000-0000-0000-504944564944 instance_7ca524c0-2358-11e5-8001-444553540000)
Input: Adding joystick #1: I-PAC Ultimate (device id: I-PAC Ultimate product_0411d209-0000-0000-0000-504944564944 instance_28d046c0-4a9c-11e5-8001-444553540000)
Input: Adding joystick #2: ATRAK Device #1 (device id: ATRAK Device #1 product_1601d209-0000-0000-0000-504944564944 instance_0c7d1210-0f12-11e6-8002-444553540000)
Input: Adding joystick #3: ATRAK Device #3 (device id: ATRAK Device #3 product_1603d209-0000-0000-0000-504944564944 instance_b1fd84d0-6bc5-11e6-8002-444553540000)
Region ':maincpu' created
unzip: opened archive file C:\ROMS\MAME_171\maxforce.zip
unzip: found C:\ROMS\MAME_171\maxforce.zip ECD
unzip: C:\ROMS\MAME_171\maxforce.zip has no ZIP64 ECD locator
unzip: read C:\ROMS\MAME_171\maxforce.zip central directory
unzip: closing archive file C:\ROMS\MAME_171\maxforce.zip and sending to cache
unzip: found C:\ROMS\MAME_171\maxforce.zip in cache
unzip: opened archive file C:\ROMS\MAME_171\maxforce.zip
unzip: closing archive file C:\ROMS\MAME_171\maxforce.zip and sending to cache
unzip: found C:\ROMS\MAME_171\maxforce.zip in cache
unzip: opened archive file C:\ROMS\MAME_171\maxforce.zip
unzip: closing archive file C:\ROMS\MAME_171\maxforce.zip and sending to cache
unzip: found C:\ROMS\MAME_171\maxforce.zip in cache
unzip: opened archive file C:\ROMS\MAME_171\maxforce.zip
unzip: closing archive file C:\ROMS\MAME_171\maxforce.zip and sending to cache
Region ':waverom' created
unzip: found C:\ROMS\MAME_171\maxforce.zip in cache
unzip: opened archive file C:\ROMS\MAME_171\maxforce.zip
unzip: closing archive file C:\ROMS\MAME_171\maxforce.zip and sending to cache
Starting Maximum Force v1.05 ':'
Optional device ':eeprom' not found
Optional memory region ':romboard' not found
Optional shared pointer ':cart' not found
Optional device ':cdrom' not found
  (missing dependencies; rescheduling)
Starting R3041 ':maincpu'
Starting Jaguar GPU ':gpu'
Starting Jaguar DSP ':dsp'
Starting NVRAM ':nvram'
Optional memory region ':nvram' not found
Starting Watchdog timer ':watchdog'
Starting VIA VT83C461 ':ide'
Starting ATA Connector ':ide:0'
Starting HDD CoJag ':ide:0:hdd'
Starting Harddisk ':ide:0:hdd:image'
Starting ATA Connector ':ide:1'
Starting Video Screen ':screen'
Optional device ':screen:finder_dummy_tag' not found
Starting Speaker ':lspeaker'
  (missing dependencies; rescheduling)
Starting Speaker ':rspeaker'
  (missing dependencies; rescheduling)
Starting 16-Bit R-2R Twos Complement DAC ':ldac'
  (missing dependencies; rescheduling)
Starting 16-Bit R-2R Twos Complement DAC ':rdac'
  (missing dependencies; rescheduling)
Starting Voltage Regulator ':vref'
Starting Maximum Force v1.05 ':'
Optional device ':eeprom' not found
Optional memory region ':romboard' not found
Optional shared pointer ':cart' not found
Optional device ':cdrom' not found
  (missing dependencies; rescheduling)
Starting Speaker ':lspeaker'
  (missing dependencies; rescheduling)
Starting Speaker ':rspeaker'
  (missing dependencies; rescheduling)
Starting 16-Bit R-2R Twos Complement DAC ':ldac'
Starting 16-Bit R-2R Twos Complement DAC ':rdac'
Starting Maximum Force v1.05 ':'
Optional device ':eeprom' not found
Optional memory region ':romboard' not found
Optional shared pointer ':cart' not found
Optional device ':cdrom' not found
  (missing dependencies; rescheduling)
Starting Speaker ':lspeaker'
Starting Speaker ':rspeaker'
Starting Maximum Force v1.05 ':'
Optional device ':eeprom' not found
Optional memory region ':romboard' not found
Optional shared pointer ':cart' not found
Optional device ':cdrom' not found
Input: Remapped joystick #3: ATRAK Device #1 (device id: ATRAK Device #1 product_1601d209-0000-0000-0000-504944564944 instance_0c7d1210-0f12-11e6-8002-444553540000)
Input: Remapped joystick #4: ATRAK Device #3 (device id: ATRAK Device #3 product_1603d209-0000-0000-0000-504944564944 instance_b1fd84d0-6bc5-11e6-8002-444553540000)
Input: Remapped lightgun #0: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_1601&MI_02#8&253a70e3&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Remapped lightgun #1: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_1603&MI_02#8&1544c414&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Average speed: 99.91% (56 seconds)
Sound: buffer overflows=2 underflows=0