Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2020.1.X
Votes
0
Found in
2020.1
2020.2
2020.2.0a18
Issue ID
1263936
Regression
No
[DXR] SNorm16 can't be used for mesh's normals when ray traced reflections are enabled
How to reproduce:
1. Open the attached project named "Case_1263936"
2. Open the Test Scene and enter Play mode
3. Observe two meshes and their reflections in the Game view
Expected result: Both meshes are drawn correctly and receive accurate ray-traced reflections
Actual result: The reflection of the mesh which uses SNorm16 for normals is completely black indicating the SNorm16 normal attribute is missing in the ray-traced reflection
Reproducible with: 2020.1.0f1(8.1.0, 8.2.0), 2020.2.0a18(9.0.0-preview.38, 10.0.0-preview.19)
Could not test with: 2018.4.26f1(DXR was not yet available), 2019.4.5f1(Error when entering Play mode - RayTracing for Dynamic Geometry not implemented yet.)
Notes:
1. When ray-traced reflections are not used, the expected reflection is rendered for the SNorm16 mesh
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
- 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
Resolution Note (fix version 2020.2):
Fixed in - 2020.2.0b1