Search Issue Tracker
Fixed in 12.1.4
Votes
0
Found in [Package]
12.0.0
Issue ID
1390079
Regression
Yes
UNITY_PREV_MATRIX_M and UNITY_PREV_MATRIX_I_M errors are thrown when enabling GPU Instancing on a material
Reproduction steps:
1. Open the user's attached project
2. Select "Assets/Broken Graphs/New Shader Graph" Shader Graph
3. Notice there are no error messages
4. Select "Non Instanced Shader Working" material
5. Enable GPU Instancing
6. Select "New Shader Graph" again and observe the Inspector
Expected result: No errors are thrown
Actual result: 'UNITY _PREV_MATRIX_M' and 'UNITY_PREV_MATRIX_I_M' errors are thrown
Reproducible with: 12.0.0 (2021.2.0b9), 12.1.3 (2021.2.8f1)
Not reproducible with: 10.9.1 (2020.3.34f1), 12.0.0 (2021.2.0b8), 12.1.4 (2021.2.9f1), 12.1.6 (2021.2.19f1, 2021.3.2f1), 13.1.8 (2022.1.0f1), 14.0.2 (2022.2.0a13)
Couldn't test with: 7.7.1 (2019.4.37f1) (used Shader Graph breaks)
Note:
- user notes that after the errors appear, Shader Graphs become difficult to work with (some properties are not displayed and can't be set through script)
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note (fix version 12.1.4):
Fixed in 12.1.4 available in 2021.2.9f1