I'm sort of new to this software, about a month since I bought it. I never had much of a chance to test it because 10 days isn't enough time to learn it and test. So I bought it trusting that what was advertised was correct but in fact it appears that I paid for a beta instead of a final version. I have been having all sorts of problems with it and made multiple adjustments according to what I find in the forum but more issues appear randomly.

The latest is with the flight plan scattering the waypoints all over. I enter waypoints and they can be inserted at the bottom of the flight plan or at the top or anywhere it chooses. I move them up or down to the correct position but when I validate the plan they get scattered again wit the TOD at some crazy location near the departure airport. P2A wants me to fly back and forth between waypoints but of course I declined to use those flight plans when this happens. Sometimes it's like P2A reversed the entire flight with the waypoints in sequence but backwards from the destination to the departure. So, the first waypoint at the departure is the last waypoint at the destination. Crazy ah?

What I found that fixes that issue is to export the flight plan to the sim folder then import it to P2A. Then everything falls in the right place and I can fly the plan. But I shouldn't have to do that.

I feel like I'm a guinea pig testing this software for the people whom I paid. Sorry.

I doubt you are a guinea pig.  There are thousands of happy users.

You are obviously doing something incorrectly, but without any details about what you entered and in what order, it's impossible to diagnose the problem.

In general the waypoint entry goes in this order:

Departure Airport ICAO

Destination Airport ICAO

Any route fixes in the correct order. 

Add procedures, if desired: SID, STAR and/or Approach

Set Cruise Altitude, Planned GS, Descent rate, etc

Validate the plan.

Dave

 

I always do all that in that order. And that was my point. There's no indication of anything being wrong. Please note that when I export it to a *.pln and re-import it it all works fine. Also all my old *.pln files import well. At this point if I need a new flight plan I create it with Plan-G and import it to P2A to avoid the hassles. Hardly what I anticipated.

Out of about 29 flights only three were successful with P2A. All others failed in one way or another. Yesterday I flew a short flight and it went well to touchdown. I got instructions from tower to advise after vacating runway and the copilot read back correctly. When I vacated the runway the copilot would not advise atc so I did. I waited a long time but never heard from atc, so I taxied to the gate and when I shut the engines off the copilot called atc indicating runway vacated. ATC called back and told us to contact ground. Is that the way it's supposed to work?

I was on a flight for my VA and I could not wait for all that to be resolved so I paused the sim and filed my PIREP, then shut everything off.

Some of us fly for VAs and all the delays caused by waiting for P2A are recorded and in some cases if we run late on the schedule we get penalized. That being the case in some flights I had to disconnect P2A and continue without it.

If you send me an example of entering waypoints that doesn't work, just a list of the waypoints in the order entered, I can test and try and find the problem.

Some calls must be initiated by you either using your voice or manually pressing the SayIt button.  These calls are the calls, like requesting clearance, taxi, etc. and also the "Clear of Active" call.  This is so you can determine when you are clear and make the call to Tower.

Dave