Search Issue Tracker
Won't Fix
Votes
3
Found in
2021.3.21f1
2022.2.11f1
2023.1.0b8
2023.2.0a6
2023.3.0a3
Issue ID
UUM-30755
Regression
No
Lights are only rendered on painted Terrain Textures of certain Layers when a certain Rendering Layer is selected
How to reproduce:
1. Open the attached user project “22_Testing.zip“
2. Open Scene “SampleScene“
3. Observe the “BadTerrain“ GameObject
Expected result: The “DirtLayer“ painted textures on the “BadTerrain“ GameObject are rendered bright
Actual result: The “DirtLayer“ painted textures on the “BadTerrain“ GameObject are rendered dark
Reproducible with: 2021.3.21f1, 2022.2.11f1, 2023.1.0b8, 2023.2.0a6
Can’t test with: 2020.3.46f1 (Rendering Layers feature doesn't exist)
Reproduced on: macOS 13.0.1 (Intel), Windows 10 (by reporter)
Note:
- Issue is reproducible in Builds
- Issue is reproducible if Rendering Path is set to Deferred (in the “URP_Renderer“ asset)
- Issue is only reproducible with the fifth in line “DirtLayer“ Terrain Layer of the Terrains (the Layers can be seen by selecting the “BadTerrain” or “GoodTerrain” GameObjects and selecting the Paint Terrain symbol in the Terrain Component)
- If another Rendering Layer is added (by selecting the “UniversalRenderPipelineGlobalSettings“ asset and pressing the plus symbol below “Rendering Layers (3D)“), the “DirtLayer“ painted texture on the “GoodTerrain“ GameObject becomes dark, unless the Rendering Layer Mask is changed to have the “15 unused Layer” Layer (this can be done by selecting the “GoodTerrain“ GameObject, going to the Inspector, selecting the Terrain configuration options in the Terrain Component, scrolling down and selecting the mentioned Layer in the Rendering Layer Mask option under Lightmapping)
- Some Unity versions might need different Rendering Layers to be selected for the issue to reproduce
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
Thank you for bringing this issue to our attention. Unfortunately, after careful consideration we will not be addressing your issue at this time, as we are currently committed to resolving other higher-priority issues.
We acknowledge that the current Terrain system has a number of limitations, so we are currently investing in a large amount of discovery work to determine exactly what is needed most and how we can bring it to you at the quality level you have come to expect and address the most pervasive pain points in the most effective and efficient manner. However, we know each case is different, so please do continue to log any issues you find, and provide general feedback on our roadmap page to help us prioritize.
Forum to discuss feature requests: https://forum.unity.com/threads/world-building-public-roadmap-and-feature-requests.1437163/
Roadmap: https://unity.com/roadmap/unity-platform/3d-world-building