Main Restorations Software Audio/Jukebox/MP3 Everything Else Buy/Sell/Trade
Project Announcements Monitor/Video GroovyMAME Merit/JVL Touchscreen Meet Up Retail Vendors
Driving & Racing Woodworking Software Support Forums Consoles Project Arcade Reviews
Automated Projects Artwork Frontend Support Forums Pinball Forum Discussion Old Boards
Raspberry Pi & Dev Board controls.dat Linux Miscellaneous Arcade Wiki Discussion Old Archives
Lightguns Arcade1Up Try the site in https mode Site News

Unread posts | New Replies | Recent posts | Rules | Chatroom | Wiki | File Repository | RSS | Submit news

  

Author Topic: Two light guns still show up as the same first gun within MAME  (Read 3133 times)

0 Members and 1 Guest are viewing this topic.

Carlisimo

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 10
  • Last login:October 10, 2017, 12:58:03 am
  • I want to build my own arcade controls!
This topic has been covered here (http://forum.arcadecontrols.com/index.php?topic=150393.0) and here (http://forum.arcadecontrols.com/index.php/topic,150452.msg1572347.html) and was supposedly resolved as of the 0.177 release (http://mamedev.org/history.html).  However, this issue still persists for me.  I have tried 0.173, 0.175, and currently 0.179 all with the same results — the second light gun appears the same as the first light gun (i.e. Gun 1).

Any guidance on how to resolve would be greatly appreciated. 

Here’s my set-up:

I have Gun 1 configured to ID #2, and Gun 2 configured to ID #5.

__________________________________________
mame.ini (relevant settings)

coin_lockout              1
ctrlr                     lightgunControls
mouse                     1
joystick                  1
lightgun                  1
multikeyboard             0
multimouse                1
steadykey                 0
ui_active                 0
offscreen_reload          1
joystick_map              auto
joystick_deadzone         0.3
joystick_saturation       0.85
natural                   0
joystick_contradictory    0
coin_impulse              0

paddle_device             keyboard
adstick_device            keyboard
pedal_device              keyboard
dial_device               keyboard
trackball_device          keyboard
lightgun_device           lightgun
positional_device         keyboard
mouse_device              mouse

global_inputs             0
dual_lightgun             0


__________________________________________
lightgunControls.cfg

<mameconfig version="10">
 <system name = "default">
  <input>
     <mapdevice device="VID_D209&amp;PID_1602" controller="GUNCODE_1" />
     <mapdevice device="VID_D209&amp;PID_1605" controller="GUNCODE_2" />
     <mapdevice device="ATRAK Device #2" controller="JOYCODE_1" />
     <mapdevice device="ATRAK Device #5" controller="JOYCODE_2" />
   </input>
  </system>
</mameconfig>


__________________________________________
verbose output from mame

Video: Monitor 65537 = "\\.\DISPLAY1" (primary)
Direct3D: Using Direct3D 9
Physical width 1280, height 800
Direct3D: Initialize
Direct3D: Configuring adapter #0 = Intel(R) HD Graphics 4600
Direct3D: Using dynamic textures
Direct3D: YUV format = UYVY
Direct3D: Max texture size = 8192x8192
Direct3D: Device created at 1280x800
Direct3D: Initialize HLSL
Direct3D: First store options
Direct3D: HLSL initialized
Direct3D: Restore options
RawInput: APIs detected
RawInput: APIs detected
RawInput: APIs detected
DirectSound: Primary buffer: 48000 Hz, 16 bits, 2 channels
Input: Adding Kbd #0: Standard PS/2 Keyboard (device id: \\?\ACPI#PNP0303#4&157e8752&0#{884b96c3-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding Kbd #1: HID Keyboard Device (device id: \\?\HID#VID_03F0&PID_034A&MI_00#8&158f8666&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding Kbd #2: HID Keyboard Device (device id: \\?\HID#VID_D209&PID_0430&MI_01#7&66eee11&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding Mouse #0: Microsoft PS/2 Mouse (device id: \\?\ACPI#PNP0F03#4&157e8752&0#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding Mouse #1: HID-compliant mouse (device id: \\?\HID#VID_03F0&PID_134A#7&2b4abb25&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding Mouse #2: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_0430&MI_02#7&cc12e2d&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding Mouse #3: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_15A1#6&394bd7e1&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding Mouse #4: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_15A2#6&36b9c664&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding Mouse #5: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_1602&MI_02#7&23fea4a1&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding Mouse #6: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_1605&MI_02#7&384d7fd2&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding Gun #0: Microsoft PS/2 Mouse (device id: \\?\ACPI#PNP0F03#4&157e8752&0#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding Gun #1: HID-compliant mouse (device id: \\?\HID#VID_03F0&PID_134A#7&2b4abb25&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding Gun #2: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_0430&MI_02#7&cc12e2d&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding Gun #3: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_15A1#6&394bd7e1&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding Gun #4: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_15A2#6&36b9c664&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding Gun #5: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_1602&MI_02#7&23fea4a1&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding Gun #6: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_1605&MI_02#7&384d7fd2&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
êe`â"Input: Adding Joy #0: I-PAC 4 (device id: I-PAC 4 product_`â" instance_êe)
êe`â"Input: Adding Joy #1: ATRAK Device #2 (device id: ATRAK Device #2 product_`â" instance_êe)
êe`â"Input: Adding Joy #2: ATRAK Device #5 (device id: ATRAK Device #5 product_`â" instance_êe)
Region ':maincpu' created
Region ':gfx1' created
Region ':proms' created
Region ':namco' created
Direct3D: Store options

___________


Thank you.
« Last Edit: July 28, 2017, 01:40:15 am by Carlisimo »

Pitou

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 101
  • Last login:May 28, 2020, 05:56:46 pm
Re: Two light guns still show up as the same first gun within MAME
« Reply #1 on: July 31, 2017, 11:27:34 am »
Can you try with a new fresh mame.ini (adjusting only the required parameter to enable the lightguns)?

Pitou!

Pitou

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 101
  • Last login:May 28, 2020, 05:56:46 pm
Re: Two light guns still show up as the same first gun within MAME
« Reply #2 on: July 31, 2017, 09:31:54 pm »
Just tested with Mame 0.188 and Police Trainer and everything is fine.

Pitou!

dgrace

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 341
  • Last login:April 11, 2024, 01:43:59 am
  • I want to build my own arcade controls!
Re: Two light guns still show up as the same first gun within MAME
« Reply #3 on: August 02, 2017, 06:49:50 pm »
It needs to be a raw input MAME version.

Haze

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1296
  • Last login:October 04, 2023, 08:30:02 am
  • I want to build my own arcade controls!
    • MAME Development Blog
Re: Two light guns still show up as the same first gun within MAME
« Reply #4 on: August 03, 2017, 09:36:42 am »
It needs to be a raw input MAME version.

Which has been the default for a long time, including the versions being mentioned.

Unless the OP is being one of those moronic idiots and asking support for some unofficial build with it ripped out without mentioning it, but I don't think anybody is that stupid in this day and age.  They're posting links to the official site, so it implies they're using official builds.  The -verbose log also implies rawinput is being used (there are no dinput related lines) so something else is going on I feel.

Somebody posting their mame.ini and  -verbose output from a working version might be useful for the poster to compare against.

The issue is meant to be fixed, and plenty of people have reported it works fine, but we do still keep getting people saying it doesn't work.

« Last Edit: August 03, 2017, 09:41:11 am by Haze »