Not sure where this problems lies. I have a registered fusipc and have configured my throttles for the 737. I have dual quadrants from Saitek so that I can have bot a two engine and four engine profile. When I advance the two throttles I am able to closely match the N1 until stable at 40% and then hit the TO/GA. I have seen that at this point I should advance the throttles to match the performance but what happens to me is that the throttles unsy and the auto throttle is disconnected and I have a engine over N1 situation. The only remedy I have found so far is to pull back to idle, wait for both N1's to be close and re-engage the A/T. Ideas???? Anyone??

I have found that after engaging TOGA if I advance the throttles too fast it will disengage the A/T, when it does I am able to re-engage the A/T easily though.

IMHO the FSUIPC.ini file get messy sometime and setup from scratch can clean this problem.But is also depend on what method you have select.Mine is set any axis as direct to FSUIPC then disable control in FSX and remove any axis in Standard.XML.But it would be nice to know which is the right one, I have been looking for this, but didn't get any reply and find info.If Peter will adapt FSUIPC with the NGX SDK we will have a better solution.

I use fsuipc for all calibrating and have fsx control disabled. I will try to advance more slowly to see if that cures the problem. If they get too far out of sync then the A/T will not arm and pulling back to idle starts getting them closer together and allows for arming again.

This has probably got nothing to do with FSUIPC. Make sure that in the FMC you have set A/T manual override to "In hold/arm mode only". In this way you have the most realistic throttle simulation cuz it works the same in real life. In this way, after pressing TO/GA, put your own throttles to full right after it, and now A/T shouldn't disconnect anymore.

Thanks for that reminder Arjen, I also noted that the bug on the N1 gauge is gone. That is the spot where you can move your throttles to to match what the A/T is doing. I bet that is it...

So still not having any luck. Arjen was right about the settings though they all went away with sp1c. I will have to start from scratch with fusipc again. my throttles just won't stay sync'd so TO/GA will not stay connected. Try again tomorrow, too frustrated tonight.

Phill,We specifically state in the NGX intro manual not to use FSUIPC to process joystick axes - we do our own processing of them and using FSUIPC processing as well conflicts with this...

Thanks Ryan, I must have missed that one. I have all of the manuals in front of me now and will review that procedure. I will report back tomorrow.

I had read this in the manual:"During testing, we came up with some general recommendations that wefelt were important to pass along:• The PMDG 737NGX is fully compatible with FSUIPC except thatwe recommend that you do not calibrate your flight controllersthrough FSUIPC. We recommend that you use thedriver/software that comes with your hardware. (Calibratingthrough FSUIPC may not cause any problems, but in certaincircumstances with certain hardware we found that problemsexisted that could only be resolved by having the user conductthe calibration via the driver/software.)• During testing we have found that in extremely rarecircumstances, users with FSUIPC installed would need to deletetheir FSUIPC.ini file after installing the PMDG 737NGX in order toget everything playing well together. We recommend that you trythis if it seems the NGX is not behaving normally after installation."I have all my twin jets and props axis (Saitek throttles) assigned and calibrated thru FSUIPC.No problems with any aircraft ...yet.But, this is what I do not understand:"We specifically state in the NGX intro manual not to use FSUIPC to process joystick axes - we do our own processing of them and using FSUIPC processing as well conflicts with this..."How does PMDG do the the axis/calibration or "process" them?

How does PMDG do the the axis/calibration or "process" them?

let's seehttp://forum.avsim.net/topic/366827-ngx-fsuipc/

let's seehttp://forum.avsim.n...827-ngx-fsuipc/

How does that link answer my question?

I said let's see, not that you will got your answer, in any case my thread is just to get this answer.

Phill,We specifically state in the NGX intro manual not to use FSUIPC to process joystick axes - we do our own processing of them and using FSUIPC processing as well conflicts with this...

I use FSUIPC to process my joystick axes (Saitek). Never had any problem.... works great

I use FSUIPC to process my joystick axes (Saitek). Never had any problem.... works great

I am happy for you unfortunately I got AT disconnect at takeoff like Phill Dant.