I have a problem that I only seem to have with the PMDG 737 NGX: when I start the plane and haven't touched my toebrakes yet, I can get moving with just a litte throttle (25 to 35 or something like that). However, whenever I have used the rudder and the toebrakes and have to stand still and get moving again (for a hold on the ground but also for taxi after landing) I have to give almost full throttle and the plane won't start moving before I hit something like 70! This means I quite often hear that beep during taxi that my throttle is opened too far...

 

What setting should I look at to remedy this?

 

BTW Yesterday suddenly the rudder wouldn't stick when I applied them: whenever I used rudder I could see the rudder onscreen move but immediately they went back again... I had to open the rudder's control panel and check the axes there (all was fine) and after that it suddenly worked again in the 737 NGX too... Odd...

If you don't use this all ready I would recommend it 100%, works so well with the NGX. Well every aircraft.

http://forum.avsim.net/topic/392772-inherent-flaw-of-fsx-to-give-too-much-ground-friction/

If you don't use this all ready I would recommend it 100%, works so well with the NGX. Well every aircraft.

http://forum.avsim.n...round-friction/

 

I don't feel like going through that thread but I heard it makes the NGX taxi too easily?

It will taxi on idle, unless your loaded up then you need a bit of break away.

At around 100 PAX 7000 fuel and 5000 cargo it taxi's on idle around GS15, I think that's perfect, last night I had around 150 PAX 7000 fuel and 6000 cargo, I needed to just break free and then on idle GS was 5.

I'm sure PMDG said the NGX IRL taxi's on Idle.

 

When full and more fuel etc you will need a bit of throttle, but not much.

 

I love this mod.

Er... and where can I find that mod? I see numerous links and files and dropboxed and what not...

http://forum.simflig...pdated-modules/

 

FSUIPC4.859m

 

You will have to go back to that long post because unless this version changes a link in your FSUIPC4 you need to add a line to make it use the module.

I had this same problem last night. I don't suppose you use FSUIPC to calibrate your rudder pedals? I do, it is fantastic for calibrating them and my yoke and throttle quadrant. Since I have the registered version I create profiles. In my situation last night I had installed the ASA 900 livery for the NGX and forgot to assign it a profile. For some reason this was causing FSX to apply full braking power even though there was no brake message. All I had to do was assign the new livery to my B739 profile and everything worked fine. Just sharing because something there may prove useful for you.

Jeroen, i've had exactly the same problem. After touching the brakes for the first time, and releasing again, i had to apply more throttle to move my NGX again. Something to do with a screwed up saitek driver i guess. I found a solution which solved the issue for me. http://forums.eagle.ru/showthread.php?t=85210, post #8 especially, the regedit.

 

Only thing I had to re-assign saitek controls in FSX again.

 

Hope it helps.

Jeroen, i've had exactly the same problem. After touching the brakes for the first time, and releasing again, i had to apply more throttle to move my NGX again. Something to do with a screwed up saitek driver i guess. I found a solution which solved the issue for me. http://forums.eagle....ead.php?t=85210, post #8 especially, the regedit.

 

Only thing I had to re-assign saitek controls in FSX again.

 

Hope it helps.

 

Bummer... didn't help.

 

http://forum.simflig...pdated-modules/

 

FSUIPC4.859m

 

You will have to go back to that long post because unless this version changes a link in your FSUIPC4 you need to add a line to make it use the module.

 

Bummer again. I don't own FSUIPC. Maybe I should contact Saitek... Strange thing this is.

 

EDIT

Hm, odd, I can't register on the Saitek forum... However, I found a FAQ about the rudders and I noticed by default the null zones in FSX are wrong: I just changed them to what Saitek advices and it seems the problem is cured... I will report back after completing a few flights.

Report: the default null zone that FSX applied seems to have been the problem indeed. I just finished a flight and WOW do those rudder pedals and toe brakes work well now...! I never taxied this easily!

 

Here is the information from the Saitek site that helped me (in case anyone reads this in the future):

 

Start by going opening FSX and going to Settings > Controls > Control Axes. Select the Rudder Pedals in Controller Type. Double click the Event Brake (left axis) and depress the left brake when the change assignment box appears. Left toe will appear in the window, and then click ok. Repeat the process for Brake (right axis) and the right pedal. Make sure that there is a tick in the Reverse box for both brake axes. Finally, double click Rudder Axis and perform the rudder movement, so that the Change Assignment window detects the rudder axis. These are the only three axes that should be set to the pedals, if there are any more in the list delete them using the Delete Joystick Assignment command.

 

Now that the axes are set, go to the Calibration window. Select the Rudder Pedals and then select Advanced Controls. Make sure that the sensitivities for both brake axes are set to 75-80% and that the null zones are set to 0% for both. The rudder should be set to 50-75% sensitivity with a small null zone of about 5%.

 

Before you load a flight, you will need to disable Auto Rudder. To do this, go to Settings > Realism and make sure that the Auto Rudder box does not have a tick inside it.

 

By default the null zones were something like 25%...!!! Setting them to 0% (and also changing the other settings a little to come closer to what Saitek advices) did the trick!

You don't need a reg version for it to work.