You can take a look at what you can do with Mask 6 at 1080p in these presets. There are several settings you can adjust to make things brighter, for example, Bloom, Mask Gamma, Mask Strength, Gamma, CRT Gamma - In, CRT Gamma Out and Post-CRT Brightness. A touch of Halation can also go a long way.
These were all designed and tested on a 4K LG TV.
Feel free to look at them as well @nfp0.
I’ll take a look. Thanks!
Still shows the same problems. I presume @crtJoe’s preset was already on the latest version.
But thanks for the help!
Yeah, but maybe with one difference which is causing the issues:
shader10 = "shaders_slang/crt/shaders/guest/advanced/crt-guest-advanced.slang"
filter_linear10 = "true"
wrap_mode10 = "clamp_to_border"
mipmap_input10 = "false"
alias10 = ""
float_framebuffer10 = "false"
With this pass float_framebuffer changed to “true”. Without float framebuffer enabled there are issues like black crush and other artifacts.
That’s why it’s important to update the presets also, not only the shader files.
Ah makes sense! I’ll try it as soon as I can. Thank you!
Some people were asking why a black and white mask looks comparing an LG C1 Oled to the qn90a QLed. Here are two shots with the same shader settings. I could have better separation of phosphors if I upped the mask from 90 to 100. I like the colors more on the qn90a but they are close enough you could tweak the shader settings to be nearly identical and I wouldn’t be able to tell the difference.
Which one is the OLED? Both look good.
OLED is the first one.
I thought so when I saw them. Notice how much more detail can be seen in the dark areas and of course in the bright areas the colors aren’t as oversaturated as on the LCD. So there’s your contrast advantage at play right there and it applies to everything. Add to that no blooming and light bleed and those are some of the features that make OLED special.
What settings are you using here? Looks good
@guest.r I recently posted some presets using your integrated integer scaling parameter but I noticed something when I load up any game that has interlacing in it, for some reason the screen crops off more picture than it normally would on non interlaced games. Here’s an example, the playstation start up screen with no integer scaling set to 0:
It’s normal and the way it’s suppose to look but then I switch it to 3 and it looks like this:
It’s as if the image gets cropped vertically twice over or something. Same thing when I switch to 4:
Is that how the integer scale settings 3 and 4 suppose to look on interlaced content?
Yeah, each vertical resolution is processed differently with integer scaling. The greater it gets, more chance for loosing too much lines or get too much cropping. Bigger display resolution helps a lot here.
For example, with 200 vertical pixels and 1080p, a multiplier of 6x is used, means a ‘virtual resolution’ of 1200px, 120 output or 20 native pixels are not shown or 10%.
With 480 native vertical pixels and 1080p, a multiplier of 3x is used, meaning ‘virtual resolution’ of 1440, 360 output or 120 native pixels are not shown, meaning 25%.
But it’s a nice idea to disable integer scaling with laced screens, it’s not this hard to implement.
I see, everything is mathematics and numbers when it comes to this. And yes that idea you suggested would be great, I was going crazy trying to figure out why the screen was stretching so much lol
New Release Version (2022-03-26-r1):
Notable changes:
Download link:
https://mega.nz/file/khRBgJLa#KaILpAw98VnhMwEjv-Ky7g7Kru1RpVuF9ts01yUqh_w
Nice, let me check this out right quick.
@guest.r, please, always inform us when is only necessary copy the new files or copy and create a new preset.
It’s a self-sustained edition since a long ago, copy-paste into crt folder friendly. I would suggest to always copy paste from the root of the included folder, including presets.
This specific version only changes the shader files though.
Edit: a problem that happens is that older saved preset need a refresh since new ‘deconvergence’ implementation, because pass before the last pass needs float framebuffer enabled.
Nice, that fixed the issue right up when I loaded up my integer scaled preset but then I noticed the Integer Scaling parameter no longer does anything at all from modes 1-4. You shut integer scaling off completely for laced content? It definitely still works for non laced content. I figured you would make it so that with each mode the scaling on laced content would match up to how it looks with non laced content. I haven’t had a situation yet but I figure it would look weird on games where a scene will be non laced and the screen is stretched accordingly then it switches to a laced scene where it shrinks to non integer scale then zoom back out again when it goes back to a non laced scene, or something like that lol
This should not be an issue with modes 3-4 at all, since both fill the screen completely in vertical direction. Otherwise you can have old or the new handling, there is no simple regular middle ground.
If we think about the main purpose of integer scaling - even scanlines, there is really no need for it with laced modes, so i guess it will stay like in the most recent version.
Got it. If anything that was a more of screen “consistency” thing I pointed out, but the screen doesn’t stretch absurdly anymore on laced games and that’s all matters to me in the end. Thanks once again guest
