ghulley

Found the problem. I had to reset FSUIPC flaps settings and all is working well.

This might be an issue with the Airbus install after all. After setting aircraft state to "ready for take-off" the flaps are set to full instead of 1+F. I installed the 1.16 update over my existing 1.10 so maybe something got messed up. Will try reinstall from scratch.

No, flaps are unassigned in both FSUIPC and in FSX. I've been using F7 to get the flaps extended. This is the first time I'm using FS2Crew with the bus. Going to try re-install and see if that helps any.

Just installed Airbus x v1.16 and everything works fine except the FO is not setting flaps correctly. After start: FO sets flaps to full instead of 1+F (as set in MCDU) After takeoff: FO correctly retracts flaps Approach: FO does not set flap 1,2 or 3 but announces speed check correctly. Flaps full is however set After landing: FO sets flaps up correctly Replicated it now on 3 separate flights. Seems like FO is only setting flaps full or up, nothing in between. I am pretty stumped.. Any help?

In addition to the 13 suggestions above, keep LOD_RADIUS at 4.5 for the PMDG 777 and tweak AI and autogen to stay within limits. Use FSUIPC to monitor your VAS usage during the flight. I find if I don't switch views too much I stay within limits. Glynn

Does PFPX calculate derated thrust options on takeoff for different aircraft? Or do we still need TOPCAT for this?

Anyone know what liveries are released with the product, and where to find repaints?

Just thought I'd chime in here and let everyone know that I can vouch for RJ McGill's credibility as an experience pilot. I have spoken with him at length via PM about his flying background and he has responded with a wealth of information on his flying experiences with the JS41 for Delta Connection, which was very informative for me, and has helped me to fly the PMDG JS41 correctly. I suggest anyone else interested should contact him directly, as he is more than willing to give advice. It has also been interesting listening to his 763 experiences, as I am a huge Level-d fan.

The reason I didn't reply to your post is because my problem had nothing to do with navigation skills, i.e. tracking a VOR radial. Perhaps you should have read my problem a little closer. Thanks for sharing your knowledge anyways. Paul I set up the OKSET departure again exactly as I did before and this time NAV worked! So I'm a little confused with this, it seem to occur randomly. Frank thanks, I will try the GPS trick the next time it happens!

Oh thanks, but I figured out my problem. I was unknowingly mixing FSX and FS9 flightplans in my scenery folder, and in this case FSX defaults to using only the FS9 flightplans, while my CRJ aircraft were in the FSX flightplans. I updated all my FS9 plans to FSX plans and the CRJs are all appearing fine now

Okay thanks for that, there must be something weird going on then because I am also following the tutorial line-by-line, including the FMS programming. I will post my screenshots later tonight when I have more time.

Mmm.. interesting. Can you tell the FMS waypoints you used until OKSET? Or did you simply use FAPE-OKSET as your first nav waypoint?

Hi Paul, Yes, exactly right. At DME 15 I set a heading direct to OKSET using HDG bug, and then select 'Direct to' on the FMS, and change to NAV lateral mode. The aircraft then turns right off track to 360 degrees and maintains that course. This behaviour is repeatable, and I've tried this departure 3 times with the same effect. I have the same issue at FAJS when flying the APDAK departure, so my conclusion is that NAV with 'direct to' will not work if your first hard fix is >90 degrees from your initial departure heading. As I said before I'm surprised no-one else has picked up on this, but perhaps just because South African airports have some unorthodox departure procedures. Although I did see some posts with similar NAV problems that were unresolved, so perhaps this is the cause. What I eventually did was modify the AIRAC OKSET SID for FAPE by replacing the 'Heading to DME' procedures with hard fixes (i.e. PEV9, PEV15 etc). Now when stabilized on the climb out to PEV9 I can hit NAV and everything works fine. I'll attach a screen shot later if that helps. But it does seem like a bug that should be fixed. Other than that little quirk, this aircraft is just such a joy to fly!

Are there any CRJ base models out there that work for FSX AI traffic? I have almost given up looking. All the models that used to work in FS9 AI traffic for me (e.g. TFS, Opensky) all do not work with FSX.

Actually there is nothing wrong with my planning and have been flying this departure for many years with other aircraft, but perhaps I should've been more clear. I'm flying a perfectly normal departure out of FAPE - the OKSET2A from rwy 08: (http://www.caa.co.za/resource%20center/Charts/AERONAUTICAL%20CHARTS/P/FAPE_PORT%20ELIZABETH%20INTERNATIONAL/DEP_03/FAPE_DEP-03.pdf) The fms scrambles the SID from the latest AIRAC so I have to fly the departure using VOR instruments, which is fine, but After circling right, the last part of the SID calls for direct to OKSET at 15nm from FAPE flying west (Cape Town is west of PE), and using 'Direct to' OKSET in the FMS and NAV does not track to OKSET. So I'm assuming the fms does not like your initial waypoint to be in the opposite direction of your initial rwy heading. I will have to try get the SID programmed correctly, maybe try another AIRAC cycle. My FROM and TO are initialized in the NAV page as FAPE and OKSET. I've tried RWY08 and OKSET and that doesn't work either.