Jump to content

Mission 5 LANTIRN/Gbu run issue


Go to solution Solved by Reflected,

Recommended Posts

Posted

Hello all. For whatever reason I'm having a hard time having Chig lase the target and callout the drop. I'm pretty sure I got the pattern down 11k@450, 15 sec...break right climb to 15k@400 while keeping the target 5mile on 90 degree on my right. I was watching various YouTube others flying this mission and at some point Chig will call out the target about 90 degree east bound, but I never got that.  He's just quiet on the entire mission.  I must have retried it >10 times.  I also notice at the start of the mission and throughout the duration of the pattern the laser code keep blinking on the 2nd digit 1x88 (x is blinking and keep cycling from 5,6,7 and back to 5) even though it seems Chig is aiming the LANTIRN correctly at the power station.  Despite lack of his cue, I drop the bomb anyway and it's definitely become dumb bomb as he's not lasing the target. Has anyone ever seen this ?

PS: I was thinking something is wrong with my binding so I reset it to default and re setup (even reset the Rio binding too)

Posted

Happy to report the fuse changes was it.  What I did is I just copy that mission to my saved games so I can just replay that piece. If I just open and play it straight up the problem I described above occurs. The only thing I change was to just go to Mission Editor, swap the fuse to be something else, and reselect the original and proceed to fly with that configuration.  The whole problem goes away.  I guess no need for screenshot since that's definitely the issue.  Thanks for your help.

Posted

Now that we know what's the root cause is, how do we proceed though since paid campaign are protected and lantirn miz file is loaded automatically since no way to set your own ordinance?   Wait for next update ?

  • Solution
Posted
1 hour ago, ReemanChamp said:

Happy to report the fuse changes was it.  What I did is I just copy that mission to my saved games so I can just replay that piece. If I just open and play it straight up the problem I described above occurs. The only thing I change was to just go to Mission Editor, swap the fuse to be something else, and reselect the original and proceed to fly with that configuration.  The whole problem goes away.  I guess no need for screenshot since that's definitely the issue.  Thanks for your help.

Awesome, thanks! I’ll submit a fix to ED ASAP

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...