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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Add comment