Time More isnt working correctly anymore

[Knock-Knock]

Edit: Can ignore this. Appears I have fooled myself for quite some time.

 

 

 

In latest OB, it appears that the TIME MORE trigger condition doesnt work correctly anymore. Instead of time more since condition, its time more since mission start now.

 

For example.

FLAG IS TRUE (1) -> Message to ALL (Flag 1 is true)

TIME MORE (20)

 

20 seconds into mission start and Flag 1 is true, the message will appear. Not 20 seconds after Flag 1 is true (as it used to be).

 

I know I can use Time since flag, but the above is just a test example, cause I was pulling my hairs as to why things didnt work.

 

Ive attached that described test. Pay attention to the messages and mission time.

time more.miz

Edited October 25, 2019 by Knock-Knock

[Fisherman82]

As far as I know TIME MORE has always worked like that. I use TIME SINCE FLAG to get the result you want

 

Skickat från min D5503 via Tapatalk

[Knock-Knock]

As far as I know TIME MORE has always worked like that. I use TIME SINCE FLAG to get the result you want

 

Skickat från min D5503 via Tapatalk

 

No it hasnt. An empty condition with a Time More works from mission start. But place a Time More after another condition, and it would be time since that condition (thats broken now).

I have two very trigger heavy mission based around this, and it worked like I describe. Now it doesnt, thats how I discovered that something was a bit off. Well actually while making a new similar mission.

[Fisherman82]

Ok I did not know it worked like that

 

Skickat från min D5503 via Tapatalk

[Grimes]

It has never worked like that. Time more and time less have always been relative to mission start. Time since flag is the only condition like what you are thinking. The order of the conditions has never had an impact how other conditions are interpreted.

 

Tested in open beta and release build. I would revert an install back to 2.5.4, 2.5.3, or older but that is to much effort to test something that has never been the case.

[Knock-Knock]

Nah you shouldnt either.

 

Maybe it has been bugged then, cause it really worked like that for a period. I experimented heavily to find a way to do what I wanted a few months back (july it seems), and placing a Time More after a condition added a delay of set time, and it worked, cause I can tell a few seconds apart from 3 minutes, especially while trying to maintain a close formation.

 

Shame if that isnt the case anymore though - for me at least.

And it has been working like that until very recently. I have a small trigger zone attached to a given plane (unit inside moving zone), which triggers a random flag (1 to 4). Each value is then tied to a time more. 30, 60 and 90, while the 4th doesnt exist (want no change/reaction). Now I would fly next to a plane (intercept), close, inside 164 feet, and it would randomly 'react' after a given time, depending on what flag values was picked. Some even as much as 5 minutes, and others just a few seconds. And it worked.

 

Attached shot of what Im trying to explain.

[Grimes]

So it was something like this?

 

Flag 101 == 1 and time more 30

Flag 101 == 2 and time more 120

Flag 101 == 3 and time more 180

Flag 101 == 4 and time more 300

 

Were you testing it right at mission start as opposed to testing after however long within the mission? If you are testing that functionality right at mission start then the results should be as you expect, however if done later then chances are whichever option gets chosen will execute immediately.

 

At any rate, the time since flag condition will do what you are wanting.

[Knock-Knock]

Oh man, now I just have this stinging sensation that I have been fooled all along. Cause I remember sitting with AI vehicles driving into a zone with then 10 sec or so time more etc, to delay an action. But I could just have been fooled by the mission time, since I made short tests.

Now for the flying on the wing, I have those trigger 'small', so I need to get in real close. Im pretty good and going very close and keeping it there, but here it triggers a waypoint change (returning to base for landing), and since AI is so abrupt, I might just keep that little bit of extra distance and not realizing I might even be outside the zone.... oh man if this is the case. i have place hundreds of triggers in those two missions, haha....

Oh man I really hope that isnt the case, cause using time since flag and having multiple choice, ouf, thats a lot of extra triggers.

[Knock-Knock]

Oh well, I guess I can just use a Continuous Action -> Random (1) instead, and save a lot of triggers (and time). After numerous tests, it triggers anywhere between a few seconds to 6m20 was the longest I had. I wont have a ignore, well maybe if the dice falls 'my way'.