Search Issue Tracker
Fixed in 13.1.2
Votes
0
Found in [Package]
12
Issue ID
1378335
Regression
Yes
Attributes set in the Initialize context of GPU Event systems return 0.
Repro steps:
1. Import the attached VFX asset and add it to the scene
2. Open it and enable size or color in Initialize
3. Observe that the particle either disappears (size) or turns black (color)
Expected outcome:
Setting attributes to set the new values.
Note:
- Both inheriting and setting attributes in Initialize don't work
- Setting attributes in Update or Output works fine
- Inheriting Event attributes works fine
However, 2 new issues surfaced after that fix:
- All particles in capacity are rendered, even if they are not spawned yet. Without this fix, you would see a pink particle but also 39 smaller black ones at origin. Can be fixed with package only.
- If you enable and disable the VFX (maybe a few times, as it is not deterministic), you will stop seeing the particles. Needs both a new editor and package.
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
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment