PilotEdge Forums

Now that we're done with the AOPA Summit here are the steps to launch:
1) resolve the remaining issues (pilot/controller stability issues and pilot client compatibility issue with some machines) (one stability issue remains)
2) determine the operating hours for the public beta (done)
3) launch the public beta on X-plane (done)
4) develop FSX client (now in alpha)
5) develop FS9 client (now in alpha)
5) finish work on billing system and account management for public network
6) resolve issues that arise during the public beta
7) swap to the production operating hours, launch, and hold on tight.

9) Change pants.

10. ??????????????????????????????????????????????
11. PROFIT

It seems like when we got everyone onboard during the AOPA summit, my system would start to have issues before the plugin would crash Xplanes. I'm curious if I was the only one?

Maybe we should arrange some play sessions in the evenings to put a load on the system and see what shakes out.

Pending a system test, step 1 is done. I agree, Adam...the problems we've seen on the pilot side are traffic related. The problems we've been seeing on the controlling side are a mixture of pilot and controller related.

I'm organizing a system test for this week, see the Pilot's forum for info.

Step 1 is done. Step 2 has been proposed internally, just verifying controller availability. Public beta will be starting in a couple of days.

Step 3 done

Edit Dec 29: Mac client released for X-Plane.

Clearly a few things came up and we're a teensy bit behind schedule. The FS9/X client is coming along (at long last). Hang in there, this will be off the ground soon!

I must be missing something. I don't understand how the FSX client (still in alpha) is different from what we've been using up to now.

I don't understand the question. Can you rephrase?