Search Issue Tracker
Fixed in 7.1.1
Votes
0
Found in [Package]
3.3.0
Issue ID
1048287
Regression
No
Lightweight render pipeline creates unpredictable batches when used with GPU instancing and point or spot light
How to reproduce:
1. Open user's attached project
2. Enter Game mode
3. Enable Frame Debugger
4. Select Frame Debugger's slider and slide it on a second job
5. While stepping forward inside Frame Debugger keep an eye on the Game View
6. Notice how many batches are created with only one GameObject
Expected result: GameObjects are created in similar sized batches
Actual result: GameObjects are created in very random sized batches between 1 - 20+ at a time
Reproducible with: 2018.1.5f1, 2018.2.0b8, 2018.3.0a2
Not reproducible with: 2017.x (Lightweight Render Pipeline introduced in 2018.1)
Note: while using directional or area light type, batches are similar and there are no batches containing only one GameObject
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 7.1.1):
Fixed by SRP batcher.