Search Issue Tracker
By Design
Votes
0
Found in
5.4.0a6
Issue ID
755099
Regression
No
[HardwareInstancing][AssetBundles]Non-instanced draw calls are increased after importing instanced prefabs by using AssetBundles
Steps to reproduce:
1. Open Unity;
2. Open attached 'Instancing-Example' project and 'Main.unity' scene;
3. Enter Play mode;
4. Observe Rendering tab inside Profiler window;
5. Notice that instanced draw calls are batched, that means that instancing works correctly;
6. Close Unity;
7. Open Unity;
8. Open attached 'Instancing-Example_bundle" project;
9. Open 'main.unity' scene;
10. Notice that in this scene all prefabs with instanced shaders are loaded via AssetBundles;
11. Enter Play mode;
12. Observe Rendering tab inside Profiler window.
Actual result:
Non-instancing draw calls are increased comparing to initial project without AssetBundles (see attached actual.png screenshot).
Expected result:
Instancing should produce consistent behaviour when using AssetBundles loading, that means that non-instanced draw calls should be the same as in the initial project (see attached expected.png screenshot).
Notes:
- Reproduced on 5.4.0a6 and on 5.4.0b1 for Windows 10.
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
Add comment