solisto

I also had this same exact issue. I ended the mission and moved on.

I landed RWY 25. Straight in approach from WP15. I double and triple checked the diagram, and checked the situation map (F9 I think) to see if I was in the wrong place. I tried stopping in the second spot on the left but did not get a shutdown prompt. I re-parked in the spot with the C130 and finally got a shutdown prompt. Once completed and I got a passing rating, I did see the extra congratulatory items, nice touch btw.

Good to know, I did not know this was an option.

The mission is great and I like how all the previous missions are incorporated in this final mission. It's pretty exhilarating making 90 degree banks at 300 kts just a few hundred feet off the ground. One last thing I noticed, there is a C-130 parked in the designated parking spot (first revetment on the left). The end of the mission does trigger properly if you park behind him but there is no room to do pull a U-turn at.

Well as I stated before, staying in formation with the FE is a guaranteed fail(at least for me), his DTOT's are late and so he arrives late. I have run this at least a dozen times in the past couple of days with various changes and adjustments including take off time. The only adjustment that works for me is to break formation and ensure that I am at the WP on time. That being said, I really enjoy this mission and the campaign and I am a much better pilot as a result of these. I wouldn't provide feedback if I didn't like them. Thanks for the work you put into these and the support you provide.

BFT12 weirdness There is something wrong with BFT12 on the A10C for 1.5.2. It's been brought up a couple of times in the past, but as was said before this mission is impossible to pass by following the FE in formation flight because the he arrives at each WP late. I do not believe this is due to the AI's wonky flying but rather by the DTOT set in the CDU for each WP. Somewhere or somehow in the campaign version, the DTOT for each WP is being miscalculated. I can pass this PO in the practice version of it with no problem but fail the campaign version because I get to the WP too late. For the campaign version, checking the DTOT on the CDU; WP5, WP10 , & WP15 are set past the required time. I have tried turning on the CDU as soon as possible (06:15:50) and tried turning it on later during the startup (06:23:00) and various points in between. This results in differing times for each WP, with the earliest DTOT for WP5 being 06:42:01 at the earliest CDU start of 06:15:50. What I did find was that the elapsed time between the WP's are consistent even if the DTOT is different. So from WP5 to WP6 the elapsed time between WP5's DTOT and WP6's DTOT is always 55 seconds. This consistency is always there in the campaign as well as the practice version. The difference is that the practice mission's DTOT for WP's 5, 10, & 15 are set correctly. The only way I was able to pass this was to manually set the DTOT for each WP and then leave the formation once I joined to hit each DTOT within requirement. When I reached WP15, the FE was several minutes behind me. My guess is that the AI is flying erratically (>140kts from WP4 to WP5) because it is trying to hit the RIAS for the DTOT. WP5 to WP6 RIAS is over 330Kts and I assume the AI is gaining altitude to gain speed by zooming down. Take off time is 06:30:00 +/- 10s I have watched Recon Stewart's video (SOP prior to each mission) I do not get Unq'd for breaking altitude limits DCS World 1.5.2.48720 OpenBeta BAQ as well as the latest version released 12/30 Attached is a pdf showing the DTOT that was set in the CDU by default for both campaign and for practice for each WP. Practice had some weirdness for WP2-4 but did not effect passing the mission. To pass the campaign, I had to manually set the DTOT for each WP in the CDU using the practice mission DTOT (thanks BFT10). BFT12.pdf

This is for OpenBeta A10C BFT missions in DCS World 1.5.2 In BFT10 for A10C, during the third user input waypoint objective (the UTM one) when flying at the prescribed altitude of 12,000 feet, I get a failure due to incorrect altitude. I was failing this whether at the default altimeter pressure setting or at Batumi QFE of 29.89. With cockpit altimeter indicating 12,000 at 29.89, the altitude reported in the F2 screen is ~12,493. This issue was reported in the F15C forum. But search did not find a reference to this anywhere in this thread or in the A10C forum. And since I've ran this several times thinking I was doing something wrong, I am putting this out there as a general FYI. So either fly at a few hundred feet below target or check the F2 view to verify altitude