Bug 93970 - Second Life - Advanced Lighting Model shader fails to compile on Radeon SI driver
Summary: Second Life - Advanced Lighting Model shader fails to compile on Radeon SI dr...
Status: RESOLVED NOTOURBUG
Alias: None
Product: Mesa
Classification: Unclassified
Component: Mesa core (show other bugs)
Version: 11.0
Hardware: Other Linux (All)
: medium normal
Assignee: mesa-dev
QA Contact: mesa-dev
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-02 20:06 UTC by MirceaKitsune
Modified: 2018-09-15 01:50 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Shader compilation log (90.65 KB, text/plain)
2016-02-02 20:06 UTC, MirceaKitsune
Details
System data from the Help -> About menu (652 bytes, text/plain)
2016-02-02 20:08 UTC, MirceaKitsune
Details

Description MirceaKitsune 2016-02-02 20:06:59 UTC
Created attachment 121467 [details]
Shader compilation log

Advanced Lighting Model shader for Second Life fails to compile. When enabled, the menu waits for a moment then turns the option back off. I attached a log of the messages printed to the console during shader activation... there seem to be a lot of complaints about FXAA.

The problem only exists in the RadeonSI driver, not the R600 driver! Until yesterday I had a Radeon HD 6870 video card (AMD BARTS) and the shader worked perfectly, now I got a Radeon R7 370 (AMD PITCAIRN) and the problem occurs since I installed it.
Comment 1 MirceaKitsune 2016-02-02 20:08:37 UTC
Created attachment 121468 [details]
System data from the Help -> About menu
Comment 2 Ilia Mirkin 2016-02-02 20:17:44 UTC
Try running with force_glsl_extensions_warn=true in the environment. Looks like the shader tries to use some advanced functionality without enabling the extensions. It checks with #ifdef GL_ARB_gpu_shader5, without enabling the ext, which is unfortunate. My understanding is that the preprocessor macros are set to 1 even when the ext isn't enabled with #extension.
Comment 3 MirceaKitsune 2016-02-02 20:27:01 UTC
(In reply to Ilia Mirkin from comment #2)

Thank you, that got the shader working again! I already had to add allow_glsl_extension_directive_midshader=true to my ~/.profile file for Second Life shaders, so until either the driver or SL fix this I'll include that one too. If the problem lies with Mesa this bug should stay open, if not someone close it please.
Comment 4 Ilia Mirkin 2016-02-02 20:30:52 UTC
There's a drirc entry for Second Life already:

        <application name="Second Life" executable="do-not-directly-run-secondlife-bin">
            <option name="allow_glsl_extension_directive_midshader" value="true" />
        </application>

You could just add the other option there as well - no need to set them globally (in fact, it might cause other things to break as a result - various exts can cause older shaders to become invalid, as keywords are added/etc).
Comment 5 Timothy Arceri 2018-09-15 01:50:10 UTC
I downloaded the latest Second Life viewer (which is apparently not longer supported for Linux) and Advanced Lighting Model seems to work without any workarounds so seems this was fixed in the game at some point. Closing.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.