September 24, 20205 yr Hi Dave, I don't know if you've used MSFS 2020 yet but I ran across something odd when importing a flight plan. This is a flight plan from KPHX to KSAN. It was constructed using Simbrief. I exported to MSFS 2020 and P3Dv5. Once I import into P2A and do autoplan I get the normal output with the P3D plan but get a plan with a bunch of extra waypoints when using the MSFS 2020 plan. I've added screenshots of both to compare. I'd be curious to know what you think. MSFS 2020 P3Dv5
September 24, 20205 yr Have you looked at the .pln file contents as it comes out of simbrief? I have not found MSFS adding interim waypoints and instead if a numbered airway is spec'd in a .pln file MSFS seems to strip it out. my experience is limited to general aviation flights using low altitude victor routes in he USA. Edited September 24, 20205 yr by fppilot Frank Patton Corsair 5000D Airflow Case; MSI B650 Tomahawk MOB; Ryzen 7 7800 X3D CPU; ASUS RTX 4080 Super; NZXT 360mm liquid cooler; Corsair Vengeance 64GB DDR5 4800 MHz RAM; RMX850X Gold PSU;; ASUS VG289 4K 27" Display; Honeycomb Alpha & Bravo, Crosswind 3's w/dampener. Former USAF meteorologist & ground weather school instructor. AOPA Member #07379126 "I will never put my name on a product that does not have in it the best that is in me." - John Deere
September 24, 20205 yr There is something about the .pln file for MSFS 2020. It's been a gamble on weather any one piece of software will like it. What's been working for me is I've made it a habit to export an .fms (X-Plane 11) and a .pln file from what I'm using (Simbrief, Little Navmap, P2ATC). The .fms I use to import my flight plans into other software and the .pln I reserve just for importing into MSFS. Have had very few problems since.
Archived
This topic is now archived and is closed to further replies.