Search Issue Tracker
Won't Fix
Votes
1
Found in
4.0.0f7
Issue ID
512356
Regression
Yes
Terrain Exporting to Beast takes longer than in 3.5.
Terrain Exporting to Beast takes longer then in 3.5.
Repro Steps:
1. Launch 4.0.1f2 with attached project
2. Bake the terrain with / without a normal map texture
- I've not seen a difference in having one or not, though user says he does.
3. The process to export the terrain to Beast takes a lot longer then in 3.5
Desired outcome: Optimize and speed up the process of exporting terrains to beast
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
Add comment