Headrush69

We need what fromlostdays requested and also, please state exactly what happens when you try to launch from LB. Absolutely nothing? Does it appear to try to start anything?

Does using START instead of call work?

The file you want to edit is Retroarch/retroarch.cfg The defaults are probably fairly close to what you the iPac defaults to, but look for the lines beginning with input_player1_ You can see from my example above that we are just setting the keys for a Retropad gamepad which is similar to a SNES joypad: Up, Down, Left, Right, A, B, X, Y, L1 = Left Shoulder, R1 = Right Shoulder, Select, Start.

That is a very nice write up JaysArcade, I'm sure it will be very helpful. I have my setup working. I had done all that and my problems were because I was setting up VP9, VPX and Future Pinball all at the same and missed 2 important things. 1) I had setup B2S in my VP9 table folder, but not in my VPX table folder. (or vice versa, can't remember) 2) VPX has an option to disable the B2S server in Preferences -> Configure Keys, Nudge, DOF. I would have expected that option in the Video preferences. I'd like to do a real virtual pinball cabinet some day, but for now this will have to do:

I would suggest starting FPLoader.exe manually and in video preferences set for Windowed mode. Close FPLoader.exe and try launching from LB again. Now right click on the Windows takbar and start Task Manager and see if your compiled AHK is still running.

Yes, you just set the executable for Future Pinball to either the compiled AHK or your BAT file. (So as a Launcher, no extra apps) One thing I forgot to mention is that to compile the AHK you will need need to download the full AutoHotKey. (It’s small and free) just make sure you set the paths correctly in the script to the locations on your system. i prefer the compiled AHK since it’s one less layer or redirection, but the BAT works just as well.

It's very simple. When you set up LEDBlinky you can can do it per platform or even per game. You can set the primary control as 2-way, 4-way, or 8-way and it will change automatically if you enable Servostick in LEDBlinky preferences. For MAME games, LedBlinky comes with several database files and also reads the mame.xml file and preconfigures a lot of games with joystick mode and buttons colors automatically.

If you are going to use LedBlinky, it supports setting Servo sticks too, so it’s as simple as setting up LEdBlinky only. If you have LedBlinky already running with anything else, just enable it in LB and should be working.

Right now I'm making a folder for each table that has a "clean" name. Within that folder I can have several versions of that table, which have the full name with versions etc in the name. When I import I select to use the folder name as the rom name and allow duplicates. I generally only keep one for each table, so after testing I delete the others or rename specifically if I decide to keep a variant.

I've got a lowly i3 in my cabinet and it's handling the job fine. Always on the look out for a used cheap i7 upgrade though. ? I am the same but I don't mind video/audio upgrades that don't affect the game play. Tested an upgraded VPX Terminator 2 table that added explosions on the playfield and absolutely hated it. The kids like that scrolling camera view feature, I don't, but with FP it's just a simple keystroke to switch views, no messing with tables parameters, so it's easy to leave them that option in a cabinet set up. I have a lot of his tables and have been upgrading tonight quite a few of them. LOL. When the kids are asking me everyday, is it done yet, I need to stop. ? Once pinball is completely set up, I'm done. (Except for adding some Sinden light guns ? ) Edit: OMG. Countless hours later... Disable B2S option in Preferences -> Configure Keys, Nudge and DOF. Backglass working with VPX now. Not using a DOF I would have never thought to look there.

I never intended to use a second monitor, but I was setting up my marquee cut LCD I saw that Future Pinball displayed a full screen backglass & DMD automatically and thought this was pretty cool. I have messed with all those settings in VPX and haven't found one that works, yet. I have gotten suggestions to use PINUP player with VPX, but that's just another thing to setup and not all tables have media/backglass packs to use with it. Frankly I'm torn between VPX and Future Pinball. I was always in the VPX camp because the physics where so much better, but newer tables with Future Pinball that use the latest physics, have a dynamic 3D rendering system, media upgrades for the backglass, might make it better for a dedicated cabinet and playability overall. LOL, I love tinkering, but I want to be done tinkering too and just play. ?

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