| Main > Main Forum |
| Wandering USB Controller Order |
| << < (3/4) > >> |
| vindic8r:
Yep. That's the only difference between when it works and when it doesn't. The -ctrlr parameter. |
| drventure:
I just tried from the command line, loading your cfg file. I gave you the wrong command line. don't specify the .cfg extension, so just Mame {romname} –ctrlr motumame When I load from command line with the cfg extension, I get a message "Unable to load motumame.cfg.cfg" So it appears that mame wants to add the extension. When I took it off, it loaded up fine. |
| vindic8r:
Of course! I'll give this a whirl back when I'm in front of my cab next, hopefully tonight. |
| vindic8r:
Sorry for the delay. Went out of town for a wedding. This did the trick! So all is well now, except one minor issue. On my CP, I've got P1 B1 mapped to both L-Control and Trackball B1 (lft mouse button). P1 B1 is also mapped to Gun 1 B1. Herein lies the trouble. Where in my .cfg do I define this button? Should it be under Gun 1, or under the trackball? I've currently got it defined under Gun 1, and the result is that Gun 1's trigger doesn't work properly. It's very odd, though, given that the GUNCODE_X_BUTTON1 assignment seems correct, while the MOUSECODE_X_BUTTON1 assignment is not. Note that Gun 2's trigger button works perfectly, so I'm pretty confident this has something to do with the mouse button assignment. Any ideas what to try? My post-ControllerRemap'd .cfg file is attached, so you can see the output. |
| drventure:
I'm not positive it would make a difference but shouldn't there be a OR between the LCONTROL and the MOUSECODE GUNCODE_BUTTON1 OR KEYCODE_LCONTROL (OR) MOUSECODE_BUTTON1 I can't test right now to be sure, but just glancing at my other CFG files, they all have OR between the different input map elements |
| Navigation |
| Message Index |
| Next page |
| Previous page |