| Main > Main Forum |
| ActLab guns with the new mame (v0.105) |
| (1/3) > >> |
| Farmboy90:
Has anyone gotten the ActLab gun set up and working with the new mame, v0.105? I tried last night and could not make it work. The gun shoots icons in XP and seems to work well in windows. But when I load up Mame and try Operation Wolf the cursor never moves. I remap the trigger and grenade buttons and those work fine. I can fire shots and throw grenades, but the cursor will not update when I pull the trigger. The in game setup mapped my trigger and grenades to MOUSE_5, so I figured I would need to get Lightgun Analog X/Y to map to mouse 5 as well. Since you can't do that in the game I tried to modify the opwolf.cfg. No matter what I used, MOUSECODE_5_ANALOG_X, MOUSE_5_X, etc... Nothing worked. I also tried different combinations of mame.ini device settings like: mouse 0 and 1 (tried both) lightgun_device none/mouse/lightgun (tried them all) Any ideas what is going on? |
| ahofle:
Can you try moving your actual mouse swiftly for the x/y mame in game setup stuff, then exit and edit the CFG and change the mouse number value to 5? I was a little confused as well -- my trackball wouldn't work at first, until I realized I had to go in a remap everything because it was now being detected as MOUSE2 for some reason even though it's the only mouse device currently connected?!? What is mouse1 I wonder hehe. I will try and hook up my act labs guns this weekend and see what I find also. |
| Farmboy90:
--- Quote from: ahofle on April 14, 2006, 01:08:46 pm ---Can you try moving your actual mouse swiftly for the x/y mame in game setup stuff, then exit and edit the CFG and change the mouse number value to 5? I was a little confused as well -- my trackball wouldn't work at first, until I realized I had to go in a remap everything because it was now being detected as MOUSE2 for some reason even though it's the only mouse device currently connected?!? What is mouse1 I wonder hehe. I will try and hook up my act labs guns this weekend and see what I find also. --- End quote --- Yeah this is what I did. I wiggled the trackball and edited that value. It did not work. I also went in and remapped it using the spinner and changed that value as well. Still no luck. What is weird though is that MAME recorded different strings when I did that. As a test, for the analog x axis, I spun the trackball. Then I went to the analog y axis and spun the spinner. Then I exited and looked at the .cfg file. Oddly the values were totally different!! It was something like MOUSCODE_2_ANALOG_X for one thing, and MOUSE_4_Y for the other. I mean the strings aren't even close to each other. Another weird thing is that when I changed MOUSECODE_2_ANALOG_X to MOUSECODE_5_ANALOG_X, MAME stopped recognizing the value. So when I went back into the game, after editing the value to 5, the in game setup said n/a. :lame: I laughed at this since MAME was the one who chose this to begin with, and now all of a sudden it is invalid?? WTF?? :dizzy: I think the new mame has a bug or something. Anyway, if you could let me know what strings are in your .cfg that would be great. Also post your mame.ini if you can. Thanks! |
| Derrick Renaud:
http://derrick.mameworld.info/lightgun/Act_Labs_Light_Guns_on_XP.html |
| Farmboy90:
By the way I using mame (not mame32) launched from mamewah. Not sure if that matters, just thought I would point it out. Derrick, thanks, I will try it out tonight and let you know. |
| Navigation |
| Message Index |
| Next page |