Jump to content
LaunchBox Community Forums

BezelLauncher 2.1.2

   (9 reviews)
JoeViking245
 Share

2 Screenshots

About This File

What is it?
Use this plugin to display bezels for emulators that don't natively support them.

What does it do?
It displays a bezel and resizes the emulator window to fit within the bezels transparent area.

What's required to make this plugin work?
LaunchBox v13.3 (or newer), the plugin file, bezel images and some minor setup.  No more. No less. (See Setting up)

Do I need to provide my own bezel images?
Yes. (See Setting up for where to place them)

Will it work with game specific bezels?
Yes.

Will this work with all emulators?
Yes, with exception. RetroArch and MAME emulators will not show in the list of emulators and cannot be used with this plugin. 

The emulators that have been tested so far all work. Some adjustments may be necessary. (see Emulator Settings)

Will this work with storefront games or Windows games?
No.

Can I use my existing RocketLauncher bezel configuration files?You can use the existing platform.png and platform.ini files from RL.  These existing files should be located under:
   /RocketLauncher/Media/Bezels/platform_name/_default/something.ini (and something.png) 
(See Setting up [step #3])

What are the .ini files for?
The .ini (configuration) files tell the plugin how to resize and move the emulator window to fit within the bezel.  (See .ini (configuration) Files for more info and Testing for creating and saving them)

Can this plugin add shaders as well?
No.  Yes. See Using Shaders  (new v2.1.0)

 

Disclaimer

This works on my test PC.  I didn’t test it on my cab because I didn’t want to change my emulator settings to not use fullscreen (see Emulator Settings).  Outside of RetroArch and MAME, I don’t use bezels, so didn’t want to mess-up-a-good-thing.

There are no guarantees, express or implied… blah blah blah blah blah blah blah.

There is no risk. This plugin makes no changes to LaunchBox or your emulators.  If you decide this isn’t for you, simply undo any fullscreen changes you made and (with LB/BB not running) delete the BezelLauncher folder.

 

Special Thanks
Special thanks to @MadK9 for the idea, direction and help with testing!  Without him, I would have never contemplated starting this project. :D  Also a big thanks to @Sbaby for testing un-tested emulators with the plugin.

 

Installing

With LaunchBox/BigBox not running...

  1. Download the plugin .zip file
  2. "Unblock" the file
    1. Right-click the file, select Properties, check the box "Unblock", click OK.
    2. Or better yet, just use 7-zip to open the file
  3. Copy the contents (a folder called "BezelLauncher") into your \LaunchBox\Plugins\ folder
  4. Start LaunchBox

 

Setting up

  1. Start BezelLauncher Setup from the LaunchBox Tools menu, then click Close
    • This will create the \Plugins\BezelLauncher\Bezels\platform_name\ subfolders
  2. Copy your bezel images into their respective platform_name subfolders
    • See Bezel Images for more information
  3. (optional) If you have existing RL platform_name.ini files, copy those alongside the image files
    • See .ini (configuration) Files for more information
  4. Restart BezelLauncher Setup
  5. Select a platform
  6. Choose an emulator you wish to use for that platform.
  7. Check Disabled to enable it
    1. Click Test
    2. Adjust (Move/resize) the orange frame to fit within the view area of the bezel (See Testing)
    3. Click Shaders to enable, adjust and change shader (see Using Shaders)  (new v2.1.0)
    4. Click Save [to save the .ini file]
    5. Click Save on the main setup screen to add the emulator to the list of Enabled platform emulators
  8. Repeat for other platforms and emulators you wish to add
  9. You must click "Save" for each emulator you've enabled, separately.

image.thumb.png.c97c031560f6d11d832627f112c7d1b2.png

 

Maintenance
After adding/removing platforms or emulators

  1. Run BezelLauncher Setup
  2. Click Refresh
  3. Continue with Setting up, step #5

 

Testing
To configure the placement of the emulator window within the bezel (Requires an existing bezel image):

  1. Run BezelLauncher Setup
  2. Select a platform and an emulator
  3. Enable it (if it's not already)
  4. Click Test

image.thumb.png.ceb55f1ed0005e34f820e0d6caf0e08f.png

Move and resize the frame

  • Click [and hold] the left or right side of the frame to move it around
  • Click [and hold] the bottom right corner to resize image.png.c72de1ad9780af93759750bd7818c070.png
  • Use the on-screen buttons to fine-tune the adjustments

The on-screen display will show information about the emulator window.
(You can click and drag the OSD to move it around as needed)

  • x, y = upper left monitor-coordinates of the emulator window
  • w, h = width and height of the emulator window
  • x, y = lower right monitor-coordinates of the emulator window

image.thumb.png.df3e2713204f043555ce2afd9ba6f25a.png

  • If any of the values are red, they are off the screen
  • The OUTSIDE edge of the frame is the emulator window extents

After adjusting, click Save.  This will overwrite any existing configuration file.
 

Using Shaders  (new v2.1.0)

  • First you need some shaders.  Place the .png images in the /Bezels/Shaders/ folder
  •     (Scanline.png 'shader' is included)
  • Start BezelLauncher Setup
  • Select your platform and emulator and click Test
  • Click Shaders
  • Check the box to turn shader on
  • Use the slider to adjust the shader
  • Adjust the opacity down to lighten the shader
  • Use the drop-down box to select a different shader
  • Click Save to save your settings

 

Parameters
Depending on the emulator and the bezel, you may need to check 1 or more of the following parameters:

(h) hideStuff

Check this if you see the desktop behind bezel while the game is loading.  This adds a black background during the startup process.

(s) startupSleeper

“Hide stuff” for a little longer during startup (3 seconds)

(l) longerSleep

Same as above (4 seconds)

(g) hideGameStartup

Check this if LB Game Startup screen is showing behind the bezel at game startup

When selecting a platform, if the plugin detects an emulator that has been tested, “suggested” parameters will be shown.  Your mileage may vary.

 

Emulator Settings

For the plugin to move/resize the emulators’ window, you will need to disable fullscreen in the emulator(s).  This may be as easy as removing "-f" or "-fullscreen" from the Default Command-line Parameters (depending on the emulator).

Beyond that, of the emulators I've tested, the only one that needs to have its Default Command-line Parameters altered is SuperModel.  You will need to manually set the resolution.

  1. Start BezelLauncher Setup
  2. Select your Super Model 3 platform and Enable it
  3. Click Test and after adjusting the frame to where you want it, make note of the W(idth) and H(eight) #'s shown in the OSD.
  4. Save and Close.  (Be sure to click Save on the main Setup screen to save Enabled as well.)
  5. Edit your SuperModel emulator (in LaunchBox) and set the Default Command-line Parameters to "-res=W,H"  (no quotes, no spaces and replacing W & H with the #'s noted above)
    1. Example:       -res=1420,1076

 

Bezel Images

When you run BezelLauncher Setup for the 1st time, the plugin creates subfolders for each of your eligible platforms. They are created in:
                \LaunchBox\Plugins\BezelLauncher\Bezels\[platform_name]\

The platform image file needs to be in the [platform_name] folder and must be named the exact same as the platform.
                \BezelLauncher\Bezels\Sony PSP\Sony PSP.png

 

Game-specific bezel files

Game-specific bezel folders (or files) can be named after the games ROM filename or the games Title.

Using the games Title:
If the Title has 'invalid file name characters', those characters will need to be replaced with _ (underscore).  The exact same way LaunchBox does with its image files (but without the -01 suffix).
      Example:  Title = Disney-Pixar's Toy Story 2: Buzz Lightyear to the Rescue!
                      Bezel = Disney-Pixar_s Toy Story 2_ Buzz Lightyear to the Rescue!.png

NOTE: Additional Apps game Titles are (i.e.) "Play USA Version...".  So the bezel would be "Play USA Version....png".  Same rules apply with 'invalid file name characters'.

Invalid characters are:   

<  (less than)
>  (greater than)
:  (colon)
"  (double quote)
/  (forward slash)
\  (backslash)
|  (vertical bar or pipe)
?  (question mark)
*  (asterisk)
'  (single quote) Not technically invalid (post-DOS), but consistent with LaunchBox character replacement


 

Storing game-specific bezels:

 Option 1:

  • Place your game bezel images directly inside their respective \[platform_name]\ folder.

Game-specific image files must be named the exact same as the games ROM file or the games Title (accounting for invalid characters).

example:

  • \BezelLauncher\Bezels\Sony PSP\After Burner - Black Falcon (USA) (En,Fr,Es,It,Nl) (PSP) (PSN).png

 

Option 2:

  • Place your game-specific bezel image folders under the \[platform_name]\ folder.
  • The subfolder must be named the exact same as the games ROM file or Title (barring invalid characters).
  • The .png and .ini files in the subfolder can be any filename.

 example:    

  • \BezelLauncher\Bezels\Sony PSP\After Burner - Black Falcon (USA) (En,Fr,Es,It,Nl) (PSP) (PSN)\thisIsAnyFileName.png

 See Launching different game versions for information about bezel requirements for games that are combined as Additional Apps.

 

ScummVM

Setting up ScummVM for use with this plugin:
In LaunchBox, Edit games using ScummVM.  In the ScummVM section, have both checkboxes un-checked.  (Fullscreen and Aspect Correction).  This cannot be done using the Bulk Edit Wizard, so will need to be done on a per-game basis. One-at-a-time.

If it's not displaying correctly with just the above, try the (optional) following:

  • Navigate to /LaunchBox/Third Party/SummVM/ and start ScummVM.exe.
  • On the Graphics tab, set Graphics Mode to opengl.  Leave the other 2 as default and the check box's un-checked.  Click OK and Exit.

ScummVM Bezel Files:
To use bezels with games using LB's integrated ScummVM, you will need to set them up manually.  It will not appear in BezelLauncher Setup.

  1. Navigate to the plugins Bezels subfolder and add your platform folder.
    • i.e.    \LaunchBox\Plugins\BezelLauncher\Bezels\ScummVM\
  2. Add your platform default png and ini files to this folder.
    • i.e.    ScummVM.png   ScummVM.ini

Game specific bezels for ScummVM must be named the same as the Game Data Folder.
    i.e.    D:\LaunchBox\Games\ScummVM\King's Quest 1 - Quest for the Crown\[game files]
             use:     "King's Quest 1 - Quest for the Crown.png"
 

DOSBox
The integrated version of DOSBox is NOT supported by this plugin.  I couldn’t get it to cooperate 100% of the time.  So going with plan “B”.

To use DOSBox with this plugin, you will need to install and set up DOSBox-X.

Setting up DOSBox for use with this plugin:
Note: BezelLauncher Setup will NOT show your DOSBox platform ('MS-DOS') as an available platform.  So don't bother looking for it.

Download DOSBox-X
DOSBox-X releases can be found here:  https://github.com/joncampbell123/dosbox-x/releases

  1. Download the vsbuild-win64 version. (direct link for the download file)
  2. Create a new folder under \LaunchBox\ThirdParty\ and name it DOSBox-X
  3. Extract the contents of the downloads "\bin\x64\Release\" folder into the new folder
    • Be sure to unblock the zip file before extracting (unless you’re using 7-Zip)

Configuring DOSBox-X

  1. In Windows Explorer, navigate to \LaunchBox\ThirdParty\DOSBox-X\.  
  2. Make a copy of dosbox-x.conf.  
  3. Rename the copy to [something like] "BL-dosbox-x.conf"
  4. Right-click the new 'BL-dosbox-x.conf' file and select edit (Notepad++ works great for this. But any text editor (Notepad) will work)
  5. Look for the following keys and change their Values as shown:

(starting on approximately line 78)
fullresolution          = 1400x1080
windowresolution  = 1400x1080
windowposition      = 260,0
output                      = ttf
showmenu              = false

"1400x1080" (2 locations) is the dimension of the transparent area of your bezel.  Adjust as necessary.
    From your MS-DOS.ini file, use [Right X]-[Left X] for the 1st value (1400) and [Right Y]-[Left Y] for the 2nd (1080)

"260,0" is the upper-left coordinate of the transparent area.  Use the Left-X value for the 1st number and Left-Y for the 2nd.

Save the changes and close the editor.


Configure games to use DOSBox-X
The following assumes your MS-DOS platform games are already setup to use the integrated version of DOSBox.

  1. In LaunchBox, select all your DOSBox games and press Ctrl+E to start the Bulk Edit Wizard.
    • (Select 1 game in the MS-DOS platform, then press Ctrl+A to select all)
  2. On the 2nd screen
    1. select the Field Custom DOSBox Version EXE Path
    2. for Value, Browse to and select dosbox-x.exe
  3. Click Next, Next
  4. Click “Yes, I would like to make more changes”
  5. select the Field DOSBox Configuration File 
    1. for Value, Browse to and select the new file you created (BL-dosbox-x.conf)
    2. Click Next. Next (again). 
    3. Click "No, I would not like to make more changes"

 

MS-DOS Bezel Files:
This assumes your DOSBox platform is called "MS-DOS".

  • In the Bezels subfolder under the plugin folder, create a new folder called 'MS-DOS'.  
  • In \LaunchBox\Plugins\BezelLauncher\Bezels\MS-DOS\, add your bezel files (MS-DOS.png and MS-DOS.ini).

Game specific bezels for DOSBox need to be named the same as the Game Data Folder
    i.e.    D:\LaunchBox\Games\MS-DOS\Cosmos Cosmic Adventure\COSMO1.EXE
            use     "Cosmos Cosmic Adventure.png"    
 

 

.ini (configuration) Files

The .ini files contain the monitors' coordinates for placing the emulator window.
The Upper Left x,y coordinate and the Lower Right x,y coordinate

Example:
Upper Left X Coordinate=240
Upper Left Y Coordinate=100
Lower Right X Coordinate=1680
Lower Right Y Coordinate=1080

The platform ini file must be named the exact same as the platform.  If copied from RocketLauncher, you may need to rename it (removing any under_scores).

i.e.   \BezelLauncher\Bezels\Sony PSP\Sony PSP.ini  

For game-specific ini files, if they are located in a subfolder below /[platform_name]/ (see Bezel Images, Option 2, above), they can have any filename.  If they are inside the /[platform_name]/ folder (Option 1), then they must be named the exact same as the games ROM file or Title.

If a game-specific .ini file doesn’t exist, the plugin will use the games platform.ini file.

 

 

Launching different game versions

Also known as Additional Apps, when right-clicking a game and selecting Play Version, the Additional App is not required to have its own bezel files.  If the Additional App doesn't have its own bezel, the plugin will look for the Default Games' bezel.  If neither of those exist, it will use the platforms’ bezel.

This eliminates the need to have a separate set of bezel files for each version of the game. Useful since they most likely all use the same image.  This only works for games that are Additional Apps.

 

 

Plugin Folder Structure

Spoiler

Main plugin files

 D:\LaunchBox\Plugins\BezelLauncher\
            BezelLauncher.dll
            BLSetup.xml

 

(default) Platform Bezel

D:\LaunchBox\Plugins\BezelLauncher\Bezels\platform_name\
            platform_name.ini
            platform_name.png
 

Game-specific Bezels

Option 1:

D:\LaunchBox\Plugins\BezelLauncher\Bezels\platform_name\
            game-1-ROM_name.png / game-1-ROM_name.ini
            game-2-ROM_name.png / game-2-ROM_name.ini
            game-3-ROM_name.png / game-3-ROM_name.ini
 

Option 2:

D:\LaunchBox\Plugins\BezelLauncher\Bezels\platform_name\ game-1-ROM_name_name\
            anyNameYouWant.png  /  anyOtherOrSameNameYouWant.ini
D:\LaunchBox\Plugins\BezelLauncher\Bezels\platform_name\ game-2-ROM_name_name\
            anyNameYouWant.png  /  anyOtherOrSameNameYouWant.ini
D:\LaunchBox\Plugins\BezelLauncher\Bezels\platform_name\ game-3-ROM_name_name\
            anyNameYouWant.png  /  anyOtherOrSameNameYouWant.ini

 

Log files

D:\LaunchBox\Plugins\BezelLauncher\Logs\
            log [date/time].txt        (Up to 5 files max)
            SetupLog [date/time].txt    (Up to 5 files max)

 

As always, any thoughts, views, opinions, [constructive] criticism, comments and suggestions are welcome.

What's New in Version 2.1.2   See changelog

Released

v2.1.2
Fixed:    DOSBox and ScummVM bezels not showing (introduced in v2.1.0)

 

v2.1.0
New Feature:     Added Shader capabilities
Improvement:    Bezel loads faster when launching a game
Improvement:    Recalibrated sizing buttons on Test screen. Can now click-and-hold for faster adjustments
Improvement:    Now works with when display scales are set above 100%
Fixed:                   Bezel Window Width & Height not properly fitting the screen during Test

  • Like 14
  • Thanks 2
  • Haha 1
  • Unusual Gem 5
 Share
Previous File Rename Media Images/Videos as Rom Name or Game Name Format
Next File How Long to Beat Custom Fields Tool

User Feedback

Recommended Comments



SatorSquare

Gosh you're quick. Good call on unchecking 'Hide Game Startup'. Everything works perfectly now. Thank you!

  • Game On 1
Link to comment
Share on other sites
Solly4Life

Each time I update to the new version my shader is disabled and I have to re-enable each one. The bezel settings remain untouched. Is this normal?

Link to comment
Share on other sites
JoeViking245
2 hours ago, Solly4Life said:

Each time I update to the new version my shader is disabled and I have to re-enable each one. The bezel settings remain untouched. Is this normal?

It is (was) normal during the beta testing phase when shaders were being added and then when updating to the official release 2.1.0 (and, well, the fix of v2.1.1).  

Now that they're 'officially' incorporated, subsequent updates shouldn't reset them.

Link to comment
Share on other sites
JoeViking245
4 hours ago, Solly4Life said:

I get the attached crash error when I click save trying to add the shader using the Hatari emulator. 

Can you share the SetupLog....txt file for when the error occurred. Please.  (located in /Plugins/BezelLauncher/Logs/).  

Does this happen when enabling the shader on other platforms as well?  Or just Hatari?

Were you selecting the included "Scanline.png" shader? Or one of your own?

If you exit then restart LaunchBox and run BezelLauncher Setup again choosing Hatari, does the error still occur?

 

Link to comment
Share on other sites
Solly4Life
1 minute ago, JoeViking245 said:

Can you share the SetupLog....txt file for when the error occurred. Please.  (located in /Plugins/BezelLauncher/Logs/).  

Does this happen when enabling the shader on other platforms as well?  Or just Hatari?

Were you selecting the included "Scanline.png" shader? Or one of your own?

If you exit then restart LaunchBox and run BezelLauncher Setup again choosing Hatari, does the error still occur?

 

I just tried again and attached the SetupLog from that. 

So far this is just Hatari (I am working my way through re-enabling the shaders for the systems).

I am selecting the included (very nice) shader.

The error still occurs and the SetupLog provided is from a restarted instance. 

SetupLog 2024-04-25 21-36-10.txt

Link to comment
Share on other sites
JoeViking245
58 minutes ago, Solly4Life said:

I just tried again and attached the SetupLog from that. 

So far this is just Hatari (I am working my way through re-enabling the shaders for the systems).

I can't reproduce the error.  Can you attach your "BLSetup.xml" file.

What are the values you're (trying to use) using for the shader and its opacity?  (below shows 1.4 and 1.0 respectively)

To clarify, the error is occurring when you click Save in the Test screen?  If you uncheck On/Off and then click Save, does the error still occur?

image.png.907c5ffe7418d03edb1755a2a14c2bda.png

Link to comment
Share on other sites
Solly4Life
9 hours ago, JoeViking245 said:

I can't reproduce the error.  Can you attach your "BLSetup.xml" file.

What are the values you're (trying to use) using for the shader and its opacity?  (below shows 1.4 and 1.0 respectively)

To clarify, the error is occurring when you click Save in the Test screen?  If you uncheck On/Off and then click Save, does the error still occur?

image.png.907c5ffe7418d03edb1755a2a14c2bda.png

BLSetup.xml attached.

The opacity values are 1.6 and 1.0.

Yes, the error is when I click save in the Test screen. When I uncheck On/Off and click save I still get the error. However, when I loaded the game the scanlines were there but when I restarted LB they were gone and the BLSetup.xml was not updated with the values. 

That did give me an idea to just manually update the xml myself and that works and is fine after a restart.

I have kept the old xml if you want me to test further to find the issue.

BLSetup.xml

Link to comment
Share on other sites
JoeViking245
6 hours ago, Solly4Life said:

Yes, the error is when I click save in the Test screen. When I uncheck On/Off and click save I still get the error. However, when I loaded the game the scanlines were there but when I restarted LB they were gone and the BLSetup.xml was not updated with the values. 

It looks like that emulator didn't get added or updated to the xml file correctly.  My guess between the betas and the final 2.1.1, something went awry. 

 

7 hours ago, Solly4Life said:

That did give me an idea to just manually update the xml myself and that works and is fine after a restart.

Sounds like you may have already done that, but if not...

With LaunchBox not running, edit BLSetup.xml and for the emulator (<EmuName>) "Hatari"...

  • Change UseShaders to true (assuming you want to use them for this emu)
  • Edit ShaderFile to look like <ShaderFile>Scanline</ShaderFile>
  • Add in the line <ShaderOpacity>1</ShaderOpacity> 

image.png.42b80341cc060df85139b6103cbc9316.png

 

It looks like this is the only emulator missing ShaderOpacity, and I suspect that was the culprit all along.

Link to comment
Share on other sites
Solly4Life
1 hour ago, JoeViking245 said:

It looks like that emulator didn't get added or updated to the xml file correctly.  My guess between the betas and the final 2.1.1, something went awry. 

 

Sounds like you may have already done that, but if not...

With LaunchBox not running, edit BLSetup.xml and for the emulator (<EmuName>) "Hatari"...

  • Change UseShaders to true (assuming you want to use them for this emu)
  • Edit ShaderFile to look like <ShaderFile>Scanline</ShaderFile>
  • Add in the line <ShaderOpacity>1</ShaderOpacity> 

image.png.42b80341cc060df85139b6103cbc9316.png

 

It looks like this is the only emulator missing ShaderOpacity, and I suspect that was the culprit all along.

Yes, I did notice the ShaderOpacity was missing so I added it.

  • Game On 1
Link to comment
Share on other sites
LendriMujina

I just installed it, and it works IF I don't click on anything. As soon as I do try to click, though, Launchbox stops responding.

If it matters, this is on Launchbox 13.12, and this happened when using Project 64 3.0.1.

Link to comment
Share on other sites
JoeViking245
46 minutes ago, LendriMujina said:

I just installed it, and it works IF I don't click on anything. As soon as I do try to click, though, Launchbox stops responding.

If it matters, this is on Launchbox 13.12, and this happened when using Project 64 3.0.1.

Sorry, kind of confused. 

You setup BezelLauncher for your P64 emulator and when you launch a game, the bezel and game window(s) show as they should. 

Then while playing the game, you try to click something, LaunchBox stops responding?  Does the game require clicking?  Or are you trying to do something else while in the middle of the game?  Does it do this with emulators other than P64 that you've setup?

If you exit the game, is LaunchBox responsive again? 

The way it's setup to work, it's not conducive to multitasking during gameplay.  At least not beyond using the Pause menu.

Link to comment
Share on other sites
LendriMujina
30 minutes ago, JoeViking245 said:

Sorry, kind of confused. 

You setup BezelLauncher for your P64 emulator and when you launch a game, the bezel and game window(s) show as they should. 

Then while playing the game, you try to click something, LaunchBox stops responding?  Does the game require clicking?  Or are you trying to do something else while in the middle of the game?  Does it do this with emulators other than P64 that you've setup?

If you exit the game, is LaunchBox responsive again? 

The way it's setup to work, it's not conducive to multitasking during gameplay.  At least not beyond using the Pause menu.

Well, the game doesn't require clicking, but PJ64's fullscreen mode covers up the bezel, so I tried to move the window around to fit in the frame better.

By "stops responding", I mean that thing in Windows where it fades to white and says "not responding", then it closes out. I have to reopen Launchbox entirely.

I just tested it with an NES game in Nestopia, and the same thing happens there (though there's much less need to click there, as unlike PJ64, Nestopia's fullscreen is UNDER the bezel like it should be).

One more thing, how do I... exit the game?

Edited by LendriMujina
Link to comment
Share on other sites
JoeViking245
7 hours ago, LendriMujina said:

but PJ64's fullscreen mode covers up the bezel,

Per the Emulator Settings in the description above, you need to disable fullscreen mode.

image.thumb.png.9ea17f06a1dc50e1ab36b0a930ba4f96.png

 

 

7 hours ago, LendriMujina said:

One more thing, how do I... exit the game?

I haven't use either of those emulators. But for many emulators you simply press Escape. 

Link to comment
Share on other sites
myric227

myric227 21

Posted (edited)

Does anyone have the settings for Dolphin for this to work correctly?  I got it to work once, played a bit, then turned on my cab the next day and it stopped working.  It will show the game for a couple of seconds, then seems to hide behind the bezel.  If I touch anything, like trying to alt-tab to the game screen that I can hear, everything locks up and I have to reboot.  I got it to work with Xemu easy, but Dolphin is driving me crazy. I've tried all the different flags, but it still acts the same. Also, I'm not sure if it's due to being on a 4k monitor, but the test setup with the red box doesn't match the game window.  I had to move it far right for the game window to be centered when launching a game.  This applies to both Xemu and Dolphin when setting them up so far.

Gamecube 01.png

Gamecube 02.png

Setup 01.png

Edited by myric227
Link to comment
Share on other sites
JoeViking245
8 hours ago, myric227 said:

Does anyone have the settings for Dolphin for this to work correctly?  I got it to work once, played a bit, then turned on my cab the next day and it stopped working.  It will show the game for a couple of seconds, then seems to hide behind the bezel.  If I touch anything, like trying to alt-tab to the game screen that I can hear, everything locks up and I have to reboot.  I got it to work with Xemu easy, but Dolphin is driving me crazy. I've tried all the different flags, but it still acts the same. Also, I'm not sure if it's due to being on a 4k monitor, but the test setup with the red box doesn't match the game window.  I had to move it far right for the game window to be centered when launching a game.  This applies to both Xemu and Dolphin when setting them up so far.

It looks like you have Dolphin running in fullscreen. 

image.thumb.png.963f2bac0a8297f5dfa80c8a3ba6a483.png

Open stand-alone Dolphin (in LaunchBox, right-click a GameCube game and select Open Dolphin).   Go to Options - Graphics Settings and un-check Start in Fullscreen. 

For Xemu, make sure you don't have "-full-screen" in the default command-line parameters.

 

As for the test frame needing to be offset, to be centered, the above should fix that.  If not, do you have you Windows Display Settings scale set to something other than 100%?  The latest release of the plugin (V2.1.1) should [have] fix[ed] that.

Link to comment
Share on other sites
myric227

So Dolphin isn't running in fullscreen, when I did have it in fullscreen it would show the game fine and not have the bezel.  I believe with this screenshot I had it set to forced 4:3 and fullscreen not checked.  I've also tried fullscreen with borderless fullscreen enabled in advanced, but that didn't do anything.  I've tried other display options, such as running in the main window instead of generating a separate, and have fully deleted Dolphin and the various save folders, then reinstalled it since I made so many changes testing options.   My Windows scale is 200% since everything is tiny at 100% at 4k on a 32in monitor.  Xemu was done instantly minus the border being off, so I'm sure there is some setting I'm missing, but I can't seem to get it to work again.

Link to comment
Share on other sites
Solly4Life
3 hours ago, JoeViking245 said:

It looks like you have Dolphin running in fullscreen. 

image.thumb.png.963f2bac0a8297f5dfa80c8a3ba6a483.png

Open stand-alone Dolphin (in LaunchBox, right-click a GameCube game and select Open Dolphin).   Go to Options - Graphics Settings and un-check Start in Fullscreen. 

For Xemu, make sure you don't have "-full-screen" in the default command-line parameters.

 

As for the test frame needing to be offset, to be centered, the above should fix that.  If not, do you have you Windows Display Settings scale set to something other than 100%?  The latest release of the plugin (V2.1.1) should [have] fix[ed] that.

V2.1.1 fixed the issue of not displaying at full screen and only in the left upper corner. However, my 4k monitor is set to 150% and I still have to offset the test frame.

Link to comment
Share on other sites
JoeViking245
40 minutes ago, myric227 said:

So Dolphin isn't running in fullscreen, when I did have it in fullscreen it would show the game fine and not have the bezel.  I believe with this screenshot I had it set to forced 4:3 and fullscreen not checked.  I've also tried fullscreen with borderless fullscreen enabled in advanced, but that didn't do anything.  I've tried other display options, such as running in the main window instead of generating a separate, and have fully deleted Dolphin and the various save folders, then reinstalled it since I made so many changes testing options.   My Windows scale is 200% since everything is tiny at 100% at 4k on a 32in monitor.  Xemu was done instantly minus the border being off, so I'm sure there is some setting I'm missing, but I can't seem to get it to work again.

For testing purposes, run the BezelLauncher setup, select your GameCube platform and then the emulator, then disable and click Save. Close the setup window.  Launch a GC game.  Is it indeed windowed?  You should see the window title and the min/max/close buttons above 'the game'.

image.thumb.png.088bd54a318ccefb01806f75460d6625.png

For my graphics settings (in Dolphin), I have Aspect Ratio set to "Stretch to Window" and Fullscreen not-checked.  In Advanced, the only thing I have checked is "Borderless Fullscreen" (don't recall if I ever changed it).

 

If it's still not working correctly, (more testing), Exit LaunchBox, reset the scale to 100%.  Restart the computer.  Start LaunchBox, enable BezelLauncher for GC and reset the Orange Frame, Save and start a GC game.  The game and bezel should be 'tiny'. Even at 100%. 

Link to comment
Share on other sites
JoeViking245
5 minutes ago, Solly4Life said:

V2.1.1 fixed the issue of not displaying at full screen and only in the left upper corner. However, my 4k monitor is set to 150% and I still have to offset the test frame.

If you offset the test frame, save, then run a game, does everything [else] work OK?

Link to comment
Share on other sites
myric227

Picture one is my default settings with just the emulator itself running.  Picture two is with your settings at 200% scale with it showing a small window, then the game window pops behind the bezel like previously.  Picture three is at 100% scale and has the same behavior.

Gamecube 01.png

Gamecube 02.png

Gamecube 03.png

Link to comment
Share on other sites
JoeViking245
1 hour ago, myric227 said:

Picture one is my default settings with just the emulator itself running.  Picture two is with your settings at 200% scale with it showing a small window, then the game window pops behind the bezel like previously.  Picture three is at 100% scale and has the same behavior.

For some reason, your pictures are showing the GUI in the background as if you don't have -b in the command line parameters.  So that's probably what the plugin is attempting to resize.  The GUI shouldn't be showing, or be a window at all.

Link to comment
Share on other sites
myric227

I forgot to show a screen of those settings previously.  Maybe something missing here, although it's just the default?

Emulator Settings.png

Link to comment
Share on other sites
JoeViking245
5 minutes ago, myric227 said:

I forgot to show a screen of those settings previously.  Maybe something missing here, although it's just the default?

Looks good there.  Can you show the Associated Platforms section.  Somewhere, somehow you have something set that is making the GUI appear when launching a game.

Link to comment
Share on other sites
myric227

I just took a screenshot of everything there just incase.  These should all be default or I at least never remember adjusting them.

Screenshot 2024-06-01 174653.png

Screenshot 2024-06-01 174716.png

Screenshot 2024-06-01 174730.png

Screenshot 2024-06-01 174749.png

Screenshot 2024-06-01 174831.png

Screenshot 2024-06-01 174841.png

Screenshot 2024-06-01 174855.png

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Add a comment...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
×
  • Create New...