Search Issue Tracker
Fixed in 12.0.0 (in review)
Votes
0
Found in [Package]
12.0.0
Issue ID
1361601
Regression
Yes
[VFX Graph] Error is thrown to the console and VFX is not displayed when assigning Vector property to Shader Graph's blocks
How to reproduce:
1. Open the attached package on HDRP project
2. Open SG
3. Connect Vector3 node to Position block
4. Save ShaderGraph
Expected result: VFX is displayed at 0,0,0 pos
Actual result: VFX disappears and error is thrown to the console
Reproducible with: 2021.2, 2022.2(public 12.0.0, master)
Note: Happens with any kind of vector when assigning to blocks - Position, Smoothness, Metallic, etc.
Error message:
ArgumentNullException: Value cannot be null.
Parameter name: key
System.Collections.Generic.Dictionary`2[TKey,TValue].FindEntry (TKey key) (at <231f6c5a042647adb84a9cc42c982c35>:0)
System.Collections.Generic.Dictionary`2[TKey,TValue].ContainsKey (TKey key) (at <231f6c5a042647adb84a9cc42c982c35>:0)
UnityEditor.VFX.VFXCodeGenerator.BuildFragInputsGeneration (UnityEditor.VFX.VFXContext context, UnityEditor.VFX.VFXContextCompiledData contextData, System.Boolean useFragInputs, System.String& buildFragInputsGeneration) (at C:/Users/vita.skruibyte/Documents/SRP/com.unity.visualeffectgraph/Editor/Compiler/VFXCodeGenerator.cs:483)
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][BiRP] Depth processing is handled incorrectly on certain Android devices when using 2 camera's
- [APV] Cancelling Display Dialog Error is thrown after Adaptive Probe Volumes tab is open in Lighting Window
- [APV] NullReferenceException is thrown when baking Adaptive Probe Volume for a Terrain with Non-GI Contributing Tree Prototypes and multiple APV objects with different LayerMasks are present on the scene
- Hands are not recognized when using Hololens 2
- "OnTriggerExit2D" is called before "OnTriggerEnter2D" when object is destroyed immediately
Resolution Note (fix version 12.0.0 (in review)):
Fixed in 2022.1.0a12
Resolution Note:
Fixed in 2021.2.0b15