OK, this has caught me out but fortunately I have figured out how to get back to how I was. I downloaded v115 and replaced the Mega_Bezel (112) folder in my Shaders_slang folder and that’s when I discovered that my custom shaders wouldn’t load because they were referencing v112. I completely deleted the new 115 folder, updated s_s from the menu and I am working again. I have now renamed this 112 folder as “old” (just in case) and have put in v115. Now, oddly, if I choose one of my customs, it loads something but Retroarch locks up completely. If I go back in and load the base preset with the same name as I had used from v112, it loads but in widescreen (I’ll figure out why after lunch). Recreating my customs is no great hardship but I would like to know if there was a “correct” way to upgrade from v112 to v115 and still be able to load my custom shaders without having to change anything?
Can you post a log showing the shader failing to load? Upgrading shouldn’t stop them from loading.
Which log and from where?
A retroarch log. Please read the log info from the beginning of the thread.
I am getting a message telling me that I cannot upload the log file. Do I have to change the format or do I just cut’n’paste the contents directly here?
Possibly caused by using the Online Updater? I know it’s been lagging behind for a while.
The updater is still on 112
That is when I got my 27" HDR10 1500R Monitor. I was planning on getting a different one later but said “screw it”, when I saw it at the store.
Is that the right link? That one doesn’t seem curved?
It is. Here is one from the manufacturer website: https://www.acer.com/us-en/monitors/gaming/nitro-ed0/pdp/UM.HE0AA.201
I think that I was probably having a “Batocera says nooooo” issue.
I had previously set my shaders folder as “userdata/shaders” as per Bato/RA instructions. I have changed this to “userdata/system/configs/retroarch/shaders” and put all my files in there. I haven’t had a lockup so far. My previous custom shaders load in widescreen but I am guessing that is because the default aspect ratio in the v115 set is now 16:9?
Cool, I have a 24" Acer with a VA panel and I’m really happy with it. VA panels get a bad rap IMO, they have much better, more even blacks and at least for retro gaming I don’t really see a ghosting problem. I had a 24" LG IPS with really bad backlight glow, this was less expensive and blacks compare favorable to my CRT’s.
An update that allows Megatron to work correctly, is not an update to Megatron. I am assuming that the current standalone version is ahead of the Mega Bezel integrated version.
There was an update to Megatron that basically implemented the same or a similar fix to get the broken HDR in Vulkan bug working.
I assumed that the Mega Bezel implemention was updated to the latest version of Megatron as well.
Since the version just after the HDR not working bugfix, which was version 5.6 if I recall correctly, there would have been some significant changes to the tonemapping in the subsequent version, 5.7.
I think the fix @HyperspaceMadness mentioned is local to the Mega Bezel. Although he thinks it will fix it, he has said he is not sure why the scaling breaks it.
I assume if Megatron was updated it would be in this list.
Exactly what I assume makes the standalone look different from the Mega Bezel version.
You have much more experience than I do with Megatron. Does the default Megatron standalone look the same to you as the Mega Bezel version?
It’s been a while since I’ve used Mega Bezel extensively but I can give it a go once I get a chance sometime over the next day or two to check and see.
The latest release does not have an update of the Megatron version, only an update to the last pass scaling issue which seems to cause problems.
Yes, they do look different and there are several reasons why this might be so.
These include the Preprocessing that the shaders which have been integrated in Mega Bezel might apply, other Mega Bezel customizations as well as the changes made between Megatron V5.6 and 5.7.
Do also remember that the Mega Bezel Megatron Base and Root Presets are all using Megatron in SDR mode so you’ll have to switch the SDR/HDR parameter to HDR in order to set things up correctly and for changes to Peak Luminance and Paperwhite Luminance to have any effect.
With that said you can still achieve good results with the older version of Megatron included in Mega Bezel.
I did notice some glaring bugs with the reflections though. Not the same rainbow effects but in some dark scenes there was a huge red reflection while in some bright scenes there was a large green reflection. These anomalous reflections were blended with the proper reflections.
Here are two presets I made while testing.
The second one references the first one and so is dependent on it being in the same folder using the exact filename referenced.
CyberLab Mega Bezel Megatron 4K HDR Game SNES RC1.slangp
#reference “shaders_slang/bezel/Mega_Bezel/Presets/Base_CRT_Presets/Root_Presets/MBZ__0__SMOOTH-ADV__MEGATRON.slangp”
HSM_STATIC_LAYERS_GAMMA = "0.560000"
HSM_CORE_RES_SAMPLING_MULT_SCANLINE_DIR = "100.000000"
HSM_SCALEFX_ON = "0.000000"
hcrt_hdr = "1.000000"
hcrt_colour_accurate = "0.000000"
hcrt_max_nits = "660.000000"
hcrt_paper_white_nits = "660.000000"
hcrt_expand_gamut = "1.000000"
hcrt_lcd_subpixel = "1.000000"
hcrt_crt_resolution = "0.000000"
hcrt_saturation = "0.260000"
CyberLab Mega Bezel Megatron 4K HDR Game SNES Fine RC1.slangp
#reference "CyberLab Mega Bezel Megatron 4K HDR Game SNES RC1.slangp"
hcrt_crt_resolution = "1.000000"Hellos, I love the project I use it all the time on my Retroarch set up on pc, but I was wondering? will this work on android? I’d like to have these bezels on my phone so I can play on the go.