Your Friendly A.I Overlord

Right click supermodel.exe > Properties > Compatibility > High DPI Settings > Tick the checkbox "Ignore scaling" and select "Application".

You could try the following: 1. Verify that your display runs at 60 hz. (or 120 hz.) during gameplay. 2. In the nvidia control panel > Manage 3D Settings > Program Settings > Add, add retroarch.exe and redream.exe and set the Power Management Mode to "Adaptive" or "Prefer Maximum Performance". 3. Use NTSC games. (Or PAL games that have a 60 hz. setting.) 4. Verify that Redream and RetroArch are using V-Sync.

Also, in the Windows controller control panel, can you verify that button 7 and 8 light up if you press them together?

If you delete (backup to somewhere else) InputBindings.xml from the LaunchBox\Data folder, LaunchBox will create a new InputBindings.xml upon reboot with the default bindings. You will have to remap the changes you've made to the default bindings. This applies to LaunchBox and BigBox.

First rule of LaunchBox, setup your emulators and check if your games are running BEFORE adding them to LaunchBox. If you use RetroArch for arcade emulation, go to Tools > Manage > Emulators > RetroArch. In the Details tab make sure "Extract ROM archives before running" is unticked. Then go to the Associated Platforms tab. If the platform name you used when importing the roms is not in the list, scroll down to an empty field, double click and select the name of your platform. Then in the Core column double click and select the appropriate RetroArch core. You should not download some random roms and expect them to work in RetroArch or Mame. Like C-Beats mentioned, Mame is the default emulator for arcade roms. Mame roms come in sets and the set versions corresponds with the versions of the Mame emulator. A rom from an old romset might not work with a newer version of Mame and vice versa, let alone if you don't know from which romset version your roms come from. As a general rule, emulation has a learning curve. Learn how to set up emulators and how frontends work. LaunchBox has a YouTube with tutorials and there are plenty of threads on this forum that could be of help to you.

Have you set up your games to use Duckstation? You can select all your games (ctrl + a) and right click a game > Open Bulk Edit Wizard > Next > Field: Emulator > Value: Duckstation.

It works for me when I hold down the Select button while pressing Start. In BigBox make sure you map your exit button (combo) to "Close the Active Window".

This exit script works for me. In Tools > Manage > Emulators > PCSX2 > Running Script, copy / paste the following AutoHotKey script: $Esc:: { WinClose, ahk_class wxWindowNR WinWaitClose Sleep 500 WinClose, ahk_exe {{{StartupEXE}}} }

PCSX2 supports the following file formats:

In Tools > Manage > Emulators > Mame > Startup Screen, you can try lowering the "Startup Load Delay" and see if that makes any difference. (Or disable "Game Startup Screens" for Mame.)

For me the Pause Menu for Supermodel works correctly when in LaunchBox > Manage Emulators > Supermodel > Pause Screen all three check boxes are ticked.

Also untick "Extract ROM archives before running".

CHD's are separate downloads and come in their own set. If you do a google search, you can find them individually. (certainly from a well-known archival site.) There are not many mame games that require CHD's.

Simpsons Bowling requires a CHD.

Like what neil9000 said. But I want to add: If a game does not have an explicit menu option for exiting the game, they usually close with Escape. Or if you use a (Xbox) controller, with the B button.

In LaunchBox > Tools > Manage Emulators > Rpcs3 > Running Script: $Esc:: { WinClose, ahk_exe rpcs3.exe } In Rpcs3 (also for all custom game configurations): Right click rpcs3.exe > Properties > Compatibility. Make sure "Run as Administrator" is unticked.

The script needs to be in the "Running AutoHotKey Script" section. Also check if your aren't running Rpcs3 with Admin rights.

Me too. I use LaunchBox / BigBox on a 65 inch screen with a pc next to my tv stand for a console like experience. I sit ~11 feet away and have set DPI scaling to 250 %. But my gripe is that most BigBox themes are developed for cabinets and even with 250 % scaling a lot of BigBox themes are not clearly readable from my sitting position. I have to edit xml's or edit the theme in the Community Theme Creator (if the theme creator provided the files) to increase the font-size. My question: Is there a way BigBox theme font-sizes could be adjustable from BigBox common to all themes? If not and this is considered a request, I will put in a Bit-bucket request tomorrow. I understand that adjusting the font-sizes can mess with theme layouts. But right now it prevents me from using a lot of great themes. (I'm sorry for the OT post. I won't make a habit out of it.)

Did you also check if the Associated Platform name exactly matches the platform name in LaunchBox?

If you use a keyboard, use "Keyboard Automation" and set to Escape. If you use a controller, you can use any button or button combination you like. I have mine set to the Xbox Guide button + Start.

1. Check your emulators if they don't run with Admin Rights. Right click the emulator's .exe > untick "Run as Administrator". 2. In BigBox > Options > Controller Mappings: enter a button (combo) in "Close the Active Window". 3. In LaunchBox > Tools > Manage Emulators > [your emulator] > Running AutoHotKey Script, enter: $Esc:: { WinClose, ahk_exe {{{StartupEXE}}} }

Sorry, I can't help you with that. I emulate Neo Geo with Mame stand-alone. But I am sure someone else knows.

You don't specify which core or system, but in the Associated Platform tab you can click the field with the core. On the right side of the field a dropdown arrow appears. Click the arrow to select your core.

For me Naomi 2 works fine from LaunchBox. If you like I can walk you through my setup because using bat files for this, you bring a lot of troubles on yourself. Exiting Demul, startup/shutdown screens and pause screens won't work as easily. For Demul arcade emulation make sure you have roms from a Mame romset as Demul uses that naming scheme and does a check on the included roms in a .zip. Also make sure you have the appropriate bioses. 1. Add the bios and rom paths to Demul. (Demul > Config > Plugins and Paths > Roms and Bioses Paths.) 2. In LaunchBox add a "Demul Emulator" with the checkboxes "Remove file extension and folder path" and "Remove space before ROM" ticked. If you emulate multiple systems with Demul leave the "Default Command-Line Parameters" field empty. Else (in this case) put in: -run=naomi -rom= If you emulate multiple systems with Demul, go to the "Associated Platforms" tab. Enter your platform name *exactly* as you have named it in LaunchBox. With the appropriate command-line parameters, in this case: -run=naomi -rom= For exiting Demul, in the "Running Script" tab add: $Esc:: { WinClose, ahk_exe demul.exe } P.s. At the time of writing this, I am on LaunchBox version 12.0 beta-2. So my screenshots are of that version.