I’m thinking of exchanging my Bsnes core for non-HD
My PsOne core gave me a lot of work to configure, I think I will keep it and not use this shader on it, despite wanting a lot, the core works well, even better than the game in its originality.
it’s well changed, I have a reasonable machine so I managed to extract a lot of processing from this core.
I think we can assume that the changes (Tweaks) you made are the problem with the shader. If your tweaks are important to you then, of course, don’t use the shader.
Yes, we can say that my core is very changed and I can say that the problem is not the shader
I’ve been looking and apparently the source where I learned to install the cores, says to download Bsnes, not Bsnes HD, I don’t know how I ended up installing it here, I’ll try again now with Bsnes normal version
I need this shader working, it brings nostalgic effects
So I would hold a bit before creating a lot of presets until the new shader and retroarch version come out, the new version of retroarch will allow you to have much simpler and more manageable presets, and a lot of the parameter names will change between the old and new versions .
What I mean to say is that make whatever presets you like, but it will get much easier in the new version and you will not have to redo so much stuff after you start using it.
Hi, can you post an example? Basically showing the original graphic and the final result with the Mega Bezel?
One thing the Mega Bezel has on by default is a vignette on top of the background image, It looks something like you see in this SNES example. You can turn this off if you like by reducing the opacity parameter for the vignette.
I don’t think he is talking about gradiation, but saturation - i.e. LESS saturation.
I would see if you’re using a icc profile in Windows. In Photoshop, you can open your image, goto View, Proof Setup, then either choose “Custom” and then your monitor, or choose “Monitor RGB”, this should give the true colours.
NTSC Adaptive doesn’t work in either “hsm__MEGABEZEL__0__EASYMODE” or “hsm__MEGABEZEL__0__GUEST-DrVENOM”. It shows up in the parameters when I switch out GTU, but turning it on simply has no effect. It seems to work fine in Newpixie, however. Haven’t tried Royale yet.
I’ll check this out tonight, there’s probably something wrong in the preset I’ll need to fix, I put it in a long time ago and I don’t think it’s been tested recently.
I took the opportunity to review the entire shading of the MegaBezel and in fact had no values for vignette.
But the problem was precisely in the Photohops color profile, as suggested. I was working on CMYK instead of sRGB.
What confused me was the fact that Windows’ native photo viewer showed the most vivid colors, just like Photohop’s canvas. So, I believed that the problem was in the MegaBezel.
I installed another viewer (IrfanView) and was able to check the facts. The photoshop image output was correct, but the canvas was in CMYK profile.
The conclusion:
No problem with MegaBezel
I have to rework the coloring of my graphics!
Native Windows 10 photo viewer ignores the RGB profile?
To compare, see below the same image opened simultaneously in the native Windows photo viewer and IrfanView:
Make sure you have a icc monitor profile installed, you can normally get one at your monitor manufacturer’s website. But, like the poster above me, I would use the old viewer, it respects the icc profile.
I use Photoshop CS6, and it opens all images with the default icc, so images look washed out like your images. I always have to remember to select my monitor profile before I do any work.