Straight up conversion of a Quest 2 BIRP 2020.3.48 project (btw, kuddos for keeping things compatible enough)
Hardware Monitor:
2020.lts version run at 72 fps steady
U6 however runs at 54 fps.
A 25% drop in performance!
Whatever is being done to stop this decay isn’t working.
After upgrading a project, you may have to wade through at least Player settings (possibly also Graphics, Quality) to check for any new settings or changed defaults.
For instance, when you use a default Player setting that has the effect of “fast but possible issues” and Unity for whatever reason changes that default in the new editor version (or removes it, or splits it and adds multiple sub-toggles), it may now be set to “slow but more compatible” and for this alone you may now experience a performance regression. I’ve had that happen to my projects before.
Check if you can bump the fps by making a few settings adjustments. All the while adjusting the same setting (if available) in the old project to keep both builds comparable.
Also worth noting is that BIRP is now legacy in U6 and just because of that there may be less or little or no time spent on maintaining its performance. You may want to try 2022.3 as well.
Thanks for the reminder @CodeSmile, I forgot the default shuffle, so I verified and the settings are the same.
Hi. This issue appears even on a freshly created 3D BiRP project. I’ve filled out a bug report for this and the developers are currently looking into it. You can follow the progress here (link will be reachable in about an hour). Thank you for reporting this!
Hi @laurentlavigne !
We’re investigating the bug that Jonas mentioned, but it doesn’t look to me like it will fix the issue you’ve raised here. Are you able to share anything with us to help us track down where the difference is? Access to the project or before/after profiler captures would make it easier for us to figure out what’s slower in your specific case.
Sure, you can DM me a upload link and I’ll send you that.
Thanks.
Hi all. I’ve closed the bug we had for this originally because it’s actually describing a different and more minor problem. @laurentlavigne - I dropped you a DM but am still waiting for a reply! I’d like to open a new bug about this issue which seems more serious.
