Search Issue Tracker
Won't Fix
Votes
0
Found in
4.1.2f1
Issue ID
550843
Regression
Yes
Using Draw Calls affects performance in 4.2
Steps to reproduce :
- import the project attached in 4.1
- open LoadTest_UnityGUI and press play, wait for 10-20 seconds; write down FPS and draw calls
- open LoadTest_NGUI and press play, wait for 10-20 seconds; write down FPS
- upgrade the project to 4.2
- open LoadTest_UnityGUI and play, wait for 10-20 seconds - note that FPS dropped even though there's less draw calls
Note :
Regression from 4.1.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- 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
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment