JoeViking245

Yes. Sorry about that.

I guess it was too quick and very dirty. 😊 Sorry about that. This should be better. ImportGameBase v1.0.2.7z

This can help you do them all at once.

That makes total sense. Thank you!! I'm fairly positive that LB/BB will scan for images based on the games Title and/or ROM filename. This was quick and dirty and untested, but "on paper" it appears it should work. If you can prove me right (please?), I'll update the official release. This gives the option (a CheckBox) to "Use ROM name for images". (and maybe this should be default) Unblock and copy (replace the existing file with the one in this zip) as before then start LaunchBox and, if you'd be so kind, give it a try and let me know.

My 1st thought is if it's working, leave it be. lol But if it's really bothering you, you could try (here I go 'guessing' again ) to force them to 1, 2, 3 in the General Inputs section. Change the mouse ID's to the order you want to see in "mame.ini". Save and close. Start standalone MAME. Open Configure Options Select General Inputs Select Player 1 Controls Press the up arrow (a lot faster than scrolling down) You'll see Mouse X analog and Mouse Y analog Set those to the controller (spinner) you want as player one. Press Escape Now select Player 1 Controls and do the same thing for the other spinner (step 6, 7, 8, 9). Press Escape again (after pressing it like in step #9) Select Save Configuration!!!!!!!!!! Exit MAME. You may want/need to delete the games cfg file again (another 'fresh start'). Play your game and see what happens.

I don't know if LB/BB sends overrides that will preclude cfg settings, but try changing "normvol" to "normalizer" per the Wiki. But that may not even help because I thing that cfg file is more of a 'guideline' or only gets loaded via a command line parameter. You might get lucky by modifying "vlcrc" located in C:\Users\%username%\AppData\vlc\ It has no file extension and may not even exist. Hence the "lucky" part. It can be opened with a text editor (Notepad++) And if none of that works or helps, you're no worse off than you were when you first inquired about it.

If you can run it directly through mame64 but not via LaunchBox, that's probably still the issue. You'll need to remove -keyboardprovider dinput from the Default Command-Line Parameters. Assuming you're still using MAME revision 0.161. Per @dragon57 in this post, dinput support didn't become available until revision 0.173 Note, if unchecking those boxes as @sundogak suggests doesn't work (definitely try that 1st) but removing that part from the Default Command-Line Parameters does (try that 2nd), you'll want (need) to turn off Pause Screens for MAME. (Hint: uncheck the box )

Excellent! I have no idea. Are your spinners working accordingly for player 1 and player 2? With all this messing around, you may want to go in the /cfg/ folder where you have MAME installed and delete "gunfight.cfg". Then continuing troubleshooting since we now know that the spinners are [for sure] being remapped.

Do you have MAME closed when you disconnect and reconnect the spinner(s)? And then [re]start MAME? Or are you doing that while MAME (not the game you loaded) is still running? Make note of the log for the 3 Input: Remapped lines when it's working. (which is what you have above) Completely exit MAME. Disconnect and reconnect your spinners. Start MAME. Compare the new log for the 3 Input: Remapped lines with the ones from step #1. They should be the same.

Looks like only MOUSECODE_1 is getting remapped. Excellent start! Recheck the ID's for the other 2. Originally you showed them as [partial] "PID_1420\8", but the log is showing "PID_1420#8". Double check all the numbers and letters in the ID's and try changing the slash to a pound symbol.

Yes. Everything infact. Order of Config Loading - The command line is parsed first, and any settings passed that way will take precedence over anything in an INI file. Try removing that part from your Command Line Parameters.

Below "Input: Adding..." in the log(s) you should see Does it show that at all? If not, it's not even looking at/for your remapo.cfg file. MAME will add the inputs ("Input: Adding...") as it sees them (the order that Windows tells it they're in). And that part doesn't really matter because after that, MAME will parse your remapo.cfg to remap them all. Well, at least the ones you told it to in the cfg file. But if the log isn't even indicating its "Attempting to parse", then your issue is somewhere else.

The ID's can't change because they're tied to the hardware. Run "mame -v" again and check that it's showing that your Inputs are getting remapped. Or see what it says after Attempting to parse: remapo.cfg

Try, from "device=", starting with "VID", through the PID # for MOUSECODE_1. And for the other 2, continue to the next ampersand (&). You'll need to escape the ampersands by adding "amp;" [A M P semicolon] after them. <mapdevice device="VID_D209&amp;PID_0410" controller="MOUSECODE_1" /> <mapdevice device="VID_32BE&amp;PID_1420\8&amp;32888d80" controller="MOUSECODE_2" /> <mapdevice device="VID_32BE&amp;PID_1420\8&amp;16ca0db7" controller="MOUSECODE_3" /> I know MAME says you can use just a substring of the ID (like how you had it). I've never tested it that way. I've always just started at VID. But (in my setups) I've also never had to go past the PID #. So this is kind of a guess. But hopefully a 'good' guess.

Bulk Convert .cue/.bin (or files other than .bin) to .chd View File Bulk Convert .cue/.bin (or files other than .bin) to .chd Using MAME’s chdman.exe (“Compressed Hunks of Data (CHD) Manager”, included with MAME), this plugin will convert CD based game files to a single .chd file in your selected Platform. Example: Before Loom (USA).cue Loom (USA).ccd Loom (USA).img Loom (USA).sub After Loom (USA).chd Before Arctic Thunder.cue Arctic Thunder.bin After Arctic Thunder.chd Why convert? You end up with just a single file per game A CHD file is, well… compressed. Resulting in less storage space requirements Arctic Thunder.cue + .bin = 601MB Arctic Thunder.chd = 466MB Spider-Man 2: Enter Electro = 684MB CHD format = 318MB Because we can and it's easy to do Requirements This plugin file chdman.exe (included with MAME) Game rom-sets that include a .cue file. (Loom (USA).cue, Arctic Thunder.cue etc.) What happens after converting? After successfully creating a CHD Image, the games application path will be changed to the new .chd file. Also, after the files have been converted you have the option to Leave the old files in place (default) Move the old files to a separate [backup] folder Delete the old files Installing the plugin Download the plugin Unblock “cue2chd (v1.00).zip” by right clicking the file and checking “Unblock” and clicking “OK”. Open the zip file and copy the contents (1 folder containing 1 file) into /LaunchBox/Plugins/ i.e. G:/LaunchBox/Plugins/cue2chd/cue2chd.dll Using the plugin Start LaunchBox Select Tools, Convert cue to chd Select a Platform Click Convert (Optional) Check Delete old files when complete This will permanently delete the old files (.cue, .bin, .img etc) after successfully converting them to .chd. Check Move old files when complete This will move the old files (.cue, .bin, .img etc) after successfully converting them to .chd to a folder you specify [for ‘backup’]. If you do not select Delete or Move, all files will remain in their current location along with the newly created .chd file. If you opt to delete the old files and later want/need to convert the CHD files back to .cue etc., you can use chdman.exe to "reverse the process". The command line is: chdman.exe extractcd -i “file_name.chd” -o “file_name.cue” Special thanks to @faeran for coming up with the idea for this plugin and his support and testing. As always, all comments and suggestions are welcome. Submitter JoeViking245 Submitted 04/02/2022 Category Third-party Apps and Plugins  

Correct on Send and Sleep. You only need the { } around 'special' named keys. {Space}{Enter}{Tab}{F1}{Alt}{Ctrl}{LWin}{Shift} etc. And to convolute things more, the last 4 I list have alternate characters that can be used !, ^, # and +. Respectively. Individual numbers and letters don't need { }. Examples (with options): ; Copy your highlighted text Send, {Ctrl down}c{Ctrl up} Send, ^c ; Close the active window Send, {Alt down}{F4}{Alt up} Send, !{F4} ; Type text Send, Joe was here So, you know what the command line looks like: "D:\Utilities\WinIPAC\WinIPAC.exe" Xinput_profile.ipc "D:\Utilities\WinIPAC\WinIPAC.exe" Keyboard_profile.ipc (quotes, in case your path has spaces in it) The most straight forward way to do this is to load it directly, as an additional app. No batch file nor script needed. (if it doesn't seem to load correctly, may need to check Wait for Exit) Then add a second Additional App to the game(s) changing the Command-Line to "Keyboard_profile.ipc" and check Run After (instead on Run Before). You won't need the Wait for Exit. If that creates an undesirable window appear/disappear (though it shouldn't because "it can be run invisibly"), you could create 2 batch files, shortcuts to the batch files, edit the shortcuts as described here, and have the Additional Apps point to the shortcuts. If you have a lot of games you need to add these Additional Apps to (AND they worked after testing them first ), you can add them in bulk using this:

The easiest way is to do a [Google] search for what it is you're wanting to do. For example: "AutoHotkey send keypress" (or even easier "ahk send keypress"). My I-Pac is old and doesn't have the option to switch between input modes. But from what I can see here (click on the Multi-Mode tab), you can switch on-the-fly via a couple of key presses. Translating from the link above, to switch to Xinput mode you press "1" and "Space" (in that order) and hold them for 10 seconds. In AutoHotkey lingo, that'd be: Send, {1 down} Sleep, 50 Send, {Space down} Sleep, 10000 Send, {1 up}{Space up} Here, we add "Sleep, 50" (50 milliseconds) to ensure "1" (I-Pac's default "shift control-key" [not to be confused with "Shift" on the keyboard]) is pressed and held PRIOR to "Space". For Keyboard Mode, it's "1" and "[Left] Ctrl". Send, {1 down} Send, 50 Send, {LCtrl down} Sleep, 10000 Send, {1 up}{LCtrl up} Both of these assume you haven't reprogrammed the default "Start1" and "P1SW3" (and "P1SW1" respectively) input assignments. An issue you may run into with switching modes just prior to launching a game via LaunchBox is Key point being "It will take the host PC up to 30 seconds to notice this and initialize the new device." As a side note, I think most emulators/games that use Xinput also allow you to assign keyboard inputs. And ones that don't, well... that's where having something like a wireless Xbox 360 controller comes in real handy.