You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, translation controls are input-only. The vr code does not drive the transforms of the prop; we leave it up to rpm or mas to do that.
The habtech rcs control was never set up for rpm or mas, so it doesn’t have the 3 layered transforms that it would need to do that smoothly. Eventually we should drive the transforms from the vr modules themselves, like the flightstick and throttle levers do.
The text was updated successfully, but these errors were encountered:
Currently, translation controls are input-only. The vr code does not drive the transforms of the prop; we leave it up to rpm or mas to do that.
The habtech rcs control was never set up for rpm or mas, so it doesn’t have the 3 layered transforms that it would need to do that smoothly. Eventually we should drive the transforms from the vr modules themselves, like the flightstick and throttle levers do.
The text was updated successfully, but these errors were encountered: