Unanchored parts/models in team create move erratically when moving

Describe the bug. Describe what is happening when the bug occurs. Describe what you would normally expect to occur.
Parts/models that are unanchored in a cloud edit/team create session behave erratically when moved.

How often does the bug happen (Everytime/sometimes/rarely)? What are the steps that reproduce the bug? Please list them in very high detail. Provide simple example places that exhibit the bug and provide description of what you believe should be the behavior.
100% of the time.

Where does the bug happen (www, gametest, etc) Is it level-specific? Is it game specific? Please post a link to the place that exhibits the issue.
Any team create/cloud edit session.

Would a screenshot or video help describe it to someone? If so, post one.

For graphics bugs, it is sometimes helpful to know your system specs, especially graphics card.
i9-7920x, 16GB DDR4-2400, 500GB M.2 SSD, 4TB HDD, 2x MSI 1080ti, Windows 10 64-bit, Acer Predator X34.

When did the bug start happening? If we can tie it to a specific release that helps us figure out what we broke.

Anything else that you would want to know about the bug if it were your job to find and fix it.
The bug occurs when you try to move a part/model that’s unanchored via the dragging/axis tool in a cloud edit/team create session. The bug does not occur when you edit a place stored on your computer.

Repro steps:

  1. Open a team create/cloud edit session w/any place.
  2. Insert an unanchored part/model (All part(s) must be unanchored - if one part is anchored, the issue doesn’t occur).
  3. Move the model quickly via the dragger tool/selection tool, and let go.

Can confirm

1 Like

This is extremely annoying and makes it impossible to work on anything involving physically simulated parts in Team Create… hope it can be fixed before code freeze.


I’m confirming, and I believe it’s related to a problem we’re having where if we move a model out of serverstorage into the workspace to work on a bit, it starts its simulation in the workspace.

I’ve reported a similar bug about what happens when you copy and paste models here: Team Create models are having their physics simulated in the workspace even though game is not running


Yeah, this sometimes results in the parts not returning to where they were originally, destroying buildings and models.

1 Like

Can you verify if this still happens? I just disabled something that should’ve been a fix for a subtle non-user facing bug.

1 Like

It’s behaving worse now - the parts are acting like they’re running when the game isn’t in play test mode.

1 Like

Did you restart Studio?

1 Like

Appears to be fixed now, thanks for the quick response/fix!

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.