Search Issue Tracker
Won't Fix
Votes
2
Found in
5.3.4f1
Issue ID
790583
Regression
No
Lightmaps for objects far away from transform origin have artefacts
Workaround: assign a http://docs.unity3d.com/Manual/LightmapParameters.html to the distant mesh and set pushoff to a higher value. This should take care of the floating point precision issues on faraway objects.
Cause: A high pushoff value means that the raytrace is started further from the surface of the objects. This can lead to artefacts if the pushoff is too high, caused by floating point inaccuracies. It will not slow down the bake.
Steps to reproduce:
1. Open attached project "790583.zip"
2. Open scene "test"
3. In hierarchy, select "Far" and notice that its position is (3000, 3000, 3000)
4. In lighting window, build lightmap
5. In hierarchy, double click on "Far" to focus on it
6. Notice artefacts
Note: Some artefacts are also visible when "Far" is as close as (500, 500, 500)
Reproduced with: 5.1.4f1, 5.2.4f1, 5.3.4p5, 5.4.0b16
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- 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
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Add comment