Thanks! This works as expected for me.

wat da hail is "cm for blur" and shadow

Blur uses a main fb which can be in HDR and modifies it like it is sRGB. So main fb -> sRGB. Without it you get a gray smudge in HDR mode.
Shadows and borders are defined in sRGB. So sRGB -> main. Without it you get oversaturated shadows and borders.
Probably need to have 3 image descriptions: source, main fb and output. And keep main at something simple and precise like linear fp16. But main fb -> output will require a second draw pass if decoration:screen_shader is used.

Basically everything that has some color should go through CM before going to main fb.

error at https://github.com/hyprwm/Hyprland/pull/9600/files#diff-90a04c13f5ee4e0258fd226a879957a956751d2906c1e5b13ccf47f7dc8a7dc5R1577

should be

- if (shader == &m_RenderData.pCurrentMonData->m_shCM && !usingFinalShader && (texType == TEXTURE_RGBA || texType == TEXTURE_RGBX)) {
+ if (shader == &m_RenderData.pCurrentMonData->m_shaders->m_shCM && !usingFinalShader && (texType == TEXTURE_RGBA || texType == TEXTURE_RGBX)) {

this is not really what I envisioned for extracting shaders from source. My idea was more along the lines of:

CShader({
   .vertex = false,
   .type = TEXTURE,
   .cm = true,
   .rounding = true
 });

which would build the string. But this is fine too, however:

• I'd move the version to the source. When you create a shader, pass the string and version, and the shader class should append it.
• the 320 ES vertex is still needed. We allow screen shaders to be 320 ES and some people use it. (Another reason for the above)

When testing a local build without installation shaders should be copied/linked to ~/.config/hypr/shaders

Oi oi, does that mean hyprland will not launch without shaders installed to the system? That is not acceptable.

* I'd move the `version` to the source. When you create a shader, pass the string and version, and the shader class should append it.

One of the reasons to extract shaders was syntax highlighting and static checking.

* the 320 ES vertex is still needed. We allow screen shaders to be 320 ES and some people use it. (Another reason for the above)

It's there and supported (both 300 and 320).

When testing a local build without installation shaders should be copied/linked to ~/.config/hypr/shaders

Oi oi, does that mean hyprland will not launch without shaders installed to the system? That is not acceptable.

I'll think of something. Probably won't be as clean as I'd like it to be.

One of the reasons to extract shaders was syntax highlighting and static checking.

hm, fair, tho syntax highlighting for shaders aint that important

This seems to cause a regression in #9795 for me according to a bisect. Not a huge deal but hopefully fixable