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
- Crash on UnityPlayer!profiling::ProfilerManager::DisposeProfilerRecorder+0xa when Player gets relaunched and exited after running for a long amount of time
- [Input system] When releasing one touch and pressing a second touch during a single frame, the second touch is not translated into UI event line OnPointerDown by the InputSystemUIInputModule
- URP Samples - multiple "Attempting to resolve render surface" and other errors appear when setting Quality pipeline asset
- OnDemandRendering.willCurrentFrameRender returns incorrect values in the Player when UnityEngine.Rendering.OnDemandRendering.renderFrameInterval is greater than 1
- Root motion is not reapplied when transitioning from an animation without root motion to an animation with root motion
Add comment