Search Issue Tracker
Fixed in 2022.2.X
Votes
0
Found in
2018.4
2019.4
2020.3
2021.1
2021.1.9f1
2021.2
Issue ID
1340282
Regression
No
Low framerate when looking at GameObjects that are far away from Light Probe Group
How to reproduce:
1. Open the attached project "CreateShaderRendererScene.zip"
2. Open “Zone3-Raid1-Lighting” Scene (Assets > AVZ > Lighting > Zone3-Raid1 > Zone3-Raid1-Lighting)
3. Look at the "Sandbags_grup1_temp" GameObjects
Expected result: Framerate is normal when looking at the GameObjects
Actual result: Framerate is low when looking at the GameObjects
Reproducible with: 2018.4.36f1, 2019.4.28f1, 2020.3.13f1, 2021.1.12f1, 2021.2.0b1
Notes:
- If it's not reproducible, make sure there is a generated Lighting Data
- If generating new Lighting Data you might need to reopen the Scene for it to take effect
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
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.0a1, select "Use Ambient Probe" on "Renderer Light Probe Selection" field found in Graphics Settings