Studio Immediately Crashes when changing the OriginPosition of a Model inside of ReplicatedStorage

Bug Reports Engine Bugs
#1

Reproduction Steps

1. Create any basepart in the workspace, and parent the part to a Model
2. Drag the Model into ReplicatedStorage
3. Change the OriginPosition of the Model to anything by typing and clicking Enter

Expected Behavior

I expect the OriginPosition of the Model to be changed

Actual Behavior

Studio instantly crashes with this message:

Crash
Crash1903×1001 1.01 MB


Issue Area: Engine
Issue Type: Crashing
Impact: Critical
Frequency: Constantly
Date First Experienced: 2022-08-10 15:08:00 (-07:00)
Date Last Experienced: 2022-08-10 00:08:00 (-07:00)

Reproduction Place File:
Origin Position Model Crash.rbxl (34.3 KB)

5 Likes
#2

Can reproduce. Calling PivotTo on the model also crashes Studio.
Roblox Crash™
…even when not selected.
image
And it doesn’t have to be ReplicatedStorage either, based on my testing with ServerStorage.

2 Likes
#3

This is a bit more serious.

I can reproduce as well with 100% consistency with any BasePart or Model outside of the workspace, alongside with Origin Orientation, regular Position, and regular Orientation.

I went down the list of all of the root items in the Explorer and changing the regular / Origin Position and regular / Origin Orientation in any way in anything but the workspace will crash Studio. This also includes SetPrimaryPartCFrame.

I guess if it’s literally out of sight and out of mind then Studio breaks? I don’t know.

#4

I tested this with both a local script and server script, and PivotTo does not seem to crash when the game is running. This only appears to happen during edit mode.

#5

I was able to reproduce :
image

This issue is completely blocking me from working on my game, since we use rojo & make use of its livesync server, which edits this property.

2 Likes
#6

It’s blocking me too :frowning:

#7

This is also causing me crashes too, entirely destroying my workflow

RobloxStudioBeta_wPr3EyLg3F

2 Likes
#8

Thanks for your reports. This issue should be resolved now once you restart studio. Please let me know if you continue facing this.

6 Likes
#9

Yep, it seems to be fixed now! I was not able to reproduce.
Thanks :slightly_smiling_face:

#10

@ShinyGriffin Could you mark the response from elephant as solution?

1 Like
#11