Like Cyber said if you need any help just let us know. We will be able to help with just about anything dealing with the shader presets.
So I couldn’t quite put my finger on why i thought your shaders looked better in the beginning and then kinda (to my subjective pov) looked worse. I think the reason is that i initially applied the RGB preset and then after reading your recommended section switched to the composite-sharp preset.
I asked a couple of weeks ago on how to make the shader brighter, but then i saw you mentioning how you keep your brightness on your OLED on full blast. That explains why i find these presets so incredibly dimm. The thing is, I don’t like setting my OLED light in SDR over 60. It really excellerates the occurance of burn-in and is officially adviced against. But even if i do bump up the brightness, it obviously gets better, but it’s still fairly dimm. I guess you get used to it somewhat. I played like that for a few weeks, but it was still something that i had in the back of my mind.
However, the real issue is the change in color temperature. It seems like - and correct me if i’m wrong - the color temperature gets cooler compared to the RGB preset, no? I understand that with the low brightness, it’s a trade-off. I guess with the strength of the scanline you just have to sacrifice some brightness, correct? But i think aside from the lack of brightness it’s really the color remperature that is bothering me.
Don’t take this as a criticism per se, i’m just throwing out some impressions of mine and trying to learn more about it. For the time being i basically switched to the RGB preset. But you’re not really working on that preset anymore, is that right? I still love this shader to DEATH
Thanks for the feedback. My entire Shader Preset Pack is still under development so over time it should continue to improve, evolve and is subject to change without notice. You’re free to play around with the parameters to dial things in just the way you like them and also to suit the way your equipment is set up.
You say I have my brightness at full blast as if that’s a bad thing. I’ve had my OLED E6P since early 2016 or 2017 with no burn-in and I don’t consider myself lucky. I never read anywhere that LG recommends that you don’t set your OLED light to 95. With that said to each his own but it’s kinda sad to have to walk on eggshells and not be able to take full advantage of what the hardware has to offer.
I don’t have my brightness setting higher than 56. I use low Black Level and my Energy Saver is set to Medium. All of these settings also affect brightness of the TV.
So I suggest you play around with things like white point and Post CRT Brightness. You can also adjust Mask Strength and Scanline Type to suit your tastes. When finished just save a New Preset, Game Preset or Core Preset.
Make sure you have Use Simple Presets on before you do.
People need to remember that shaders are different from person to person and monitor to monitor. Tweaking is always welcome to a person’s liking since everybody has different tastes.
@Cyber I added the pictured tutorial.
That’s true, another thing some may not fully appreciate is that many of us do this in tiny slices of free time in our busy lives filled with responsibilities. It’s a miracle that more mistakes aren’t made when I release my presets!
When an overhaul is required or desired for whatever reason the final vision might take a few updates or a while to come to fruition as its improved and being worked on one tiny bit at a time.
For example, you use my 1080p presets, I have some updates that I’ve been working on for my 1080p Optimized Arcade - Sharp and Raw presets. Those might take a while for me to release and after that, I might want to see if I can also improve my Composite__Pure__1080p__PVM-EDITION__ADV preset as well.
So I’m beginning to appreciate @Duimon’s position even more now in that he seems to want users to use the parameters and learn to customize things to their liking.
Thanks for this! I’ll take a look when I get a chance! I’m sure you did an excellent job!
Yeah I do that because that is what I have specifically. No sense of using the other ones when my monitor can only go to 1080p.
That is one of the reasons I started the variations. I am trying to figure how much I can actually customize. Lately it has just been a whole chunk of Nintendo handhelds.
@Cyber HyperspaceMadness had the right thinking dealing with upscaling and shader. I set the resolution to 1600x1200 and everything still loads up fine. I used MBZ__3__STD__DREZ-480p__GDV.slangp for the shader in the picture.
@Cyber I’m getting a “Failed to apply shader” error (first time trying to use these shaders!). I’ve extracted the Mega_Bezel_Community director into ./shaders/, and then I try loading ./shaders/Mega_Bezel_Community/CyberLab/MBZ__1__Advance_Full_Reflections\1440p_Optimized_Presets/CyberLab__Composite-Sharp__1440p__PVM-Edition__ADV.slangp (I’m using Flycast core and Retroarch 1.10.0). I get the error every time! I’ve tried reinstalling Retroarch to make sure there’s nothing wrong with my install. Any ideas?
I get it to load fine. The shader points to the 4K shader with #reference “…/…/…/…/…/shaders/shaders_slang/bezel/Mega_Bezel/Presets/Base_CRT_Presets/MBZ__1__ADV__GDV.slangp”. Make sure you have HSM Shader pack downloaded and in the shaders_slang folder as well.
Can you post a log so we can see where it’s failing?
What graphics card are you using, how much VRAM does it have and what internal resolution are you trying to run Flycast at? If not native resolution, have you tried running it at native resolution instead?
We await your logs to see exactly what is occurring but this is not uncommon for people trying to run Flycast at greater than native resolution with limited GPU resources. It can even affect native resolution as well due to the internal upscaling taking place within the shader pipeline.
There have been several posts talking about this type of error using this same core so I suggest you search or browse back a little and see what others have been advised to do. You can also check the HSM Mega Bezel Reflection Shader page for similar posts and possible solutions providing that the cause of your issue is the same of course.
Have you also installed the latest HSM Mega Bezel Reflection Shader from here?
This probably a path issue. It usually means either a preset or an image that is needed cannot be found.
That what I was thinking. I think the user didn’t download the HSM Reflection Shader that is why I suggested them to download it.
I’ve seen that happen to users before. That usually means they didn’t read or understand the setup instructions properly. Let’s see what it is in this case.
Perhaps you can move the instructions so they are before the large number of screenshots. New users may not be aware they need to scroll so far down the thread.
Or add a note before the shots, mentioning that the instructions follow and MUST be read.
Yeahhhhhhhh, I’d do a couple (no more than 4) screenshots, then the instructions, then more shader porn if so desired (in this context, it’d be desired/necessary, mainly because we’re talking multiple presets instead of an individual preset).
This is just my opinion tho man, everybody can just do whatever at the end of the day.
My instructions also follow a lot of shots, but I say to read the last section of the post for installation info.
Yeah you want to do only a select few images because if there are to many it gets really busy. Instructions to me are more important than the screenshots but they are really needed with Shader Preset as well. I would do Instructions and then screenshots. I did it that way with my topic.
We could go big brain and do all of the instructions in “screenshots”, then the whole post is pictures ROFL.
(No shade Cyber, personally it doesn’t matter to me how you structure your thread. I was just jumping on the discussion and adding my suggestion to the mix.
Look at this @duimon:
This is before a single screenshot and even before the download of my presets pack.
If you open my presets pack the first thing you’ll see is a folder and a readme.txt file. This file is supposed to be read. Even if a user didn’t scroll through the pictures to get to rest of the information in my first post, the readme file has all of that and more (without any pics) in the installation and usage section including links.
I am all for user friendliness but getting the most of my presets requires the user to at least read my recommendations. I kinda deliberately left things like that just to encourage users to read. I even had an Easter egg of one of my older and special presets for download as a reward for those who took the time to read. I only removed it when the release candidate broke compatibility with older presets.
If a user isn’t interested or inclined enough to read through a single post, (they don’t have to stop and look at the pics), then they might end up coming back with even worse problems and questions that might have been easily covered by the information that I’ve shared.
I’m not saying what you’all have suggested isn’t valid but there should be a point where users have to take a bit of responsibility and initiative. The readme files are very important and useful resources.