Martin Connor

JIm, Thank you so much for the information. I will mark it as closed and delete the comms. Hopefully that will make it function correctly. I have unintentionally set about a revised version of KORD, but it is going to be a lot of work. I can see from the Sat pictures that they are a long way from finished with Taxiways to nowhere in evidence. I must do some homework and find out what the plans are. Happy new year. Martin

After a flight to KORD, I noticed they have finished adding runway 10R, so I got to work adding it and all the taxiways. I looked up the new ILS Freq and Call Sign and all seemed to be well. However, when I flew in with 10R entered in the FMC, and 110.9 on Nav 1 and Nav 2, all was well to start with, but as I approached the field, the FMC changed to I-OHA with a course of 144 degrees. Further investigation revealed that KORD now has 14L and 10R on the same frequency, and the FMC flipped over at some point. Presumably this works in the real world, but I wonder if it was an unforeseen condition for PMDG ? I checked the charts from AirNav and confirmed the data set from Navigraph, and they have definitely used 110.90 twice.

Many thanks, but I I thought I heard the FO confirm Hyd were off when they were on. I'll check it again.

Hi, I've noticed that the hydraulic pumps are left on during the shutdown procedure, then not caught by the Shutdown Checklist. Martin

Having published KMSP Scenery, I've had a user point out that the ATC never says Minneapolis Tower, but simply Tower, and this is true of all the other communications with this airport. The stock airport works correctly, I've checked that in ADEX (Current) the Comms are all set with Minneapolis prefix, and the Airport Properties are identical to stock, so not sure where to look.

Thanks Bryan, grovel to PMDG in order I guess.

I'll apologize before I start this thread, because I know the answer will be obvious when it's given. On the descent, I get the QNH value for the arrival airport before getting to the transition level, and set it in the captain's altimeter. I have my aircraft set to sync, so all three altimeters take the same value. However, when passing the transition level, the FO states he is setting his altimeter to 29.92. What do I need to do to get the FO to set it to the value I have entered? Thanks Martin

Thanks Bryan.

Thanks Guys, I was missing the "Select". It looks like a long stretch for the pilot flying to reach to the far side of the MCP to press the CMD A button whilst in control of the aircraft. Martin

When as pilot Flying, I have the autopilot off on climb out, and can instruct the PM to select LNAV, VNAV HDG SEL, but not Autopilot. The PM responds with CHECK but does nothing. I can press Cmd A myself, so the conditions for engagement are met. Any ideas please? Martin

I'd like to be able to simulate realistic traffic at my new KMSP-AI version of Minneapolis St Paul International, but I just don't seem to be able to lose NWA. If I knew exactly which airlines can use which stands, I could simply leave them nowhere to park, but there should be no schedule for them, yet there they are. I am using World of AI to simulate the main airlines, but NWA isn't among them. I've tried moving trafficaircraft.bgl out of the relevant folder, but they doesn't kill it either. Any ideas folks? Martin

I used the model method to compile and distribute the airport. Am I right in assuming that had I created a library of my custom models, people would be able to extract the models, but by using the Models method, they are embedded in the <airport>.bgl file, and cannot be extracted? All in all, I'm happy with the way it works. I don't want my models being used without permission. Many thanks for a great product. Martin

I've recently published my version of KMSP airport on the avsim library, and one user has come back and said that he loaded the bgl file into ADEX, and the buildings are missing. Am I right in assuming that this is because all the MDL files that make up the project are unique to my computer? Again, I assume that this works on MS provided projects, as there is a library of models backing it up on every FSX install. Martin

Whilst the previously described registry fix worked when applied to my Vista 32 based system, my new Windows 7 64bit seemed reluctant to bend to my will. I then discovered a conversation in which the user changed the rudder peddle sensitivity to max, i.e. sliders to the far right. I tried this, and discovered that it worked just fine, when prior to that, I had the brakes coming on and staying on when applied. I wonder if removing the registry key somehow resulted in the sensitivity setting being deleted, and the firmware setting itself to max. Anyway, I thought I'd add this addendum to the solution.

Again, thanks to all who contributed their thoughts. I'm old enough to remember being totally on one's own when trying to resolve these kind of problems, and when drivers came in the mail, or if one was blessed, by CompuServe. Not so happy days Regards Martin

Many thanks Patrick, Deleting the registry entry worked. Unplugging deleting and replugging didn't quite hit the mark, had to quit out of Profiler and restart it, and also reset the controls in fsx, but in the end the result was a fix. Regards Martin

No sign of this behaviour from 747-400. I think I remember reading that PMDG added some modifications to improve ground friction modelling. Could something derail this with the Saitek Rudder?

I've tried using both methods. What I find interesting is that FSUIPC Logging shows no activity from the rudder pedals when brakes are off, so I am rather discounting noise. I assume that when using the toe brakes, variable amounts of braking should be available. Since the default B key is either on or off, did this variable braking get included as normal behaviour? I am guessing that most people find it works ok, but then I lived with it until I realised the effect of toggling the Autobrake switch on the PMDG. I'm also wondering if my take-off rolls have been excessive due to this drag, which doesn't heat up the brakes as it should. Going to see if the PMDG 747-400 also does this.

I've tried all the options suggested, and no deal I'm afraid, though I did find a new and exciting way of Blue Screening by setting the Rudder Pedals (Saitek) to Bands - 0-100%. Checked Saitek site for new drivers - download site down -. Guess I'll just continue trying to taxi without using the brakes.

Proved that the problem relates to the rudder pedal usage, but using FSUIPC (Free addition). I can see no evidence of the pedals sending spurious signals. I'll try Scott's solution tomorrow and hope that cures it. Thanks to all for your responses.

Thanks again Kyle, I'll try experimenting with the pedals when I get home. I don't use FSUIPC Paid version, so basically FSX and Vista standard.

I have Saitek rudder pedals Kyle

I've always noticed that once pushed back, the initial power required to get the aircraft moving is minimal, but as soon as any braking.or thrust reduction is needed, getting the a/c moving again needs a lot more power. I discovered by accident that switching from RTO to Off reset the braking effect, and we were back to low thrust inputs again. I originally thought that it was RTO itself causing the problem, but then I realised the problem occurred even with RTO off, but could still be cured by cycling RTO. Anyone have a clue if this is a local problem, or is fixable? Martin

I don't think the real aircraft can detect turbulence on radar, but we all wish it could.

Thank you Dave.