Tiny Core Linux
Tiny Core Extensions => TCE Talk => Topic started by: GNUser on April 03, 2025, 01:37:02 PM
-
At this point, 0ad is only game that's not working perfectly on TCL16. I'm trying to run the AppImage for 0ad version 0.27 available here (https://github.com/0ad-matters/0ad-appimage/releases/download/v0.27.0/0ad-0.27.0-x86_64.AppImage).
Game seems to successfully start, but I see this error message superimposed on the title screen:
error: Failed to compile shader 'shaders/glsl/compute_upscale_fsr.cs':
error: 0:1(10): error: GLSL 4.30 is not supported. Supported versions are: 1.10, 1.20, 1.30, 1.40, 1.50, 3.30, 4.00, 4.10, 4.20, 1.00 ES, and 3.00 ES.
error: 0:0(0): error: Compute shaders require GLSL 4.30 or GLSL ES 3.10
Followed by similar errors related to shaders/glsl/compute_rcas.cs and shaders/glsl/compute_downscale.cs
Game is sometimes playable after those errors scroll by, sometimes crashes. When quitting from game, X consistently crashes.
Any ideas how to make these errors go away? I already tried everything I learned in this thread (https://forum.tinycorelinux.net/index.php/topic,27576.0.html) but nothing there seems to help with this.
P.S. I just noted how strange it is that first it says that GLSL 4.30 is not supported, then it says GLSL 4.30 (or GLSL ES 3.10) is required.
-
I discovered that 0ad writes log files to ~/.config/0ad/logs. The logs are attached (the errors that apper on the title screen also appear in mainlog.html).
-
Hi GNUser
... P.S. I just noted how strange it is that first it says that GLSL 4.30 is not supported, then it says GLSL 4.30 (or GLSL ES 3.10) is required.
I think that's just the softwares way of politely saying "you're screwed" ::)
-
I think that's just the softwares way of politely saying "you're screwed" ::)
Hi Rich. Yeah, that's a great paraphrase ;D
I don't have time to investigate this further. Sorry for the noise.
Happy hacking :)
-
In the unlikely event that another TCL user bumps into this issue: The solution turned out to be appending postproc = "false" to ~/.config/0ad/config/user.cfg
Root cause was a bug in how the game determines which graphics features to turn on based on the available hardware. The game was turning on a feature ("post processing compute shaders") that requires GLSL 4.30, even though my old X230 laptop doesn't have the specs for that:
$ ./glxinfo | grep -i opengl
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) HD Graphics 4000 (IVB GT2)
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
Ref: https://gitea.wildfiregames.com/0ad/0ad/issues/7734
The 0ad developers fixed the bug for next release (https://gitea.wildfiregames.com/0ad/0ad/pulls/7737)
Thread may be marked as Solved.
-
Hi GNUser
... Thread may be marked as Solved.
Done. :)