Sony Megatron Colour Video Monitor

[MajorPainTheCactus]

Hi Cyber, firstly thanks for all your hard work and effort over the years its greatly appreciated by me (and I’m sure the community at large).

When users go to RTINGS they see multiple Peak Luminance values as it relates to different window sizes so it’s a bit confusing. Which Window Size are we to use when we go to RTINGS to determine our display’s Peak Luminance value to use in our RetroArch or Sony Megatron Colour Video Monitor setup? Is it 2% Window Peak Brightness, 5% Window Peak Brightness, 10% Window Peak Brightness, 25% Window Peak Brightness…e.t.c.?

Yes its a very good point and sadly doesn’t have a simple answer. The general rule of thumb is that OLEDs should look at 2-5% Peak Luminance figures and LCD (backlit LEDs) should look towards the 50-100% Sustained Luminance figures.

Why?

Well that’s a bit more interesting. For a OLED it can turn on/off each subpixel as in it doesn’t use power for off subpixels and so they don’t contribute to the ABL (Auto Brightness Limiter) power limits. This works great for the Sony Megatron with its strict full mask and scanline simulation as most of the sub pixels are turned off. See this table of calculations:

Component	Efficiency	Cumulative Percentage
Native Panel	100%	100%
RGBX Mask (3/12 subpixels)	25%	25%
Bezier Scanlines (45% AVL)	45%	11.25%
G-Sync Pulsar (Strobing)/BFI@240hz	25%	2.8%

So if you ran the Sony Megatron just on its own on a full white screen you’d get 11.25% of the pixels lit up and if you have BFI on then its just 2.8% of them turned on over a four frame cycle. Hence 2-5% Peak Luminance is the metric to look at for OLEDs.

For MiniLED LCD’s though its a different story they use dimming zones i.e a group of LEDs lighting up a section of LCDs and its these LEDs that use the power and cause the heat. As such they cant take advantage of turning off sub pixels and so a full white screen with the Sony Megatron uses the same power as a full white screen without the Sony Megatron masks and scanlines. Hence for backlit LCD users they need to look at the 50-100% Sustained Luminance figures.

Luckily it just so happens that LCD’s are much better at sustained luminance than OLEDs are and so in a lot of cases LCD’s at 100-50% sustained are still brighter than OLEDs at 2-5% Peak. But the Sony Megatron certainly narrows the brightness gap between the two technologies drastically.

Just out of curiosity I plugged in the above figures to see what would be required to simulate various CRT displays would require to simulate on a OLED/LCD with backlight strobing/BFI turned on for motion clarity and we’re looking at these kinds of figures (its worth noting nits in human perception of brightness, scale logarithmically i.e exponentially higher nits are required for ever smaller perceptual brightness increases - i.e. gamma 2.2 curve):

• To match a 100-nit BVM: You need 3,571 nits .[2]

• To match a 150-nit “Punchy” BVM: You need 5,357 nits .[2]

• To match an “HDR CRT” (400-nit peaks): You need 14,285 nits .[2]

[MajorPainTheCactus]

As for the Vulkan AMD driver issue its something to do with the drivers messing up the output. Sony Megatron is pretty simple it just turns off sub pixels - if the driver does some kind of reconstruction/compression/fancy new ai feature its going to wreck the Sony Megatron and to an extent all other output. Sadly this is one for AMD as I cant do anything about it. Maybe post on Phoronix forums - they do a lot of work with AMD Vulkan drivers see if they know if its a known issue.

[Azurfel]

Welcome back! Very excited to see these updates in action.

(Just as well that i hadn’t gotten around to actually posting that fork topic xD)

[Azurfel]

This is an absolutely massive night and day upgrade. Well done and thank you for your efforts. I eagerly await digging into a version of Megatron that includes these updates.

In case anyone is wondering, with this update:

• Setting both Peak Luminance and Paper white to 100cd/m2 matches SDR baseline.

• Colour Boost “Off” uses Rec709/sRGB primaries. “On” stretches the gamut to Expanded709.

@MajorPainTheCactus Could you consider adding additional options to Colour Boost for P3-D65 and Rec2020 primaries? This would allow non-HDR aware shaders with WCG options to work correctly.

(Rec601 and PAL/EBU would be nice as well, but admittedly wouldn’t really fall under the definition of “boost” xD)

[colourofsound]

@MajorPainTheCactus

HDR support on Linux through the KMS/DRM layer and the Vulkan driver rather than the desktop Wayland/X11 (the tech used by the Steam Deck/SteamOS). This has actually mostly already been done by others we just need to pass through the vulkan hdr metadata correctly and enable HDR.

Whats the impact of this for HDR users who run Retroarch in Gamescope? Steam Deck and SteamOS is growing in popularity; and with the advent of the Steam Machine we may see even more users running Retroarch (or solutions like Retrodeck/Emudeck). Most (including myself) will be running SteamOS or a fork like Bazzite. Will HDR still work after this change to KMS/DRM Layer?

Excited to see the new updates to the shader!

[DevonCM]

Really excited to see HDR updates, but unfortunately this completely breaks HDR in RetroArch on my setup. Windows 10 22H2, 5090 on 591.74, vulkan and dx11 drivers show the same super crushed high-gain look, on dx12 it doesn’t open. The HDR settings don’t change anything.

Previous implementation worked fine, except for the lack of a separate “UI Luminance” setting, making high-luminance setups like you need for BFI or CRT beam simulator extremely annoying to use with the ultra-bright UI you’d get as a result.

[MajorPainTheCactus]

Yes sadly I haven’t had the time to devote to the Sony Megatron - hopefully I’ll be able to devote a bit more time towards it now.

[MajorPainTheCactus]

Great stuff, yes I might add those things features depending on the direction people want to go but then again this is a built in scanline simulation and specifically tailored to casual users who dont venture into shader land - I dont want to over load them with options.

What I’ll probably do instead is to update the Sony Megatron - I basically already have and to update it in the shader repo (I’ll rename the current one to legacy so people can keep all their old presets working as is with just a repointing to the old shader). That should hopefully meet all the demands of a power user whilst keeping the HDR menu relatively straight forward for casual users (Ok subpixel layouts and luminance levels aren’t the best).

[MajorPainTheCactus]

I have no idea what Gamescope is - is that related to SteamDeck/Machine? As for compatibility hopefully we wont stop anything that was working from working in the future - there isn’t any need to.

[MajorPainTheCactus]

Righty ho so this is an issue, as I’m running Windows 11 on both my main desktop machines. I have a laptop with Windows 10 I think so I’ll go away now and test it on that. In the mean time can you tell me the exact location you got your build from? Also if it was installed over the top of a previous version could you try installing to a fresh directory? Can you tell me your display setup as well - what monitor are you using?

As for the UI luminance issue really we need a brightness setting in the UI or ideally for it to just draw with paper white when HDR is enabled. It currently renders itself over the top of the end result of the HDR conversion (as it should) and I dont have any control over it. I can understand it would get eye seeringly bright on a 10,000 nit TV though.

[MajorPainTheCactus]

Can you also do me a favour and run the Sony Megatron shader (crt-sony-megatron-default-hdr.slangp) located in:

C:\RetroArch\pkg\msvc\x64\Debug\shaders\shaders_slang\hdr

and tell me what it does? Using a HDR native shader like that should have different behaviour as it overrides all the settings in the menu and does its own HDR10 and inverse tonemapping etc.

Actually if you have the Sony Megatron running you wont see anything change as its a native HDR shader as in it does all the HDR10 and inverse tonemapping itself - you have to turn it off as its a to see my changes. I will update the Sony Megatron to use the menu options and use the same hdr10 conversion and inverse tonemaper shortly - I just need RetroArch to be released before I do that as otherwise it will just break the shader for end users.

So if that is the case we just have the DX12 failure - in that case can you post any logs for that build?

[colourofsound]

https://wiki.archlinux.org/title/Gamescope

Gamescope is a microcompositor that Valve has developed for games. My understanding is that basically it is a standalone Wayland instance which can be manipulated to run custom resolutions, HDR, VRR and so on.

It essentially sandboxes whichever application you run in it for efficiency and performance.

It’s great for Steam’s use case (mainly running games in Proton) but I can see it having great advantages for HTPC and emulation too.

Because it sort of ignores desktop settings (I think) it can behave oddly or unexpectedly.

[MatheusWillder]

I’ll try testing it as soon as the PR is created/merged, and report the results. For some reason, the last time I tried the HDR option didn’t appear in the Linux AppImage build, only in the Flatpak build, which I couldn’t compile, but maybe that changed with the PR merged to update the RetroArch HDR system.

Thanks!

[Cyber]

@MajorPainTheCactus

Hi Cyber, firstly thanks for all your hard work and effort over the years its greatly appreciated by me (and I’m sure the community at large).

You’re most welcome @MajorPainTheCactus. It has been a labour of love. I can’t begin to express how grateful I am to you and all other developers who have been creating these wonderful tools which bring so much joy to so many lives.

One request though. Is it possible to have some more granularity with respect to the slot mask height? for example, I started using some of the 4K Slot Mask options but I found the phosphors to be a little too tall. When I switched to 8K, I found the height to be much more ideal in that situation. The problem with the 8K masks was that they wern’t pure RGB like the 4K ones.

So my next step was to transfer the 4K masks over to the 8K section in order to keep the pure RGB effect with the shorter slot mask height that I preferred.

Also, I’m not sure if this can be helpful or not, I recently read a post by @Nesguy that stated that CRT-Guest-Advanced uses XRRGGBB masks instead of RRGGBBX.

[Azurfel]

@MajorPainTheCactus

Great stuff, yes I might add those things features depending on the direction people want to go but then again this is a built in scanline simulation and specifically tailored to casual users who dont venture into shader land - I dont want to over load them with options.

Additional Colour Boost options would be desirable when using HDR without any scanlines or CRT simulation whatsoever.

For example, the gba-color.slangp shader has an parameter for WCG displays (“Color Profile (1=sRGB, 2=DCI, 3=Rec2020)”), and looks best using this parameter, but that parameter is currently incompatible with the way RetroArch does HDR, forcing you to leave it set to sRGB/709 mode (matching Colour Boost “Off”), giving inferior results to those possible using WCG SDR.

Adding additional options to Colour Boost for “DCI” (P3-D65) and Rec2020 would allow such shader parameters to operate intended in HDR.

Alternatively, i suppose you could revisit your old “hdr10.slang”/“inverse_tonemap.slang” idea, and create a shader called “Retroarch Advanced HDR Options” or something like that, which could override the UI settings, and contain additional parameters for advanced users like these additional color gamut settings, and decoding gamma.

[MajorPainTheCactus]

Ah interesting what was the reasoning behind XRRGGBB masks instead of RRGGBBX? I am going to revisit the slot masks because 5K monitors can probably do them properly with their 12 pixel height scanlines - the bar across will be proportional to the height of the scanline at that resolution - about 8.333% ish lol.

[MajorPainTheCactus]

The problem if I’ve understood you correctly is that unless you know about these things you wont have the faintest idea what option to select. For casual users in the main RetroArch menu they can understand ‘Colour Boost ON/OFF’ but I doubt they would understand ‘Colour Boost DCI/Rec2020/sRGB’ etc. Isn’t it better this keeps in the advanced section of the shaders? Dont get me wrong its a great thing to have but surely simplicity has to reign or otherwise you end up with the Sony Megatron’s rats nest of options scaring people off? lol

[Azurfel]

@MajorPainTheCactus

Isn’t it better this keeps in the advanced section of the shaders?

Tbh, i would suggest that by that logic, the Colour Boost setting shouldn’t exist at all, for the exact same reason that you removed the Contrast setting. The “correct” Colour Boost setting for someone who doesn’t know what that setting does is always going to be Off/standard 709 primaries.

[Azurfel]

Thinking on it further, i would propose the following:

• Make “Colour Boost” an advanced setting, so it is only visible when RetroArch’s “Show Advanced Settings” option is set to On.

• Rename “Colour Boost” to “Content Colour Gamut” (or something along those lines?), rename “Off” to “sRGB/Rec709”, rename “On” to “Expanded709”.

• Add options for at least “P3-D65” and “Rec2020”.

Proposed transformation matrices for hdr_common.glsl:

kaDisplayP3_to_2020
   0.753833034361721f, 0.198597369052617f, 0.047569596585662f,
   0.045743848965358f, 0.941777219811693f, 0.012478931222948f,
   -0.001210340354518f, 0.017601717301090f, 0.983608623053428f);

k2020_to_2020
   1.000000000000000f, 0.000000000000000f, 0.000000000000000f,
   0.000000000000000f, 1.000000000000000f, -0.000000000000000f,
   0.000000000000000f, 0.000000000000000f, 1.000000000000000f);

This would allow WCG SDR options to work correctly with RetroArch’s HDR without adding additional confusing menu options for non-advanced users.

[Cyber]

@MajorPainTheCactus

Ah interesting what was the reasoning behind XRRGGBB masks instead of RRGGBBX

I haven’t the slightest idea. Just thought I’d give you some food for thought.

New CRT shader from Guest + CRT Guest Advanced updates

It’s worth a shot! I found something else that might be improved: [image] What would be nice is something closer to this: [image] EDIT: Ok, so mask 12 is actually XRRGGBB (Not RRGGBBX as I had assumed) No biggie, but that’s what was throwing me off. I’ve got the overlay working now. Here’s what I’d like to accomplish (without the use of a clunky overlay):

@MajorPainTheCactus

I am going to revisit the slot masks because 5K monitors can probably do them properly with their 12 pixel height scanlines - the bar across will be proportional to the height of the scanline at that resolution - about 8.333% ish lol.

I’ve learned quite a bit about slot masks over the last few months. The most important probably being that they require the most brightness to be emulated well, especially with BFI. Another thing is that they look much better when the horizontal slots near the center are evenly centered between the scanlines as well as when there are no upper and lower slots horizontal slots too close to the scanlines. For those situations, I have experimented with increasing the size of the scanline gaps until they occlude any near scanline gap horizontal slots. For the vertical centering and alignment, I use the vertrical Offset Shader Parameter.

The thing is, this vertical alignment changes at different Integer Scale values.

I do similar things for dot masks as sometimes it looks weird when the scanline gaps appear to cull dots leaving less than half a dot or a quarter or third or sliver of a dot at the top and bottom of a scanline. Perhaps some sort of optional clamping or snapping mechanism to prevent “unnatural” clipping of the slots and dot mask phosphors might be a useful feature.

This may not be a completely accurate feature as I’ve seen unaligned slotmasks and scanlines in real CRT photos but it doesn’t look as bad as when it’s emulated.

CyberLab Death To Pixels Shader Preset Packs

Some more beautiful JVC-D Series pics! https://www.reddit.com/r/crtgaming/s/urjg3HSRmz If you look closely, you’ll see that even on a real CRT the horizontal slots on the slot mask are not perfectly centered and aligned with the scanlines. Also note the saturation levels of the phosphor primaries and the subtle bloom/halation that can be seen behind and in between the phosphors. I’m also sure that just as the scanlines add something to the final image, so too do the vertical unexcited phosph…

@MajorPainTheCactus

Yes its a very good point and sadly doesn’t have a simple answer. The general rule of thumb is that OLEDs should look at 2-5% Peak Luminance figures and LCD (backlit LEDs) should look towards the 50-100% Sustained Luminance figures.

Why?

Well that’s a bit more interesting. For a OLED it can turn on/off each subpixel as in it doesn’t use power for off subpixels and so they don’t contribute to the ABL (Auto Brightness Limiter) power limits. This works great for the Sony Megatron with its strict full mask and scanline simulation as most of the sub pixels are turned off. See this table of calculations:

@MajorPainTheCactus

Yes its a very good point and sadly doesn’t have a simple answer. The general rule of thumb is that OLEDs should look at 2-5% Peak Luminance figures and LCD (backlit LEDs) should look towards the 50-100% Sustained Luminance figures.

Why?

Well that’s a bit more interesting. For a OLED it can turn on/off each subpixel as in it doesn’t use power for off subpixels and so they don’t contribute to the ABL (Auto Brightness Limiter) power limits. This works great for the Sony Megatron with its strict full mask and scanline simulation as most of the sub pixels are turned off. See this table of calculations:

These are exactly the kinds of discussions and comparisons we’ve been having here:

CyberLab Death To Pixels Shader Preset Packs

This sound like the kind of stuff @nesguy and I have been discussing over here. The G5 might need a Subpixel swap on the CRT shader side because it’s RGBW instead of RWBG. I’m hoping to see a tandem² OLED panel with MLA. Or a tandem³ True RGB with MLA and no white subpixel! In the meantime, we have some miniLED TVs that can put even the G5 to shame in the areas of CRT emulation where OLED doesn’t do as well in. Of course on the flip side OLED still shines in the areas that miniLED does…

This is the taller Slot Mask with slot mask and scanlines aligned and scanline gaps adjusted to cull horizontal slots appearing too close to the scanline gaps:

https://forums.libretro.com/uploads/default/original/3X/d/9/d971b3362444712fcf0a087a99749d763d3feb73.jpeg

CyberLab Death To Pixels Shader Preset Packs

Best viewed in fullscreen or zoomed in, in HDR mode or on a screen with bright settings for the full effect. You can download the .jxr files as well for proper HDR viewing. CyberLab Megatron miniLED 4K HDR Game BFI Turbo Duo_DC 3D Comb Filter Shadow Mask Epic CAR9x8x.slangp [RetroArch Screenshot 2025.09.14 - 01.41.20.14] .jxr image file with HDR image as well as SDR image with HDR to SDR tonemapping [RetroArch Screenshot 2025.09.15 - 03.02.29.25] .jxr image file with HDR image as well as …

This is the consensus @Nesguy and I have reached when it comes to Slot Masks with BFI and brightness:

CyberLab Death To Pixels Shader Preset Packs

Yeah, I can’t detect any moire pattern with that configuration. The triads are a bit elongated, but looks good. Currently I’m using RRGGBX sans slot mask because the brightness with slot mask added is just a bit too dim, even with 1000 nits Every time I enable the slot mask and let my eyes adjust, I always find myself wanting that extra brightness. The real glow effect at 1000 nits using RRGGBBX is incredible. The coarse dotmask is interesting, even if not commonly seen in TVs. …

CyberLab Death To Pixels Shader Preset Packs

Yeah, I recently switched back to the 4K Mask from the 8K Mask which I modified to be RGBX/BGRX. The 8K Mask was stubbier. I’ll probably revisit it if I could fine tune it to get that type of alignment. I think I did though but when looking for my example to show you it wasn’t as perfect as the 4K Mask. The whole purpose of me going through the hassle of modifying the 8K Mask Layout was because I actually preferred the shorter Mask Height of the 8K Mask. When I say I recently went back to th…

8K Masks Modified to 4K Mask Layouts:

In this example the slot mask height is not as tall and overall the alignment is not as strict. similarly for the using scanline gaps to cull the horizontal slots appearing close to the scanlines it doesn’t look so bad when the scanline gaps are larger in the darker areas but it looks a bit strange on Tyris’ forearm where you can see the slot mask slots appearing close to the scanline. I think on a real CRT there would be a more gradual fade/drop off to black which might make things like that less jarring/noticeable.

So in other words what I’m trying to say is that when horizontal slot mask slots and dotmask dots appear close to thin or similarly sized scanline gaps, it produces strange moire pattterns.

https://forums.libretro.com/uploads/default/original/3X/6/a/6a3b71b29803ae7a3e5a44f5e16541429e690e7d.jpeg

CyberLab Death To Pixels Shader Preset Packs

Thanks, I went ahead and tweaked the modified 8K Mask (RGBX with lower Slot Mask Height)) version until I got it to an acceptable level. .jxr files to follow later. CyberLab Megatron miniLED 4K HDR Game BFI Old Skool 36in Arcade Slot Mask Short Epic CAR8x8x.slangp [RetroArch Screenshot 2025.09.21 - 04.52.54.65] .jxr image file with HDR image as well as SDR image with HDR to SDR tonemapping [RetroArch Screenshot 2025.09.21 - 04.49.55.35] .jxr image file with HDR image as well as SDR imag…

Proposal: Add a 1440p Display’s Resolution section and replace the 8K section with additional 4K Masks with similar height as the existing 8K Masks or revamp the Mask/TVL selection to show the actual Mask Layouts for more advanced users to have a little more control and transparency.

I think 1440p users might be feeling a bit lost or left out when there isn’t a 1440p selection in the Display’s Resolution section while 1440p is one of the most common PC Display Resolutions and it does a great job with many mask layouts and TVLs and some of the highest refresh rate monitors are of the 1440p variety.

CyberLab Death To Pixels Shader Preset Packs

Here’s an example of my setup when it comes to scaling and latency. I intend to publish these so that users can have as great of an experience as I do. If not using VRR then Set Automatic Frame Delay to On. [RetroArch Screenshot 2025.10.12 - 02.48.07.61] [RetroArch Screenshot 2025.10.12 - 02.48.20.56] [RetroArch Screenshot 2025.10.12 - 02.48.43.59] [RetroArch Screenshot 2025.10.12 - 02.48.56.25] [RetroArch Screenshot 2025.10.12 - 02.49.27.57] PSA for 1440p Users: From the user pagge from Di…

You have to check out the Shader Stack I use in my latest “CyberLab Megatron miniLED Epic Death To Pixels 4K HDR Shader Preset Pack 31-12-25”.

It adds quite a few quality of life features via additional shaders:

It has the awesome CRT-Guest-Advanced-NTSC section with features like Afterglow, RF Noise and Font Preservation thanks to the amazing work of @guest.r !

It uses a modified IMG-Mod shader by @HunterK, which adds built-in support for proper overscan mask cropping and automatic recentering, along with film grain and rounded corners. I recently replaced the film grain version with one that doesn’t include film grain in favour of CRT-Guest-Advance’s RF Noise.

It also includes the full Grade, which was needed for things like the Sega Genesis/Mega Drive Luma Fix and Pallete as well as the SMS Blue Fix.

Last but not least, it integrates XBR-LVL-2 for subtle smoothing which helps bridge the gap between analog CRT displays and their “natural” anti-aliasing and modern digital displays which can sometimes be either a bit too sharp and aliased or a bit blurry.

The only optional feature that I might have liked to see that’s missing is support for reflective bezels and overlays, internal handling of scaling and aspect ratios and maybe CRT-Beam-Simulator Support but I have never gotten that to work properly on my display so I stick with my TV’s built-in BFI/Strobing.

These are examples of what the stack is capable of in the right hands:

CyberLab Death To Pixels Shader Preset Packs

These are from my brand new CyberLab Megatron miniLED Epic Death To Pixels HDR Shader Preset Pack Be sure to click/tap on Download Original Image to view them in the most optimal fidelity. For a long time now, I’ve noticed while experimenting with lower scale factors that sometimes when the viewport is smaller the image looks more authentic and has a special vibrancy and sharpness to it which looks and feels better and more CRT like to me. I’ve noticed every time I’ve switched back and forth …

CyberLab Death To Pixels Shader Preset Packs

[20250406_225529] [image-2] Real CRT [20250406_214556] [20250406_214848] CyberLab Megatron miniLED 4K HDR Game BFI PSX S-Video CyberTron Sharp Advanced Neo-GX_Ultimate.slangp

CyberLab Death To Pixels Shader Preset Packs

New CyberLab Megatron miniLED reference video! For best results, watch at at least 1080p resolution. [CyberLab Megatron miniLED]

CyberLab Death To Pixels Shader Preset Packs

From my latest CyberLab Megatron miniLED Death To Pixels 4K HDR Shader Preset Pack. [484718579_581867774900816_4134216722763196591_n] Real CRT [20250314_131835] CyberLab Megatron miniLED 4K HDR Game BFI SNES S-Video Slot-Mask Sharp Advanced Pro Monitor Edition CRT Shader Preset [20250314_023813] CyberLab Megatron miniLED 4K HDR Game BFI SNES S-Video Slot-Mask Sharp Advanced Neo-GX Super Fine CRT Shader Preset Powered by Sony Megatron Color Video Monitor, CRT-Guest-Advanced-NTSC, Grade …

CyberLab Death To Pixels Shader Preset Packs

CAR stands for Custom Aspect Ratio in the Settings–»Video–»Scaling menu where Integer Scale is set to On, Integer Scale Axis is set to X + Y, Integer Scale Scaling is set to Underscale and Aspect Ratio is set to Custom. So 9x8x is shorthand for set Custom Aspect Ratio (Width) to 9x and Custom Aspect Ratio (Height) to 8x. Of course it makes a difference. Over time I’ve noticed many quirks and anomalies with respect to many different aspects of shaders and their interactions with digital displ…

CyberLab Death To Pixels Shader Preset Packs

CyberLab Megatron miniLED 4K HDR Game BFI Turbo Duo_DC Composite CyberTron Epic CAR9x8x or CAR7x6x.slangp and CyberLab Megatron miniLED 4K HDR Game BFI Turbo Duo_DC Composite CyberTron Epic CAR9x8x or CAR7x6x.slangp [RetroArch Screenshot 2025.11.12 - 01.36.08.54] [RetroArch Screenshot 2025.11.12 - 01.36.41.35] [RetroArch Screenshot 2025.11.12 - 01.37.28.14] [RetroArch Screenshot 2025.11.12 - 01.37.54.00] [RetroArch Screenshot 2025.11.12 - 01.39.24.10] [RetroArch Screenshot 2025.11.12 - 01.55.0…

CyberLab Death To Pixels Shader Preset Packs

CyberLab Megatron miniLED 4K HDR Game BFI Turbo Duo_DC Composite CyberTron Epic CAR9x8x or CAR7x6x W3.slangp featuring Sony Megatron Colour Video Monitor and CRT-Guest-Advanced-NTSC 2025-11-11r1 NTSC Section [20251126_005714(1)] [20251126_005742(1)] [20251126_005745(1)] [20251126_005753(1)] [20251126_005757(1)] [20251126_005804(1)] [20251126_005846(1)] [20251126_005853(1)] [20251126_005858(1)] [20251126_005905(1)] [20251126_005917(1)] [20251126_013843(1)] [20251126_013845(1)] [20251126_013855…

CyberLab Death To Pixels Shader Preset Packs

Introducing CyberLab Megatron miniLED 4K HDR Game BFI Turbo Duo_DC S-Video CyberTron Epic CAR9x8x or CAR7x6x W4.slangp [RetroArch Screenshot 2025.12.05 - 03.34.53.35] [RetroArch Screenshot 2025.12.05 - 03.34.57.87] [RetroArch Screenshot 2025.12.05 - 03.35.35.41] [RetroArch Screenshot 2025.12.05 - 03.35.46.03] [RetroArch Screenshot 2025.12.05 - 03.35.57.65] [RetroArch Screenshot 2025.12.05 - 03.41.17.98] [RetroArch Screenshot 2025.12.05 - 03.43.05.06] [RetroArch Screenshot 2025.12.05 - 03.49.03…

CyberLab Death To Pixels Shader Preset Packs

[20251206_025020(1)] [20251206_025411(1)] [20251206_025601(1)] [20251206_025609(1)] [20251206_025616(1)] [20251206_025632(1)]

CyberLab Death To Pixels Shader Preset Packs

In a nutshell, I found out that slot masks, shadow (dot) masks and scanlines align differerently depending on the vertical scale factor so I started testing and adjusting my scanlines and vertical offsets differently depending on the vertical scale factor.

Most recently I’ve been focusing on making things brighter for “normal” folks.

CyberLab Death To Pixels Shader Preset Packs

This really made me happy. It’s much brighter than before. Thank you for posting the preset, I really wasn’t sure how to adjust the parameters. Thank you so much, @Cyber !! I just need help fixing this cut-off at the bottom edge. This only happens with the shader active. [Streets of Rage 2 (USA)-251218-210258]

CyberLab Death To Pixels Shader Preset Packs

[RetroArch Screenshot 2025.12.20 - 04.07.10.45] CyberLab Megatron miniLED 4K HDR Game BFI Arcade Pro Monitor Edition Epic CAR9x9x W4.slangp shaders = "18" feedback_pass = "0" shader0 = "shaders_slang/misc/shaders/img_mod_CyberLab.slang" alias0 = "" wrap_mode0 = "clamp_to_border" mipmap_input0 = "false" float_framebuffer0 = "false" srgb_framebuffer0 = "false" scale_type_x0 = "source" scale_x0 = "1.000000" scale_type_y0 = "source" scale_y0 = "1.000000" shader1 = "shaders_slang/edge-smoothing/xbr…

CyberLab Death To Pixels Shader Preset Packs

CyberLab Megatron miniLED 4K HDR Game BFI SNES Composite Sharp PVM Edition Epic W4.slangp [RetroArch Screenshot 2025.12.31 - 04.15.59.82] [RetroArch Screenshot 2025.12.30 - 20.02.21.89] [RetroArch Screenshot 2025.12.30 - 20.02.52.37] [RetroArch Screenshot 2025.12.30 - 20.06.08.94]