Headrush69

Sounds like you are doing something wrong in ClrMamePro. What you want is something in the lines of 1G1R mode which means 1 Game 1 Rom. This might help: https://forums.launchbox-app.com/files/file/1488-quick-1g1r-no-intro-rom-sets-batch-files-usaeujpneu/ Or just check out tutorials on 1G1R feature of ClrMamePro.

I have LEDBlinky working fine, but have an issue where some roms pass "unique" emulator and rom values. I assume Launchbox just passes the following command on a game start: If that is true, where does Launchbox take these values from? (Emulator name, platform name and the rom name?) I ask because every so often a rom passes a different emulator name. Here is a sample from my LEDBlink debug log: First example is 2 Atari 2600 games, and the second is 2 Sega 32X games. You can see in the second example for each, a different emulator name is passed in. I can make specific entries in ControlsEditor for these to "hide" the problem, but checking and auditing all my roms would be a lengthy task. Here is the full debug log for the second Sega 32X game: Has anyone else seen this or is there a way to debug the ledblinky output Launchbox is sending LEDBlinky? Solution: Turns out this was rather simple once I looked at it better. The ~ character is used to by LEDBlinky to separate message fields. These problem roms had ~ in their filenames which throws LEDBlinky's parsing off since it interprets the ~ in the filename as a separator. SImple fix, change the filename.

If you check your Launchbox/Data/BigBoxSettings.xml do you have <KeyboardSelect>118</KeyboardSelect> 118 is the keycode for left Ctrl I believe. You don't have any other commands mapped to that key as well?

I’ll put my nod for Ultimarc products. Their iPac line for buttons/controllers are top notch, provide plenty of flexibility and Andy provides great support. i recently switched my cabinet buttons to their illuminated gold leaf buttons and absolutely love them. After trying various joysticks, I settled on their ServoStiks. They have other joysticks with different feature sets, but These are probably closer to what most people expect in arcade sticks. Their Spintrak and U-trak I endorse as well

I think a lot of apprehension is probably to not understanding what is meant by Android support. From the poll: I think the perception is that Android being a prominantly mobile OS, that the current desktop view is just going to be directly ported to Android, noteably small phones, and that just doesn't seem realistic or practical to take a visually big GUI and cram it into these device screens. I'm not worried.

Agreed. Currently I have both a Dolphinbar to use the Wii remote in a gun shell and an Aimtrak. As Lordmonkus stated, I find the Aimtrak do need recalibration often, as the difference between an adult and a child using it, make a huge difference. My setup is in an arcade cabinet, so it's a center piece when people come over, so I'm looking forward to a better out of the box experience that it looks like the Sinden guns will provide.

That is the right folder, mine are there as well. Too many windows open, I was looking where I stored the copies I use with MAME, sorry. A while back I looked for information on the artwork file format as well, but didn't find much. Hence why I was using MAME as well. In the end, I just used ParaJVE as is.

Strange, mine is a standard install as well, no cartridge folder though. Trying moving them up a directory.

You do have the actual roms required in the ParaJVE/data/roms folder?

If you have the standalone working fine, probably not much benefit. You can get Retroarch's shaders, and overlay support, but MAME can do those as well on it's own. For me, I just find native MAME can handle a variety of input devices, joysticks, keyboards, steering wheels, track balls, spinners, mice, etc, with a lot less work. As long as you have your ctlr file set up to keep device IDs static, it's quite painless. You can always use both and use only specific games with one or the other. (For example to get alternate music for some games in MAME 2003+)

JoeViking245, this only works for dinput devices and normally XBox 360 controllers are using Xinput. You could have Retroarch use dinput for XBOX 360 controllers as well, but there are trade offs. (I wouldn't suggest it) There doesn't seem to be a complete solution for all situations, so you have to use different techniques depending on the emulator. For example, with the Sega Model 2 Emulator, XBox 360 controllers alway change the device order for my steering wheel, so the easiest solution so far is make sure to them turn off when using this emulator. (In my case, I have arcade controls and never use the 360s with this emulator) Edit: Somehow I missed this information, but if your application initializes dinput8 through COM, the devinput8.dll in your application's folder method will NOT work, you have to use the system wide approach. You can still put a devreorder.ini in each application's directory. So now in Sega Model 2 emulator, I have static entries for all my hard wired devices, and the XBOX controllers get allocated after. Works great.

Does it do this with all cores in Retroarch? I recently had this issue with a single core, delay to start Retroarch, starts loading, another delay, (no response to key strokes during this), and then finally ran. Tried everything I could think of, deleted retroarch configs, deleted and redownloaded core and still no change. On a hunch, redownloaded Retroarch and installed to a second location and ran from there and it worked. Didn't want to go through the hasshle of determining the exact file in Retroarch causing the issue, so re-installed Retroarch again, directly over my original install location. Fixed the problem and all my custom configs and remaps still in place. Hope that helps.

The issue is MAME will reset the controller bindings if it is ever started and the controllers are not online. I don't know what other controllers you have attached to your system, but you might want to look at https://docs.mamedev.org/advanced/devicemap.html and set up mapping so your controller IDs don't change. On my system I map the devices that are always attached first, and then the XBOX wireless controllers as Joy3 and Joy4. Than I config all the control how I want in MAME. NOW, if you start MAME again and the wireless controllers aren't online, they will get reset, so to make sure that doesn't happen, set the default.cfg in the mame cfg folder to read only. If you change specific game bindings you will have to mark each of those as read only as well. If you need to edit these bindings again, make the appropriate files read/write again, and only start MAME once the wireless controllers are online. Reset to read only after making you changes.

Running directly through Mame is always best as it will tell you exactly which file you are missing. Sometimes you can have the rom set, but still be missing a single individual rom within the set.

Are they still working if you start directly with Mame?

Great tool but it doesn't work with XInput devices, just Direct8Input devices. MAME has great input device ordering builtin that you can check out online in the MAME docs which helps for that emulator as well.

This is one of the biggest problems that MAME noobs face, trying to keep a complete MAME rom set and update it with every MAME release. Generally speaking, for most cases there is no need to update MAME and it's rom set with every release. Without going into detailed information, get a set working and don't update unless you need to. (Cases like specific NEW game added, or improvement in a specific driver for one of your games.) For example, the mame_2003_plus core in Retroarch is based on Mame 0.78, yet you'll find it plays the majority of the popular games of the 80s-90s well. If you do want to try to maintain and update romset with every release, a rom manager like ClrMamePro is essential and will do all the hard work of updating your romset without redownloading complete sets.

Start Retroarch. Select Load Core and pick the Genesis Plus GX core. Scroll down to Information in Retroarch and select Core Information If you scroll down it will should show if the proper BIOS is loaded. It's likely you don't have them, These are the files you need: https://docs.libretro.com/library/genesis_plus_gx/ Once you get the ones you need you copy them to your Retroarch/system folder.

Isn't that the truth. I have CCS64, CCS64 in DOS, Hosx64, MAME, WInVice and Retroarch Vice as options for running C64 games. IMHO, when it comes to C64 loading, the Maximum 1541 Speed option in CCS64 is amazing and warp mode in the other emulators doesn't come close. The issue I was having with CCS64 was audio "hiccups". I had almost given up and switched to using WinVice, but found a copy of CCS64 that was compiled differently and it eliminated the major audio hiccups. (There are a lot of CCS64 compiled versions out there; different compilers, release, debug, etc) SID emulation is still better in Vice, but with this version was much improved in CCS64 and what I use. Since I have a custom iPac2 map for my cabinet controls, I have access to the important C64 keys I need. (space, RUN/STOP, F1, F3, F5, F7, Return, Swap Joysticks, Y, N)

Huge difference. The U360 can be used as an analog joystick, or as a general directional stick. In my case I started with just the cheap Happ type joysticks that came in my Xarcade Tankstick. They were terrible for 4-way games, so I upgraded one of the joysticks to a Ultimarc Mag-Stik Plus. This joystick allowed true 4-way/8-way switching and 4-way mode worked great. I didn't find 8-way mode was as good and I had trouble hitting diagonals easily. I then switched to a U360 (with harder spring and restrictor plate), and using downloadable maps was able to get great 8-way, 4-way, and whatever type control I needed. Playing games like Q-bert that required diagonal 4-way worked terrific. Being an analog joystick the throw of the stick was much greater and although I got used to it, the kids didn't like it. Additionally, with how the young kids played, this extra play was fairly rough on the cabinet. Another issue was if I used this joystick in analog mode, it appeared as a joytick and I was having issues with usb device ordering with so many devices connected to my cabinet. (Currently I don't use the gamepad support with the iPac2, and just use the keyboard mapping.) After a lot of googling and reading, I decided to try a true IL Eurostick. Overall much better feel and diagonals work well. The U360 and Mag-Stik Plus are better with 4-way games, but most 4-ways games that matter I run are in MAME and for these I use the Retroarch core mame2003plus which has improved 4-way detection. So far it seems to be working well. A nice feature of leaving the iPac2 in keyboard mode, is for Retroarch cores I can use the cabinet joysticks or the wireless XBox 360 controllers without a need to change any configuration.

I no longer have a U360 in my cabinet. Switched to some authentic IL Eurosticks. For games/emulators that I need true analog input I have Wireless Xbox 360s attached as well. Between the Eurosticks, trackball, Aimtrack lightgun, XBox 360s, and Logotech MOMO steering wheel, seem to everything covered so far.

I know this is a old question, but I'll post my solution in that it might help others. There are several ways of doing this. Launchbox includes pre-run and post,-run AHK scripting tools,Launchbox also allows additional apps to be run before and after each emulator is run. I have had random issues with using these methods and currently if you are using the additional app features, currently Launchbox doesn't let you set this per emulator. You would have to set to each rom/file. (It's been on the feature request vote but hasn't received enough votes.) I find it's much simplier to just create a bat file in the same directory as your emulator and in Launchbox, point the emulator executable to this bat file instead of the emulator exe. (Your bat file will call the emulator executable.) Here is an example of WinVICE.bat I use for loading in a custom iPac2 map for Commodore 64, and restoring the default iPac2 map after the emulator is closed. @echo off call "C:\Program Files (x86)\WinIPAC V2\WinIPAC.exe" "C:\Program Files (x86)\WinIPAC V2\WinVICE.ipc" call C:\Users\ARCADEPC\LaunchBox\Emulators\WinVICE\x64.exe %1 call "C:\Program Files (x86)\WinIPAC V2\WinIPAC.exe" "C:\Program Files (x86)\WinIPAC V2\Default.ipc" exit 0 Obviously you have to create your custom iPac2 maps using WiniPac, (the *.ipc files), but I found this to work flawlessly.

Seems with current versions (1.7.7 here), you need to load a dummy file named cannonball.game Now you set it up just like any other core/rom and things like overrides work as well.

Removed.

I have a dedicated arcade machine with an exit button, so I have not. My GUESS would be, with the Dolphin bar in Mode 4, all the Wii remote buttons are captured by Dolphin itself and mapping to an exit key would not work. Looking in the controller configuration inside of Dolphin, doesn't look like it possible to map buttons outside of the emulation itself. (aka an exit key)