JoeViking245

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

Since the games "rom" is a text file with the same name as the games folder, and they all use "Game Loader All RH.exe" to launch (both deduced assumptions)... @echo off cd "E:\Taito_Nesica\%1" start "" "Game Loader All RH.exe"

@CosmicC 4.04-beta-1 - Removed: Copy to Clipboard Feature introduced in v3.11.3-beta-17 due to conflicts when running the plugin remotely - Fixed: Accidental 2nd click while Importing is already in progress ImportMameSoftwareLists v4.04-beta-1.zip Let me know if that fixes your Remoting in issue and the coffee-jitter extra clicks.

Ya. Don't do that.

Unfortunately, they're not related. lol The error message you posted is a result of remoting into your cab (thanks for mentioning you were doing that!). If you run the plugin locally (from the cab itself) with tightvnc turned on, does the error still occur?

The list of roms I use for the plugin comes directly from running "demul.exe –listroms". This tells me the systems and roms it can emulate. As far as I know, Demul hasn't been officially updated since 2018. So there would be no additions to 'the list'. Now there's a really good chance that MAME itself has made updates/additions to roms for the systems Demul can emulate. There's also a chance that, even though the Demul emulator hasn't been updated in a couple years, it can actually run some of the "new" roms (if any). But I honestly have no idea on either of those accounts. If you happen to come across a list of roms that Demul can emulate and are not mentioned in the v0.7 release (via the above command), please let me know and I will definitely add those in.

When selecting a Platform from the dropdown list (one of your existing Platforms), don't start typing a bunch of letters to find your [existing] Platform. It's best to just click in the box, then scroll down to and click on your Platform. Or if you click Add New, it will automatically put in the name (as defined by MAME) in the window that pops up. At this point you can modify the name and/or click OK. If that name already exists (is an existing Platform), you'll get a message saying so. Just click OK. This has been an inherent problem with the plugin ever since it was 1st created and you, my friend are the lucky one to have discovered it. Thank you for bringing that to my attention. I will have my team incorporate a fix for that with the next plugin update. Until then, try not to get too happy with the keyboard and let the mouse 'do the walking'.

It is updated for use with the latest version of Demul. Which the most current version I see is v0.7 (Apr 28, 2018).

Instead of using the (almost square [600x578]) Banner, could you use the (more rectangle [1040x214]) Clear Logo instead?

The Dot Matrix Display is the that little DMD window thingy (how's that for tech jargon? lol). The backglass is the one that uses the b2s backglass server. They both get the info to display [typically] from the rom file. Though I think the DMD reads it directly and the backglass has to extrapolate from it (maybe that's where the 'server' comes into play??). Or something like that. Regardless, DMD tiny. Backglass big. Let me know if that wiggle trick works for you.

This was from a post 4 years ago, and I have no idea if it still holds true.. Again, no idea if MAME still uses 9.0c or has since 'updated'. The full thread is here: Sound stuttering / slow down in MAME. Video card settings to blame? : MAME (reddit.com) You'll need to click "Continue this thread" under MAMEHaze's 2nd comment to see the rest. But his 1st one has a direct link to DirectX 9. Anyway, just throwing that out there.

Maybe change this to true (default I believe is false) if it's not already? [../Visual/ Pinball/VPinMAME/] Mine was set to false, and don't have issues (though I probably will NOW that I've said something. lol). But I do recall, when starting a new (to me) table, the DMD would sometimes appear behind the table. So I'd Alt-Tab to the DMD, click and 'wiggle' it a little bit in place, then unclick. (ya, sounds funny. But it seems to do a somethin') Click the table (set focus). DMD would remain on top. Exit the table. Restart the table, and wha la!

I assume it's safe to say you're using MAME 0.220 to match your 0.220 romset. (srry, but have to clarify ) And also you're seeing this using standalone MAME (vs via LB/BB). Try setting the video mode (in MAME) to something other than auto or GDI and see if makes any difference (a sort-a process-of-elimination).

You won't find it under Tools. You need to Select more than one game (or all of them) in your Platform. Then Right click on one of the selected games and select "Bulk Run Before/After Main Application". Similar to what it says under "Using the plugin:". It'll be at or near the bottom of that menu that comes up. I just tested with the latest LB v12.6 and it was there (image above). If it still doesn't appear in the right-click menu, turn on debugging (if it's not already on) under Tools, Options, Debugging. Exit LaunchBox. (wait a sec for it to 'completely' exit) Restart LaunchBox. Right click on a game. If it [still] doesn't show at all in the menu, Exit LaunchBox (again). Then reply to this message and drag-and-drop the most recent file located in your ../LaunchBox/Logs/ folder onto your reply. Then I'll see if I can 'see' anything in the log indicating what's going on (or NOT going on, as the case may be ).

Only have one of them in your plugins folder. The latest, v2.0 is your best bet. I assume you can see it when you right-click, but it's 'greyed-out' and you can't select it. If that's the case, you must select more than one game and then right-click. Selecting just one game won't work because then it wouldn't be 'bulk'. If it's still not working, let me know.

@whazzzzzup17 So glad it's working as it should!!!!!!! Well, I broke down and actually tested it with RA on my cab. Finally. lol Though I did 'cheat' and used [up to 4 instances of] the same retroarch.exe for each launch. 😊 Going through this (now, properly) I saw some things with the code that could be improved and cleaned up. The Sleep 'timer' was kind of a cheesy and was bugging me, so I changed it to WinWait. Now there's no guessing as to how long to set it. I looked closer at the RemoveMenuBar method and saw it was only working on the "Active window". Doh! It was also long and ugly, so I revamped the 24-lines of code into 2 lines AND it [now] works on the window we tell it to. I know this is a moot point because of the recent 'discovery' of turning off the menu bar directly in RA. But it now actually works, regardless of the setting in RA. The Loops inside each "If (UserInput=)" are all the exact same, so I moved them to single method and now just call that method. Fun project! Thanks. (Edit Dec-31: Fixed window positioning. Added code to hide all background stuff)

It might be an RA thing then (I never tested it in RA). There is a setting in RA where you can remove the title bar (at least). Settings, Video, Window Mode, Show Window Decorations. (Above) your 1st image (left 2) didn't have the title bar, but the 2nd one (right 2) did.

There might be a loading time issue. Start with a UserInput = 2 (load only 2 instances of RA), and increase the "Sleep" right before the Loop to something like "Sleep, 10000" (ten thousand, aka 10 seconds) .... else If (UserInput == 2) { Run, "%RA1%\retroarch.exe" -L "%RA1%\cores\%1%.dll" "%2%", , , p1 Run, "%RA2%\retroarch.exe" -L "%RA2%\cores\%1%.dll" "%2%", , , p2 Sleep, 10000 ;give the windows TEN SECONDS to load Loop, UserInput { .... If it's still not working, get crazy and put it to 20 seconds. If that does eventually work, do the same for UserInput = 3 and then 4. Later on you can find the 'sweet spot' for each of the sleeps.

Revised (fixed programmer error, actually) and improved WinHide, ahk_class Shell_TrayWnd ;Hide taskbar ; RetroArch locations RA1 := "E:\_arcade\LaunchBoxPortable\Emulators\RetroArch1" RA2 := "E:\_arcade\LaunchBoxPortable\Emulators\RetroArch2" RA3 := "E:\_arcade\LaunchBoxPortable\Emulators\RetroArch3" RA4 := "E:\_arcade\LaunchBoxPortable\Emulators\RetroArch4" ;Ask the user how many single player games InputBox, UserInput, Enter RetroArch Instances (up to 4), Please enter the amount of single player games (<=4):, , 300, 150 If (UserInput == 1) { Run, "%RA1%\retroarch.exe" -f -L "%RA1%\cores\%1%.dll" "%2%", , , p1 } else If (UserInput == 2) { Run, "%RA1%\retroarch.exe" -L "%RA1%\cores\%1%.dll" "%2%", , , p1 Run, "%RA2%\retroarch.exe" -L "%RA2%\cores\%1%.dll" "%2%", , , p2 Sleep, 1000 ;give the windows a sec to load Loop, UserInput { pidInt := p%A_Index% WinSet, Style, -0xC40000, ahk_pid %pidInt% RemoveMenuBar(ahk_pid %pidInt%) } WinMove, ahk_pid %p1%, , 0, 0 ,A_ScreenWidth/2, A_ScreenHeight WinMove, ahk_pid %p2%, , A_ScreenWidth/2, 0 ,A_ScreenWidth/2, A_ScreenHeight } else If (UserInput == 3) { Run, "%RA1%\retroarch.exe" -L "%RA1%\cores\%1%.dll" "%2%", , , p1 Run, "%RA2%\retroarch.exe" -L "%RA2%\cores\%1%.dll" "%2%", , , p2 Run, "%RA3%\retroarch.exe" -L "%RA3%\cores\%1%.dll" "%2%", , , p3 Sleep, 1000 ;give the windows a sec to load Loop, UserInput { pidInt := p%A_Index% WinSet, Style, -0xC40000, ahk_pid %pidInt% RemoveMenuBar(ahk_pid %pidInt%) } WinMove, ahk_pid %p1%, , 0, 0 ,A_ScreenWidth/2, A_ScreenHeight/2 WinMove, ahk_pid %p2%, , A_ScreenWidth/2, 0 ,A_ScreenWidth/2, A_ScreenHeight/2 WinMove, ahk_pid %p3%, , 0, A_ScreenHeight/2 ,A_ScreenWidth/2, A_ScreenHeight/2 } else If (UserInput == 4) { Run, "%RA1%\retroarch.exe" -L "%RA1%\cores\%1%.dll" "%2%", , , p1 Run, "%RA2%\retroarch.exe" -L "%RA2%\cores\%1%.dll" "%2%", , , p2 Run, "%RA3%\retroarch.exe" -L "%RA3%\cores\%1%.dll" "%2%", , , p3 Run, "%RA4%\retroarch.exe" -L "%RA4%\cores\%1%.dll" "%2%", , , p4 Sleep, 1000 ;give the windows a sec to load Loop, UserInput { pidInt := p%A_Index% WinSet, Style, -0xC40000, ahk_pid %pidInt% RemoveMenuBar(ahk_pid %pidInt%) } WinMove, ahk_pid %p1%, , 0, 0 ,A_ScreenWidth/2, A_ScreenHeight/2 WinMove, ahk_pid %p2%, , A_ScreenWidth/2, 0 ,A_ScreenWidth/2, A_ScreenHeight/2 WinMove, ahk_pid %p3%, , 0, A_ScreenHeight/2 ,A_ScreenWidth/2, A_ScreenHeight/2 WinMove, ahk_pid %p4%, , A_ScreenWidth/2, A_ScreenHeight/2 ,A_ScreenWidth/2, A_ScreenHeight/2 } else { MsgBox Invalid Selection WinShow, ahk_class Shell_TrayWnd ;Restore TaskBar ExitApp } Sleep, 1000 ; because you never know last := p%UserInput% Process, WaitClose, %last% WinShow, ahk_class Shell_TrayWnd ;Restore TaskBar ExitApp RemoveMenuBar( hWin ) { ;static associative array for keeping track of all windows that have had their menus hidden static MenuArray := {} ;find active window handle in array / add to array if not found hWin := WinExist("A") hMenu := null hMenu := MenuArray.Remove(hWin) if (hMenu = null) { ;store a reference to the window's menu in the array hMenu := (DllCall("GetMenu", "uint", hWin)) MenuArray[hWin] := hMenu ;hide the menu by uncoupling it from the parent window DllCall("SetMenu", "uint", hWin, "uint", 0) } else { ;show menu by recoupling it to the parent window DllCall("SetMenu", "uint", hWin, "uint", hMenu) } } I forgot some % signs in the previous post that (would have) removed the title bars. (fixed here) WinSet, Style, -0xC00000 and WinSet, Style, -0x40000 are combined into the single: WinSet, Style, -0xC40000 0xC00000 is for the title bar 0x40000 is the the border (0xC40000 is for both of them) Added a function to remove the menubar. With these last 2 bulleted items, you shouldn't need to manually 'toggle' anything. The gaps you see are covered in one of my prior posts. To completely get rid of them, you may need to set those manually for each WinMove, inside each UserInput looped. There is a chance that with the hiding title/menu/border properly working (I hope they are, this time ), the gaps may be eliminated. Not tested, but fingers crossed.

Glad you got it working!!! Oh man! Totally missed adding in the "f:" line. It's kind of funny that yours was actually on the F: drive. lol You might be able to, when BB is open, Alt+Tab to the Command Window and then press Ctrl+Break. You'll have to press "Y" (Yes) to terminate and you may have to then Close the Command Window 'manually'. Then you can Exit BB to Windows. This isn't very elegant and not really much better than using Task Manager (Ctrl+Shift+Esc) to close the Command window. If you want to "fancy it up" a bit, you could add in a Message Box for when the batch file starts, you have the option to Start BB or 'Exit' to Windows. And another one at the end, 'start PbX or exit to Windows'. It might look something like: @echo off powershell "add-type -As System.Windows.Forms; exit([windows.forms.messagebox]::show(\"Do you want to start BigBox?\",'Launch BigBox',4))" if errorlevel 7 ( ::user chose "No" exit ) else ( ::user chose "Yes" start /w "" BigBox.exe ) powershell "add-type -As System.Windows.Forms; exit([windows.forms.messagebox]::show(\"Do you want to start PinballX?\",'Launch PinballX',4))" if errorlevel 7 ( ::user chose "No" exit ) else ( ::user chose "Yes" f: cd "F:\PinballX start "" PinballX.exe exit )

You are very welcome. I don't have PinballX, so no. But it's the same principle. Pretty much anywhere you want. As long as you can remember where that is. (in the example below, we'll put it in your LaunchBox folder) Only if your copy of PinballX is located in the directory "F:\PinballX". Try this: Open Windows Explorer, and go to folder where you have LaunchBox installed. Right click on an empty space in the directory list (like below the last file. Not next to one) and select New and then select Text Document. Type in a name that makes sense to you (i.e. "BigBox2PinballX") and hit enter. You should not have a file named "BigBox2PinballX.txt"). Click on that file and hit enter (or just double click it). This will open up Notepad. Copy the following text and paste it into Notepad. (Note: it's different from the one I showed above. Use this one) cd Core start /w "" BigBox.exe cd "F:\PinballX" start "" PinballX.exe Now you need to know where your PinballX.exe file is located. i.e. in the folder "F:\PinballX". I'm guessing it's somewhere else. So on the 3rd line (above), you need to change the part inside the quotes to the path where yours is actually located. Now close Notepad. It'll ask if you want to save it. Yes You now need to rename the file to a bat[ch]. Right now, it should look like this: If you don't see ".txt" on the end of it, at the top of Windows explorer, click the View tab and check the box File name extensions. Click (once) on the file and press F2 on your keyboard [to edit the filename]. Using the arrow keys, move right 2 times then hit Delete 3 times. This will delete "txt". Now type in "bat" (without the quotes) and hit Enter. You'll get a message box about "Are you sure you want to change it?". Click Yes. It will now look like this: Now, wherever it was that you told PinballX to launch "BigBox.exe", tell it to launch "BigBox2PinballX.bat" (or whatever you called it) instead.

In short, no. What I've done for something similar is to start BigBox from a batch file using the 'wait' parameter which will "pause" the batch file from continuing until BigBox exits. f: cd "F:\LaunchBox\Core" start /w "" BigBox.exe cd F:\PinballX start "" PinballX.exe What this does: Switches to the F drive Changes to the "Core" subfolder under LaunchBox Starts BigBox.exe and 'waits here' until it exits After BigBox has exited, change to some other folder where the 'other program' resides Start that 'other program' Then instead of PinballX starting BigBox directly, have it execute this batch file to start BigBox.