Search Issue Tracker
Fixed in 2018.2.X
Votes
0
Found in
2018.1.6f1
Issue ID
1051872
Regression
No
Editor lacks Render Loop Job call when using Frame Debugger to inspect dynamic batching
To reproduce:
1. Open attached project
2. Open Frame debugger
3. Enter Play mode, check Frame debugger Loop Job calls
4. Build for Android, check Frame debugger Render Loop Job calls when built
Expected: Editor has same count of Render Loop Job calls as other platforms (3 calls)
Actual: Editor has Render Loop Job call missing (2 calls)
Reproduced in: 2018.1.8f1, 2018.2.0b3
Not reproduced in: 2018.2.0b4, 2018.2.0f2, 2018.3.0a5
Note: compared platforms - Editor, Android, Windows Standalone
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Graphics Settings: “Use Defaults” checkboxes misaligned in Tier Settings section
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- 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
Add comment