Search Issue Tracker
In Progress
In Progress in 1.4.X
Votes
0
Found in [Package]
1.4.0-pre.3 - Physics
Issue ID
ECSB-1732
Regression
No
Excessive CPU usage happens when a Mesh Collider is attached to imported .blend models
How to reproduce:
1. Open the attached “IN-105787” project
2. Open the “Test” Scene and and expand the foldout in the Hierarchy
3. Enable and expand the “New Sub Scene”
4. Disable GameObjects “Ship_FBXImport_NotLaggy_A” and “Ship_FBXImport_NotLaggy_B”
5. Enter Play mode
6. Open the Profiler window and start recording the Profiler information by clicking the red button
7. Observe the result
Expected result: The CPU Usage does not consistently exceed the target frame time
Actual result: The CPU Usage consistently exceeds the target frame time
Reproducible with: 1.2.1 (2022.3.64f1), 1.4.0-pre.3 (2022.3.64f1, 6000.0.53f1, 6000.1.11f1, 6000.2.0b9, 6000.3.0a1)
Reproduced on: Windows 11
Not reproduced on: No other environment tested
Notes:
- The issue does not occur when the “Ship_BlenderImport_Laggy_A” and “Ship_BlenderImport_Laggy_B” GameObjects are marked as Static
- The user reports that the memory size for the Blender Import is very large when viewed in the Entities Hierarchy Inspector View for the Physics Collider
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Memory leak occurs when focused on Player while using Direct3D12
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
Add comment