Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.0.54f1
6000.1.14f1
6000.2.0f1
Issue ID
UUM-113861
Regression
No
[HDRP] "Inl_APVDiskStreamingUpdate" and "Inl_APVCellStreamingUpdate" cause poor Adaptive Probe Volume streaming performance at start when using a relatively large APV baking set, but improve after some time
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Levels/worldBlockout_mk2/Scenes/persistent_scene.unity” Scene
3. Open the Profiler (Window > Analysis > Profiler)
4. Enter the Play Mode
5. Play for 5 - 10 minutes while observing the Profiler and FPS in the Stats tab
Expected result: FPS is always 37-45 and does not improve after a while
Actual result: After playing for some time, FPS improves, from 15 to 37-45, and fewer spikes become present in the Profiler
Reproducible with: 6000.0.54f1, 6000.1.14f1, 6000.2.0f1
Could not test with: 2022.3.62f1, 6000.3.0a4 (Assets\Systems\IntelSystem\SO\RumourNodeSO.cs(11,10): error CS0592: Attribute 'SerializeField' is not valid on this declaration type. It is only valid on 'field' declarations.)
Reproducible on:
Play Mode
Not reproducible on:
Windows Standalone Player
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
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
- Location tooltip in the Viewport of UI Builder window does not update when the UI Document Asset is moved to a different location
- Audio Clip Volume and Avoid Repeating Last fields values cannot be changed in Audio Random Container window
- Setting a variable in the root selector via an imported USS file in a theme does not work
- No character limit when creating a new Scene with excessively long name, Editor can be forced to crash
- URP Decal Projector flickers/glitches when added to Cube or Quad GameObjects as a Component
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.