Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.4
2019.3.4f1
2020.2
Issue ID
1231998
Regression
No
GameObject with a Rigidbody colliding with Terrain causes massive FPS drops when Heightmap Resolution is set to 4097x4097
Reproduction steps:
1. Open the project from the attached file "1231998.zip"
2. Open "SampleScene" and enter Play Mode
3. Inspect FPS in the Statistics window(upper right corner of the Game View) at time of collision
Expected result: FPS is stable
Actual result: massive FPS drop
Reproducible with: 2018.4.22f1, 2019.3.11f1, 2020.1.0b6, 2020.2.0a8
Notes:
- Profiler shows that the frame rate drop is caused by Physics
- Also reproducible when dragging the GameObject along the terrain
- GameObject scale is set to 50x50x50
- Increasing GameObjects scale, increases the FPS drop
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Quest] Pitch Shifter causes audio degradation on Quest 2 devices when sped up
- "GUI Error: Invalid GUILayout" and "NullReferenceException" are thrown when adding Scenes to "Scenes in Baking Set" in Adaptive Probe Volumes
- Inspector window not updating when switching GameObjects in Play Mode while having a VR headset connected
- “UnityException: GetInvalidFilenameChars” errors are thrown, and the Overlay Save Preset button becomes unusable when entering Play Mode with a shortcut while Overlay Save Preset window is opened
- "UnityException: GetName can only be called from the main thread." erors are thrown when the Shortcuts window is opened and entering Play Mode with a shortcut
Add comment