Search Issue Tracker
Fixed in 7.1.5
Votes
1
Found in [Package]
6.9.0
Issue ID
1191757
Regression
No
[LWRP]Build crashes when built with shadergraph file added to Always Include Shaders list
To reproduce:
1. Open "1191757" project
2. Open Player Settings > Graphics
3. Add a new Element in Always Include Shaders list (increase Size int by one)
4. In the Assets folder locate HDRP_LWRP_Shader.shadergraph and drag to the newly created Element
5. Build for Standalone and run the built project
Expected result: the project is opened with the included shader
Actual result: getting a pink splash screen and instant crash
Reproduced on:
2019.2.0b6 2019.2.10f1
Package version:
- 6.9.1
- 6.9.0
Notes:
- Couldn't test on 2018.4 - 2019.2.0b5, 2019.3 getting LWRP package errors
- There is no shader graph in 2017.4
- Reproduced on Win 10 and MacOS 10.15 machines
-
zyzyx
Nov 13, 2019 08:45
Possible workaround: Create *.shadervariants asset in the Graphics options (Shader Loading) and add it to the Preloaded Shaders list.
It worked for me using unity 2019.2.11fI hope this gets fixed soon.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Resolution Note (fix version 7.1.5):
This issue has been verified as fixed in Universal Render Pipeline 7.1.5