Search Issue Tracker
Fixed in 2018.3.X
Votes
4
Found in
2017.1.0a1
2017.2.0p2
Issue ID
977963
Regression
Yes
CPU use spikes on Terrain.GenerateBasemap when disabling/enabling Terrain object in combination with certain Window Layouts
Steps to reproduce:
In Editor:
1. Open Scene "Bronze" from the attached project "Terrain_generateBaseMap.zip"
2. Make sure Editor Windows are laid out like the following (or just have it laid out like in the attached screenshot "layout.png"):
-Profiler and Game panels are visible
-Scene panel is not visible
3. Select "Terrain - Bronze (1)" and enable/disable it via the inspector
4. In the Profiler, you'll see Terrain.GenerateBasemap spike when re-enabling the GameObject.
In Dev Build:
1. Open Scene "Bronze" from the attached project "Terrain_generateBaseMap.zip"
2. Build the project for Player/standalone build
3. With the Game window focused, press space bar to enable or disable the GameObject "Terrain - Bronze (1)".
4. In the Profiler, you'll see Terrain.GenerateBasemap spike when re-enabling the GameObject.
Reproduced with: 2017.1.0a1, 2017.1.1f1, 2017.2.0p2, 2018.1.0a6
Not reproduced with: 5.6.0f3, 5.6.4f1
Regression introduced in: 2017.1.0a1
Comments (1)
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
- “FocusController has unprocessed focus events.” warnings are thrown after adding iOS, tvOS or visionOS Build Profiles
- Holes and different colors appear on default Tree Materials after applying them to the Tree GameObject and undoing changes
- Error indicating that the Text Asset Importer hasn't been disposed properly is logged when switching Importer Type in a Focused Inspector
- Documentation installation shows "Install failed: Validation Failed" when installing Android Build Support module
- Error indicating that the Package Manifest Importer hasn't been disposed properly is logged when switching Importer Type in a Focused Inspector
bhecra
Mar 22, 2018 23:13
Yo tengo un terreno muy grande, dividido en partes pequeñas. Lo que hago es activar y desactivar el GameObject de la escena para optimizar y me pasa exactamente lo mismo, me salen esos picos pero con unity 2017.3.1f1, lo tengo con unity 5.6.3 y no tengo ese problema.
Cómo podria solucionarlo?