Search Issue Tracker
Fixed in 5.0.X
Votes
50
Found in
4.3.4f1
Issue ID
595705
Regression
Yes
Terrain tree culling performance regression
This bug has been fixed. However, some similar regression bugs are suspected to still exist.
Please file new bug reports for them.
To reproduce:
1. Download project from case 597792
2. Open it on 4.1.5f1
3. Enter play mode
4. Note performance in profiler
5. Open the same project in 4.3.4f1
6. Enter play mode
5. Note dropped performance in profiler (as can be seen in attached screenshot)
Expected result: Similar performance
Actual result: a huge performance drop
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
GeorgeIng
Jun 29, 2015 12:27
This still seems to be a massive problem - any ETA on when we might expect a fix?
TheOtherMonarch
Apr 17, 2015 18:45
Hope this is fixed soon :( it seems to take 6 months plus to fix these major bugs.
zniszczacz666
Apr 03, 2015 12:26
Im adding myself to DAHRRR's question. When we could expect version with this fix... After 2 patches it still have "Status: Fixed in future release ".
k0mbain
Mar 27, 2015 13:58
Indeed, fixed in future release hangs too long. It's over a year since initial notification.
Jog
Mar 27, 2015 09:15
+1
dahrrr
Mar 26, 2015 12:26
When we could expect version with this fix... After 2 patches it still have "Status: Fixed in future release "
Griautis
Mar 13, 2015 13:11
Hello everyone,
An update about this one: This bug has been fixed. However, some similar regression bugs are suspected to still exist.
Please file new bug reports for them.
I've also added the info inside the description.
GoGoGadget
Feb 13, 2015 05:43
Seems like this is still an issue... Really? 4ms for this on my terrain, this is completely unacceptable.
frostbitenl
Feb 02, 2015 14:09
Currently using 5.0.0.b18 and still experiencing this issue. This is a total performance killer on our open world game.
Jog
Feb 01, 2015 19:51
It is totally killing our game performance. Should be fixed ASAP otherwise engine is being broken for any Open World production.