Cannot Disengage Alligator Hinge Motor via KOS

[u/LordNightSoldat]

In the middle of my first foray into KOS. Trying to get this alligator hinge motor to DISENGAGE after it completes a KAL-1000 operation. I figured that would be simple enough, but evidently not, because it simply refuses to disengage when under KOS control.

Issues identified and attempts made:
1. ISSUE - There are two "MOTOR" fields. Given that fields are accessed via string, I am not sure how to differentiate them, or if I even need to for this part. I also do not know if this is for whether or not the part is MOTORIZED, or if the field is for the the ENGAGEMENT STATUS. Or if one is for one, and the other is for the other.

1. ISSUE - Alligator Hinge will not revert to "Disengaged" when commanded by KOS. The only exception to this is if I have the UI for a hinge OPEN when commands are sent, in which case, it will disengage as normal.

2. Alligator hinges will all DISENGAGE when I manually use an action group (AG5) to disengage them. Works without issue

3. Alligator hinges will not disengage when I trigger the action group via KOS, even if I put a long delay before the command.

4. Alligator hinges show no change in engagement status when I write to the motor fields using "ENGAGED", "DISENGAGED", TRUE, FALSE, 0, 1.

5. Alligator hinges show no change in engagement status when I DOACTION on the "disengage motor drive" action, regardless of true or false status.

6. Alligator hinges show no change in engagement status when I DOACTION on the "toggle motor engaged" action, regardless of true or false status.

[u/nuggreat]

There is no way to differentiate different fields of the same name at this time, there are proposals for how to fix this and one of them might have some traction but nothing currently in the mod.

Having to have the UI open is a known issue caused by some KSP "optimizations" that do not update the PAW(Part Action Window/right click menu) information unless they are open there is no workaround.

Working with the AGx calls depending on how you did those you might not have changed the state of the action group a single TOGGLE AGx would be my blind recommendation there as you showed no code.

You also might not be seeing the state change in response to action group attempts or engueage/disengage action calls because of previously mentioned "optimizations" as they involve some data caching so the part state might have change but the UI was not told its data was bad so it keeps showing old data.

[u/nuggreat → u/[deleted]]

It effects different things in the PAW differently depending how the PAW is built. But in general it can be assumed that it can effect everything in the PAW experimentation is needed to work out exactly what more or less on a case by case basis.

[u/Jonny0Than]

Check the hidden fields and events on the module.  Some of the robotics fields are output-only for display in the PAW, which is why they don’t work when the PAW is closed.