Recently we have seen a lot of codes used to unlock our products being offered for discounted prices. Almost all of them are bought using stolen credit cards. These codes will all be blocked by our systems and you will have to try to get your money back from the seller, we are unable to assist in these matters. Do be very careful when you see a deal that is almost too good to be true, it probably is too good to be true.

Jump to content

dmiannay

members
  • Content Count

    33
  • Joined

  • Last visited

Community Reputation

4 Neutral

About dmiannay

  • Rank
    Flight Student - Groundwork
  1. All went well, Steve. Only thing I'm seeing now is an inability within PFPX to add a CI value for A319 liveries. Thoughts?
  2. Ok Stephen. I typed in "20" and it entered "CI 20" in the field. I saved the Aircraft config and will see how it goes with the next flight. Thanks a ton for all your time. Doug
  3. Ok, I see where that is done in the Aircraft Editor under Cruise/CI in the "Default Speed Schedule" section. The three choices there are .78, AE250, and LRC. I'm not knowledgeable enough to understand what values to change. Thanks for your patience. Doug
  4. Thanks for taking a look, Stephen. Here you go... KLAS-KIAD.pdf
  5. Stephen, I d/l the files and installed per your attached ReadMe. The created FP now shows "TOC ISADEV: +01C", but I can't find any Cost Index. Furthermore, when I import for FP into the A320 via the MCDU INIT A page, the Cost Index field is still empty. Am I doing something wrong? Probably. Please add a bit more detail about how to tweak PFPX using the new files and then the specific steps to get the appropriate FP imported into the FSL A3xx. Thanks again! Doug
  6. Is there some way to modify PFPX so the exported flight plan for my FSL A3xx includes the computed/recommended cost index? I did a fairly extensive search here and haven't found an answer yet. Thanks for any suggestions. Doug
  7. Steve - I just created a flight plan that did not include DCT in the alternate destination routing, and the flight plan imported as expected when entering the flight number and selecting "Init Request". Happy camper here! Thanks, Doug
  8. I did this exact same procedure prior to PFPX v2.x and it always worked perfectly. After updating to v2.03 it no longer works. I get the same "Invalid Flightplan" error. For the time being, I can still import the FP by adding the departure and destination airports ICAO codes into the MCDU and it then shows me the exported flight plan, which I can then import. But I did prefer the former procedure that is no longer working. I have confidence you will get this sorted soon enough. Doug
  9. Check this thread where Stephen led me to the correct procedure. My "Save" button finally lit up. Doug
  10. It appears you are using the older AIRAC 1607 database that comes with PFPX v2.03. I can't be positive about this, but I had some issues with my install as well until I updated PFPX to the latest AIRAC, 1813. Perhaps the "tracking" code doesn't see valid NAV data.
  11. Got it... thanks again, Stephen for all your hard work. Truly magnificent tool. Doug
  12. I did all that, and I now see tracks on the map, but the Save botton is still grayed out. See my screenshot below with the following questions: 1. When I CTL-A and CTL-C on the PilotWeb page, it takes all the text on the page, which includes the title section. 2. There is a special symbol that now appears between each text grouping. 3. Is there something else I need to do with the copied PilotWeb data to edit it before pasting into the Tracks page? Thanks again! Doug
×
×
  • Create New...