I am having some issues importing a P2A flightplan into MSFS. I create a plan in SimBrief, import into P2A and add SIDS / Stars / Approaches as required. 
(At this stage MSFS is already open waiting at the front menu) I then export from P2A to MSFS format, open the world windows and import the P2A flight plan.

When the flightplan loads in the create flight window all of the Nav points are correctly listed (ie Rainy Pulox CS LOC10 etc). My problem is when I go to fly, the majority (but not all) of the Nav points in the FPL (and on the G1000 display) are labelled User1 User2 User3 etc. it definitely changes all the Fix point names of the Approach to the word USER, and I think it also changes the STAR names, but it doesn’t always change the e route names.
Is there something I might be doing wrong going from SimBrief to P2A to MSFS. I just figured that if I used the P2A flightplan in MSFS then I would have a better chance of them working well together.

Since the plan is correctly displayed by MSFS in the Flight Planning window, the problem is likely with the aircraft.  It could also be a data issue where the aircraft is looking at outdated data and not able to find valid waypoints.

Also, make sure you're using the latest Beta of P2A as there have been some changes to the export for MSFS in the betas.

Dave

Hi Dave thanks for your quick reply. What I have been able to ascertain that your flight plan seems to correct, but when I am importing it into MSFS no STARS and appraoches are being recognised. No STAR or Approach is listed in the flight plan - just the final destination. On the main 'create a flight' page both of the MSFS drop down list for arrival and approach are empty.  All of the STAR ans Approach nav points are being labelled 'User' and they appear in the enroute section of the flightplan.

I have been testing this in my Kodiak simulator, so I will try again using in a C172 with glass cockpit, but my first thought is that I possibly have a setting wrong which means MSFS doesn't recognise that I have slected the STAR/Approach. Do I have to 'ignore SIDS and Stars' when i export from P2A and just always have to manually input them?

 Any thoughts or suggestions are greatly apprecaited.

 

Cheers Chris

Hi Dave. I just tested the same flight plan with the default Cessna G1000 and had the same issue. The nav points for stars and approach are relabeled 'usr1' etc and appear under the enroute section. Just wanted to give you as much info as possible. Happy to send you the pln but I have checked it and it looks fine (all nav points are properly named) just hoping there is a way to get MSFS to recognise the stars and approach we have selected in P2A

Cheers Chris

Yes.  Please email the .pln file to [email protected] along with the P2A log file so I can check them to see what might be going wrong.

P2A Log files are located in: C:\Users\<UserName>\AppData\Roaming\P2A_200\Logs where <UserName> is your PC user name. 
Portions of the path may be hidden by default, so be sure Windows Explorer has Show Hidden Items checked in the View tab.
A new one is created each time you start Pilot2ATC, and is closed when you shut it down. So if you take the most recent one after you have the error and after you shut down P2A, you should have the correct one.  

Thanks,

Dave

There were some bugs in the program causing this.

2.6.4.2 Beta 5o should fix this.

Dave