Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
2017.3.0f3
Issue ID
994056
Regression
Yes
Material won't render unless a default shader is used
How to reproduce:
1. Open Unity
2. Load user-submitted project (Space_Shooter.zip)
3. Load "Main.unity" scene
4. Instantiate "Bolt.prefab" prefab and position it so it is not occluded
5. Change prefab material shader to "Particles/Additive" (Material should be )
Expected result: Unity continues to show any visible shader result despite the shader used.
Actual result: Object disappears if the user chooses any shader but the default ones.
Notes:
* Refresh or reimport doesn't fix the problem
* It seems it cannot be reproduced on other materials (including ones that come with the tutorial and newly made ones)
* On early 5.6 Unity versions the material will fix itself and won't reproduce the issue even when run on a newer Unity
* On some early tests Unity threw assertion errors concerning Quaternion conversion to Matrix(Might not be connected to the issue)
Reproducible with - 5.6.0f2, 5.6.5p1, 2017.1.3p1, 2017.2.1p3, 2017.3.0p4, 2018.1.0b5
Not reproducible with - 5.6.0a1, 5.6.0f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment