Moving and resizing small parts causes geometry to lag

[Oseday]

Yeah, I see. I also found this thread:

Event that fires when rendering finishes

Ah yes, changing the CFrame causes the clustering system to use dynamic clusters for moving parts, which have far less capacity… So if you try to force updates by wiggling the parts, that will also proportionally increase the number of draw calls, and no, it won’t solve the geometry generator throughput problem.

in which @maxvee and @zeuxcg said:

@maxvee

It’s not a bug, you are simply submitting more work than the clustering system is able to process. The “there’s no lag” part is because the clustering system is working as intended on a tight time budget. Realtime is real.

@maxvee

Ah yes, changing the CFrame causes the clustering system to use dynamic clusters for moving parts, which have far less capacity… So if you try to force updates by wiggling the parts, that will also proportionally increase the number of draw calls, and no, it won’t solve the geometry generator throughput problem.

@zeuxcg

That’s correct - CFrame currently is the only “fast” property in that you can change it every frame without really heavy code kicking in. Everything else is expensive.

We’re working on a new system that would make most properties cheap to update. But for now you’ll have to live with the limitations of the existing system.