Your Friendly A.I Overlord

I don't claim to be an expert on pinball games, but a lot of them allow you to directly launch into tables. I myself do this with Pinball FX and Future Pinball. On the matter of RetroArch, RetroArch has a command-line parameter: --appendconfig PATH Appends a different set of config files to the config file loaded in -c (or default). Multiple config files are delimited by ','. Every config file will be appended in order where the key-value pairs of the next config file takes priority over the old ones. First put your save state in its own folder and then create a config which contain the lines: savestate_auto_load = "true" savestate_directory = ":\states" Ofcourse ":\states" should point to your new folder. You can add those save states to LaunchBox as new games, or as additional apps with your existing games and (with the custom command-line option in the "Edit Game" menu) append the new config. P.s. Not that I actually tested this, but it seems doable.

You already can do this in the LaunchBox or BigBox controller mappings settings in their options menu. If it's not auto-filled by LaunchBox, you can look it up and fill it in yourself. Go to: LaunchBox > Tools > Manage Emulators > ePSXe > Pause Screen tab > Save State tab. Enter: Send {F1 down} Sleep 50 Send {F1 up} Do this for Load State as well.

If you mean core configuration files you have to set it up in LaunchBox. In LaunchBox go to: Tools > Manage EmuLators > RetroArch > Associated Plaforms tab. Then in the "Extra Command-Line Parameter" column add: -c "config\mame_libretro.cfg" (or whatever the core is called).

You can use the LaunchBox \ BigBox pause screen for that. But because every emulator uses its own hotkeys for saving and loading, you have to set it up per emulator. You can do that in LaunchBox and for popular emulators the hotkeys are already filled in. Then you set up a button (combination) to pull up the pause screen. Alternatively you can use key \ controller mapping software like: JoyToKey, Xpadder or antimicro and bind hotkeys to controller buttons (or button combinations) and make emulator profiles that auto load.

Have you tried to find out why your controller isn't working, like @JoeViking245 suggested. Because if you have to put in: Joy8:: { Process, Close, {{{StartupEXE}}} } that means autohotkey is doing the exiting, not the BigBox controller automation. You can select different controllers in BigBox (like LaunchBox) for controller automation.

https://github.com/mborgerson/xemu/wiki#mcpx-boot-rom-image Google it.

If you want different versions of the same game, for PCSX2 Configurator to work, you have to name these games differently in LaunchBox. For example Game Name (EUR) and Game Name (USA). PCSX2 Configurator creates folders with config files after the game name in LaunchBox in your PCSX2\inis install folder. Obviously these folders can't have the same name.

In LaunchBox you could add the parameter: --startMinimized to your command-line in the Edit Emulator setting for TeknoParrot. Obviously this launches TeknoParrot minimized so it doesn't interfere with the startup screens. Also in TeknoParrot's settings there is an option "Hide Console Window". You could try that as well. (Although I doubt if it actually works.) You can set the duration for the startup screen per game . The maximum length is 30 seconds. After that you get a black screen for 10 seconds (with a startup time of 40 seconds for your game.) With startup screens you can also try the option "Hide all windows that are not in exclusive fullscreen mode". But with TeknoParrot you have to set this on a per game basis because, with this option checked, it can hide some games completely behind the startup screen and they won't show up at all.

Just for future reference, quite often the cause for stuttering is the power management setting of your graphics card. For Nvidia the default setting is "Optimal Power". That puts your graphics card in its lowest power state faster and is sluggish to clock up. This can result in stuttering, lag or screen tearing. For gaming the "Adaptive Mode" is better. Adaptive Mode switches to a higher power state and thus higher clocks faster. Sometimes its even necessary to select "Prefer Maximum Performance" which forces the card in its highest power state. It is best to set the power management on a per game \ emulator basis, because for most of the time "Optimal Power" is fine. You don't want your graphics card on full throttle while browsing the web.

I'am having the same problem. In launchBox sometimes after returning from a game I hear the audio from the video of that game. Sometimes even after editing a game I hear the audio from the video of the previous game I edited. Funny thing is, I don't even use de "Game Details view" in LaunchBox and I don't have game audio files. Disabling "Show video's" for LaunchBox's Game Details view solved the spontaneous audio issue for me.

Yes, that's the transition from FPLoader to Future Pinball. If you have configured LaunchBox with FPLoader as the emulator, as far as LaunchBox is concerned the emulator has exited. The startup screen is aborted and no shutdown screen. If you make and compile a script that only stops after Future Pinball has exited and set that as your emulator then LaunchBox keeps seeing that script as a running emulator. I got perfect startup and shutdown screens for Future Pinball that way. IMO, that's one of the best features of RocketLauncher. I stopped using RocketLauncher when most of it's major features where implemented in LaunchBox. But I still like it's fine grain configurability. I hope one day Jason implements some "more advanced" options into LaunchBox, but I get that he whats to keep it as simple as possible.

You're right. Sometimes when you are new to a platform or emulator and read something in a thread and it works, you don't think twice about it. What I suggested only works if you have a platform with just Future Pinball. Then putting /open %romfile% /play /exit in the Emulator Details tab of Future Pinball is a way better solution.

Aside from having Pinball FX3 on steam, this is my first foray into pinball emulation. After reading this thread I decided to start with Future Pinball and this Star Trek table. I got it working thanks to the comments of JoeViking245, Headrush69 and sundogak. In Future Pinball and in LaunchBox. Thanks! I did however, run into a problem with startup screens terminating early due to LaunchBox seeing the BAM launcher as the emulator. After reading some comments in this thread about compiling an AutoHotKey script to exe I came up with mine. The AHK script can be compiled with Ahk2Exe.exe and must be placed in the BAM folder (where FPLoader.exe is). Then point LaunchBox to the exe. Run, FPLoader.exe /open "%1%" /play /exit Process, Wait, Future Pinball.exe Process, WaitClose, Future Pinball.exe ExitApp BTW, I read in another thread that the command line parameters: /open %romfile% /play /exit must be put in the Manage Emulator > Future Pinball > Associated Platforms tab, under "Default Command-Line Parameters". That worked for me.

I am curious too. But more of Android emulation in general. In the past I read that most Android emulators, if not all, are riddled with malware. I dabbled in Android-x86 in a vm once (about 2 years ago), but back then it didn't have a big compatibility. Is Android emulation/virtualization improved (or safe) in the mean time?

Maybe he could copy the .xml of his platform from the Backups folder. That way his games would show up and then he can delete them again, but this time also delete the rom. Just look if the oldest backup still has the roms.

I'm on v0.5.0-4 and it does work. Look a this thread for my setup: I suspect it is a Xqemu feature on which Xemu is based. I Remembered from a year ago, when I was testing Xqemu.

It all depends on what the o.p.'s use case is. If the main goals is mobility, sure an external HDD is absolutely fine. But is you're going to fill 8 TB to the brim with games, frontend artwork and play recent emulators, then an large internal HDD + (Sata) SSD for image and emulator cache would be ideal.

1. On the first screen check: "View ISO Details" > Next 2. Load ISO file > Next (ticking "Check for crosslinkable files" could potentially reduce file-size, but in my one test it didn't matter.) 3. If you get warnings, ignore them and click "No" 4. On the ISO details screen go to de "Other" tab then click "Extract Data Partition" 5. Save your new ISO. Note: I had only one Redump DVD9 ISO to test with, but the rebuild ISO played fine in Xemu, *Edit* @Wally After the rebuild process I ended up with a ISO 6,9 GB in size. After a "Mulleted" rebuild pass (like described 5 comments above) I ended up with a ISO 4,35 GB in size (DVD5). That is the same size as the CXBX-R folder game I had and plays well in Xemu. Although this is not always possible.

Generally speaking, games on Steam are modern pc games. 100+ GB in size is no exception. They require fast storage for booting, loading and swapping data in and out of memory, especially texture data. SSD's are pretty much a must for modern pc games. Retro games are generally MUCH smaller in size and even emulated systems that are fairly recent had no more than a mechanical hard drive to begin with. Although I still would recommend a Sata SSD if you are going to emulate recent systems, even then a (USB 3) hard drive is absolutely fine. Let alone for older systems. One thing to look out for though. High density hard drives can use Shingled Magnetic Recording https://en.wikipedia.org/wiki/Shingled_magnetic_recording which slows read/write operations down. And as I don't have experience with USB drives and emulation, USB drives don't have fixed drive letters by default. But that would be easy to solve, I think. BTW, I don't know the youtuber "Unbox Junkie", but for reviews I would look for more specialized youtubers or respected techsites.

In BigBoxSettings.xml : <KeyboardBack>2</KeyboardBack> = Back(space) or in InputBindings.xml : <InputBinding> <InputAction>BigBoxBack</InputAction> <ControllerHoldBinding>None</ControllerHoldBinding> <ControllerBinding>Button2</ControllerBinding> </InputBinding> = Controller button B (Xinput)

Go to: Tools > Manage Emulators > RetroArch. Under the "Exit AutoHotKey Script" tab enter: WinClose, ahk_exe retroarch.exe BTW, You can use controller automation in LaunchBox and BigBox and set a button (combo) to exit out of games. You don't have to use the pause menu for that.

1. Check "Build/Rebuild an ISO" > Next 2. The top/left tab "Load local folder" > Browse > Select your game folder > OK > Next 3. Bottom option "Create standard XBOX 1 ISO (No XBE checks) " > Next 4. Check "Optimise for disk size" > Drop-down menu select "Small as possible" > Next 5. Click "Make ISO" > Select save location > Save

See my post above! ? XDVDMulleter Beta 10.2 works fine for me.

Pro tip, you can do this via the command-line! -full-screen -dvd_path If you prefer software with a GUI, XDVDMulleter Beta 10.2 works also. Some iso's don't work in Xemu. For example from Redump. Then first you have to extract the iso to folders, then rebuild back to iso. (Or directly rebuild to a new iso.)

I got Xemu working with command-line parameter: -full-screen -dvd_path