This repository has been archived by the owner on Feb 28, 2024. It is now read-only.
[BUG-228914] [EEP] Deferred Soften Shader fails to link when Atmospheric Shaders are disabled. This causes Debug viewer builds to crash. #6889
Labels
Steps To Reproduce Deferred Soften Shader linking Error
Install the current release viewer: Second Life Release 6.4.3.542964 (64bit)
Make sure ALM is enabled in Preferences -> Graphics
Log out after checking this.
Edit logcontrol.xml file in viewer install folder\app_settings
Add ShaderLoading to logcontrol.xml & save changes.
Launch the viewer.
You can test this from the login screen or when being logged inworld, it doesn't matter - easier to read logs from the login screen though.
Look in secondlife.log at the #ShaderLoading# lines & observe there are no problems with loading or linking shaders.
Open Preferences -> Graphics.
Untick Atmospheric Shaders.
Look at the new #ShaderLoading# lines in secondlife.log
Observed Behaviour
Observe the shader linking errors in Deferred Soften Shader
Because Deferred Soften Shader fails to link, doesn't this mean that there will be rendering glitches inworld?
Steps To Reproduce Viewer Crash
Build viewer release with RelWithDebInfo
Make sure ALM is enabled in Graphics preferences before you launch the viewer.
Launch viewer - you can reproduce the viewer crash at the login screen or when logged inworld.
Open Preferences -> Graphics.
Untick Atmospheric Shaders.
Observed Behaviour
Viewer crashes to desktop as soon as Atmospheric Shaders is unticked.
Crash in ASSERT (success).
I believe debug viewer builds are set to crash on any shader linking error?
It wouldn't be unusual for devs to use debug level builds so this crash will be a problem for them.
Expected Behaviour
No Deferred Soften Shader linking errors when Atmospheric Shaders is disabled.
No rendering bugs caused by the Deferred Soften Shader linking failure.
Debug level builds should not crash when Atmospheric Shaders is disabled.
Other Information
Bug found by Kitty Barnett, who is a LAZY Kitty & asked me to file the JIRA.
No Catnip for Kitty!
Attachments
Original Jira Fields
The text was updated successfully, but these errors were encountered: