Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.21.20
2.0.8
Issue ID
ADDR-3652
Regression
No
Terrain material is rendered incorrectly when changing a scene and instancing a Terrain using Addressables in Play Mode
How to reproduce:
1. Open the “TerrainProblem.zip“ project
2. Open the “SampleScene”
3. Open the Addressables Groups window
4. Build the Addressable group using the “Default Build Script” option
5. Select the “Use Existing Build“ for “Play Mode Script“
6. Enter the Play Mode
7. Click on “Load Scene“ in the Game view
8. Observe the Game view window
Expected results: Material for the Terrain is rendered correctly
Actual results: Material for the Terrain is rendered incorrectly (more shiny) than it is supposed to be
Reproducible in: 1.21.20 (2021.3.36f1, 2022.3.21f1, 2023.2.15f1), 2.0.8 (6000.0.0b11)
Could not reproduce in: 2.0.8 (2023.2.15f1) (System.Exception console errors preventing from Loading a Scene)
Reproduced on: Windows 11 Pro (23H2)
Not reproduced on: No other environment tested
Notes:
- If in the Inspector in the Play Mode the “Draw Instanced“ field is checked, the mesh will not be rendered at all
- There are a couple of workarounds:
- Reasign the Terrain Material in the Inspector in Play Mode after loading the scene
- Select the ”Use Asset Database“ for “Play Mode Script“ in the Adressables Groups window
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
- [VFX] Missing Expand Option with Output Slot
- [OpenGLES][XR] Zooming in on the camera's URP opaque texture causes "double vision" on Quest in OpenGLES3
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.