Search Issue Tracker
Fixed
Fixed in 2021.3.7f1, 2022.1.8f1
Votes
0
Found in
2021.3.3f1
2022.1.1f1
Issue ID
UUM-827
Regression
No
[Backport] Duplicate Unlit Particle System draw calls can't be batched when there are multiple Lights in the Scene
Reproduction steps:
1. Open the user's attached "UnlitBatchingRepro.zip" project
2. Open the "BatchBroken" Scene
3. Enter Play mode
4. Open the Frame Debugger (Window > Analysis > Frame Debugger)
5. Enable Frame Debugging
6. Select the "Particle System (1)" draw call
7. Observe the panel to the right of the draw call list
Expected result: The draw call is batched, no such message as "objects are affected by different forward lights"
Actual result: A message says that this draw call can't be batched with the previous one because "objects are affected by different forward lights"
Reproducible with: 2019.4.36f1, 2020.3.29f1, 2021.2.12f1, 2022.1.0b8, 2022.2.0a5
Notes:
- Reproducible with Realtime, Mixed, and Baked Lights with the Built-in RP
- Does not seem to happen in either Universal RP or HDRP
- Tested with macOS
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note (fix version 2022.1.8f1):
Fixed in 2022.1.8f1