AlignOrientation in OneAttachment mode does not update regularly

Reproduction Steps
Use the following place, which simply has a part with an AlignOrientation, Attachment, and Script inside of it. The script “aims” the AlignOrientation’s CFrame towards the “TargetPart” object.

AlignOrientationBugReproduction.rbxl (34.2 KB)

Expected Behavior
The oriented part should consistently face towards the TargetPart at any given moment, especially since the axes of the AlignOrientation that is controlling it are clearly updating.

Actual Behavior
The AlignOrientation seems to only exert influence on the part when specific properties of the orientation are changed. For example, toggling the RigidityEnabled boolean will “wake up” the object and face it toward the TargetPart. The same can also be done by deactivating and reactivating the Enabled boolean.

Here is a video demonstration: AlignOrientation bug demonstration - YouTube

I wanted to use an AlignOrientation since it is apparently the newfangled object that we’re supposed to use, and BodyGyro objects are supposed to be legacy or deprecated. Unfortunately, with the inconsistency of this object for a pretty standard use case, I can’t. Using a BodyGyro is my only other option if I want this rotation to be based on physics and not direct manipulation of the object’s CFrame.

Issue Area: Engine
Issue Type: Other
Impact: Moderate
Frequency: Constantly
Date First Experienced: 2022-01-04 00:01:00 (-05:00)
Date Last Experienced: 2022-01-05 00:01:00 (-05:00)


How much Force are you using for the AlignOrientation?

Irrelevant. With RigidityEnabled, theoretically infinite force is applied to rotate the object. It’s also irrelevant because it does succeed in rotating the object, just not when the CFrame (PrimaryAxis and SecondaryAxis) are updated, only when certain other properties are updated. This limits the usefulness of the object in an arguably unexpected way. Did you watch the demonstration video?


I experienced similar behavior when using an AlignPosition as well. My current workaround is simply enabling and disabling the Enabled property every time the position is updated (as you described) but this feels rather inefficient and should not be necessary. Hoping to see a fix soon!

Thanks for the issue report! I have submitted an internal ticket for it.


Finally!! This has been a bug for ages!

I first experienced this bug in early October

1 Like

Thanks God! It got reported a second time and this time it dragged the attention of the staff. Anyways, how do we know if the bug got fixed? We will get a response here? I am worried because there are some bugs that have been fixed and new features has been added without telling the developer anything. (Sometimes release notes are not even updated)

I hope this bug gets fixed quick because I want to just update such properties without needing to disable and enable the object.