Meddo

Me too on the having 2 rear end me on several missions. On some collisions there was no damage so I continued. On one mission he damaged my A10 after several minutes of startup, so I was a bit upset. I turned the plane around and rammed 2 which caused a large conflagration and both planes exploded. Haha. Restarted. I thought it might be that I forgot to turn on the “ant-collision” lights. But it happened again with the lights on. This might be an interesting feature to add the night flights... forgetting anti-collision light causes a random chance of crash. Haha. Sneaky.

My DCS is currently 2.5.0.14138.321. I looked at the briefing and saw a table of radio frequencies at the end. Maybe I had the old version? Or maybe I don’t know what I’m looking for. Sorry I’m a bit confused on this point. After looking at the briefing, I noticed just now that there is a new update as of today 14304, and I updated to it by exiting DCS, rerunning the updater and allowing the update. I didn’t see any relevant notes in the changelog for Basic Flight Training missions, however, being in the software biz, I know that not everything that changed is always listed..... perhaps there were some related changes after all? Perhaps you could shed some additional light. Cheers

BFT09 trigger issues #me-too! I am having similar issues on BFT09. My first problem was that I had DEFERRED SHADING enabled and that caused my cockpit to be horribly dark. I thought the extreme darkness was a bit of joke (flying by Braille method), and it was impossible to see the dim runway until you were about 500 ft away. I searched around and found that DEFERRED SHADING is a problem for night lighting, and disabled it. Now I can see at night normally. Daytime is not an issue apparently. Unfortunately that is not where problems on BFT09 stopped. Here is a description of my current problems: I takeoff heading 300, fly heading 010 to Angels 8 (WP2). Once at WP2 I hear Rick bark 2 commands, "call the ATC for approach vectors to Batumi", and then immediately after he says "turn heading 260 angels 8 at 260 knots". I turn to 260 and follow the rest of the instructions. ** At this point there seems to be indication that multiple triggers are firing near the same waypoint** About 1/2 way to WP3 I get commanded to call ATC for vectors to Batumi. I follow instructions. Shortly after Rick tells me to turn towards ILS intercept and descend to pattern alt at 230 knots. I follow instructions. To skip a bit, I intercept the ILS at pattern alt, turn on final, and call Batumi to request clearance for landing, and begin slowing descent to 150 kts, and maintaining ILS glideslope and final heading until runway visual acquired prior to M.A.P. I land on the paint in the required zone, with a emphatic "GOOD" from Rick, and roll out and perform a go around as instructed, climb to angels 7 at 260 knots. Once I reach the waypoint on 120degrees after touch and go at angels 7, I get the ending "Let's see how you did...." sequence... however, I also get the "turn left to 040..." trigger as well. First several times I ended the mission there, and got a Q-rating... but I did not progress to BFT10. On subsequent trials I continued past and turned 040, and then 300, and got a new approach vector, and landed, taxied to parking, and shutdown. At that point I got a "Shutdown looks good" from Rick, and then nothing else for many minutes of waiting. There were no further instruction or indication of anything. I ended the mission, figuring I would have to try again, and at this point I progressed to BFT10. Something is obviously fouled up with trigger points. It seems that at least me and one other person are seeing this in the 2.5 open beta ( as of 2/14/2018 ) but I would bet many more are seeing this as well. Instructions and workarounds for problem areas and/or notices of bug fixes in these missions for 2.5 would be much appreciated. Regards, David