Headrush69

I'm in the same boat. Do you use a second display for backglass on your setup? I have both VPX and Future Pinball tables setup and running fine from LB. There are some great tables for both and each has it's pros and cons. After lots of reading on several Pinball sites, the one issue I can't seem to find an answer to is can you use VPX in a dual screen setup, but leave the main playfield screen in landscape mode? I can rotate my display but I would rather not have that set up and seems VPX always rotates the playfield when I try to use a backglass display. (Basically always switches to cabinet mode)

Which part, the per system overlay or the size of the game play area? FYI, Retroarch now has a per directory override so it's real easy now to save per system overrides.

The issue is FPLoader.exe runs and than starts Future Pinball.exe, so since LB is set to run FPLoader.exe, it indeed has ended. I use a simple compiled AHK script and use it for launching FP tables. The script waits for Future Pinball screen to close before returning control to LB. If you can't compile the AHK you can just as easy make a BAT file that calls the uncompiled script as well.

You likely need to update the mame.ini file to point to your rom directory. Even if you store the MAME emulator on the external drive as well, if your desktop PC doesn't assign the same drive letter as your laptop it would be a problem.

Not 100% sure but it appears you are dealing with cores that support multiple systems that have different controls? If so, a much easier method is just put each system in a different folder and save a per directory remap. Works like a charm.

The only gotcha to watch out for when combining layouts is stick to one coordinate system since there are several options. The mame guides on layout basics is very helpful in explaining them. Once you get the hang of it, it's easy to make layouts that are specific to your setup. I have a Logitech steering wheel modded into my cabinet, but I use the arcade buttons for shifting. (Removed the Logitech stick to fit in an all in one cabinet.) I grabbed the layout code from one of the internal layouts to add an on screen shifter in addition to the bezel for games that support it.

These built in options are just regular layouts as well which you can grab from the mame source. So if you want to create a layout using default artwork or a specific bezel and combine it with the built in color overlay, it's not to hard to mesh the two together.

The issue is we are using FS-UAE's Launcher.exe which calls fs-uae.exe. So when the launcher is done they pass off to execution to fs-uae.exe which does the actual emulation, so to LB, launcher.exe has ended. I used a simple BAT file and a simple AHK script to watch for the real emulator (fs-uae) closing and LED lights stay on like expected. See here: https://forums.launchbox-app.com/topic/52889-fs-uae-ledblinky-problem/?do=findComment&comment=335865

Set up your keys in BigBox and it follows that.

LedBlinky will set Servostick controls as well and LB has support built in. (You don't have to have LEDs to use LEDBlinky)

Are you calling fs-uae.exe directly or using Launcher.exe from FS-UAE? If you are using Launcher.exe, after doing things like setting up WHDLoad, it calls fs-uae.exe for actually running the emulation. So Launcher.exe ends and the closed/quit message is returned to Launchbox. I'm currently trying several options to fix this myself including calling fs-uae.exe directly with custom configs. Edit: Normally in cases like this I use RocketLauncher to work around apps that start multiple subprocess, but then I found WinUAE Loader which is an even better solution for me and my iPac arcade panel/ Edit 2: I use a different technique now. I make a BAT file as my emulator and in it I start the real emulator and also start a custom AHK script. The BAT file waits on the AHK script to close, so LB never sends Quit to LEDBlinky until the BAT file ends. The AHK script just waits for the real fs-uae.exe process to end. FSUAE.BAT FSUAE.ahk Edit: Or you can add everything to the AHK, compile it and use that.

I don't think it's anything to do with your setup. Lately I've been getting the same error after working for over a year. Maybe something changed with wikipedia API that LB uses. Not a huge deal since not much gets scraped from there, the LB database and emumovies usually has everything needed.

Yes but impossible to say by how much and per game will differ. (I have a dual core i3 @ 3900Ghz that makes a massive difference over a 4 core i5 @ 3500 Ghz in another machine) If you have a suitable cooling system, doesn't hurt to test and see how much difference it makes and how much you can increase clock speed.) Do you have auto frame skip enabled in MAME? My cabinet has a much lower benchmark CPU than yours and with frame skipping NFL Blitz 2000 Gold is very playable.

A better GPU won't make a difference in your case. Core speed is king when it comes to MAME. (for the most part) The Intel chip is just better in real benchmarks. Doesn't that chip turbo up to 4.5 Ghz? Edit: According to this that Intel chip looks considerably more powerful: UserBenchmark comparison

You can't map keys in the GUI. You have to edit Retroarch/retroarch.cfg manually. You can see from the post above a sample of my player1 key mappings in retroarch.cfg. You will need to know they keys that are mapped to each of your controls, which you can see in the WiniPac application. My control panel as 8 buttons each player, so I assign them to Retropad buttons A, B, X, Y, L1, R1, L2, R2 and the joystick to the D-Pad.

Without seeing your configs, I would guess either you have something configured wrong in your retroarch.cfg or your default iPac key map. (You don't have any previous saved Retroarch remaps do you, by core, by directory or by game?)

Here is part of my retroarch.cfg player 1 control settings, which I believe are the standard iPac layout.

No. Just set your keys as needed. I would start with General input and than only change specific games that differ from those defaults. If you look at the file Retroarch-> retroarch.cfg and look for input_player# entries, you can set any not wanted to "nul". I would suggest leaving that until you have the rest of Retroarch set up as you want. I have my arcade controls set to resemble a Retropad layout, so I have the option to use the arcade controls or the XBox wireless controllers.

You will NOT need a static mapping for the Mini-iPac. Normally MAME does not use multi-keyboard mode and all keyboards and keyboard encoders (like the Mini-iPac), appear as the one device.

If you are replacing the USB Mayflash stick with a Mini-Pac in keyboard mode, you will greatly simplify your set up and avoid most issues. If you want to use multiple USB devices, especially ones that are hot pluggable, that doc DOS76 posted is a must read to maintain a static device order so your MAME set key mappings stay consistent. Be aware that MAME deletes key mappings to hot pluggable devices if they aren't attached when MAME is started. To avoid that you'll have to set cfg files for those games to read-only.

If you set the miniPac to keyboard mode, you can use keystrokes in MAME and than set no keys in your Retroarch default.cfg and it will use the usb gamepads only in Retroarch. No need to worry about joystick indexes than, I have mine set up like that, except I have my default.cfg in Retroarch mapped to the Arcade controls so I can use them or my XBox controllers.

All you can do is try a different set or modify the audio yourself if it's something simple like pitch or tempo.

Are you using standalone or with Retroarch? I'm on MAME 0.215 standalone and the Tape menu is right above File Manager in the MAME menu. I'm not 100% sure, but I'm not sure Appple II cassettes self boot, so you might have to load to DOS 3.3 first and than load your cassette. Edit: Do you have some cassette only software? I ask because cassette loading works but is obviouskly very slow.

Did you get it working with Daphne and Singe games, or just Daphne? (Singe = Mad Dog McCree for example)

Daphne doesn't have built in support for bezels and LB doesn't provide that functionality, so you will have to use RocketLauncher for Daphne if you want bezel support. It does work and LB will call Rocketlauncher so it appears to launch from LB like any other platform.