Search Issue Tracker
In Progress
Won't Fix in 6000.2.X
Under Consideration for 6000.3.X
Fixed in 6000.4.0a6, 6000.5.0a2
In Progress in 6000.5.X
Votes
5
Found in
6000.1.0a6
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-99382
Regression
No
[VFX Graph] Position Jitter in RestState with Collision SDF
Steps to reproduce:
- import the provided package
- open the scene named SDFIssue
- in the Scene View, Zoom very closely on the different VFX.
Actual results: The particle properly collides with the SDF, and due to high friction and no bounce, instantly stops on the Collider. When zooming, we can see that although they should be in rest state, some position jittering is happening.
!image-2025-03-05-11-04-04-789.png|width=464,height=362!!image-2025-03-05-11-04-26-531.png|width=463,height=387!
Expected results: No jittering should occur like when colliding with other type( Plane, Sphere etc...)
Comments (1)
-
steveshg
Aug 15, 2025 10:39
Any updates? still happens.
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note:
Forward-ports for this version need to be handled at a later time.
Resolution Note (6000.2.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.