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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment