Search Issue Tracker
By Design
Votes
0
Found in
2018.1.8f1
Issue ID
1071377
Regression
No
Shader reference from Scene Asset Bundle is different from one obtained from Shader.Find reference
Steps to reproduce:
1. Open user-submitted project "DecalAssetBundle.zip"
2. Load Scene Scenes\Example
3. Check out the plane and the decal on it
4. Load Scenes\SampleScene.unity
5. Enter Play Mode
6. Click the Button or Test->Read Asset Bundle in the Menu Bar
7. See that the scene loaded from a bundle does not have the decal and that the shader reference number is different (see the three numbers logged in Warnings)
Expected result: the shader reference is correct when loaded from an asset bundle
Actual result: the shader reference is incorrect when loaded from an asset bundle
Reproduced with: 2017.4.8f1, 2018.1.9f2, 2018.2.6f1, 2018.3.0a10
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
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
- Previously deleted “DefaultLookDevProfile“ is present when upgrading the Editor version
- [Ubuntu] UI text and buttons are missing spaces in Unity Version Control > New Workspace window
- "Inherit attribute is not supported" warning is shown but attributes are available in VFX Graph Output and Update blocks
Resolution Note (2019.1.X):
Shader.Find only returns shaders that were included with a player build, not shaders loaded from or contained in asset bundles.