Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
5.4.4p3
Issue ID
881138
Regression
No
Self-shadowing artefacts appear on players and editor
Steps to reproduce:
1. Open attached project
2. Open scene test
3. Notice artifacts visible on cube. You can select "Main Camera" and "Allight View With Selected"
4. Build and run on device
5. Notice that artefacts are still present
Increasing shadow bias to ~0.5 makes artefacts disappear
Not reproducible: 5.3.7p4
Reproduced with: 5.4.0b4, 5.4.4p3, 5.6.0b7
Nexus 9, Android 7.0 (artefacts only on 5.4+)
Huawei P8, Android 6.0 (artefacts only on 5.4+)
Galaxy S6, Android 6.0 (artefacts only on 5.4+)
Meizu MX5, Android 5.1 (Had artefacts on 5.3 too, but on 5.4+ they are much more visible)
IPad Pro (9.7 inch), iOS 9.3.1 (artefacts only on 5.4+)
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