Weird issue with saving part orientations

[RaymondLWeston (Ray)]

I have a persistent building game. Sometimes, (seemingly when an object is rotated at odd angles), their data for their orientation gets messed up, and when you load it back in it turns out something like this (this should be a straight sloped rooftop, and it was built as such):

I am not sure why this is happening and I can only get it to replicate sometimes, so I am going to drop my code here to see if anyone can point me in the right direction.

--Saving The Data
table.insert(data, {
	building.Name,
	building.PrimaryPart.CFrame.Position.X,
	building.PrimaryPart.CFrame.Position.Y,
	building.PrimaryPart.CFrame.Position.Z,
	building.PrimaryPart.Orientation.X,
	building.PrimaryPart.Orientation.Y,
	building.PrimaryPart.Orientation.Z,
	building:FindFirstChild("PartsListGui").Data.Owner.Value,
	building:FindFirstChild("PartsListGui").Data.CurrentlyBuilding.Value,
	building:FindFirstChild("PartsListGui").Data.AllMaterials.Value
})
end

--Loading
newBuilding:PivotTo(CFrame.new(obj[2], obj[3], obj[4]) * CFrame.Angles(obj[5]*math.pi/180, obj[6]*math.pi/180, obj[7]*math.pi/180))

Any thoughts why this is happening? It’s seemingly occurring for objects rotated on two axes or more, but I can’t be completely certain what’s causing it and cannot get it to reliably replicate.

[dthecoolest]

@RaymondLWeston

CFrame.Angles(obj[5]*math.pi/180

Is CFrame.Angles() broken?

Not really, If you want to do it with CFrame .angles it’s more YXZ is orientation, XYZ is CFrame.angles order. To force it to apply it on the Y axis first you can do this: part.CFrame = CFrame.new(10,10,10)*CFrame.Angles(0,math.rad(30),0)*CFrame.Angles(math.rad(15),0,math.rad(45)) TBH just use CFrame.fromOrientation()

[RaymondLWeston (Ray)]

Not sure I understand. I should put the Y value first, instead of X? Or use CFrame.fromOrientation()?