Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.3
2020.1
Issue ID
1180450
Regression
No
Visualization baked albedo is broken for rescaled terrains
If you draw a pattern on a terrain surface and then resize the terrain (using terrain settings), the pattern may be stretched differently when shown in the Shaded visualization mode and the "Baked Albedo" visualization.
Repro:
1) Create a new legacy/builtin project.
2) Create a terrain and set size to 100x100 (terrain settings)
3) Add two terrain layers and draw a recognizable pattern (e.g. an "X")
4) Set size to 300x300
5) Bake and inspect the Albedo visualization.
Expected: The drawn pattern should appear in the same positions in Baked Albedo and Shaded view, i.e. the modes should "agree" on the position and size of the drawn pattern.
Actual: They don't. It seems the Shaded views properly stretches the drawn pattern while the Baked Albedo view stretches it too much.
Note: Under the assumption that the Shaded view is showing the patterns correctly, it seems that the final bake is also correct. This suggest that the bug is in the Albedo visualization code.
Verified in 2020.1.0a1.
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
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
- Editor crashes on D3D12GetInterface when repeatedly enabling and disabling 256 text components
- Flickering bright white dots in the Scene when the Android Platform is selected and DX11 Graphics API is used with Iris(R) Xe Graphics GPU
- Inconsistent capitalization and misaligned text in multiple query blocks in Search window
Resolution Note (2020.1.X):
This issue has been identified as having low priority and has been closed without a fix. If the bug has no workaround and is blocking your production please feel free to reopen it with any additional information you might have. Sorry for the inconvenience this might cause.