Search Issue Tracker
By Design
By Design in 6000.0.X
Votes
0
Found in
2021.3.44f1
2022.3.50f1
6000.0.23f1
Issue ID
UUM-84066
Regression
No
Sample Bezier node in VFX Graph breaks when the Particle count is higher than 32
Reproduction steps:
1. Open the attached “Unity6_test.zip” project
2. Open the “Bug Scene” Scene
3. Observe “VFX_Bezier_Beam” GameObject in the Scene
Expected result: A clean particle strip that follows a curve is visible
Actual result: A broken particle strip is visible
Reproducible with: 2021.3.44f1, 2022.3.50f1, 6000.0.23f1
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Notes:
- “Spawn Count” can be increased on the 'VFX_Bezier_Beam' GameObject
- The higher the “Spawn Count” the more the strip breaks
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
- LocalizationSettings.InitializationOperation hangs when re-entering Play Mode with Domain Reload disabled
- [UI Toolkit] Delete key deletes the incorrect character and allows for an extra character deletion when language direction is set to RTL
- Dropdown property is cut off and adds unnecessary side padding when a Sub Graph is used as a node in Shader Graph
- All text in the Project Settings Window is still Tinted White after deleting Text in the Search Window
- "WebGL Template" icons disappear when building the project with the Project Settings opened
Resolution Note:
Sample Bezier node works fine, the issue is the index that is being used to compute the parameter T.
In the sample provided, the user is adding a custom attribute "Spawn_Index" to compute the ratio in strip, using "Get Spawn Index" as the base.
This is not correct, because particles are spawned in parallel and we can't control the order if we have more than 1 group (that is why it only happens after 32).
Instead, the user could use "Get Spawn Index In Strip", which computes the correct value.
From U6, the user can also use the new node "Get Ratio Over Strip" to avoid doing the calculation themselves.
Resolution Note (6000.0.X):
Sample Bezier node works fine, the issue is the index that is being used to compute the parameter T.
In the sample provided, the user is adding a custom attribute "Spawn_Index" to compute the ratio in strip, using "Get Spawn Index" as the base.
This is not correct, because particles are spawned in parallel and we can't control the order if we have more than 1 group (that is why it only happens after 32).
Instead, the user could use "Get Spawn Index In Strip", which computes the correct value.
From U6, the user can also use the new node "Get Ratio Over Strip" to avoid doing the calculation themselves.