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
2020.1.0a18
Issue ID
1207755
Regression
No
[PLM] 'Firefly' artifacts after baking the project with high lightmap resolution and padding
Steps to repro:
1. Open the attached project;
2. In the Lighting window press 'Generate Lighting' button;
3. Wait for the baking to finish.
Actual result:
'Firefly' artifact are visible on the floor after baking the project with high lightmap resolution and padding.
Expected result:
No artifacts are visible on the floor.
Notes:
- Reproducible in 2020.1.0a18, 2019.3.0f4;
- Could not test in 2019.2.17f1, since all the geometry is black;
- Not reproducible with lightmap resolution=1 and lightmap padding=1;
- Reproducible when baking with both CPU and GPU lightmappers;
- Workaround is add pushoff to the embedded mesh on the ground. There is a screenshot of the setting in the thread.
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note (2020.1.X):
This is a larger task of refactoring the compositing step of the directionality output of lightmapping. This will be handled as part of our regular sprints.