Search Issue Tracker
By Design
Votes
2
Found in
2019.4
2020.1.0b13
2020.2
Issue ID
1261269
Regression
No
Mesh with VertexAttribute.Position format set to Float16 does not receive any projection from the Projector
How to reproduce:
1. Open the user's attached "ProjectorFloat16-2020.1.zip" project
2. Open the "SampleScene" Scene
3. Observe the meshes in the Scene view
Expected result: Both meshes with Float16 and Float32 positions receive shadows from the Projector
Actual result: Left mesh with Float32 position receives shadows, Right mesh with Float16 position does not
Reproducible with: 2019.4.3f1, 2020.1.0b15, 2020.2.0a17
Could not test with: 2018.4.24f1 (VertexAttributeDescriptor not available)
Notes:
- The issue is reproducible in the Editor and on Windows, Mac build
- The issue is reproducible with both Projector/Light and Projector/Multiply materials
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
- [URP][Lighting] The skybox doesn't render after changing the settings of the Material when using the URP Render Pipeline
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
Resolution Note:
By design, user code was constructing vertex data with w=0 values for the position, and some shaders (Projector one of them) do not expect that. Fixing code to produce w=1 values fixes it.