Search Issue Tracker
Won't Fix
Votes
2
Found in
6000.0.26f1
6000.1.0a7
6000.2.0a1
Issue ID
UUM-89979
Regression
Yes
Average FPS in Play Mode degradation on a newly created BiRP project when it's upgraded from 2020.3.48f1 to a newer Editor version
Reproduction steps:
1. Create a new "3D (Built-In Render Pipeline)" project on 2020.3.48f1 with Unity Hub
2. Open the created project
3. Enter the Play Mode
4. In the Play Mode overlay, press the "Stats" button
5. Observe the FPS (on the machine this was tested on, average FPS was around 700-800)
6. Exit the project
7. Open the same project with a newer version
8. Enter the Play Mode
9. Observe the FPS in the "Stats" window
Expected result: Average FPS stays about the same as in 2020.3.48f1
Actual result: Average FPS goes down to around 500-600 (depends on the machine)
Reproducible with (when upgraded to): 2023.1.0a20, 6000.0.30f1, 6000.1.0a7
Not reproducible with (when upgraded to): 2021.3.46f1, 2022.3.53f1, 2023.1.0a19
Reproducible on: Windows 10 (22H2)
Not reproducible on: No other environments tested
Notes:
* The results can easily be inconsistent depending on the other processes running on the computer, so it’s best to test this on a freshly restarted computer with no other applications running in the background
* Player, with VSync disabled, shows around 3000 FPS (used a custom script to display the “Stats“ information on the screen), so will leave this as the Editor issue
* Tested on Alienware M15 R4, 32 GB RAM, i9-10980HK @ 2.40GHz, NVIDIA GeForce RTX 3080
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
- Undoing Animator Parameter name change breaks references to it
- Crash on BV4_OverlapBoxAll when moving in play mode
- Custom mesh water surface normal map fades out when Y Position increases
- Sprite renderer does not issue draw calls correctly when using SRP Batcher
- [Android] Flickering artifacts when using "ScriptableRenderer.EnqueuePass(RenderPassEvent.BeforeRenderingPostProcessing)" multiple times
Resolution Note:
We've investigated the cause of this slowdown, and there is a small difference in font rendering time showing in Play Mode in the Editor. This particular difference does not appear to get worse with larger projects, so in a project running at 30fps (rather than 700fps) the <1ms time will make little difference.
However, I see that there was another Discussions thread this originally linked to that was not related to playmode performance. I've replied there and am attempting to get the reproduction project for that. Will open a new bug for that if/when I get it and link it to this one.
(Have marker this as "Won't Fix", but could also have been "As Designed" since UI was deliberately changed in between these versions.)