Search Issue Tracker
Fixed
Unknown (hidden) 2019.4.X
Fixed in 2021.3.6f1, 2022.1.13f1, 2022.2.0a17
Votes
0
Found in
2019.4.36f1
2021.3.3f1
2022.1.2f1
2022.2.0a7
Issue ID
UUM-571
Regression
No
VFX Property Binder breaks when connecting GPU Event to Initialize Particle Nodes that are connected to Output Particle Nodes
How to reproduce:
1. Open the user's attached "T1175885_VFX" project
2. Open the "Test_VFXGraph_Subgraph" VFX file from the Project Browser
3. Connect the "Initialize Particle" or "Initialize Particle Strip" Node to the "GPUEvent" Node
Expected result: Nodes are successfully connected without any errors thrown
Actual result: "Test_VFXGraph : Exception while compiling expression graph: System.InvalidOperationException: Unexpected link context : SpawnerGPU" error is thrown in the Console log
Reproducible with: 7.7.1 (2019.4.36f1), 10.8.1 (2020.3.30f1), 12.1.5 (2021.2.14f1), 13.1.6 (2022.1.0b10), 14.0.0 (2022.2.0a7)
Note:
- Connecting GPUEvent to a new Initialize Particle Node doesn't reproduce the issue. It's only reproducible when the Initialize Particle Node is connected to Output Particle Nodes
- Not reproducible with HD RP
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
- 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
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note (fix version 2022.2.0a17):
Fixed in 2022.2.0a17
Resolution Note (fix version 2021.3.6f1):
Fixed in 12.1.7 (2021.3.6f1)
Resolution Note (2019.4.X):
I won't take the risk of introducing this kind of change for a low user pain just before the end of support.