System failure as switched condition?

[DarkFire]

Is it possible to have a system failure toggled by a switched condition? For example, would it be possible to force a radar failure if the unit in question is within a zone?

[ESAc_matador]

You can switch the IA radar off and on

[Apache600]

In what aircraft?

[ESAc_matador]

All, in advanced tasks-orders, create a trigger activated with a flag one for on and one for off

Then

Put continuous trigger, unit in zone, flag value

[Apache600]

I have had some odd issues with failures, and found a work-around to make my campaign work.

 

In one of my missions, I have a failure occur after a set amount of time passes after activating a certain trigger. The interesting thing I had though, was while testing (say having it happen 10 seconds after mission start) it would ALWAYS work. But in the mission, the failure doesn't happen until at least 20 minutes in. While testing the mission, I found that the failure would never happen, because of some unknown reason. If to much time in the mission elapsed, the failure would not occur.

 

So in order to work around this I found, in testing, that the "time since trigger" WILL work, as long as I also put in a generic "time to failure" in that particular aircraft's failure page (the page next to loadouts, summary, specific triggers, etc.) It's like you needed to double it up in order for it to remember to work on your specific trigger [Note: in the "time to failure" I always had the time set for a considerable time after the "time since trigger" would have activated the failure anyway]

 

It took a long time to figure this out. But with this, it worked as I wanted it to 100% of the time.

[DarkFire]

I have had some odd issues with failures, and found a work-around to make my campaign work.

 

In one of my missions, I have a failure occur after a set amount of time passes after activating a certain trigger. The interesting thing I had though, was while testing (say having it happen 10 seconds after mission start) it would ALWAYS work. But in the mission, the failure doesn't happen until at least 20 minutes in. While testing the mission, I found that the failure would never happen, because of some unknown reason. If to much time in the mission elapsed, the failure would not occur.

 

So in order to work around this I found, in testing, that the "time since trigger" WILL work, as long as I also put in a generic "time to failure" in that particular aircraft's failure page (the page next to loadouts, summary, specific triggers, etc.) It's like you needed to double it up in order for it to remember to work on your specific trigger [Note: in the "time to failure" I always had the time set for a considerable time after the "time since trigger" would have activated the failure anyway]

 

It took a long time to figure this out. But with this, it worked as I wanted it to 100% of the time.

 

Thanks for the info everyone.

 

So for me to be clear: if you have the "time to failure" set to say 20 minutes, but the failure in question set to a flag that activates after 30 minutes, will the failure always happen when the flag activates or earlier? What I'm trying to achieve is to get certain systems on a player aircraft to fail when the player is within a certain distance of another specific unit, but only under those conditions, and then to start working again once the player has flown away from the 'trigger' unit.

Edited July 14, 2016 by DarkFire

[Apache600]

It should happen at whichever time comes up first.

 

With your dilemma though, to have something fail, and then come back ... I never tried doing that one. Sorry I'm not sure you're able to "Set Failure" to an OFF position. I figured it was just one and done. No turning back :P

 

You'll have to test it out, but even if you have it set to a flag like ESAc_matador mentioned, I don't think turning off the flag would also turn off the failure. I could be wrong though.

[DarkFire]

OK thanks, I'll give it a go...