Search Issue Tracker
Fixed in 2019.1.X
Votes
2
Found in
5.6.0p4
Issue ID
923897
Regression
No
InstanceID is not transferred from vertex to domain shader
Steps to reproduce:
1. Open attached Unity Project "923897-TesselationShader.zip"
2. Load Scene "Tesselation x Instancing"
3. Option 1: Select Material "FixedTesselation" and enable "Enable Instancing" in the Inspector
4. Option 2: Select "Instanced Cube" GameObject in the Hierachy and enable it.
Note: the user is using a shader script (modified to support instancing) described in Unity documentation, can be found here:
https://docs.unity3d.com/Manual/SL-SurfaceShaderTessellation.html
Expected result: The instanced object and its material will be displayed correctly
Actual result: Error "Shader error in 'Tessellation Sample': 'disp': output parameter 'v' not completely initialized at line 37 (on d3d11)" is displayed and the material does not work
Reproducible with: 5.5.4p1, 5.6.0p4, 5.6.1f1, 5.6.1p2, 5.6.2p1, 2017.1.0b1, 2017.1.0b10
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Add comment