![]() My arrangement is Win10 with a wireless KB, pair of XBOX controllers w/ wireless adapter for 8-way games, Mayflash F300 Elite w/ gate rotated for 4-way games, and Kensington trackball. Getting ready to work on controls and found this thread very helpful. I've got it running (.205 w/ complete ROM set) and have Launchbox / Big Box running as well. New user here, and new to MAME as of the last month. Input: Adding joystick #4: XInput Player 4 (device id: XInput Player 4) Input: Adding joystick #3: XInput Player 3 (device id: XInput Player 3) Input: Adding joystick #2: XInput Player 2 (device id: XInput Player 2) Input: Adding joystick #1: XInput Player 1 (device id: XInput Player 1) Skipping DirectInput for XInput compatible joystick Controller (Xbox 360 Wireless Receiver for Windows).ĩ¨83Input: Adding joystick #0: vJoy Device (device id: vJoy Device product_¨83 instance_9) Skipping DirectInput for XInput compatible joystick Bluetooth XINPUT compatible input device. so I just dont get it! here is paste from the text file I created to see ID's in mame: (2 xbox one controllers that I want as P1 and P2 and 2 xbox 360 controllers for P3 and P4) I also dont see any solid device id's to make it work right either. If I boot up all 4 controllers, it randomly changes which controllers are what and the 2 additional xbox 360 controllers then become P1 and P2. If I program it for my 2 xbox one controllers its great. I suck, I am usually not bad at this stuff, but for whatever reason this is throwing me for a loop! You all gave me so much extremely valuable information! Here is what I have realized happens. Then whatever you name it reference that in the CTRLR entry within the MAME.INI file. Then copy the DEFAULT.CFG file located in the CFG directory to the CTRLR directory and rename it. It never seemed to cause issues (or whined that was read only) but the CTRLR way is the "right" way to do it and less likely to cause issues (or if you forget it is write protected, your changes you make will not be saved).īecause of the above, the easiest way to generate your custom CFG file for the CTRLR entry is to setup in MAME as you want. MAME will then not be able to overwrite the file if controller is not on when launches. The other "cheat" you can do and which I used before I got the CTRLR option working was I setup controllers the way I wanted and then went into the CFG folder, found the Default.CFG file and set it to read only (via Windows properties). That is why when you don't use the CTRLR option you can get everything setup and working (which saves everything to the Default.CFG file) and then if you launch MAME and the controller isn't on the Default.CFG gets overwritten with "null" entries since the controller isn't there. If there is an entry it copies those settings within the named CFG file to the Default.CFG file located in the \CFG folder at MAME launch. Then you don't have to use the -ctrlr flag in LB as noted by TheNewClassics since the MAME.INI file will tell MAME where to pull the CTRLR file.īasically, all this does is that when MAME launches, it looks to the CTRLR setting. You should see an entry (default) of: ctrlrpath ctrlrĪlso within the MAME.INI file is an entry under "Core Input Options" that is "ctrlr" which is where you can set which controller file you want MAME to use. ![]() ![]() However, check you Core Search Path entries in your MAME.INI file. The ctrlr directory is typically in the root. should i create one in root of mame folder and download a ctrlr file as a guide to try this tip? I do not have any folder named this that i can find?. ![]()
0 Comments
Leave a Reply. |