So for some reason only recently I’ve found out that :SetPrimaryPartCFrame is deprecated and has been replaced by some space alien technology called :PivotTo
I’ve always been using the deprecated method, because i just find it more optimal instead of some weird thing called “PivotTo”
Are there any downsides to using SetPrimaryPartCFrame??
The only downside is if you use it for moving models over a long period of time. Not sure if pivot to is any different.
Other than thst well it works and does the job.
as stated in the doc:
performant replacement and does not change your code’s behavior. Use PVInstance:PivotTo() for new work and migrate your existing Model:SetPrimaryPartCFrame() calls when convenient.
read the documentation for both for more information
SetPrimaryCFrame
PivotTo
Edit:
After bench marking it
SetPrimaryCFrame is considerably faster than PivotTo almost 3x
so I guess in the end it’s your choice on if you want to switch over. Personally I would use whatever’s not deprecated but than again this is coming from the person that references Lighting service with game.lighting which is deprecated
Basically, if you liked SetPrimaryPartCFrame, you’re going to really love PivotTo.
Here’s some details from when it was released: Pivot Editor: Full Release
A snippet from the post:
ok that is pretty cool
relationship with SetPrimaryPartCFrame ends here
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.