When moving a UI element with a descendant Path2D, all descendant elements in front of the path (including the path) update their position at a slower rate. This is very noticeable at 60 FPS.
Note that I’m on a virtual machine with the GPU passed through.
0.25x speed:
Expected behavior
All UI elements are expected to update their position without any frame skips caused by the Path2D instance. If this is an optimization, it should only affect the path.
They are, which fixes the original issue, but the UI still updates at a lower framerate. This is very noticeable to me at 60 FPS. I assume that it’s not a bug but a performance optimization? Why not disable it at the highest graphics setting? I don’t really see any problem with Path2Ds updating/rerendering more frequently, as I usually use studio with 240 FPS to notice any FPS drops early.
The laggy movement is only really visible at 60 FPS, so maybe the update rate can be adjusted to hide that?
Oh you mean that the UI is behind the mouse? That’s a separate issue that’s not entirely solvable. If the Path2D issue is fixed, I’ll close out this ticket.