Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ModuleAdvancedLookAtConstraint incompatable with multiple "sets" of gimbal transforms #20

Open
Rodg88 opened this issue Jul 20, 2024 · 0 comments

Comments

@Rodg88
Copy link

Rodg88 commented Jul 20, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant