When trying to move a model using the move tool, the entire model will teleport a few studs away (number can vary from 6 studs to around 220 studs away)
This issue often happens on large games, but it only has a random chance of occuring. I was not able to figure out what specifically causes the move tool’s draggers to glitch out like this.
Betas: Assistant preview, avatar joint upgrade, dragger qol improvements, gamepad emulator, import queue, improved constraint tool, multilayer wrap fix , new studio camera controls, occlusion culling, preferred text size setting, script sync, studio solid modeling improvements, texture generator, UIDragdetectors, unified lighting, vr emulator and video uploads.
Disabling dragger qol improvements and uidragdetectors does not fix this issue. The only way for me to drag the move tool without it snapping is by holding tab to bring the handles to a specific point and to move individual parts one at a time.
i’ve have this happen the past couple months, i’m honestly not sure what causes it but it typically happens for me after importing models and it doesn’t fix it self unless I reset the pivot. I have had it occur on just regular models but again resetting the pivot seemed to work.
I assume you largely encounter with Meshparts. Check your Pivot offsets on those Meshparts. I suspect you’ll find Pivot offsets set on them, which is typical on imports from Blender. I’ve noticed when you click on Meshparts to move with these Pivot offset values, it immediately moves the Meshpart at that offset from the cursor’s current location to move the part based on the offset, which seems wrong with all their recent Draggers updates to move parts.
If you dont actually need the Pivot offsets for scripted actions to move or orient them based on the offset, then setting the Pivot Offset Position and Orientation to zeros should be a quick work-around.
I agree it’s a bug that I hope they solve, but this approach should at least work-around it.
I have a multitude of community plugins installed but disabling all of them does not stop this issue from happening.
It happens to all models, regardless if they are MeshParts or not.
I believe it has an increased likelihood of occurring in places with Team Create but it can occur no matter the size of the model, the size of the place and regardless if there is a “place size reaching limit” warning or not
I’m only suggesting work-arounds to the Roblox issues. I sometimes still encounter the same as you, although generally it’s when any of the parts in the model still have a Pivot offset with a weld or constraint to the PrimaryPart, or when the PrimaryPart isn’t set, or if you have a high stud value in the Move tab. I also noticed you have a large number of parts with same name in that model, maybe change the name of the primary one and perform a union on like parts to reduce the count. I do find that the more objects under a model, the more it tends to have issues.
Heya guys, I recently discovered this bug on my own, and was researching on how I could resolve this odd and frustrating bug. I realized that there are a few issues here. First off, by setting the pivot position to 0, it’s likely setting it to the world space 0, 0, 0 instead of the center of the model. Having this offset is what’s causing this issue.
The current fix for this issue is to edit the pivot in the model and then click on reset. You should notice that the pivot position is now a random position (this should be the center of the model’s position). Though more than likely, I don’t believe that this is intended
behavior.