JoeViking245

I swear NES was working for me yesterday. But it's not working today. However, I did find an apparent 'fix'. (at least it's working for me, today) Edit your emulator and change the Emulator Name: to "Get-Game MAME". Or "MAME Get-Game". Or "Get-MAME-Game". Or some variant that has the word "MAME" in it. "ThisIsNotTheMAMEemulator" will also work.

Just look at mine. I guess I have something similar in my running script. To 'play nice' with PCSX2, you may want to change out that Process, Close $Esc:: { WinClose, ahk_exe {{{StartupEXE}}} } Also, unless you always exit from the pause menu (uses the Exit Script), you'll want to put this in the Running Script section.

Here's what I found... It works in some Platforms and not others. Why? I have no idea. For me it works in Arcade and in NES. But it didn't work in SNES or Wii. So you may want to test in a different platform, until you find one that doesn't express concern that the ROM file doesn't exist. Then in that platform, do your full-blown testing with the proper batch file to see if it'll even work as you'd expect. Once that all for-sure works, you can jump back to resolving the ROM file doesn't exist issue.

Do you have "-nogui" (without quotes and a single dash) for your command line parameters?

If you can find MAME category ini files for those playlists you want, you can create the playlists with this plugin. In the plugin description, it describes where you can find some and also create-and-download them (read this comment) for importing. You could also create them long-hand if you follow the ini formatting (though may be tedious).

You can add/set-up both emulators in LaunchBox and assign their Associated Platform to Xbox. But only one of those can be the Default Emulator. Then in LaunchBox, you can right-click a game, select Launch With and choose one or the other of those 2. If say you set xemu as the Default Emulator and you have a specific game that you want to always launch with cxbx, you can edit that game and in the Emulation section, change the emulator to cxbx. Likewise, you can select multiple games and use the bulk edit wizard to change them to use cxbx.

When you open Dolphin by itself and start a game from there, does it do the same thing? Is the game "playing" such that you hear sound from it and just the game screen is black? Or does it just show a black screen, until you exit the game?

2 possible options for adding individual games are: Drag and drop the ROM files onto the LaunchBox UI (follow the prompts) Click Tools, Import, Manually Add Game (you'll need to do this for each game)

Correct. LaunchBox does not innately support marquee monitors. aka, a second or even a 3rd monitor. And requires aa 3rd party app or plugin to do so.

Try having LaunchBox change the paths for you. Select all games in your Arcade Platform (click on one, then press Ctrl+A). Then click Tools, File Management, Change ROMs Folder Path for Selected Games and follow the prompts.

Any chance you have Steam running in the background?

If you're using a recent version of PCSX2, specifically QT (recommended), in your Default Command-line parameters (when you edit the emulator in LaunchBox) put -nogui "Old" PCSX2 would have you put "--batch" (I believe that's what it was). Also, to have it start in full screen, you can either open PCSX2 emulator and check the box for fullscreen, or add "-fullscreen" (old way was "--fullscreen" (2 dashes) [both without quotes]) to the command-line parameters. (sorry. I had forgot about the -nogui part)

Better than using a script.... verify that you don't have Confirm Shutdown checked.

It's recommended to always use the Exit selection from within the PC games menu for exiting these types of games. This is to ensure a proper shutdown of the game. That said, if the games executable starts the game directly (vs being a 'launcher' app that then loads the game), it may be possible to save your above script to an .ahk file (MyScript.ahk) and then set that as an Additional Application for the PC game and have it Automatically Run Before Main Application. No. The only way to dedicate a single image type (i.e. Box-Front) to a game is to remove the other images of that type for that game. Otherwise, you get to cool effect of having that image type alternate through the other images [of that type].

Did you set up the Controller Mapping in BigBox itself for Close Active Window? LB and BB controller mappings are set independently from each other. You can use the same button combo. Just need to map them in each program separately.

But the batch file needs some information 1st to make it dynamic (aka universal to many ROMs). The games ROM (.exe in your initial testing) doesn't need to physically be there. But the game does need to point to where it's going to be. i.e. game.exe is going to be downloaded (copied) to d:\no\where\in\particular\ Then, launching the game with the [batch file] Emulator (like the one I posted earlier), 2 parameters get passed to the batch file. The 1st one is the %romlocation% parameter and the 2nd one is the full path to the ROM file (or .exe in your case). Now, that batch file can look for GamesSource.txt in the romlocation's parent directory (extrapolated in the 1st FOR statement). blah blah blah and so on. You can adjust your games Launching File Location so that it looks for GamesSource.txt in the appropriate parent folder. And if all your game's download info is coming from the .txt file, you'll still need a fake "game.exe" in the Launching path for the above batch file (as written) to work correctly. You can always adjust the Location path and/or batch file contents accordingly. My Dummy.bat file (emulator) that gave the above output when launching "game.exe" looks like @echo off set path=%1 set fullRom=%2 echo. echo RomLoaction: %path% echo. echo FullPathToRom: %fullRom% echo. echo. echo The End pause

What ROM are you passing to the Emulator (batch file)? The ROM shouldn't have changed any. Thus it exists. Just the Emulator you're passing the ROM to changed. I did forget to mention (remind you) to associate the new emulator to the platform. You can set it as default, or leave that unchecked and right click the game and choose Launch With, then select the original emulator or the new one. This [has and] will work. If it's still causing issues, share screen shots of your new Emulators Details section and the Associated Platforms section. Then also, the game you're trying to launch, its Launching section and Emulation section.

Well, if it ain't broke, don't "fix" it. It may very well be valid. I've just never seen it in a set parameter. Though I've never used /p in there either. So may be a part of that?

Yes. Get your stuff to process in less that 40 seconds. Didn't realize there was a 40-second 'safety net' for Additional Apps. But makes good sense. Well, except for your unique circumstance. I think this puts you back to creating a new emulator. You wouldn't have to use cmd.exe. Just point to the batch file. But you would have to create one for each emulator you need to do this 'download' process for. This might work for something like PCSX2.. and you can put this batch file anywhere. It doesn't rely on where it is located. Not tested but looks good in print. Note: parameter %1 and %2 both include quotes. You'll see where I removed them at the beginning for %1 (path). And on the last line, did not put quotes around the path to Rom because %2 (fullPathToRom) already includes them. May need to modify eof to either start the game or just completely exit the script. oh... where you set the GameSource, is that less-than symbol supposed to be there? set /p GameSource=<"%parent%\GamesSource.txt" @echo off set path=%1 set fullPathToRom=%2 rem remove quotes set path=%path:"=% if exist "%path%\CopyComplete.txt" ( goto eof ) FOR %%A IN ("%path%\..") DO SET "parent=%%~fA" if exist "%parent%GamesSource.txt" ( set /p GameSource=<"%parent%\GamesSource.txt" ) else ( cls echo %parent%GamesSource.txt does not exist. echo This file must exist at the root of games directory. echo It must contain the path where the games are stored on your network. echo The path must end with a \. pause Goto eof ) for /f "delims=" %%A in ('cd') do ( set FolderName=%%~nxA ) if exist "%GameSource%%FolderName%" ( robocopy "%GameSource%%FolderName%" "%~dp0." /e echo Copy Completed. > "%~dp0.\CopyComplete.txt" echo Game Launching... ) else ( cls echo The directory "%GameSource%%FolderName%" does not exist. echo If the path above is not correct, check %parent%GamesSource.txt. echo This file must exist at the root of games directory. echo It must contain the path where the games are stored on your network. echo The path must end with a \. pause ) :eof start "" /w "D:\LaunchBox\Emulators\pcsx2.exe" %fullPathToRom%

Hi @dummy-account. Welcome to the forums. What controller issues specifically are you experiencing? Do note that LaunchBox does not configure nor adjust controllers in and for the emulators themselves. That is completely independent of controller configuration for navigating within LaunchBox. To answer @roofamilyh's question, yes, a Premium account is required to be able to navigate LaunchBox with a controller. But this has no effect on using a controller within an emulator. The caveat to the latter is with Steam when you have its' UI set controller configurations. So I've heard as I've never set them in Steam itself. Steam games, ya. Steam UI, no.

In short, no. You can't pass variables to Additional Apps. One possible solution is to create a new emulator in LaunchBox that points to a batch file. Use this emulator as the default. The Application Path for your emulator would point to this .bat file. The Default Command-Line Parameters could/would be %romlocation% This will send to the batch file parameter %1 = "C:\Path\To\Rom\" (aka %PathToGame%). Parameter %2 will depend on the boxes you check (or don't check). Remove quotes and also Remove file extension and folder path. But you'll probably want to at least keep Remove Quotes un-checked. %2 will be the ROM_file. Either "full\path\to\ROM_file.ext" or "ROM_file" (without the path and file extension). In the batch file, start the ps1 script using a /w for "wait for exit" and use %1 in its parameters. set PathToGame=%1 set ROM=%2 start "" /w "C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe" -file "%PathToGame%/Get-Game.ps1" On the next line, start the actual emulator with any of its parameters and %2 (actually %ROM%) for the ROM. You should use /w here as well so the games Shutdown Screen will work correctly and also if you want to remove the downloaded game after it exits [on another line]. Or if, unlike me, you're PowerShell savvy, you can do all this in a single ps1 script rather than a batch file calling a ps1 script. If you do go this route, to make the scripts 'less visible' when executed... for the batch file, create a shortcut to it, right click the shortcut, select Properties, next to "Run", choose "Minimized" and click OK to save. Then point to the shortcut in LaunchBox. For PowerShell, right before "-file", add in "-WindowStyle hidden" (without quotes).

Look for and delete: Path_to_your_emulator/MAME/ini/ptblank.ini Or it may be in MAME's root folder: Path_to_your_emulator/MAME/ptblank.ini If you're not using the parent ROM, look for ptblanka.ini Edit: Just reread that you said it was mirrored. In that case look for and delete Path_to_your_emulator/MAME/cfg/ptblank.cfg