JoeViking245

Does this coincide with my last post? Essentially, if you manually edit the xml file (e.g. to change the comma-decimals to dot-decimals), you need to restart LaunchBox for it to read the [new] values when going into BezelLauncher Setup. What's happening is, when you start LaunchBox, the plugin loads all the settings for the different emulators into memory. So when you go into BezelLauncher Settings, it's reading all the data from memory rather than accessing the file each time. If so that's good news! Can we call it fixed (in v2.2.2-beta-1 and beta-2)?

Looking at the error log, that looks like it occurred when clicking "Test". At that point it's trying to read the old comma-decimals and erroring. The 'fix' was to save changes as a dot-decimal. That said, you'll need to edit your BLSetup.xml settings file and change the <ShaderRect> and <ShaderOpacity> values. You can reset them to: for ShaderRect 0,0,0,0 or replace the comma-decimals with dot-decimals. e.g. 0,0,0.2,0.2 for ShaderOpacity 1 Note: You'll need to restart LaunchBox after editing the xml file.

I thought so too. Can you share your "BLSetup.xml" file. Plan "B" BezelLauncher (v2.2.2-beta-2).7z

Correct. The free version of LaunchBox has all sorts of goodness in it and lets you play your games. It also allows you to preview Big Box with the limitation you can't launch the games. You can get a 1-year license that will unlock features unavailable in the free version (e.g. the Startup/Shutdown Screens, where you can disable the mouse during gameplay) and can get version updates for one year. This will give you time to decide if the unlocked features are 'worth the price'. If you decide at a later date to upgrade to the lifetime license, you can do so at a discounted rate. Or you can get the lifetime license from the get-go. And, of course, you can stick with the free version and still have fun playing games.

One means of doing that is to create a new "emulator" that points to the reader executable. e.g. "D:\LaunchBox\System\Software\LaunchBox Reader\LaunchBox.Reader.exe". The make that "emulator" default for that platform. You can get possible command-line parameters by running at the Windows Command prompt "LaunchBox.Reader.exe --help". e.g. Basic usage: LaunchBox.Reader.exe --path "C:\Docs\Manual.pdf" LaunchBox.Reader.exe open --path "C:\Docs\Manual.pdf" --theme black --fullscreen I suspect that 2nd set of parameters can be rewritten to "--theme black --fullscreen --path". Then when launched with the "game", LB will append the path at the end. Just like you see with regular emulators. EDIT: Found this in the LaunchBox Strategy Guide. Using LaunchBox Reader as a standalone app

When you purchase LaunchBox Premium, it opens up more features available in LaunchBox as well as gives you uninhibited access to Big Box. I guess I didn't know what you were meaning when you asked "That's with Big Box isn't it?".

Full instructions are included in the link.

That's good. It's also a different part of the whole process. So the beta should fix what's needed should you decide to go that route.

Guess maybe you're back to having to read the wiki.

That's Edit Emulator in LaunchBox which should carry over to BB.

If you have them already, adding bezels to Demul is a breeze when using the BezelLauncher plugin. However, it doesn't do the fancy CRT effect or bloom. But is does have a simple shader effect available that could give some CRT resemblance.

Are you wanting borders for a lightgun (though I'm not sure if Hikaru has any lightgun games)? The Sinden Wiki has some info about adding a border. But says you need to use ReShade for borders/bezels. Otherwise, if you just want fullscreen, there's "the checkbox". If you just want bezels (or have a bezel that has a built-in 'border'), you can use the BezelLauncher plugin for that. The wiki also says to use nomousy to hide the cursor. You can use LB's built-in hide mouse feature. This, I have no idea about.

Good thought. I think™ it's been fixed in this beta. FWIW, now using "CultureInfo.InvariantCulture". v2.2.2-beta-1 Fixed: Shader values are now forced saved using the imperial decimal. Fixed: Miscellaneous spelling errors in generated log files Added: pcsx2x6 to list of suggested configurations BezelLauncher (v2.2.2-beta-1).7z

(1) will, for any new ROMs added to the new location, will import those new games (if Automated Imports is enabled [for that platform]). If you don't plan to use the Automated Imports [for this platform], this step is not necessary for moving your ROMs. (2) after having relocated the ROMs, will update the app path to those games. If you don't plan to use the Automated Imports [for this platform], The caveat with (2) is, if the ROMs are in their own subfolders (e.g. E:\Emulators\Atari2600\Games\Adventure\Adventure (1978) (Atari) [!].7z) this will not work. Not sure if it's changed over time, but for my parameters I have: -baseinappdir -fullscreen 1 The 1st one runs it in portable mode (otherwise datum is saved to \AppData\Roaming\Stella\), but is not required. The 2nd sets fullscreen=true. Using -fullscreen 0 will set it to 'false' and not go fullscreen. If you set fullscreen via the UI, this is not needed. Note: When opening the emulator, either by double-clicking the exe or right-click a game in LB and selecting "Open Stella", ANY AND ALL changes made will be saved to its AppData folder. So, if you subsequently run a game with the -baseinappdir parameter, the "ANY AND ALL" changes will not be reflected. IF you've made all sorts of cool changes via Stella's UI and you want to make it portable, you can simply copy (or move) all the subfolders and files under \AppData\Roaming\Stella\ into your emulators actual folder. Then make sure you launch the game(s) with the -baseinappdir parameter. If later you want to access the UI to make changes, what I've done is created a batch file ("run portable.bat") next to Stella.exe containing stella -baseinappdir, and run it [instead of the exe]. Just remember to not open the emulator directly from LB to make any changes.

Is it working (bezels get downloaded and show) for other platforms? If you're on version 13.27, there was a bug with the download procedure. And if so, you can roll back to v13.26 [where it last worked], hop onto the 13.28 beta release (where it's been fixed), or wait until the official v13.28 is released (I'm not sure of the ETA for that release).

Well dang it. With that, I'm out of ideas. Hopefully someone who has this game and knows a fix/work-around will chime in.

Using "select start on my controller to exit emulators" essentially the same as pressing Alt+F4. The Exit Game (LB) and Close the Active Window (BB) will "press" Escape. If the emulator stays active, it will then "press" Alt+F4. At least that's my understanding. You can test it by making a backup of your save(s), then play the game a little and press your button-combo to close it. If it does work to close it, then restart the game and see if all's still good.

What version of LaunchBox are you running? One thing you can try is to disable automated imports (2 locations). Tools < Options < General < Automated Imports Tools < Manage < Storefronts...

I have yet to look into this. It's sitting somewhere on my to-do stack.

@AZUR3US @Rlad Been doing some testing and indeed, when BezelLauncher is enabled, it is not incrementing play time. But... it is incrementing the play count. However, if you go back to LB version 13.22 (an arbitrary version I had installed) it will track time. But only 2 seconds for each game startup. Play 20 minutes, it tracks 2 seconds. So, yeah... confirmed it never worked. 😊 I looked at (refreshed myself what exactly I did way-back-when) my code for this plugin and I can't see rhyme nor reason why this is affecting LB from tracking playtime with the plugin enabled. The only thing I can think of is it's an emulator window focus or an emulator top z-order thing. Where the bezel window may take focus for a second, but then gives it back to the emulator window. All while forcing itself (the bezel) to the top z-order. Another thing is you can play for "that 20 minutes" with BezelLauncher enabled and when you exit, LB's shutdown screen will show. Which itself is a good thing. But to me is perplexing because the shutdown screen knows when the game exits, but the time tracker isn't following suit. Long story short... it ain't gettin' fixed anytime soon.

It's weird that it's just locking up LB/BB (vs. the whole PC). I missed this earlier. Are you saying the when you launch the game from LB, and you press Alt+F4, there are no issues with it closing and LB regaining focus? Or was that an actual question? I don't own the game, so can't test. If pressing Alt+F4 does exit the and returns focus back to LB, what happens if you press your controller mapped button(-combo) to Exit Game (LB) or Close the Active Window (BB)?

When you Ctrl+Alt+Del, are you restarting the whole PC at that point? Or selecting Task Manager and just force closing (End Task) LB?

Did you try disabling Startup Screens? (not sure if it'll change anything, but worth testing) Edit game. (left panel) scroll to the bottom Startup/Pause. Check Override Default Startup Screen Settings. Click OK to save and close.

Ah Ok. Sounds like it may be the game then. Is it a stand-alone exe? Or are you running it through Steam? Is it only in Big Box this happens? Or does it cause issues when ran through LaunchBox as well? If you have startup screens enabled for it, can try turning them off [for process-of-elimination testing]. To clarify, when you say "exit through the game", you're exiting through the games' Menu? Vs. exiting using Big Box's controller mapped Close the Active Window.