Search Issue Tracker
Feature Request
Feature Request in 5.3.X
Votes
0
Found in [Package]
5.3.0
Issue ID
WBTRB-163
Regression
No
Draw Instanced is disabled by default on a new Terrain GameObject
Reproduction steps:
1. Create a new project
2. Install the “com.unity.terrain-tools” package
3. Create a new Terrain GameObject in the Hierarchy (3D Object > Terrain)
4. Select the newly created “Terrain“ GameObject
5. Go into the Terrain Component’s settings tab in the Inspector
6. Observe the “Draw Instanced“ option
Expected result: “Draw Instanced“ is enabled by default
Actual result: “Draw Instanced“ is disabled
Reproducible with: 5.3.0 (6000.0.57f1, 6000.1.16f1, 6000.2.3f1, 6000.3.0b1)
Reproducible on: M1 Max MacOS 15.5 (Tested by CQA)
Not reproducible on: No other environment tested
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thank you for bringing this issue to our attention! After thoroughly reviewing the reported issue, we’ve determined that the functionality in question is operating as designed. However, we recognize that there is an opportunity for improvement or enhancement to better meet your needs.
As a result, we’ve converted this bug report into a feature request to explore the possibility of implementing this change in future product updates. Our team will assess this request as part of our ongoing development planning, prioritizing it alongside other enhancements and improvements based on feasibility and impact.
We truly appreciate your feedback, as it plays a crucial role in shaping the future of our product. If you have additional details or thoughts about this feature, don’t hesitate to share them with us.
Thank you again for your input and understanding!
Resolution Note (5.3.X):
Thank you for bringing this issue to our attention! After thoroughly reviewing the reported issue, we’ve determined that the functionality in question is operating as designed. However, we recognize that there is an opportunity for improvement or enhancement to better meet your needs.
As a result, we’ve converted this bug report into a feature request to explore the possibility of implementing this change in future product updates. Our team will assess this request as part of our ongoing development planning, prioritizing it alongside other enhancements and improvements based on feasibility and impact.
We truly appreciate your feedback, as it plays a crucial role in shaping the future of our product. If you have additional details or thoughts about this feature, don’t hesitate to share them with us.
Thank you again for your input and understanding!