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.
Reproduction:
path2d-repro.rbxl (63.7 KB)
- Set framerate to 60 FPS
- Drag the button with a Path2D in it
This happens both in studio and client.
System information:
OS: Windows 11
RAM: 12 GB
CPU: AMD Ryzen 7 5800X 8-Core Processor
GPU: NVIDIA GeForce RTX 3060 12GB
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.