JoeViking245

Ya! It's already been about 2 full business days since release! Besides, developers don't get weekends off! So that's like almost 4 whole days. Maybe 5 depending on your time zone.

Glad it worked. "Paid"? What's that? Well, I suppose I get 'paid' in flattering comments like that and people saying thanks. But that's all. Now go play some games and enjoy.

Hmmm. Worked here. Did you make the 2 changes with BB closed, saved them, then opened BB? Either way, it didn't look very good on my end. Namely, the video was offset to the left. And the rating image being cut off. Like @Maddoc1007 said, CZ-v2 doesn't [appear to] have a Wall4GamesView.xaml view file. I believe what's supposed to happen in that case is it will load "the view" from the Default theme [as a backup]. As you can see, these 2 "different" views look.. well different. So no idea where CZ2 is getting it from. If you want to use CZ2 and are ok with the Default's Wall-4 view, what you can do is: Set your theme to CriticalZoneV2 - Default Map a key (or controller button) to Switch Theme Go into Game View (aka select a platform) Press the key/button you mapped Select Default Assuming it was set to the Wall-4 view, you'll now see the Default Wall-4. The caveat is you need to do this for each platform. I couldn't see a way to do it automagically for all platforms. But admittedly I didn't look too hard. And also, I'm not a theme guy.

You can find available parameters here: LaunchBox Built-in Command Line Variables - LaunchBox The one you want to use is -rompath %romlocation% -rompath %romlocation% apple2e -gameio joy -flop1 Placement of the variable is key. (and you can leave the 2 checkboxes checked) e.g. If you want to do it similar to what you proposed, I suppose you could use: apple2e -gameio joy -flop1 "%romlocation_noquotes%\%romfilename%%romextension%" %noromfile%

@masterfulmethods Try; Edit ..\LaunchBox\Themes\CriticalZoneV2 - Default\ThemeSettings.xml Change the first 2 elements' values <ForceGamesDisableBackgroundVideos>false</ForceGamesDisableBackgroundVideos> <ForceGamesEnableBackgroundVideos>true</ForceGamesEnableBackgroundVideos> Start Big Box

In your Windows display settings, do you have the scale set to something different than 100% (or "recommended")?

The error indicates something is up with your license file. Only support@unbrokensoftware.com can help you with this. Give a little time for them to reply. May also check your spam folder in case it got placed into there.

A quick search shows there's several different builds of Snex9x-rr. I suggest go to the one you downloaded it from and look for a list of command line parameters to load a lua script.

There doesn't appear to a command line parameter to load a lua script. Supposedly there's a "rerecording" version of Snes9x in which does have a command-line parameter to load a lua script.

Try... Change your selected LaunchBox Theme to a different theme. Let LaunchBox restart to apply that theme. Change the selected theme back to Default. Let LaunchBox restart to apply that theme.

Does this folder exist? ..\LaunchBox\System\Software\LaunchBox Reader\ And does it contain all 236 files? If not, go to Tools < Manage < Plugins... Select LaunchBox Reader Click Install (or update or whatever it may say to add it)

When you edit the emulator, in the Startup Screens section there's some new checkbox options. Try playing around with those a little. (not at my main PC right, so don't have the specifics in front of me right now)

Any chance you have LaunchBox v14.0? Changes were made that "should" fix this.

Thanks! 😊 That's what we like to hear. You're welcome. Always glad to help and glad to hear it's all working. Now go play some games!

Here's some more reading for you. Media Packs - LaunchBox Here's an option: ..\LaunchBox\Images\Media Packs\Overrides\Platform Clear Logos\Platform Categories\ ..\LaunchBox\Images\Media Packs\Overrides\Platform Clear Logos\Platforms\

Simplicity is good.

Those 2 images are "Banner" and "Clear Logo". For these, it'd be a lot easier to edit the category and add those images there. Click the yellow +, select the image then set the type. LaunchBox will do the rest of the work, saving them in the correct location.

Looks like for everybody and anybody.

Yeah, all I can say is it's still being looked into. I may end up doing something cheesy like keep track of playtime myself, then on game exit, tack it onto the game's playtime. But I ain't willing to resort to something like that just yet. Thanks for testing.

I don't know "the" answer. But might try checking/un-checking these 3 options and see if any combination there-of fixes it. Myself, I'd stick with DuckStation. But that's a personal opinion.

I thought you were using the same "_Emulators\MAME 0.289\mame.exe" for both instances in LB which would have read the same mame.ini file. Which in turn directs MAME to where [all] the ROMs are located. My guess is in the Details section, the Default Command-lime Parameters contain -rompath %romlocation%. That said, you could un-edit the mame.ini and then add this to the aes parameters and it will work. e.g. -rompath %romlocation% aes %romfile% -bios usa This [added] parameter is telling MAME that the ROM files (-rompath) for the game being launched are in the same location as the ROM (%romlocation%). Regardless, it's working now. It doesn't say anything about "missing files". It mentioned "incorrect" files. Semantics matter when trying to troubleshoot. It might be with your -bios usa parameter. I've only ever seen it be -bios and then a number. e.g. -bios 16 I'm not saying "usa" is invalid. I just don't know if it is valid. In the spirit of troubleshooting: Try removing that part and see if that message still appears. If not, then try my example. If that doesn't resolve it (the message still appears), this usually means that you have a mismatched set. Like maybe mame.exe is version 0.289 and your ROMs are version 0.288.

I don't have any magazines in my collection, but this should help some: https://unbrokensoftware.github.io/launchbox-reader-releases/getting-started.html