After installing the hotfix, fsuipc lost connection with fsx. I noticed because none of my flightcontrols were working after install of hotfix. I use fsuipc for my yoke and pedals. I needed to reinstall it to get it to work again.

More likely the assigned controls are for the specific livery you were using. Did you assign the controls with 'aircraft specific' option checked? Here is an example - The default 737 livery section looks like this after I have assigned controls via FSUIPC : [Axes.PMDG 737-800NGX PMDG House Winglets]0=1X,256,D,22,0,0,01=1Z,256,D,9,0,0,02=1R,256,D,23,0,0,03=1U,256,D,10,0,0,04=1V,2565=1V,B,-16384,-13133,66080,06=1V,B,-8972,14080,66079,07=1V,B,-12613,-10142,65700,08=2X,256,D,1,0,0,09=2Y,256,D,2,0,0,010=3Z,1,D,3,0,0,0 The section for my qantas livery with the same aircraft model is this : [Axes.Boeing 737-838NGX Qantas Airways (New Livery) Winglets]0=1X,256,D,22,0,0,01=1Z,256,D,9,0,0,02=1R,256,D,23,0,0,03=1U,256,D,10,0,0,04=1V,2565=1V,B,-16384,-13133,66080,06=1V,B,-8972,14080,66079,07=1V,B,-12613,-10142,65700,08=2X,256,D,1,0,0,09=2Y,256,D,2,0,0,010=3Z,1,D,3,0,0,0 If I install a Delta paint and start FS the controls won't work as they are not assigned to that livery. Usually I would use the 'ShortAircraftNameOk=Substring' and shorten the aircraft name so that any repaint works off one controller set for that aircraft ie [Axes.PMDG 737-800NGX]0=1X,256,D,22,0,0,01=1Z,256,D,9,0,0,02=1R,256,D,23,0,0,03=1U,256,D,10,0,0,04=1V,2565=1V,B,-16384,-13133,66080,06=1V,B,-8972,14080,66079,07=1V,B,-12613,-10142,65700,08=2X,256,D,1,0,0,09=2Y,256,D,2,0,0,010=3Z,1,D,3,0,0,0 but as the livery installs have different start name I manually copy over each control section for each livery as at top of my post. EDIT Although looking at it now I could shorten the name to [Axes.Boeing 737-838NGX] and if all liveries have the same start value then I can use that one section for all liveries and have the original section for the default livery.

After installing the hotfix, fsuipc lost connection with fsx. I noticed because none of my flightcontrols were working after install of hotfix. I use fsuipc for my yoke and pedals. I needed to reinstall it to get it to work again.

Does this help? PMDG-737NGX-Introduction.pdf, page 20: FSUIPC users:

• 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 rare circumstances, users with FSUIPC installed would need to deletetheir FSUIPC.CFG file after installing the PMDG 737NGX in orderto get everything playing well together. We recommend that youtry this if it seems the NGX is not behaving normally afterinstallation.

• Late in beta testing, one of our testers found that having a parking brake axis assigned via FSUIPC would cause the sim to lock up while loading the PMDG 737NGX. We are continuing to investigate why this would be so, but the solution was simple:

Remove the parking brake axis assignment from FSUIPC.

In all cases, any “disagreement” between the PMDG 737NGXand FSUIPC was corrected by simply deleting the FSU Jackthe Swede in Spain

I have all my controls assigned via FSUIPC for every aircraft I own and I have never had a problem even with the 737ngx. Everything is fine but the only control I have assigned via FS is the parking brake and that is defined as a button. I wouldn't assign that as an axis! EDIT I have all 3 CH Products - yoke, rudders, throttle quad.

Hi Graham, can I hijack the thread slightly and ask what the advantages are of using FSUIPC instead of the CH Control Manager?

Well I cant entirely see the relevance of the quote on pmdg cautioning fsuipc users. I didnt have any problems with fsuipc. I didnt really want to install the hotfix because the plane is working perfectly. I read that everybody should install the hotfix. After starting up fsx again after installation, fsuipc was no longer registered in fsx. That's all I'm saying, and Im also asking if anybody else had this problem. And it has nothing to do with aircraft specific calibration. Im saying that fsuipc had completely dissapeared from my addon menu in fsx.

Hi Graham, can I hijack the thread slightly and ask what the advantages are of using FSUIPC instead of the CH Control Manager?

My toe brakes on my rudder pedals keep sending signals (that it shouldnt) when I use it normally with the CH calibration tool. Tweaking the settings in fsx doesnt help. Fsuipc fixes this problem. This is the only reason I disable my control devices in fsx, and purely use fsuipc.

And it has nothing to do with aircraft specific calibration. Im saying that fsuipc had completely dissapeared from my addon menu in fsx.

Well if you had stated that in the first place.......

Just reinstall and reactivate FSUIPC. It's not exactly a challenging task

Well, fellow ngx-pilots, I did say it unregistered my fsuipc. I dont know how you interpreted that, but i meant that i lost fsuipc in my fsx = not available in the addon menu. And I didnt say I found the task of reinstalling challenging. I was pointing out that it happened, and I supposed it isnt meant to do that.

I guess some form of confusion must of occurred when the installer checked the version of FSUIPC installed.

Well all that was worth it lol

More likely the assigned controls are for the specific livery you were using. Did you assign the controls with 'aircraft specific' option checked? Here is an example - The default 737 livery section looks like this after I have assigned controls via FSUIPC : [Axes.PMDG 737-800NGX PMDG House Winglets]0=1X,256,D,22,0,0,01=1Z,256,D,9,0,0,02=1R,256,D,23,0,0,03=1U,256,D,10,0,0,04=1V,2565=1V,B,-16384,-13133,66080,06=1V,B,-8972,14080,66079,07=1V,B,-12613,-10142,65700,08=2X,256,D,1,0,0,09=2Y,256,D,2,0,0,010=3Z,1,D,3,0,0,0 The section for my qantas livery with the same aircraft model is this : [Axes.Boeing 737-838NGX Qantas Airways (New Livery) Winglets]0=1X,256,D,22,0,0,01=1Z,256,D,9,0,0,02=1R,256,D,23,0,0,03=1U,256,D,10,0,0,04=1V,2565=1V,B,-16384,-13133,66080,06=1V,B,-8972,14080,66079,07=1V,B,-12613,-10142,65700,08=2X,256,D,1,0,0,09=2Y,256,D,2,0,0,010=3Z,1,D,3,0,0,0 If I install a Delta paint and start FS the controls won't work as they are not assigned to that livery. Usually I would use the 'ShortAircraftNameOk=Substring' and shorten the aircraft name so that any repaint works off one controller set for that aircraft ie [Axes.PMDG 737-800NGX]0=1X,256,D,22,0,0,01=1Z,256,D,9,0,0,02=1R,256,D,23,0,0,03=1U,256,D,10,0,0,04=1V,2565=1V,B,-16384,-13133,66080,06=1V,B,-8972,14080,66079,07=1V,B,-12613,-10142,65700,08=2X,256,D,1,0,0,09=2Y,256,D,2,0,0,010=3Z,1,D,3,0,0,0 but as the livery installs have different start name I manually copy over each control section for each livery as at top of my post. EDIT Although looking at it now I could shorten the name to [Axes.Boeing 737-838NGX] and if all liveries have the same start value then I can use that one section for all liveries and have the original section for the default livery.

Just to add an option for you, you know that you can use "Profiles" with FSUIPC. Just go into the FSUIPC.ini file and change Profiles=No to Profiles=Yes.With profiles, when you load a new livery of the NGX (or any other aircraft) and click on the "Buttons and Keys" tab, you will get your list of profiles that you have made. Just select the one you call PMDG 737NGX and all your controllers will work with that livery. Bob