Search Unity

Bug Significant performance regression. 2020.3 > 2021.3/2022.2

Discussion in 'VR' started by aducceschi, Oct 18, 2022.

  1. aducceschi

    aducceschi

    Joined:
    Feb 9, 2022
    Posts:
    39
    Hi! I have updated my project from 2020.3 to 2022.2.0b11. I work on a Quest 2. Before I had a solid 90 FPS and after updating I have a framerate of around 65-70FPS. I have compared profilers results from both versions, and for whatever reason the "EarlyUpdate.XRUpdate" call has increased its cost of 3ms to around 6-8ms consistently. Does anybody by chance know why this is the case? (I have deep profile turned on but it doesn't tell me what this call does). I compile the project always with IL2CPP on Master mode. And I use DOTS, which I updated from 0.51 to 1.0. I use Vulkan and use nearly all Vulkan optimizations provided in the project settings.

    Before updating:
    Average.png

    After updating:
    Screenshot_2022-10-18_at_17.11.05.png
    Also it has a really weird pattern now, which disappears if I toggle the cost from the graph.
     
  2. Cloudwalker_

    Cloudwalker_

    Joined:
    Jan 3, 2014
    Posts:
    140
    Unity is not monitoring these forums for performance reports, if you want their attention you need to file a bug report. Make sure to reference this ticket if you are using URP, maybe even if you aren't using URP reference it anyway

    https://issuetracker.unity3d.com/issues/meta-quest-performance-loss-between-urp-versions-when-built
     
    aducceschi, glenneroo and DevDunk like this.
  3. aducceschi

    aducceschi

    Joined:
    Feb 9, 2022
    Posts:
    39
    I'll post a bug report then, but I posted this here in hopes that someone might know a solution for this. Thanks for pointing this ticket to me!
     
    Last edited: Oct 19, 2022