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
- Tile Palette grid is moved after entering Play Mode
- Tile Palette Edit mode turns off in Play Mode
- The Editor crashes when Generating Font Atlas in the Font Asset Creator with “9999999999” padding and 256x256 Atlas Resolution
- [iOS] An “ArgumentNullException” error is thrown when GetIntroductoryPriceDictionary() method is called
- Memory leak warnings are constantly thrown when Generating Font Atlas in Font Asset Creator with 4096x8192 Atlas Resolution
Add comment