Search Issue Tracker
Won't Fix
Won't Fix in 2.1.X
Votes
2
Found in [Package]
1.19.19
1.21.21
2.1.0
Issue ID
ADDR-3719
Regression
No
Terrain is not visible in Player when loaded from an AssetBundle and Terrain.drawInstanced is enabled
Reproduction steps:
1. Open the “ReproProject“ project
2. Build and run the project (File > Build And Run)
3. Press the “Q” button in the Player
4. Observe the Player
Expected result: Terrain appears and is visible on the right side
Actual result: The Terrain does not appear and is not visible on the right side
Reproducible with: 1.19.19, 1.21.21 (2021.3.40f1, 2022.3.37f1, 6000.0.11f1), 2.1.0 (6000.0.11f1)
Reproducible on: Windows 11 Pro (22H2)
Not reproducible on: No other environment tested
Note: Does not reproduce in the Editor, pressing “Q” in Play Mode makes the Terrain appear on the right side
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
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- Module installation fails with "Download failed: Validation Failed" errors when using beta.2 Hub version
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Shader Graph Category dropdown cannot be expanded/collapsed when clicking on the text
- Different text alignment in the column header in Entities "System" window
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.
Resolution Note (2.1.X):
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.