BezelLauncher

[JoeViking245]

42 minutes ago, AZUR3US said:

edit: If I edit the config manually and replace "," with "." in the decimal values, it works as well. This also worked with the previous release.

• 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)?

 

[AZUR3US]

I wouldn't say it's completely fixed yet, but we're very close to the ideal solution. If it can't be improved any further, though, then I'd say it's fine. 🙂

LaunchBox doesn't need to be restarted. It's enough to click "Save" in the main menu, and after that "Test" works as expected. You just need to know that the settings have to be saved first. 😅

[JoeViking245]

45 minutes ago, AZUR3US said:

I wouldn't say it's completely fixed yet, but we're very close to the ideal solution. If it can't be improved any further, though, then I'd say it's fine.

I think you're the only one I've heard of that actually uses the shader feature.  Stateside, or otherwise.   So for anyone who's going to start using it [and downloads one of the recent betas or waits until I update the official release), they're good to go. 

 

54 minutes ago, AZUR3US said:

LaunchBox doesn't need to be restarted. It's enough to click "Save" in the main menu

Good point. I forgot that clicking Save in the main Settings window reloads all the settings into memory.

 

56 minutes ago, AZUR3US said:

You just need to know that the settings have to be saved first. 😅

We call that a 'hidden feature'.  

 

Thanks for all your testing and patience!!

[Joe35car]

Just came across this and was wondering why some systems don't show. For example N64. I really and to slowly rid of RL for bezel support. How would I add N64 to the list?

 

NM it is in the list now.

Edited August 14 by Joe35car

[Joe35car]

OK still a little confused. I see I have to not have it fullscreen to show bezels. I'm trying to use the ARES emulator for N64. The game view is not centered and I am unable to test it using the plugin because I suppose there is no ini? 

[Joe35car]

https://imgur.com/a/k6b3KuA

[JoeViking245]

14 minutes ago, Joe35car said:

OK still a little confused. I see I have to not have it fullscreen to show bezels. I'm trying to use the ARES emulator for N64. The game view is not centered and I am unable to test it using the plugin because I suppose there is no ini? 

I spent some time trying to be thorough with the instructions on the download description.  Please read through it all. 

It also looks like you may not have a "Nintendo 64" bezel folder (maybe you do) and you don't have a "Nintendo 64.png" bezel file.

[Joe35car]

[Joe35car]

This is what's in my Nintendo 64 folder. I just want to adjust the screen bezel so it fit properly.g

Edited August 14 by Joe35car

[JoeViking245]

16 minutes ago, Joe35car said:

This is what's in my Nintendo 64 folder. I just want to adjust the screen bezel so it fit properly.g

Copy one of your bezel.ini files and one of you bezel.png files and place them directly inside your /Bezels/Nintendo 64/ folder. Rename the files to "Nintendo 64" (with their appropriate file extension).  Then when you run setup, the file names and a preview image will appear [for that platform].

[AZUR3US]

@JoeViking245
I took a look at LaunchBox 14.0 because I saw a video where the new features were presented
https://youtu.be/b_L0atdHp-0?si=6WCdmGD53btjrzvo&t=527

Apparently, game time tracking should now also work when the emulator is no longer in focus.
So I tested it with BezelLauncher to see if game time tracking works with BezelLauncher, but unfortunately, it doesn't.
There still seems to be something wrong somewhere.

[JoeViking245]

25 minutes ago, AZUR3US said:

Apparently, game time tracking should now also work when the emulator is no longer in focus.
So I tested it with BezelLauncher to see if game time tracking works with BezelLauncher, but unfortunately, it doesn't.
There still seems to be something wrong somewhere.

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.

[andyco47]

hi a cant seem to get this to work with Spectaculator any ideas thanks

[Strangeguy]

I recently started using BezelLauncher for those emulators that don't natively support them. I've gotten good results so far, but I was wondering if it's possible, after setting an emulator-wide bezel, to also have a blacklist/whitelist of games that disable it. Some 6th-generation console games have native 16:9 modes, and so I'd like to disable any bezels meant for 4:3 viewports if I'm playing a game with that turned on.

I suppose a hacky way to do it would be to set an 100% transparent bezel as a game-specific bezel for those games, but it'd be nice to avoid the added overhead/potential for unwanted interactions of running BezelLauncher at all if I don't have to. Let me know if there's a way to do this.

[JoeViking245]

12 minutes ago, Strangeguy said:

I suppose a hacky way to do it would be to set an 100% transparent bezel as a game-specific bezel for those games, but it'd be nice to avoid the added overhead/potential for unwanted interactions of running BezelLauncher at all if I don't have to. Let me know if there's a way to do this.

You're on the right track.  That is, there isn't a way to 'blacklist' by game.

Option 1:
Create a transparent bezel for each of your 16:9 games.

Option 2:
Create a bezel for each of your 4:3 games and a transparent one used as a 'fallback' (platform_name.png and platform_name.ini)) in which the 16:9 will use (because they won't have a game specific bezel).

Option 3:
Create a 2nd emulator and assign your 16:9 games to use it and don't enable it in the BezelLauncher settings.  This "2nd emulator" will be the exact same as the '1st one' but just have a different name.  e.g. "PCSX2" for your 4:3 games and "PCSX2-16-9" for the 16:9 games. 

Option 4:
????

[Strangeguy]

On 8/20/2026 at 5:36 PM, JoeViking245 said:

You're on the right track.  That is, there isn't a way to 'blacklist' by game.

Option 1:
Create a transparent bezel for each of your 16:9 games.

Option 2:
Create a bezel for each of your 4:3 games and a transparent one used as a 'fallback' (platform_name.png and platform_name.ini)) in which the 16:9 will use (because they won't have a game specific bezel).

Option 3:
Create a 2nd emulator and assign your 16:9 games to use it and don't enable it in the BezelLauncher settings.  This "2nd emulator" will be the exact same as the '1st one' but just have a different name.  e.g. "PCSX2" for your 4:3 games and "PCSX2-16-9" for the 16:9 games. 

Option 4:
????

Ah; good thinking about setting up a secondary emulator configuration for 16:9. That seems like the most streamlined way to do it, since I only have a handful of 16:9 games and can just set the command-line parameters separately.

Might still be nice to have the ability to set a simple blacklist within BezelLauncher itself, but then I suppose you'd have to go and individually restore fullscreen parameters for those games anyway. Still, thanks for your support.

[JoeViking245]

@TekkamanBlade

Quote

Hi. I’m experiencing a sizing/focus problem with BezelLauncher 2.2.1 and Sega Model 2 Emulator.

Configuration:

• LaunchBox 14.0.1 at `D:\Launchbox`
• Emulator: `emulator_multicpu.exe`
• 3840×2160 display
• Model 2 `AutoFull=0`
• LaunchBox Startup and Pause Screens disabled
• BezelLauncher parameter: Hide Stuff (`h`) only
• BezelLauncher shaders disabled
• Bezel PNGs are 1920×1080 and displayed in a 3840×2160 bezel window

Saved emulator placement:

• Upper-left: `550,57`
• Lower-right: `3294,2095`
• Size: `2744×2038`

The game and bezel initially open correctly. Shortly afterward, the emulator goes behind the overlay and the visible bezel appears to shrink slightly, exposing parts of the underlying window around the TV’s edges/corners. The Model 2 taskbar icon also flashes orange and repeatedly takes focus. Even the window switcher immediately disappears when trying to switch applications.

This happens without clicking outside the emulator or intentionally pausing.

Without BezelLauncher, Model 2 runs normally in a smaller window with no focus problem. The issue also happens in Big Box.

The log reports that BezelLauncher successfully finds the emulator, displays the bezel, removes the borders/menu, and resizes the emulator. Around 11–13 seconds later, it repeatedly logs:

`Set Emulator as foreground window after Pause`

This continues even with LaunchBox’s Pause Screen disabled.

Live inspection showed:

• `Bezel245`: 3840×2160 at `0,0`
• Model 2: 2744×2038 at `550,57`

I also tested disabling Startup Screen, Pause Screen, Hide Game Startup, and shaders; used a clean Model 2 installation; and tested LaunchBox 13.27. The behavior remained.

Could BezelLauncher be mistakenly detecting a pause/resume or focus event from Model 2? Is there a way to stop this focus loop while keeping BezelLauncher?

To clarify:

• The bezel starts out filling the window (3840×2160)
• It then resizes to a slightly smaller size (e.g. 3825x2145) so it's no longer filling window
  • Even though your 'live inspection' is [still] showing it as being 3840x2160

Is that correct? 
Is your "live inspection" using something like WindowSpy.ahk? (Doesn't really matter. Moreso curious what others use. )

When the bezel (overlay) resizes is when you're seeing part of (all of?) the taskbar? 
And it's here you're seeing the app on the taskbar flash orange?
Or are you seeing that happen on a 2nd monitor?

I don't know what the "window Switcher" is. Are you trying to switch apps (like alt+tab) while the game is running?

 

When all this is going on, are you still able to actually play the game? e.g. insert coin(s), start then shoot or drive or whatever [based on the game].

 

Do you see the resizing of the bezel happen with other platforms/emulators?  (Supermodel, PCSX2, DEmul, Flycast, Dolphin) Or just the Model 2 emulator?

I tested here and it all worked fine. But my monitor is only 1920x1080.

[TekkamanBlade]

Quick update: the issue appears to have resolved itself. After troubleshooting for most of yesterday, I shut the PC down and left it off for a while. Today BezelLauncher and Model 2 are working correctly with the same configuration.

I didn’t make any additional changes before it started working, so the shutdown/restart may have cleared whatever focus or timing problem was occurring. I’ll continue testing and report back if it returns.

Thank you for taking the time to investigate and reply.