Would be nice to get some kind of official confirmation that it is known and being looked at. It’s not the kind of thing where it makes a lot of sense to submit a bug report. The repro steps are… try Unity 6.3. It’s not really feasible for us to attach multiple Unity versions of the same giant project.
1 Like
Sorry, but why exactly:
Clone the project → Upgrade it to 6.3 → Deep profile both → Compare and find the culprit → Create a minimal repro project and report
isn’t a viable option?
That’s what I am trying right now… But having to setup a nearly 1TB project twice on one machine is a bit of a challenge and very time consuming.
1 Like
So first profiling session revealed that our main performance drop of constant 0.2ms comes from post processing in XR (process RG_UberPost). There seems to have been changes, probably with the introduction of tile based post processing in Unity 6.3, which now seem to have negative impact on regular XR post processing. I’ll make a separate thread about this one, as it’s XR related only.
There is another very big performance issue related to the Unity hair package we are using. I guess it’s related to LOD of rendering, but we need to investigate deeper on that one.
Edit: Here is link to my separate post about XR post processing performance regression: