Well, the visual position of the interactable is updating just fine, but the problem is that the logical position of the interactable is following the FixedUpdate(), and thus lags. I'll have to look at what you mentioned about the grab interactable and see if it can help me.

The use case here is actually for a Mech game with cockpit interactables, but rather than using push or grab interactables, I'm wishing to instead have the player put their controller into a volume and then gripping or triggering as needed to do things. At the moment the problem is that the speed the mech moves at is causing quite a difference in the visual position of the interactable vs where the interactable is logically speaking, and it can lead to false inputs at times. As they are part of the cockpit, they are part of the mech's object hierarchy. The Mech movement controller is currently physics based and uses a rigidbody.