Duimon - HSM Mega Bezel Graphics and Presets - Feedback and Updates

[jferdz]

Hi @Duimon , I’m looking for a way to change the default bezel included in your preset pack. I’d like to know which file to modify and which line to change so that the current bezel points to the HSM Mega Bezel stock bezel, while still using the Duimon Mega Bezel shader settings.

I want to achieve this for handheld consoles (GB/GBC/GBA/DS/3DS); here are the presets I’m currently using:

Gameboy-[STD]-[LCD-GRID]

GBC-[STD]-[LCD-GRID]

GBA-[STD]-[LCD-GRID]

NDS_Hybrid-[STD]-[Guest]

3DS-[STD]-[Guest]

Here is a Photoshop-edited image showing a visual representation of what I’m looking for (it’s not exact, but it’s an approximation).

[Cyber]

@jferdz

I’m looking for a way to change the default bezel included in your preset pack. I’d like to know which file to modify and which line to change so that the current bezel points to the HSM Mega Bezel stock bezel, while still using the Duimon Mega Bezel shader settings.

As I said before, Duimon - HSM Mega Bezel Graphics without the background Graphics and CyberLab Mega Bezel Death To Pixels without the CRT screen effects, is just Mega Bezel.

Mega Bezel Reflection Shader! - Feedback and Updates

[Mega_Bezel_Logo] Mega Bezel CRT Simulator This thread is about the Mega Bezel Reflection Shader for Retroarch! Here you can tell me what’s working for you and what could be better. If you are wondering “What is this thing?” here’s a nice little overview up sharing our ideas around the Mega Bezel project and some of its features: RetroArch – Introducing the Mega Bezel Reflection Shader – Libretro This shader package is meant for you to experiment with and make your own creations if you like.…

It’s already included in RetroArch just read the first post and the readme.md.

If you read those resources, you’d know exactly what to do. Or at least would be asking a different question if you did and still didn’t understand.

[jferdz]

Hi @Cyber , thanks for the reply. I understand your suggestion to read the readme file, but since I’m noticing a recurring pattern, I want to clarify my stance: the documentation for HSM Mega Bezel and its derivative projects is remarkably extensive—to the point where it can overwhelm a casual, non-technical user. While I’ve read parts of the “readme.md” and CyberLab’s post, I haven’t finished reading everything for two reasons. First, as I mentioned, the documentation is dense and lengthy, and I didn’t find what I was looking for there—which is why I came here to ask after reading the essentials. Second, I’m not looking to become an expert on HSM Mega Bezel or earn a “mastery” that requires hours of reading and research; I end up jumping between readme files, posts, and Git repositories without getting anywhere. This is just my personal perspective, of course; other users might have better luck navigating the readme.md and the initial post (though it’s still not entirely clear exactly which source you’re pointing me to—I assume you mean the specific readme.md for CyberLab’s and the specific post where I downloaded it). I believe my question could be answered with direct instructions right here, rather than just being pointed to sources that leave me wandering through walls of text and hours of research. I’m really hoping for a straightforward guide rather than just a reference to a source; from my point of view, what I’m asking for is something that could be answered with a clear explanation and guidance within this very thread.

I wanted to focus on handhelds this time because Duimon has settings I’m interested in keeping. I’m not entirely sure, but judging by the screenshots I uploaded (specifically for DS/3DS), it looks like there’s more going on than just the stock HSM Mega Bezel setup, so your recommendation to simply use the “Base” version wouldn’t achieve the result I’m looking for. I apologize if I’ve been a nuisance regarding this topic; I was simply hoping for direct answers here rather than an invitation to do a more complex research. I have great appreciation for the work the community has accomplished with shaders and presets—especially iconic projects like those by @HyperspaceMadness , @Duimon , and you @Cyber . I don’t mean to bother any further with this; perhaps the whole custom shader and preset scene just isn’t for me. Thanks for taking the time to reply.

[Cyber]

@HyperspaceMadness

EDITING PRESETS

• You can then open this Simple Preset file and add other parameter adjustments or set textures as you see fit. E.G. add the following lines to change the background image:
  • BackgroundImage = "MyImage.jpg"
• Or change the path indicated on the #reference line to point at a different base preset

@jferdz

I’m not entirely sure, but judging by the screenshots I uploaded (specifically for DS/3DS), it looks like there’s more going on than just the stock HSM Mega Bezel setup, so your recommendation to simply use the “Base” version wouldn’t achieve the result I’m looking for.

Why even doubt me when you clearly seem to be confused by the documentation? I don’t think I gave you any wrong information based on my experience with both Mega Bezel and Duimon’s presets. Mega Bezel is the engine behind Duimon’s presets and he has admitted to leaving things mostly stock, apart from the background graphics, lighting, placement and those elements. What you’re seeing in those photoshop edited images is the work of both the DS Core’s output settings, which cater for different dual screen output configurations as well as the default Mega Bezel behaviour of drawing a procedurally generated reflective bezel around said game content viewports. More than one screen is in fact officially supported by Mega Bezel. The carbon fiber background which is in your edited photo, is Mega Bezel’s stock, default background.

Mega Bezel and it’s presets are already on your system since Duimon’s backgrounds require it to work and it is installed automatically once you update your slang shaders using the online updater.

How hard is it to just load a Mega Bezel Preset and see what happens for yourself?

[madspace]

The duimon shaders have been working great, but what do I do for Retroarch cores that don’t have built-in composite shaders? Usually I append a composite shader over a blargg shader to achieve both effects, but it doesn’t seem to work here since MegaBezel completely overwrites the shaders under it. Saturn, Super Gameboy, N64, etc were designed with composite output in mind so it would be nice if the duimon presets supported that look.

[Banish3d]

@madspace

The duimon shaders have been working great, but what do I do for Retroarch cores that don’t have built-in composite shaders? Usually I append a composite shader over a blargg shader to achieve both effects, but it doesn’t seem to work here since MegaBezel completely overwrites the shaders under it. Saturn, Super Gameboy, N64, etc were designed with composite output in mind so it would be nice if the duimon presets supported that look.

It does support composite preset, but you’ll have to enable it manually.

To achieve that, you have to go in your shaders folder : Duimon-Mega-Bezel-main\Presets\Advanced then choose your Console after that, choose your shader and then with notepad open it.

When your in it, at lines #reference “…/…/…/zzz_global_params/Base_Shader/ADV_Bezel.slangp” add // before it to disable it.

Then at line //#reference “…/…/…/zzz_global_params/Local_Shader/ADV_06.slangp” remove // to enable this line.

After that, to add composite effect change ADV_06 to ADV_09, after saving it, you will have more options to tweak in Parameters shader on Retroarch.

[madspace]

I use the lite shaders, so it amounted to switching the local shader from 01 to 02. But it worked, thanks! However there’s noticeably more lag on Saturn and N64 with the NTSC settings on.

[Duimon]

Thanks for chiming in.

I have comments in the preset that explain this, but few users read the actual preset.

There are also post about this, but they are years ago.

It’s nice that we have this platform so experienced users can provide help.

[Duimon]

There is no very easy way to get this done, but my preset settings are grouped in to scaling parameters etc. if you cut and paste the correct group into a saved Mega Bezel preset it should be relatively easy.

Alternatively, you could make a copy of my preset and comment out the lines that have to do with graphics and bezel parameters.

It occurs to me that you might get exactly what you want by loading the correct Mega Bezel preset and tweaking the parameters, HSM has provided presets for specific systems, like the 3DS, which work out of the gate.

[Banish3d]

Thats normal to getting more lag, shaders with NTSC preset demands more resources, combined with N64 or Saturn, or even more demanding console like PS2 or Gamecube, it can be pretty intensive.

[madspace]

I’ve been trying out the duimon koko-aio presets for the newer consoles since they’re less resource intensive. But unlike MegaBezel there’s no option to change the crt mask and the default one isn’t as good, and I’ve seen other koko-aio presets with different masks like monitor-bloom-bezel. Could the duimon ones be changed to have a trinitron-like crt mask?

[Banish3d]

@madspace

I’ve been trying out the duimon koko-aio presets for the newer consoles since they’re less resource intensive. But unlike MegaBezel there’s no option to change the crt mask and the default one isn’t as good, and I’ve seen other koko-aio presets with different masks like monitor-bloom-bezel. Could the duimon ones be changed to have a trinitron-like crt mask?

You can check out Death to Pixels shader from Cyber, there is a Megabezel compatible one : CyberLab Death To Pixels Shader Preset Packs

You can even combined it with Duimon, just have to redirect your Death to Pixel Shader in your Duimon Shader, in this line : #reference “…/…/…/zzz_global_params/Base_Shader/ADV_Bezel.slangp” (disabled the other one like i said in my previous post).

[madspace]

I found the crt mask settings for koko-aio. 08 looks good. The integer scaling seems to work differently from MegaBezel but the emulators are running a lot more smoothly now!

[madspace]

Are the MegaBezel presets compatible with any subframe BFI or is it only koko-aio?

[Duimon]

It is not built-in and you can’t add it via normal methods. We’ll have to hope HSM decides to update the Mega Bezel at some point.

RL takes precedence over our hobbies sometimes, even those we are extremely passionate about.

[madspace]

Yeah I figured koko-aio is a lot easier to work with for BFI. Thanks!

[xGowtheer]

Hi, new user of Duimon’s presets here. I really liked them, but I’m having trouble enabling ntsc (composite) signal. Is it possible? I tried changing some shader parameters, but nothing worked. I wanted the image equal to Mega Bezel ADV_GDV-NTSC.

Mega Bezel ADV_GDV-NTSC:

Duimon’s Super Famicom ADV-Guest-Bezel:

[Duimon]

Make a copy of the preset in the same folder i.e. Super_Famicom-[ADV]-[Guest]-[Bezel]-my-custom.slangp.

Open the file with a text editor and look at the following lines.

// SHADER :: CONNECTOR | Interface to Mega Bezel Presets folders.
// Edit the target file in the following reference to globally define the base preset.
// ----------------------------------------------------------------------------------------------------------------

#reference "../../../zzz_global_params/Base_Shader/ADV_Bezel.slangp"

// SHADER :: CONNECTOR :: LOCAL OVERRIDES | Interface to specific base presets.
// Comment out the top reference line and uncomment the following reference line to locally define the base preset.
// Keep in mind that some of the base presets use Integer Scale and may yield unexpected results. (e.g. Megatron)

//#reference "../../../zzz_global_params/Local_Shader/ADV_06.slangp"

// "ADV_06" matches the default "MBZ__1__ADV__GDV.slangp".
// Replace the "06" with any from the following list.
// 01. SMOOTH-ADV__GDV                  08. ADV__GDV-MINI-NTSC
// 02. SMOOTH-ADV__GDV-NTSC             09. ADV__GDV-NTSC
// 03. SMOOTH-ADV__MEGATRON             10. ADV__MEGATRON
// 04. SMOOTH-ADV__MEGATRON-NTSC        11. ADV__MEGATRON-NTSC
// 05. ADV__EASYMODE                    12. ADV-RESHADE-FX__GDV
// 06. ADV__GDV                         13. ADV-SUPER-XBR__GDV
// 07. ADV__GDV-MINI                    14. ADV-SUPER-XBR__GDV-NTSC

Change

#reference "../../../zzz_global_params/Base_Shader/ADV_Bezel.slangp"

to

//#reference "../../../zzz_global_params/Base_Shader/ADV_Bezel.slangp"

(Comment the line out.)

and change

//#reference "../../../zzz_global_params/Local_Shader/ADV_06.slangp"

to

#reference "../../../zzz_global_params/Local_Shader/ADV_02.slangp"

(Uncomment the line and change 06 to 02.)

This will give you the SMOOTH-ADV__GDV-NTSC as your reference.

Then load your preset copy.

Let me know how it goes.

[xGowtheer]

It worked, thank you very much. I put a screenshot below. But strangely, it did not work with ADV_02, it worked with ADV_09. I don’t know what the SMOOTH has differently, but with ADV_02 my retroarch froze.

There is one I like from Retro Crisis, his SNES RF100. Is it possible to also load his shader just changing the path where you pointed earlier?

[Duimon]

@xGowtheer

There is one I like from Retro Crisis

If it’s not a Mega Bezel preset, then no, it is not possible.

I use certain Mega Bezel presets as my default, and my preset boilerplate provides a method for using other Mega Bezel varieties.

@xGowtheer

it did not work with ADV_02,

I’ll take look and see what’s up. Thanks!

edit: Double-check your method. I tried ADV_02 and it worked as expected.

It could just be too resource intensive for your GPU, that is the reason for “Standard” presets. The ADV, especially the SMOOTH, take a lot of GPU power.