Search Issue Tracker
Fixed in 5.6.0
Votes
0
Found in
2017.1.0b1
Issue ID
898851
Regression
No
[GPUInstancing] Instanced objects are drawn through CommandBuffer when 'Enable Instancing' checkbox is unchecked
Steps to repro:
1. Open attached project and 'Main' scene;
2. Notice that there is 'Rock Spawner' gameobject that spawns instanced objects to the scene when launching. The shader for spawned object's material has explicitly disabled instancing flag.;
2. Launch the project.
Expected result:
- Instanced objects are not rendered;
- 'Material needs to enable instancing for use with DrawMeshInstanced' exception should be shown in the console.
Actual result:
- Objects are rendered;
- No error is shown in the console.
See attached video.
Notes:
- The bug creates inconsistency within different types of DrawMeshInstanced API in terms of new instancing enabled workflow;
- Reproducible in 2017.1.0b1, 2017.1.0a6, 5.6.0f3;
- Reproducible on Windows 10 and OSX 10.12.3;
- Couldn't test in 5.5 since new instancing workflow was introduced in 5.6.0.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- SetComponentEnabled uses class instead of struct when constraining Enableable Component type
- [iOS] Application.deepLinkActivated does not get invoked while app is running when UIApplicationSceneManifest is added in Info.plist
- Inspector scroll area stretches when using components with nested serialized arrays on FBX model prefab instances
- Crash on ConstraintProjectionTree::projectionTreeBuildStep when ConfigurableJoint uses JointProjectionMode.PositionAndRotation and connected Rigidbody switches from kinematic to non-kinematic
- ScriptableObject asset is accessed during the lookup of Build Profiles when opening the Build Profiles Window
Add comment