You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a group of five particles, each with a different color. Each UIParticle component is configured as a primary simulator, and the group is programmatically set by iterating through a list where they are assigned. However, in play mode, the random toggle button activates seemingly out of nowhere, and all UIParticles set as replicators start rendering random particles continuously.
Here’s what happens: All UI elements are placed within a scroll view. When these elements move outside the viewport (become invisible), I deactivate them. When they come back into view, I reactivate them. It is at this point that the particles consistently appear as different ones.
Probably happening when the GroupId is set via scripting.
Group:
As they are set:
How the group is set by scripting:
How the replicators are set by scripting:
Version: 4.9.1
Platform: Editor (Windows)
Unity version: 2022.3.10f1
The text was updated successfully, but these errors were encountered:
I have a group of five particles, each with a different color. Each UIParticle component is configured as a primary simulator, and the group is programmatically set by iterating through a list where they are assigned. However, in play mode, the random toggle button activates seemingly out of nowhere, and all UIParticles set as replicators start rendering random particles continuously.
Here’s what happens: All UI elements are placed within a scroll view. When these elements move outside the viewport (become invisible), I deactivate them. When they come back into view, I reactivate them. It is at this point that the particles consistently appear as different ones.
Probably happening when the GroupId is set via scripting.
Group:
As they are set:
How the group is set by scripting:
How the replicators are set by scripting:
The text was updated successfully, but these errors were encountered: