Any "crt-royale" preset fails to load. Logs are provided

I am running Retroarch 1.9.0 on a Linux PC. Whenever I try to apply any shaders of the “crt-royale” family I get this error message onscreen: image

I started retroarch with

retroarch --menu --verbose | tee retroarch.log 2>&1

as instructed in https://docs.libretro.com/guides/generating-retroarch-logs/ (actually I used “tee” to see them flowing in real time and get the significant part).

What happens when I try to load any CRT-royale shader is just this:

[INFO] [Shader driver]: Using GLSL shader backend.
[INFO] [GLSL]: Checking GLSL shader support ...
[INFO] [GLSL]: Found GLSL vertex shader.
[INFO] [GLSL]: Found GLSL fragment shader.
[INFO] [GLSL]: Linking GLSL program.
[INFO] [GLSL]: Found GLSL vertex shader.
[INFO] [GLSL]: Found GLSL fragment shader.
[INFO] [GLSL]: Linking GLSL program.
[INFO] [GLSL]: Found GLSL vertex shader.
[INFO] [GLSL]: Found GLSL fragment shader.
[INFO] [GLSL]: Linking GLSL program.
[ERROR] Failed to load GLSL shader: /home/fabio/.config/retroarch/shaders/crt/shaders/crt-royale/src/crt-royale-bloom-approx.glsl.
[INFO] [GLSL]: Checking GLSL shader support ...
[WARN] [GL]: Stock GLSL shaders will be used.
[INFO] [GLSL]: Found GLSL vertex shader.
[INFO] [GLSL]: Found GLSL fragment shader.
[INFO] [GLSL]: Linking GLSL program.
[INFO] [GLSL]: Found GLSL vertex shader.
[INFO] [GLSL]: Found GLSL fragment shader.
[INFO] [GLSL]: Linking GLSL program.
[INFO] [GLSL]: Found GLSL vertex shader.
[INFO] [GLSL]: Found GLSL fragment shader.
[INFO] [GLSL]: Linking GLSL program.
[WARN] [GL]: Failed to set multipass shader. Falling back to stock.

I couldn’t find a way to get the logs more verbose. The guide specifies how to set the log level to DEBUG but then I can’t find where the logfile is actually located if I do that via GUI.

Thanks for any help!

just go to settings > logs and set both logging verbosities “debug” and ‘log to file’ to ON.

We can see that it doesn’t like the ‘bloom approx’ pass but that doesn’t have the actual error in it.

Thank you very much hunterk.

I followed the instructions as pictured:

and then the shader started working…

Who knows what happened beforehand. I’ll post again with more detailed logs if the issue will occur again. Many thanks!

1 Like