When I run Spring (Zero-K) on Linux, only the most basic graphical effects are available. Trying to enable any shader-related effects gives me an error about lack of GLSL/ARB support for my hardware.
My hardware is fairly recent, as is my distribution release (Slackware 14.2 with the 4.6 kernel). I am using the AMDGPU driver for my videocard, which is an AMD R9 Fury. The hardware details are in the provided infolog.txt.
The issue seems isolated to shaders, as the rest of the game runs perfectly fine.
The infolog can be found here:
http://paste.springfiles.com/view/6194f2b5
Non-Working Shaders (Linux)
Moderator: Moderators
Re: Non-Working Shaders (Linux)
ATI cards tend to work poorly with Spring, but try setting ForceShaders=1 in springsettings.cfg
-
- Posts: 2
- Joined: 13 Aug 2016, 08:08
Re: Non-Working Shaders (Linux)
Looks like that did it. Thanks!
As for ATI cards and Spring, is that with the old, Catalyst drivers, or is it across all drivers? The new, AMDGPU drivers are pretty darn amazing, and since they are open source and conform to standards, I would think that Spring would work quite nicely with them.
As for ATI cards and Spring, is that with the old, Catalyst drivers, or is it across all drivers? The new, AMDGPU drivers are pretty darn amazing, and since they are open source and conform to standards, I would think that Spring would work quite nicely with them.
Re: Non-Working Shaders (Linux)
It might actually work with them (same with the Intel drivers), but the GLSL(or ARB) shader support autodetection is poor. It tends to veer on the side of caution and disable it by default on both ATI and Intel cards.
Re: Non-Working Shaders (Linux)
thats not true. the problem is that most shaders in spring are poorly written and are only tested / developed with nvidia cards. Current ATI/Intel OS drivers are much more standard-conform than the binary drivers.gajop wrote:ATI cards tend to work poorly with Spring, but try setting ForceShaders=1 in springsettings.cfg
idk why the automatic detections fails here, possible an issue of static binary build of spring.
@SylvesterInk:
did you try with spring 103.0? infolog.txt is from spring 100.0.