Jump to content

Proximity Trigger not working correctly


Recommended Posts

I have a mission i build half a year ago, that uses a proximity trigger between my plane and a bomber to escort. mission always worked perfectly.

Started flying a few weeks ago, had to resave the said mission, now for some reason the proximity trigger is broken. It fires as soon as the mission is loaded /selected (by random switch) instead of triggering when i am closing on to the bomber.

Behaves as if "further" was triggering. Tried reassigning the objects (player /bomber), tried completly new trigger, tried to switch to "further" instaed of "closer" (maybe a bug reversd it) - same, still fireing at mission start. Any ideas?

Link to post
Share on other sites

The proximity trigger is working as expected.

Post the mission as JimTM suggested.

 

Better yet as I recently said in another thread, isolate the logic into a simple test mission, use subtitle MCU's as a debugging device and run a test.

Then if it works, you know it's something amiss in your full mission.

 

I for one won't have time to delve into a full mission and debug it, but someone else might be able to. Simple test missions are best.

  • Upvote 1
Link to post
Share on other sites
12 hours ago, Gambit21 said:

The proximity trigger is working as expected.

Post the mission as JimTM suggested.

 

Better yet as I recently said in another thread, isolate the logic into a simple test mission, use subtitle MCU's as a debugging device and run a test.

Then if it works, you know it's something amiss in your full mission.

 

I for one won't have time to delve into a full mission and debug it, but someone else might be able to. Simple test missions are best.

i understand that, even i need time to get back into my own mission. But as i said, the mission work perfectly half a year ago, now after a few updates, i doesnt.

15 hours ago, JimTM said:

Please zip and post your mission files here so others can have a look.

Mission file attached -- mission is quite packed, the triggers (3 ) are the ones found NW of players base.

ProxyProblem.zip

Link to post
Share on other sites

Your mission is very complex, with logic spread out in various places so it's difficult to trace. Here's a couple of thoughts:

  • Your two proximity triggers NW of the player seem to be set up OK but I notice you have many more proximity triggers. Confirm which one of the NW triggers is firing right after mission start and what response indicates that the trigger fired.
  • Try creating a very simple mission with one proximity trigger set up as you do in your problem mission. If that works OK, then there may be a problem with your mission logic.
  • Thanks 1
  • Upvote 1
Link to post
Share on other sites

OK, tried to rebuild little proxy mission, it triggered like it should. So went back to my mission, changed proxy trigger distance, no change. Finally deleted the aircraft that players planes has to come close to, and inserted a fresh one - voila, it works again.

So in conclusion, either one of the updates, or the mission builder resave corrupted my mission file. bit of a bummer i must say, but at least there is a "solution".

 

  • Upvote 1
Link to post
Share on other sites
1 hour ago, ironk79 said:

OK, tried to rebuild little proxy mission, it triggered like it should. So went back to my mission, changed proxy trigger distance, no change. Finally deleted the aircraft that players planes has to come close to, and inserted a fresh one - voila, it works again.

So in conclusion, either one of the updates, or the mission builder resave corrupted my mission file. bit of a bummer i must say, but at least there is a "solution".

 

 

Nice recovery. That was a strange issue.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...