| Main > Lightguns |
| USB2GUN not working on PC - looking for some help - offscreen reload not working |
| << < (3/4) > >> |
| BadMouth:
Just thought of something..... Map the trigger to BOTH button 1 and button 2 in MAME. Easy so worth a try. EDIT: I guess it would be more correct to say "OR" rather than "AND". The in game menu for mapping should like: "P1 Button 1 Joy1 Button 1 or Joy 1 Button 2" |
| purbeast:
--- Quote from: BadMouth on June 26, 2023, 03:05:31 pm ---Just thought of something..... Map the trigger to BOTH button 1 and button 2 in MAME. Easy so worth a try. --- End quote --- Yeah that was one of the first things I tried and it just acted super funky. I believe it was because there is no position of the cursor when button 2 is pressed, so even though it is firing the gun, it just fired where the prior cursor position was. The whole problem with these games on MAME is there is no concept of "off screen", which was the reason the devs made it so shooting at the edge of the screen reloads. You can see that works perfectly fine when using the mouse because you can't go further than the edge of the screen. This offscreen_reload option is supposed to handle it though and simulate that. It was also hard to actually do it because when you move the aim to be off screen, it would do the direction + button 2, not JUST button 2. |
| BadMouth:
I got no more ideas other than trying the official MAME build rather than GroovyMAME if that's even possible on your setup. |
| purbeast:
--- Quote from: BadMouth on June 26, 2023, 03:19:23 pm ---I got no more ideas other than trying the official MAME build rather than GroovyMAME if that's even possible on your setup. --- End quote --- I've already tried it and same behavior. I wonder if it could potentially be a bug with the version of MAME I'm using. It's the version for both groovy and normal MAME. I'm going to try xpadder this evening and just see if that works, and if so, that will be a good enough solution for me, as long as the behavior is as expected. As long as the behavior is the same, that's all that really matters. I'd rather just do that than upgrade MAME if it was some kind of regression bug in the version I'm using. |
| purbeast:
Man this is such a pain in the ass lol... So I got a version that was from 2015.01.01 and that one worked. However, the cursor speed to move vertically at max was WWWWAAAYYYY too slow. Like when I'd test it out on the PC with the cursor, it took like a half second or maybe more to go from the top to the bottom, and I'm not sure when the other P1 button was actually fired. So I found some other versions that I believe was 5.3 and 5.7 and neither would start up in Windows 10 (it was registering as "Unknown" and said I needed 98, 2000, XP, or another early version) but then I got it to run in compatibility mode. However it wasn't really working properly either because none of the buttons would show up in there, and the UI just looked a bit wonky. So yeah, not really sure wtf to do at this point lol. I may play around with the version that worked to see if I can move the speed more. In a video I saw the cursor moved WAY quicker than it did in the version I was using. And that version seemed really old. |
| Navigation |
| Message Index |
| Next page |
| Previous page |