ModuleSpaceDustTelescope's scananimation currently causes undesirable behaviour if it's added to a part that also uses a shared animation for other modules, eg a telescope with a science experiment that also deploys a cover.
Having both SD and science modules share the same deployment animation causes the animation to replay when activating the 2nd module, or you can set the SD module to not use an animation to prevent replaying the animation, but this allows the module to run when the animation isn't in a deployed state.
Perhaps just a "deployFXmoduleIndex" would work, but would require current parts be updated with an added moduleanimategeneric, and would probably need testing with DMMSAG deployment animations (since it doesn't reference a seperate deployment module, just plays an animation itself).
ModuleSpaceDustTelescope's scananimation currently causes undesirable behaviour if it's added to a part that also uses a shared animation for other modules, eg a telescope with a science experiment that also deploys a cover.
Having both SD and science modules share the same deployment animation causes the animation to replay when activating the 2nd module, or you can set the SD module to not use an animation to prevent replaying the animation, but this allows the module to run when the animation isn't in a deployed state.
Perhaps just a "deployFXmoduleIndex" would work, but would require current parts be updated with an added moduleanimategeneric, and would probably need testing with DMMSAG deployment animations (since it doesn't reference a seperate deployment module, just plays an animation itself).