There are options in RA that you can turn on to create a log file. You can get the info from that or someone here will surely help you decipher it.
1 Like
That is the current version of the shader.
I believe the confusion is due to the current version being based on a fork developed after HSM had done a lot of new work on the experimental GitHub version. (The GitHub version number reflects the version HSM started making experimental changes to.)
I assume, since you are posting here, that it crashes when you try and use a Mega Bezel shader. (Your post doesn’t actually say that. 
)
If it hangs and then crashes it is usually due to using an Advanced preset along with increase core resolution scale.
That is just a wild guess. If you could kindly provide the bug reporting info requested at the beginning of the thread, I could probably give a better answer.
Please provide what details you can, and I will do my best to help. (Please also include your hardware specs.)
2 Likes
You will want to make sure you grab a release rather than the main branch in the repo. The releases are all the Mega Bezel V1.x, the latest main in the repo is the V2 stuff that I’ve been working on and has been taking forever.
7 Likes
I figured why VGA mode and Interlacing were not being triggered automatically for me; I had to first tweak the core res sampling params, especially this one:
HSM_CORE_RES_SAMPLING_MULT_OPPOSITE_DIR
The default value sort of disabled the int/vga trigger resolution. And as a newbie with Mega Bezel, that was quite confusing to figure out, I’m not used to playing with sampling params.
Anyways, increasing the said param will indeed trigger interlacing/VGA, but I wonder which value should I use? something that works consistently for 480i content? Also what about VGA (480p)?
Again, these are all uncharted territories for me and any hint would help.
2 Likes
What you want to do is set the interlace mode settings which will adjust when interlacing is triggered
So you may need to set the trigger res lower, as well as set the Interlace mode to 1, 2 or 3
The default is set up to not interlace, since the mega bezel often gets 480 and higher res input that the user doesn’t necessarily expect to have interlacing
4 Likes
Late feedback:
It seems no matter how low I set the trigger resolution, it still won’t trigger interlacing unless I increase this specific param by at least one value:
I’m using version V1.17.2_2024-05-18
1 Like
can you take a screengrab with the resolution info so we can see the core resolution?
1 Like
Here’s one without my workaround:
With the workaround:
Edit:
While at it, I’d like to report the following missing glcore flip fixes, they are either new introduced issues in the nightly core builds, or a recently renamed core:
glcore_LRPS2.params (new name)
glcore_dolphin-emu.params (new name)
glcore_DOSBox-pure.params (new flipping)
glcore_melonDS DS.params (new core/openg gl mode glcore flipping)Hi all, I tried searching the thread because I’m sure this has been answered but I’m embarrassed to say I couldn’t find the answer:
How can I convert the newpixie crt variant of megabezel into a screen only version? Best I could get tinkering with parameters was increasing the viewport zoom to 120, removing curvature, and making background layer opacity to zero. But…that still leaves the reflective bezel. Any way I can remove that or a more elegant solution to simply convert it to screen only?
(Cyber, if you read this first, I didn’t follow up in your thread because i realized the newpixie shader wasn’t part of your DTP megabezel preset pack and didn’t want to keep asking you about a project you’re not responsible for since I’m already asking you a million q re Megatron tinkering)
2 Likes
Do a search in the parameters dialog (By pressing the “S” key) and type in.
[ bezel
That will jump you to the “Bezel” section.
There you can reduce the opacity of the bezel and frame to 0.00000.
That will take care of the reflection.
Also, non-integer scale % of 100 should be full screen. No need to use viewport zoom. (It is really just for preset developers to get a close look at sub-pixels)
Honest question though, why not just use the standalone newpixie-crt? Is there some other Mega Bezel feature that you need?
Doing the above parameter changes will make it appear like a “screen only” version, but it will still take as much horsepower as a regular preset.
The actual “screen only” Mega Bezel presets are much leaner.
You could take the screen only GDV variant, either ADV
\shaders_slang\bezel\Mega_Bezel\Presets\Base_CRT_Presets\MBZ__2__ADV-SCREEN-ONLY__GDV.slangp
or STD.
shaders\shaders_slang\bezel\Mega_Bezel\Presets\Base_CRT_Presets\MBZ__4__STD-SCREEN-ONLY__GDV.slangp
and the parameters for the New-pixi clone.
# HSM_DOWNSAMPLE_BLUR_SCANLINE_DIR = "33"
# HSM_DOWNSAMPLE_BLUR_OPPOSITE_DIR = "33"
HSM_DOWNSAMPLE_BLUR_SCANLINE_DIR = "0.000000"
HSM_DOWNSAMPLE_BLUR_OPPOSITE_DIR = "0.000000"
HSM_INTERLACE_TRIGGER_RES = "100.000000"
HSM_FAKE_SCANLINE_OPACITY = "70.000000"
HSM_FAKE_SCANLINE_ROLL = "30.000000"
SGPT_BLEND_OPTION = 0
g_cntrst = "0.500000"
GDV_AFTERGLOW_THRESHOLD = "7.5"
# BP = "16"
glow = "-0.300000"
SIZEH = "7.000000"
SIGMA_H = "2.300000"
halation = "0.2"
h_sharp = "3.000001"
shadowMask = "6.000000"
maskstr = "0.4"
maskDark = "1.000000"
GDV_DECONVERGENCE_ON = "1.000000"
deconrr = "1.500000"
deconrb = "-1.500000"
deconrry = "1.500000"
deconrby = "-1.500000"
addnoised = "0.140000"
and create a second reference for a preset.
You would get an actual “screen only” version of the new-pixie clone.
1 Like
Thank you so much Duimon!
As for why not use the reg newpixie shader, I don’t know why but the megabezel version looks significantly different. Like there’s a soft bilinear filter missing on the standard version. I don’t know, I’ll take some photos when I get home from work to show you what I mean.
The megabezel overhead is fine, as it’s run by a 4060 and Ryzen 7945x
2 Likes
Probably because it is really the default Guest Advance with some tweaks.
If you need some help setting up the second reference (What I would really recommend.) just ask and I will give you some pointers.
1 Like
It’s okay, I have a bit of nostalgia for the Newpixie-CRT-clone preset because that’s what I started with when I ended up making my first preset pack.
You can see that right here:
After a short while, I started going for a more “realistic” look but I kept a few presets which contained the same ethos of my original presets.
They are the “RGB_SHARP/SMOOTH” presets.
There are some modern variants of those called “Upscaled No Border” which use the Screen Only Base Preset.
There are also a few novelty items like “Old Skool RF Interference” which you can try out.
These are all based on Mega Bezel 1.14.0 though.
Perfect for your True Black HDR400 mode would be the CyberLab Mega Bezel HDR folder, which has Presets which take a hybrid approach to achieving the required brightness.
Have fun with the Newpixie-CRT-clone though.
Actually, I was wondering if there was a way to keep your DTP presets installed since they require MB 1.14 which I have to manually reinstall every time I update the shaders through RA. Is there a way to change the required paths to a separate 1.14 folder I keep around?
1 Like
I really like your idea about adding the new pixie paramaters to MBZ_2_ADV-SCREEN-ONLY_GDV.
Is there a faster way of copy pasting them than manually typing everything up via retroarch? I tried opening up the .slangp shader file in notepad thinking I can copy/paste your paramaters but it showed this:
#reference “Root_Presets/MBZ__2__ADV-SCREEN-ONLY__GDV.slangp” #reference “…/…/resource/param_values/base/auto-settings.params”
1 Like
What you need to do is open some content (Even just an image file.) and load the parent preset. I recommend the STD.
shaders\shaders_slang\bezel\Mega_Bezel\Presets\Base_CRT_Presets\MBZ__4__STD-SCREEN-ONLY__GDV.slangp
Then save a new preset by any name you wish. (i.e. something easy like test1.slangp)
The create a text file named newpixie.params and paste the parameters in the new text file.
When you open up the test1.slangp in a text editor you will see…
#reference "shaders_slang/bezel/Mega_Bezel/Presets/Base_CRT_Presets/MBZ__4__STD-SCREEN-ONLY__GDV.slangp"
Add a second reference to the newpixie.params so it reads…
#reference "shaders_slang/bezel/Mega_Bezel/Presets/Base_CRT_Presets/MBZ__4__STD-SCREEN-ONLY__GDV.slangp"
#reference "newpixie.params"
Then run some content and load the test1.slanp… it should look like this.
From my quick test it looks just like the newpixie variation. (Which should be no surprise.)
From there you can turn off curvature and increase the non-integer scale to 100 and save the preset again using the same name (test1.slangp)
The result.
Keep in mind this was converted to a JPG to upload to the forum, some detail is lost.
You can rename the test1.slangp file however you wish. Just be sure to keep the newpixie.params file in the same folder.
If you wish to move the test1.slangp to a new folder you will have to change the reference path to reflect the change, or use an absolute path instead of a relative one.
1 Like
It’s quite simple to make a copy of the Mega Bezel 1.14.0 folder and rename it, “Mega_Bezel - 1.14.0” and a copy of the latest version and similarly append the version # to it and just open whichever one you wish to use and select all, copy, then open the “Mega_Bezel” folder, select all, delete, then paste the files you copied into the main Mega_Bezel folder.
You can repeat this process with the latest version if you wanted to switch back to it.
Or, if you wanted to be cool you could do the first step above, then using a mass editing tool like “Notepad++”, use the “Find in Files” feature to search for and replace every instance of “/Mega_Bezel” in my preset pack with “/Mega_Bezel - 1.14.0”.
1 Like
