JoeViking245

You mentioned something about games so I thought that's what you were asking about. My bad. For images and videos, I know some people use symbolic links and physically store them elsewhere (which you can use PowerShell to create). But there isn't a built-in, automagical way to that in LaunchBox itself. I don't use them for this purpose, but if you search here on the forums, you're bound to find something.

Select all the games in your Platform, then look under Tools

Ther isn't really any settings to run them.

$Esc:: Send, !{F4} ExitApp Under the Application Command-Line Parameters:, put "full/path/to/the/.ahk" file you created [including quotes]. But doesn't LB/BB try to pass the Esc keypress to the game and also attempt Alt+F4 when you press the button [combo] you assigned?

From LaunchBox, you can't use the Supermodel UI program. You have to point to Supermodel.exe. Well you can use the UI program, but if you want to launch the game directly from LaunchBox, use Supermodel.exe as the emulator's executable. Can you share a picture of your Supermodel settings in LaunchBox?

Edit the game, what file is it pointing to?

Press your ScrollLock key 1st. Then you can press Tab.

Did you try the: "Drag it to the monitor (TV) where you want it display on" method when launched from LaunchBox?

Dude! You're killing me!! lol You'd need to change the WinMove coordinates. But since they're not moving in the 1st place, it seems like that won't work. You might could do a WinActivate on one of the widows, then do a "Send #{Left}" (aka hold the Windows key and hit the left arrow key) which might send it to the monitor to the left. Then probably a WinMaximize to get it full screen. You wanna attach the script you're attempting to use? There could be some simple little thing that's holding you back. Just a thought.

What are you needing to configure?

Try using just "odyssey2". Or if you must, "odyssey2 -cart1". You also need "i8244.zip" (device file) and "videopac.zip" (parent rom) For MAME (and even [old school] MESS), the files need to be zipped. For example: "A Labyrinth Game / Supermind (Europe)", MAME is looking for "2lbsprmd.zip". Also, make sure Extract ROM archive before running is NOT checked.

The word "primary" is just how Windows sees it. MAME don't care. It just wants to know where YOU want the game displayed (which is what you set on the "screen" line in mame.ini). They will be in your ,,/MAME/cfg/ folder. You would have had to manually edit the games cfg file yourself. So at this point I don't think it's an issue. You WILL have config files in there for the games you've played, but they won't have the extra "video" sections in there that would output onto a specific display. Ya, do that. Make a fresh install of MAME for testing. Just don't go around changing a bunch of 'other' stuff. Just stick with "the plan".

LaunchBox will run/play pretty much anything you throw at it. Import your (mp4) videos into your 'Nostalgia' (or whatever you decide to call it) Platform. Skip past (for now) the section for which emulator to use (i.e. 'don't use an emulator'). Once they're imported, double click one of the "games" [videos] and it will open the video using your default video player. Now that you have proof-of-concept, you can add an emulator that points to your video player of choice and add in a Default Command-line Parameter(s) such as "--fullscreen". Then use 'that emulator' to launch [play] them.

@Ingabagovinanana Hmmmmm....... To start MAME, are you just double clicking mame.exe in Windows Explorer? When I set mine up like this: (everything else is "auto") MAME comes up and plays on my monitor #1. If I change the "1" to a "2", it's all on monitor #2. Now if I change it to a "3", everything's back on monitor #1 because I don't have a "\\.\DISPLAY3". Which leads me to saying: make sure it's 'spelled" correctly. As in the slashes are backslashes ( \ ) and not forward slashes ( / ). And when you input "\\.\DISPLAY2", don't add "(primary)". And also no quotes. I recall now that the latter "screen0" etc. are for your advanced setup like when your cab uses a marquee AND you have the game_rom.cfg file setup. (also used for arcade games that have multiple monitors) This is also where numscreens comes into play. So for now, leave that at 1 because if other settings aren't changed and the cfg file is not setup, it'll be as if you 'mispelled' something and it WILL show the same thing on all screens. After checking all that and it's still not displaying on any of the other 2 monitors, I'd say: Install a fresh copy of MAME into its own new folder. Copy a romfile to test with into the ../newMAME/roms folder. Create a [new] mame.ini file {type "mame -cc" at the command prompt). Open MAME and run the game. Exit the game and MAME. Now change the "Screen" line (because you haven't done it yet before this point on this fresh install) from auto to \\.\DISPLAY1.... and test as suggested before. But ONLY for "screen". Not "screen0" and the others. If after trying that and it STILL doesn't cooperate, I don't know what to tell you.

Make sure you only have 1 mame.ini file. Look in your MAME root folder (should be the one you've been editing). Look in the ../MAME/ini folder. Hopefully there's not one there [also]. Once you've verified there's only 1, edit it making the following changes: Change "screen" line to "\\.\DISPLAY1" Change "screen0" line to "\\.\DISPLAY1" Change "screen1" line to "\\.\DISPLAY1" Change "screen2" line to "\\.\DISPLAY1" Change "screen3" line to "\\.\DISPLAY1" Save. Close. MAME. Play. Make note. Exit Change "screen" line to "\\.\DISPLAY2" Change "screen0" line to "\\.\DISPLAY2" Change "screen1" line to "\\.\DISPLAY2" Change "screen2" line to "\\.\DISPLAY2" Change "screen3" line to "\\.\DISPLAY2" Save. Close. MAME. Play. Make note. Exit Does anything change?

You can't change that, but you can change which display it comes up on. open/edit your mame.ini file. Scroll down to the "OSD PER-WINDOW VIDEO OPTIONS" section. They should all be set to "auto". Change the "screen" line to "\\.\DISPLAY1" like so: Close/save the file. Start MAME. Make note of which screen it comes up on, and which screen [when you start a game] it comes up on. Should be the same. Exit MAME. Open mame.ini (again) and change "\\.\DISPLAY1" to "\\.\DISPLAY2". Close/save the file. Start MAME. Make note of which screen it comes up on, and which screen [when you start a game] it comes up on. Should be the same. Exit MAME. Open mame.ini (again) and change "\\.\DISPLAY2" to "\\.\DISPLAY3". Close/save the file. Start MAME. Make note of which screen it comes up on, and which screen [when you start a game] it comes up on. Should be the same.

Did it create that file?

@Ingabagovinanana Get MAME running on its own, correctly, before even worrying about any frontends. After watching (at least the 1st part of) the video and getting things to work correctly on the backglass, close MAME and make a copy of the mame.ini file and call it "horizont.ini". Now don't touch that file. Leave it alone. What this does is loads that ini file anytime you run a regular [horizontal] game. Now go through those steps again to gets things working on the playfield. Change the "\\.\DISPLAY2" settings, rotation, etc. as discussed in the video. Pro tip: test using an actual vertical game such as Donkey kong. Once everything is working correctly for vertical games (correct monitor, correct rotation and so on), exit MAME. Now make a [another] copy of the mame.ini file and call it "vertical.ini". Now what should happen is whenever you launch a horizontal oriented game, it'll play on the backglass. And when you launch a vertical oriented game, it'll launch on the playfield. I don't think he shows it, but he does mention how to navigate to your MAME directory inside the command prompt. Once there, type the command mame.exe -v >stuff.txt Or if you have an onder version: mame64.exe -v >stuff.txt Once MAME has loaded, exit it. You now have a file in your MAME root folder called "stuff.txt". Open that text file and a little was down you'll see your Displays, as MAME sees them.

Not true. Unless you're talking about the other "Joe". But thanks? lol But I think your question is regarding MAME. It sounds like you're saying when you launch a MAME [Arcade] game, the game comes up on your monitor #1 (which is your backglass). But before that, MAME's warning saying (something like) "This game may be screwed up, so don't blame us. Press any key to continue." will show up on your monitor #2 (which is your playfield). Or is the warning AND the game both showing up on monitor #2? What does your "OSD PER-WINDOW VIDEO OPTIONS" section in your mame.ini look like? Do your "OSD VIDEO OPTIONS" section have "numscreens 1"? Or is it set to 2? Is the only issue the Warning popup? If so, search for a "no-nag" copy of mame.exe that matches your current MAME/roms version and replace your current one with it. BTW, it was by chance that I saw this message. If you need to get my attention, the other Joe, or anyone for that matter, in your message type @ (the "at" symbol) followed by the person's name. If there're multiple options, keep typing 'til you find the right one or click it when it appears in the 'list'.

Fixed script in previous post. (read below for "other" fixes added too) The WinMove did work. The issue was you couldn't "see" it move until 'that' window took focus. (Alt+Tab to the 'other' window(s) would set focus and then show it in its proper location on the screen) [Still] no need for guessing Sleep times. YAY! After WinMove, added a WinActivate call to set focus and "show" the move(s). At least it worked in my tests. I noticed that with 3 screens, in the lower right [monitor] corner you see whatever is behind (LaunchBox, desktop icons, desktop wallpaper...). 2 possible solutions to hide that are: A) make the 3rd screen fill the whole bottom half (though would probably look bad) or B) use the "fixed script" to have it: Minimize all windows Hide the desktop icons Set the Windows wallpaper to null Set the background color to black then at the end of the script Restore LB/BB window Unhide the desktop icons Reset the wallpaper back to what it was (if one was being used) Reset the background color back to what it was (if other than black)

Try adding a sleep after RemoveExcess(). Either inline (3 locations) or in the method itself (add a 'Sleep' line in between the last 2 close brackets). Because it's part of retroarch.exe. If you need to tweak the emulator(s), you'll want to comment out RemoveExcess(). Or do them stand alone.

It's probably me that's misunderstanding in that I've never actually used Retroarch to emulate MAME. For me, using an emulator to emulate an emulator that emulates a Console just seems odd. However, since your above command worked from the command prompt, it sounds like a path issue. I think there's a "proper" folder to place MAME BIOS files into to alleviate that issue in Retroarch. But I don't know where that is. Until then, you can (should be able to) just add the rompath back into your Custom Command-line Parameter: gx4000 -rompath "F:\LaunchBox\Games\Armstrad GX4000" -cart

Is the title bar, border and menu being removed on all of them? Are the windows being stacked on top of each other? Or are some moving and the rest stacking? They're not trying to open fullscreen ae they? Is it not aligning in all 4 scenarios? (well 3 actually. Selecting "1" shouldn't need any aligning. ) Or is it they just have gaps in between them? Maybe double check the WinMove lines. I may have transposed their placement or something. It's been known to happen with me.

@Klopjero When you have a Custom Command-line Parameter, it overrides whatever is shown in the Sample Command (after the emulator (#1). For the Retroarch emulator (where you choose which Core to use), LaunchBox automatically inserts the "-L core.dll" parameter (#3) into the Custom Command-line Parameter when it executes it. I don't think you need to add "-rompath" since your games rom is already pointing to the rom file in the path that it's in (#2). LaunchBox will add the "FULL\PATH\TO\ROM\FILE" (#2) to the end of the Custom Command-line Parameter when it executes it. So for your Amstrand GX4000 Platform (make sure the Platform selected in column 1 is named the EXACT same as your actual Platform) where you select mame_libretro (column 2) as the core, your Custom Command-line Parameter (column 3) only needs to be gx4000 -cart No quotes. No slashes. Pro tip: Many of the consoles used in MAME can be launched without needing the media option. i.e. you might be able to get away with only having "gx4000" in the Custom Command-line Parameter [without the "-cart"]. At least it does for stand-alone MAME. I assume Retroarch MAME is similar. Then when you go to launch Barbarian 2, LaunchBox will send the command "F:\Emulators\retroarch stellar\retroarch.exe" -L "F:\Emulators\retroarch stellar\cores\mame_libretro.dll" gx4000 -cart "F:\LaunchBox\Games\Armstrad GX4000\Barbarian 2 (Europe).zip" Note, only the single parameters that have spaces in them needs quoted.

LEDBlinky Support