Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
5.5.0b4
Issue ID
833542
Regression
No
[TerrainSettings] MaxMeshTrees doesn't affect rendered tree meshes
Steps to repro:
1. Open Unity;
2. Open attached project and 'test' scene;
3. Select 'Terrain' gameobject in the Hierarchy view;
4. Go to TerrainSettings tab in the inspector;
5. Observe tree rendering;
Actual result:
More than 5 mesh trees are rendered, though in Max Tree Settings value '5' is set (see attached actual.png screenshot).
Expected result:
5 mesh trees should be rendered in the scene; other should be rendered as billboards.
Notes:
- Reproducible in 5.5.0b4, 5.4.2p1, 5.3.6p1;
- Reproducible on both OSX 10.11.6 and Windows 10;
- Toggling Max Mesh Trees has no effect on actively rendered trees;
- Also reproducible in standalone builds.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- NullReferenceException errors appear in the Console when changing the values of Visual Effect Control Clip Events' Attributes
- Crash on TextCore::OTL_TableReader::GetOpenTypeLayoutTables when using Japanese Font as TMP Fallback
- TreeView.AddItem performance regression when opening EditorWindow
- Shadows are not visible in Player when using DX12 with Forward+ or Deferred+ rendering in URP
- Rendering Debugger Playmode debug UI scrolling is jittery when using click and drag to scroll
Add comment