New Failure - Provide a Failure module for animated parts

[diomedea]

With the intent to write TestFlight config files for parts like SolarPanels, Chutes, Gears, Antennae, Scientific Experiments, Shielded DockingPort, Cargo Bays, one (or more) specific modules are needed to manage the transition in a deployed (open) state for that part, and produce a failure event tied to the transition. Optionally, another module could manage the opposite transition to a stowed (closed) state. Aerodynamic Control Surfaces, ReactionWheels, RCS thrusters also should have a module for the case of failures reducing the control action (selectable up to 0% of their range, so disabling them completely). Also, such modules should allow to define failure events for robotic parts and other movable parts with add-ons.

[jwvanderbeck]

My understanding is that there are more than a couple animation modules used by modders, so any help in building a list of those used would be great.

[diomedea]

Please clear what you need, I'll be happy to help listing animation modules. My doubt is what you need to reference to. E.g., with stock SolarPanels, all use the same module "ModuleDeployableSolarPanel", but each has a different animation ("solarpanels", "solarpanels2", "solarpanels4" and so on). Just one animation each, so that seems to cover all movements deployment, retraction, and sun-tracking). But, I guess you would actually be interested to either detect a call to ModuleDeployableSolarPanels.Extend() or .Retract(), or to parse the .panelStates for EXTENDING or RETRACTING. The actual animations don't really have to be considered.

So, please let me know what you need, making a list of the methods or states involved with moving parts does seem something I could make.

[jwvanderbeck]

What I mean is non-stock parts I think use various different animation PartModules like Firespitter for example. I need to know which ones are most commonly used, because I then need to do some research to figure out how to support and control them.

[Starstrider42]

Given that TestFlightFailure_Animation exists, can this issue be closed, or do you still want a way to cover all animation-related part modules? (I ask because I will be interested in animation-related failures in the mid-future.)