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
- Memory leak occurs when focused on Player while using Direct3D12
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
Resolution Note (fix version 12.0.0):
Fixed in VFX Graph12.1.2