Search Issue Tracker
Fixed in 12.0.0
Votes
0
Found in [Package]
12.0.0
Issue ID
1321713
Regression
No
[VFX Graph] Invalid operation type, Invalid value type, Invalid VFXValueType errors are thrown to the Console
How to reproduce:
1. Import the attached VFX.vfx to the project
2. Select VFX.vfx asset in Project Browser
Expected result: No errors are thrown in the Console
Actual result: Invalid operation type: 330, Invalid value type: 0, Invalid VFXValueType: 0 errors are thrown in the Console
Reproduced with: 2021.2.0a10(12.0.0)
Notes:
- Video of reproduction is attached in Edit
- Full error messages:
Invalid operation type: 330
UnityEditor.EditorApplication:Internal_CallUpdateFunctions ()
Invalid value type: 0
UnityEditor.EditorApplication:Internal_CallUpdateFunctions ()
Invalid VFXValueType: 0
UnityEditor.EditorApplication:Internal_CallUpdateFunctions ()
- In particular cases, same errors with different indices are thrown when opening graph, connecting disconnecting nodes, contexts
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 12.0.0):
Fixed in VFX Graph12.1.2