Lightgun calibration issues with USB2GUN board in MAME on PC

purbeast

Well-known member
Joined
Aug 4, 2013
Messages
2,430
Reaction score
1,132
Location
Rockville, Maryland
I have 2 happ guns connected to USB2GUN and have a JPAC hooked up to my Maximum Force cabinet with MAME. I have all of it setup and everthing.

I am having issues with the gun calibration. Like the calibration goes well and in the little preview window it looks like the gun is aiming correctly.

However when I am playing Lethal Enforcers, it seems like the further away from the center of the screen I get, the more offset my shots are. When I'm trying to aim at guys off center, like say about 1/2 way between the center and left edge of the screen, the bullet holes are showing to the left of where I am aiming.

I have noticed that this doesn't seem to be the case with the vertical positioning though. If I shoot towards the top of the screen at the center horizontally, it appears to be working fine and seems pretty accurate.

I am guessing this has to do with the screen being 4:3 yet the analog controller it THINKS the gun is, would be 4:4 or 3:3?

The odd part is I had this all setup in my other MAME cabinet as a proof of concept, and the accuracy was perfect. When I first was getting this new project setup I had another monitor in it and the tracking was even worse, so I swapped them, and now in my Maximum Force cabinet I have the exact monitor that I was using with my proof of concept that was working perfectly.

Is there some trick that I am forgetting to do with the calibration of the gun that I don't remember from doing it in my other cabinet? To be fair it was over a year ago. I'm also wondering if there are maybe some settings I need to set in MAME possibly?

Any help is appreciated, thanks.
 
I've realized that the window that MAME is opening apparently is NOT the resoultion I am running in my desktop when calibrating, so I think that may be the culprit.

My desktop is 320x240 and MAME is loading up in 360x240 video mode, which also makes sense as why I get further away from the center the larger the offset is, and that in the vertical space it seems to be fine.

5259KFi.jpg

However, when I am in the actual game and look at the machine information from the tab menu, it appears that it THINKS everything is 320x240.

3LGR7TE.jpg

So I am guessing that extra 40 pixels in the initial window size is what is going on here and causing this issue. The problem is I don't know how to force it to load up in 320x240 video mode (yet).

I also think that is why the text looks weird in the second screen shot on the menu because it's trying to render text in both like 360 and 320 pixel width. This is all theory though.
 
I can also now confirm that this is 100% a MAME issue because I got the model2 emulator working and Virtua Cop tracks flawlessly.
 
I finally got Friction working and it also tracks flawlessly, so yep, MAME issue that I still have yet to figure out.
 
Man okay so now I'm even MORE confused...

I am trying to get Singe to work with these guns, and talking with the devs, I need to get my gun to act as a mouse in order for it to work with that emulator.

So I tried to find some applications and I found this Joy2Mouse application that turns your controllers into mimic absolute mouse position.

Well after I got the app working, I noticed that the cursor is moving EXACTLY like the cursor in MAME is. Check out this video of just the cursor moving around in the desktop.


The setting I am using is "Absolute - from center to center" as shown in this link below:


So now I am wondering wtf... is MAME using this same mechanism, and if so, how were other people getting it so accurate but I am not?

It's just so strange that I can have perfect tracking with Friction, Silent Hill, and Virtua Cop, but then MAME and now using this tool that just turns the analog stick into absolute mouse, it's behaving the same way.

So confused...

EDIT:

Here is the MAME calibration issue on video - you can see it behaves identically to the Joy2Mouse video.

 
Back
Top Bottom