Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.3.X, 6000.0.X, 6000.2.X, 6000.3.X, 6000.4.X
Votes
4
Found in
2021.3.39f1
2022.3.32f1
6000.0.5f1
6000.1.0a7
6000.2.0a1
6000.3.0a1
6000.4.0a1
7000.0.0a1
Issue ID
UUM-73230
Regression
Yes
The number of Batches and Tris is higher than expected when using Application.targetFrameRate
Repro Project provided link:
https://drive.google.com/file/d/1ZSN1UP7q2hm-gXu8Jrjn4Z2wq3L73oLa/view?usp=sharing
How to reproduce:
1. Open the “Test3D” project
2. Open the “Test3D” scene
3. Open the Game View tab
4. Open the Statistics (Stats button)
5. In the Hierarchy, expand the “Main Camera” GameObject
6. Select the “Canvas” GameObject
7. In the Inspector, uncheck the “New Behavior Script” Component
8. Enter the Play Mode
9. Observe the number of Batches and Tris in the Statistics
10. Exit the Play Mode
11. In the Inspector, check the “New Behavior Script” Component
12. Repeat steps 8 and 9
Expected results: The number of Batches and Tris is similar with “New Behavior Script” Component applied
Actual results: The number of Batches and Tris is way higher with “New Behavior Script” Component applied
Reproducible with: 2021.3.39f1, 2022.3.18f1, 2022.3.32f1, 6000.0.5f1
Not reproducible with: 2022.3.17f1
Reproducible on: Windows 10, macOS 14.4 (user’s)
Not reproducible on: No other environment tested
Comments (1)
Add comment
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
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
TheFalconeerDev
Jun 24, 2024 14:05
yeh I have this , and tracked this to exactly 2021.3.35f. 2021.3.34f is fine, Everything new thatn 2021.3.34 is broken in this way.
If you framestep you always get the first frame, ridiculously low tris and batches, then the next frame something normal-esque , the third frame is double or more of the tris or batches.
I assume its some averaging not being calculated properly (to get a smooth value?)