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
242
Found in
4.3.1f1
Issue ID
579985
Regression
Yes
The amount of mesh trees being rendered does not change when changing the Max Mesh Trees value
Steps to reproduce :
- create a new project
- create a terrain and a tree
- in the terrain component open the Place Tree option
- add the tree
- select Mass Place Trees
- in the settings panel of the terrain change the max mesh trees value and notice that it does not change the amount of mesh trees being rendered
*Note :
Regression from 4.2.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
RobbyZ
Dec 31, 2019 02:31
Also having this issue on 2018.4.2f1
Perillio
Jul 09, 2019 11:06
Problem still exist on Unity 2019.1.8f0 ...
Terrain:
500x500x100
3 Layers painted on it
1 sort of tree made with Speedtree (a small Bush)
System:
AMD-FX 8320e 8 core
nVidia GTX 970 4GB
32GB DDR3
Usages:
CPU 1%
RAM 18%
GPU 2%
Cant see why there is a frameratedrop to 13 fps because GPU and CPU is almost doing nothing.
Marcos-Elias
Jul 04, 2017 15:54
I'm on 5.6 and apparently this still happens... :(
RSH1
Mar 05, 2017 15:05
Still getting this issue in 2017...
JohnRambozo
May 09, 2015 19:51
AMD FX 8350 4.0 ghz, 8 gigs ram, Radeon HD7850 GPU 2gb video ram.
Getting 16-30 FPS at 1920x1080 Max Settings in Rust. Fewer trees = better FPS.
Please focus on this problem asap as it appears to have been reported in 2013. :(
dickdefrag
May 08, 2015 22:06
I'm begging you to focus on this issue, it would really improve performance of your engine.
Neomarine
May 08, 2015 19:08
Please fix this asap!
cinders
May 08, 2015 18:43
Please fix this. Severely regretting that we switched to Unity 5 because of the performance hit. : (
XJackieChanX
May 08, 2015 18:25
Please fix this. It makes Rust quite an issue for most players
Danijel98
May 08, 2015 15:53
This is the main problem me and the company I work in are dealing with at the moment, please fix this, as it seems like this ambitious shift to Unity 5 is not a good idea on our part so far.