ipeer / agrouponstage Goto Github PK

When firing a Camera Control action group, the camera is often set to AUTO mode, regardless of the groups' setting.

When staging, AGOS' group activation code is fired twice. This isn't a major issue, but I'd rather only have it fire as many times as needed.

{
name = AGOSModule
isEnabled = True
isRoot = True
flightID = 0
EVENTS
{
toggleGUI
{
active = True
guiActive = True
guiActiveEditor = True
guiIcon = Action group control
guiName = Action group control
category = Action group control
guiActiveUnfocused = False
unfocusedRange = 2
externalToEVAOnly = True
}
}
ACTIONS
{
}
AGOS
{
GROUPS
{
8
{
0
{
groupType = BasicActionGroup
isPartLocked = True
partLink = System.String[]_4292263804
}
}
}
}
}

This is completely pointless. You can't stage a Kerbal and they're lost once then enter a vessel.

Action group configurations should be removed once all criteria for their firing can no longer be met.

Title is pretty self-explanatory here. AGOS schedules a stage lock, but the staging never actually gets locked. This was also an issue in the 1.x.x version of AGOS which caused the feature eventually be dropped.

Title of this issue is based off initial analysis. This issue is still under investigation, described scenario may not actually be the cause.

Has no effect on the vessel as they're never updated to the vessel's correct ID.

Parts and other GUI elements can be interacted with while clicking in the AGOS configuration window.

Error message:
[WRN 13:12:42.717] [Part]: PartModule AGOSModule at reserveBatteryPack, index 0: index exceeds module count as defined in cfg. Looking for AGOSModule in other indices... [ERR 13:12:42.717] ...no AGOSModule module found on part definition. Skipping...

Temporary workaround: Switching to a vessel from the tracking station or space centre view and then returning back to the space centre will unlock the button for use again.

Did this really slip though? Oh boy...