Search Issue Tracker
Fixed in 5.3.6
Votes
0
Found in
5.3.4p6
Issue ID
797235
Regression
No
Use Light Probes setting remains 'Enabled' when the object is marked as Static
How to reproduce:
1. Open attached project
2. Open scene Scene.unity
3. In the Hierarchy window, select the search mode to Type and search for “MeshRenderer”
4. Select all the objects that were found, except for the ones named “Window_01” and “Store_Closed_Small_A_01_Occluder”
5. Mark all the objects as Static
- Don’t deselect the objects at any point, or risk having to reselect them
6. In the Lightning window, rebuild the Lightmaps
7. Open the profiler window and switch to the Rendering profiler
8. Play the scene
- Note that Draw Calls are getting properly batched (i.e. there are batched draw calls)
9. Stop playing the scene
10. Mark all the objects as non-Static and rebuild the lightmaps
- This is necessary so that the Use Light Probes setting gets enabled
11. Enable the Use Light Probes setting for the Mesh Renderers
12. Mark all the objects as Static and rebuild the lightmaps again
13. Play the scene
- Note that Draw Calls are not getting properly batched anymore in the Profiler
- Light probes are not supported on objects that are marked as Static
- Reproduced in Version 5.3.5f1 (960ebf59018a)
- Not reproducible in Version 5.4.0b18 (cdaae1c8e465). The Use Light Probes setting automatically defaults to disabled on objects marked as Static.
- Not reproducible in Version 5.2.4f1 (98095704e6fe). The Use Light Probes setting is treated as disabled on objects marked as Static.
- A workaround is to manually disable the 'Use Light Probes' setting for each object that is going to be marked as Static
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- NullReferenceException is thrown when adding a Blur Renderer Feature
- [Linux] Dropdown Menus are filled with empty entries when the Menu intersects with the Editors borders
- [HDRP] [Metal] Tiled artefacts when using DRS
- [HDRP] Empty template starts with incorrect Physically Based Sky ground
- Big chunk of "Untracked" memory in the Memory Profiler screenshot when a custom .obj file is loaded while in Play Mode
Add comment