Here is another with grade, 7504 wp temperature and some contrast
3 Likes
A small update with contrast added and off switches to speedup things if it’s needed.
https://mega.nz/file/e7xESTJJ#RVfrKqFdl34F2M6CjcH1LhxcmCxWZnqVEDRl0sBYpQM
As a bonus, included a modified old guest.r shader with things backported from this shader (and some back to their natural enviroment, like color temperature)
3 Likes
Holy shit that guest revision is a blast from the past.
I can’t remember the last time his shader codebase was that simple.
2 Likes
Yeah really simple but still good looking. I think that comes from 2018, and I removed some things too, like saturation function that wasn’t working properly. That runs 70-75 fps on my old HTC One with an 80 gflops GPU.
That old dog can’t do much now, but it’s slim with stereo speakers and 1080p, used entirely as a RetroArch machine 
2 Likes
A small update, trying to save some brightness for normal monitors
https://mega.nz/file/3vJjnYqL#mEMwDXNE6OE_F6sv_4G82FaGKgUFhNF0kEETuUeVAL8
And a different profile for Guest.r shader to somehow match my Trinitron in scanlines, colors and brightness
5 Likes
Added a new mask on both shaders (CGWG Slot)
https://mega.nz/file/SmJSgDYb#j7TsvtdaovzDcighgGRXCJ1gpgMKcRH0qlt38Zvs_ag
3 Likes
Next update will include proper brightness readings from my Trinitron, real world “R-G-B color brightness weight” and proper exponential brightness function (that took me some hours of calculating).
4 Likes
Added options to control each color “scanline weight” (how intense will be scanlines on blue, red, etc) and a CRT VGA mask inspired by an old post from Nesguy. I have to sort all those masks that I did and decide which to keep. What a mess lol
2 Likes
Ight, that scanline shit is fancy. That’s all I wanted to add!
1 Like
New version that i promised with “rgb color scanline weight control”, some new masks (like CRT VGA) and glow on modified guest.r shader (which btw looks incredible now with all the changes).
https://mega.nz/file/ezwURZKY#WFzH2BSAAVLDUKcIMU4M2_m9XXJlu44y82DK-oYvi_M
3 Likes
Looking over the new update, stuff looks awesome!
Could you possibly send me a copy of that older guest version (without mods, for code comparison; sanity check 
)?
Regardless, cool work, I’m really digging the RGB scanline separation.
1 Like
Sure, old version here, 1st post or 2nd.
http://eab.abime.net/showthread.php?t=95969
Regarding RGB separation, brightness relationship on my Trinitron is around 1 red, 8 green, 1 blue. But I prefer something more rounded with not so much difference. Green is super bright there.
1 Like
So you’ve been keeping the red and blue scanline weights level, while “multiplying” greens weigh by 8?
1 Like
No I prefer something like 2-3-1 relationship because if I use 1-8-1 the LCDs are not bright enough and it kills brightness on red and blue (full dark scanlines not taking into account how bright is red or blue). But there is no any problem on CRT because it’s super bright anyway.
Full green there is around 4 times more bright than full red and blue (magenta). If I use 4 times less bright magenta on LCD it will absolutely destroy any brightness left.
2 Likes
So is there a reason you’re applying the mask before the scanlines? (Or am I reading that code wrong?)
Just seems more common to go scanlines and then mask, instead of mask and then scanlines like you did.
Just curious. (Didn’t know if there was a logical reasoning behind it, or that’s just where it looked good )
Both shaders do scanlines first, if you look the code. CRT-beam keeps a copy of screen named as mcolor and in the end of main() it applies the effect on that copy (that is before mask was applied).
Guest.r version does an “sw” function that does the scanlines taking in to account luma too. Both before mask.
1 Like
I was reading your CRT beam shader wrong, carry on!
1 Like
Can you hand hold me through this? (Because my head is still saying you’re doing it the other way around in your CRT beam shader, as having a hard time wrapping my head around how it’s applying the scanlines before the mask.)
And as far as I can tell you’re using the mcolor tag to make a copy of the zfast blur, and then apply it as part of the glow, it also goes into the scanline weight (earlier), but I don’t see where it touches the mask command/tag anywhere.
As to ME it looks like you’re applying the zfast blur, then brightness, then white point (if on), fake gamma (if on), then mask (if on), gamma out (if on), glow/color boost (if on), scanlines, contrast (if on), saturation(if on). (Please, please, please, correct me if I’m wrong, I do want to learn, not trying to nitpick.)
vec4 screen = COMPAT_TEXTURE(Source, p);
The screen is read
vec3 mcolor = vec3 (screen.r,screen.g ,screen.b);
A copy of screen is saved to vector 3 mcolor (XYZ, RGB or whatever).
float scanLineWeight = CalcScanLine(f.y, mcolor);
The scanline is calculated with y coordinates of f.y and reading color values stored in mcolor.
Then at the end it returns a value based on the luminance of the colors of the mcolor, without caring about the mask and simply multiply the vector then.
1 Like