|
Dual light guns in v0.172 not woking - bug or change in config?
#353352 - 04/21/16 11:14 PM
|
|
|
Hey there, major long-time lurker here... Been loving Mame since the early days!
I'm unable to get my ArcadeGuns.com (Ultimarc based) light guns to work in Mame v0.172. I think I've tried every possible combination in mame.ini, but whatever I do, Mame only sees one gun. (My guns are reported as mice by Windows.) This is on a completely new install of v0.172 - I have tried both the 64-bit and 32-bit versions.
Is there a problem with the rawinput handling in .172? Or is simply rawinput not implemented for lightguns reporting as mice yet? (I notice the new ini settings "mouseprovider" supports the "rawinput" keyword, but "lightgunprovider" does not. However, setting "mouseprovider" to "auto" (or "rawinput"), and "lightgun_device" to "mouse" seems to have no positive effect.
This the relevant sections of my mame.ini (Working fine in .171, but not in .172):
ctrlr
mouse 1
joystick 1
lightgun 1
multikeyboard 0
multimouse 1
offscreen_reload 1
lightgun_device lightgun
mouse_device mouse
dual_lightgun 0
Running Mame verbose, I notice these differences between .171 and .172:
[v0.172:]mame64 -v ptblank
Video: Monitor 000000000abac198 = "\\.\DISPLAY1" (primary)
Direct3D: Using Direct3D 9
Physical width 1920, height 1080
Direct3D: Configuring adapter #0 = NVIDIA GeForce GTX 760
Direct3D: Using dynamic textures
Direct3D: YUV format = RGB
Direct3D: Max texture size = 16384x16384
Direct3D: Device created at 1920x1080
RawInput: APIs detected
RawInput: APIs detected
DirectInput: Using DirectInput 8
DirectSound: Primary buffer: 48000 Hz, 16 bits, 2 channels
Input: Adding Kbd #0: HID Keyboard Device
Input: Adding Kbd #1: HID Keyboard Device
Input: Adding Kbd #2: HID Keyboard Device
Input: Adding Kbd #3: HID Keyboard Device
Input: Adding Kbd #4: Logitech HID-compliant Unifying keyboard
Input: Adding Kbd #5: Logitech HID-compliant Unifying keyboard
Input: Adding Kbd #6: HID Keyboard Device
Input: Adding Mouse #0: HID-compliant mouse
Input: Adding Mouse #1: Logitech HID-compliant Unifying Mouse
Input: Adding Mouse #2: HID-compliant mouse
Input: Adding Mouse #3: HID-compliant mouse
Input: Adding Mouse #4: Logitech HID-compliant Unifying Mouse
Input: Adding Mouse #5: HID-compliant mouse
Input: Adding Gun #0: Win32 Gun 1
[v0.171:]mame64 -v ptblank
Video: Monitor 000000000C1CC9F8 = "\\.\DISPLAY1" (primary)
Direct3D: Using Direct3D 9
Physical width 1920, height 1080
Direct3D: Configuring adapter #0 = NVIDIA GeForce GTX 760
Direct3D: Using dynamic textures
Direct3D: YUV format = RGB
Direct3D: Max texture size = 16384x16384
Direct3D: Device created at 1920x1080
RawInput: APIs detected
Input: Adding Mouse #0: HID-compliant mouse
Input: Adding Gun #0: HID-compliant mouse
Input: Adding Mouse #1: Logitech HID-compliant Unifying Mouse
Input: Adding Gun #1: Logitech HID-compliant Unifying Mouse
Input: Adding Mouse #2: HID-compliant mouse
Input: Adding Gun #2: HID-compliant mouse
Input: Adding Mouse #3: HID-compliant mouse
Input: Adding Gun #3: HID-compliant mouse
Input: Adding Mouse #4: Logitech HID-compliant Unifying Mouse
Input: Adding Gun #4: Logitech HID-compliant Unifying Mouse
Input: Adding Kbd #0: HID Keyboard Device
Input: Adding Kbd #1: HID Keyboard Device
Input: Adding Kbd #2: HID Keyboard Device
Input: Adding Kbd #3: HID Keyboard Device
Input: Adding Kbd #4: Logitech HID-compliant Unifying keyboard
Input: Adding Kbd #5: Logitech HID-compliant Unifying keyboard
Input: Adding Kbd #6: HID Keyboard Device
Input: Adding Mouse #5: HID-compliant mouse
Input: Adding Gun #5: HID-compliant mouse
DirectInput: Using DirectInput 8
DirectSound: Primary buffer: 48000 Hz, 16 bits, 2 channels
Is there anything I can do to fix this, or do I have to wait for a newer version of Mame?
PS: HLSL and BGFX/HLSL in v0.172 is simply awesome! Amazing job!
|
|
|
Tafoid |
|
I keep on testing.. testing.. testing... into the future!
|
|
|
|
|
Reged: 04/19/06
|
|
Posts: 3135
|
|
Loc: USA
|
|
|
|
Send PM
|
|
|
Re: Dual light guns in v0.172 not woking - bug or change in config?
[Re: Azrael]
#353353 - 04/21/16 11:37 PM
|
|
|
> dual_lightgun 0
>
You could try setting this to 1. Beyond that, no clues.
|
|
|
|
Re: Dual light guns in v0.172 not woking - bug or change in config?
[Re: Tafoid]
#353358 - 04/22/16 01:13 AM
|
|
|
Thanks, but I have already tried that. No effect.
|
|
|
|
Re: Dual light guns in v0.172 not woking - bug or change in config?
[Re: Tafoid]
#353373 - 04/22/16 06:16 AM
|
|
|
|
|
| Dullaron |
|
Diablo III - Dunard #1884
|
|
|
|
|
Reged: 07/22/05
|
|
Posts: 6125
|
|
Loc: Fort Worth, Tx
|
|
|
|
Send PM
|
|
|
Try this.
[Re: Azrael]
#353375 - 04/22/16 07:50 AM
|
|
|
lightgunprovider auto
to
lightgunprovider dinput
or
lightgunprovider win32
Look for the OSD INPUT OPTIONS settings on mame.ini.
I don't know it will work or not because I don't have a lightgun or two.
I do know that those settings do work on the Griffin PowerMate (volume or spinner). http://www.mameworld.info/ubbthreads/sho...part=1&vc=1
Firehawke < Talk to him. Or any others who know about this.
|
W11 Home 64-bit + Nobara OS / AMD Radeon RX 5700 XT / AMD Ryzen 7 3700X 8-Core 3.59 GHz / RAM 64 GB
|
|
|
Re: Dual light guns in v0.172 not woking - bug or change in config?
[Re: Azrael]
#353728 - 04/30/16 01:21 PM
|
|
|
Just thought I should write an update, in case somebody else with the same issue stumbles upon this thread.
Looks like this is a known bug. It's been reported and set as status "Acknowledged" at Mametesters (http://mametesters.org/view.php?id=6185)
The same person who submitted the report, also concluded that dual light gun support is broken in .172 and .173 at the BYOAC forums. (Down at the moment, so no link.)
Seems like I'll have to stick with v0.171 for the time being, and miss out on the new HLSL/BGFX goodies. Oh well. 
|
|
|
Index 
Threaded 
Dual light guns in v0.172 not woking - bug or change in config?
Reply
[Re: 
