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
- UI Toolkit Debugger search text cursor and background text are overlapping
- Screen.resolutions does not return the correct list of supported resolutions when called on a MacBook Pro with a notch
- Changing Environment Profiles in Lighting window throws "NullReferenceException" error
- Imported FBX is rendered differently in Game view when comparing to Scene view
- "GetAllOverlapping failed" Error displayed in console or endless loading process on Application.Message.LeftButtonUp when cycle-selecting GameObjects with GPU Resident Drawer enabled
Add comment