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
If you have a part with multiple sets of gimbal hardware, with the same name setup (such as when you add multiple full engine models together and switch the base transforms), only the first model's constraint setup will be active. If you switch the part to use the 2nd model with B9PS, the constraints will be static and not animate with gimbal activation. It seems like each CONSTRAINLOOKFX only gets applied to the first found transforms?
Using stock FXModuleLookAtConstraint works as expected with multiple sets, applying the individual constraints to every instance of the target/rotators.
I've worked around it by creating a whole new mu with a set of gimbal hardware with unique names, and hiding the base model's hardware.
If you wanted to look into it, I can probably provide some stock model example cfgs
The text was updated successfully, but these errors were encountered:
If you have a part with multiple sets of gimbal hardware, with the same name setup (such as when you add multiple full engine models together and switch the base transforms), only the first model's constraint setup will be active. If you switch the part to use the 2nd model with B9PS, the constraints will be static and not animate with gimbal activation. It seems like each
CONSTRAINLOOKFX
only gets applied to the first found transforms?Using stock FXModuleLookAtConstraint works as expected with multiple sets, applying the individual constraints to every instance of the target/rotators.
I've worked around it by creating a whole new mu with a set of gimbal hardware with unique names, and hiding the base model's hardware.
If you wanted to look into it, I can probably provide some stock model example cfgs
The text was updated successfully, but these errors were encountered: