Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
06491 DIP/Input Minor Always Feb 2, 2017, 22:55 Feb 9, 2017, 19:35
Tester Emu View Status Public Platform MAME (Official Binary)
Assigned To Resolution Open OS Windows Vista/7/8 (64-bit)
Status [?] Acknowledged Driver
Version 0.182 Fixed in Version Build 64-bit
Summary 06491: all gun games: Using Aimtrak light gun with 4:3 games in 16:9 screens the crosshair is not aligned in sides with the pointer
Description When using a gun game with an aspect ratio different from the screen aspect ratio (for example using a 4:3 games in a 16:9 screen) the position of the crosshair in the game is correct onli in the middle vertical axis of the screen: more the gun is moved to the edge of the screen more the crosshair and the pointer increase their distance. At the edge of the screen the crosshair is at the edge of the game screen.

After other test I've noticed that the position detected in the screen ir reproduced proportionally in the game screen, this is more noticeable if rotating the game screen.

Because the Aimtrak light gun is seen as a mouse device I suppose that the mouse pointer should always be over the crosshair.

In this situation the only way to correctly play games is using crosshair or stretching the screen game.

I've attached som screenshot of this behaviour.
Steps To Reproduce
Additional Information
Regression Version
Affected Sets / Systems all gun games
Attached Files
zip file icon (1,772,613 bytes) Feb 2, 2017, 22:55 Uploaded by Emu
MAME screenshots with pointer wrong position in sides
There are no relationsihp linked to this issue.
User avatar
Feb 3, 2017, 06:03
Please try 06426
User avatar
Feb 4, 2017, 17:55
I made al lthe tests wrote in the post, tryied changing from lightgun to other then saving, then lightun again, but nothing changed.
I tried changing lightgunprovider but it works only with rawinput.
I tried dleting the ini files and setting option in the gui before starting the game but the behaviour remained the same.

I never had any isse in detecting the guns, only with the crosshair that disalighe with the mouse cursor. The MAME mouse cursor is very precise about where hte gun point in the screen.
User avatar
Feb 6, 2017, 15:49
The problem here is trying to support umpteen amounts of different guns/controllers/input devices. Devs to not have access to a lot of then nor have setups like everyone else.
Has your issue always been present? Do earlier version of MAME show this problem as well or is it a regression in function?
User avatar
Feb 6, 2017, 21:31
edited on: Feb 6, 2017, 21:32
Hello Tafoid
Thanks for your answer.
I understaind that problem with specific hardware is harder to solve because need the hardware to be reproduced. About this issue, did anyboy take the opportunity to get the free guns from Ultimarc as reported in the "Additional Information " files of this resolved bug ?
From the exeprience I had with Andy I think it may be possible.
Backing in topic, I own those guns from Christmas, I tried them with both MAME 0.181 and 0.182. If is needed I can try old version. I'll do ASAP, in the meanwhile if you have any suggestion abut specific version to test is welcome
If other tests are needed I can do them to acquire more specific details, let me know what you need I do.

The strange thing is that the light gun is configured as emulate mouse in the Aimtrak configuration, in Windows and in MAME configuration the mouse pointer is moved perfectly, but if I configure the lightgun_device as mouse the crosshair do not move at all (using the gun). It works only if configured as lightgun. As lightgun work perfectly, I own 2 guns and always where correctly detected.

This behaviour to mee it seem determined in the code by a specific function, in fact the full screen area is the gun detection area, the the crosshair is proportionally reported in the game screen. I discovered that this is even more noticeable in the Vs games like Duck Hunt, where there are 2 screen and the crosshair is only in the lower game screen. If the detection area is not stretched to game area everythink should work as expected.
It would be good having an option to disable/enable this stretching to game area but I don't know if it's possible.

I'm also available, if needed, in running special builds with debug code.

User avatar
Feb 7, 2017, 17:42
I've acknowledged for now.
Until a qualified Dev or another user who has a lightgun can help debug or have ideas on how to address the issues, I guess this can act as a holder for gun related issues
User avatar
Feb 9, 2017, 19:35
OK, I understaind.
When somebody will start investigating on it I'll be available for testing