Search Issue Tracker
Fixed in 5.3.0
Votes
0
Found in
5.0.0b13
Issue ID
647417
Regression
No
[Terrain] Long baking times for non-default terrain sizes
To reproduce:
1. Create a terrain
2. Resize it to 100x100 or 1000x1000
3. Notice how much longer it gets (due to Clustering for smaller ones or LightTransport for bigger ones)
Full data for default terrain with only size changed (cache was cleaned between every bake):
goo.gl/KSW9ky
Will users be required to change parameters based on the size to make it more optimal? Can we do it ourselves?
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Add comment