Search Issue Tracker
Fixed in 8.0.0
Votes
0
Found in [Package]
8a6779d
Issue ID
1147581
Regression
Yes
[XR][HDRP][SPI] Performance problem with built player when vsync is enabled
UPDATE: Changing this bug to track HDRP performance problem. Universal RP performance bug is being tracked in related case 1158037 which should be fixed when PR 98447 is merged. Also flagging this case as Public.
UPDATE: Changing this bug again to track HDRP performance problem with Stereo Instancing, which will be fixed when PR 5417 lands. Even with this fix I still see bad performance with HDRP in Multi Pass stereo, possibly related to culling. I'll investigate and file a separate bug if needed.
Using HDRP, LWRP, or built-in rendering pipelines, built players on Rift are running at 60 fps using vsync with even a simple scene. Disabling vsync gives 85 - 90 fps, depending on which rendering pipeline is used.
With HDRP, Playmode performance in the Editor is higher than built player performance.
See "Case posted to website" section of this bug report for details specific to HDRP, and comments for follow-up testing on the other rendering pipelines.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Nested LocalizedStrings can not query local variables
Add comment