ObjectActivation of Triggers will not survive back to menu after LegEnd (Save/Load)

I’ve created a complex mission with many inactive/active triggers and
conditional activation by object activation. After going to menu, mainly after
a leg end, the activations don’t survive this. For testing/reproduction:
Create 4 Triggers: 1. TriggerFalseFalse Activated = False DefaultActivated =
False 2. TriggerFalseTrue Activated = False DefaultActivated = True 3.
TriggerTrueFalse Activated = True DefaultActivated = False 4. TriggerTrueTrue
Activated = True DefaultActivated = True Absolutly independed of the type of
the trigger (tested with Property/Proximity and AirportLandingTrigger) and the
state of the Activated Flag when leaving the mission. The state of “Activated”
after re-join the mission is the value of DefaultActivated 1.
TriggerFalseFalse Activated = False DefaultActivated = False 2.
TriggerFalseTrue Activated = True DefaultActivated = True 3. TriggerTrueFalse
Activated = False DefaultActivated = False 4. TriggerTrueTrue Activated =
True DefaultActivated = True From my point of view, the root cause is the
saved SPB file, because those values are included there in this state
(Activated=DefaultActivated, not current state). And of course, after loading
this SPB, the state is as saved in SPB. Any idea to keep the state of
activated flag when the user is leaving and re-joing the mission? Thanks in
advance, BuffyGC

Do you know what the intended use of DefaultActivated is? I can’t find any
documentation for it.

Not really. The only thing I’ve seen in the PropDefs is “Default state of
activate flg”. When, why and which UseCase is unknown to me. But this was not
always in the sim, I noticed it for the first time in December/January, when
the triggers of the BushTripInjector from Leg 2 did not work anymore, because
this was not set. Set then to true and everything was fine in this early state
of BTI. I had no further thoughts about it in Jan.