Search Issue Tracker
By Design
Votes
0
Found in
2018.4
2019.3.15f1
2020.2
Issue ID
1252732
Regression
No
[Vulkan] Objects are rendered in red when using DrawMeshInstanced method with Deferred shader
How to reproduce:
1. Open user's attached 'VulkanInstanceIDBug.zip' project
2. Open 'SampleScene' Scene
3. Enter Play Mode and observe that objects are colorful
4. Select 'Renderer' GameObject in the Hierarchy
5. Set Current Mode property to Complex
Expected result: Objects are colorful in Game View
Actual result: Objects are red in the Game View
Reproducible with: 2018.4.23f1, 2019.4.0f1, 2020.1.0b12, 2020.2.0a14
Notes:
- Video of reproduction attached in Edit
- Not reproducible with DX11, DX12, Open GL Core
- Not reproducible on Windows Standalone, user states that it works fine on Win64 DX11, PS4, X1 and Switch
- Not reproducible with Unity primitive meshes
- Not reproducible with unlit, lit forward shaders; Reproducible with lit deferred shader
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (2020.2.X):
the problem is at the developer provided shaders, UNITY_VERTEX_INPUT_INSTANCE_ID needs to be defined in fragment shader input, and UNITY_SETUP_INSTANCE_ID(input); needs to be called at the start of the fragment shader.