Search Issue Tracker
Fixed in 7.3.0
Votes
0
Found in [Package]
2020.1.0a7
Issue ID
1193602
Regression
No
[Output] Shader errors when compiling the runtime shader of a lit output with exposed, but unassigned additional maps
Repro steps:
1. Open the attached VFX
2. Enable Runtime Mode (Forced)
3. Observe that the effect doesn't render and console errors are shown
Note:
- Affected maps are Mask, Normal, and Emissive. Assigning a texture any of them fixes the issue, except for emissive.
- Emissive seems to throw the error and fail compilation, regardless of whether it has a texture assigned or not
- The Mask map slots throws errors usually if it's on its own (i.e. without Normal or Emissive present).
- Not a regression, repros in 6.9.2
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