For years I've been using the registered version of FSUIPC to set up and calibrate different controller profiles for different kinds of aircraft.  I don't have a strong reason to switch - but I'm mildly interested in trying to do the same thing by assigning axes and buttons directly in P3D and then using the Import/Export Controls function to swap profiles.  Reasons: I like simplifying whenever I can; some highly automated controls (like the throttles in the Airbus X Extended) can be difficult to set up in FSUIPC though it can be done; some custom configurators (like the ones for the A2A warbirds) don't read axes that are set up in FSUIPC.  But on the other hand, I'd heard that controller setup in P3D could be temperamental - with assignments and profiles being lost for no apparent reason.  Has this been resolved?  How reliable is the native controller calibration and profile creation?  Should I experiment or just dance with the FSUIPC that brung me?  Your reactions welcome.  Thanks in advance!

 

I thought the same thing and after many Frustrating hours I stuck with FSUIPC, Once you get through the Learning curve there is no

reason to use anything else.Unless your a .XML wiz  the Controller assignments in all the Sims not just P3D  are very temperamental

but i'm sure others will disagree.   

Thanks, MBacklawski - extremely helpful.  I suspected that might be the case.  It's not as though anything is wrong with FSUIPC - actually there's a huge amount right with it, including Pete Dowson's support (that's how I got my Airbus throttle moving in the right direction).  Chances are I'll stick with it - better to deal with its minor inconveniences than big ones elsewhere.  But if others feel differently, I'm open.

Thanks, MBacklawski - extremely helpful.  I suspected that might be the case.  It's not as though anything is wrong with FSUIPC - actually there's a huge amount right with it, including Pete Dowson's support (that's how I got my Airbus throttle moving in the right direction).  Chances are I'll stick with it - better to deal with its minor inconveniences than big ones elsewhere.  But if others feel differently, I'm open.

 

I've found assigning in P3D pretty flaky and export/import unreliable.

I don't see too many complaints here though.

Perhaps we are all using FSUICP.

 

gb.

I also find the export/import too broken to be usable. It is my impression that when importing controller settings, your current settings are not replaced by the import, but somehow merged together, so I always end up with multiple axis assignments etc.

At the moment I don't need switching between controllers (always flying the same aircraft), but when I start flying something else again, I will go back to using my own .bat files for switching controllers like I did with FSX.

I hear you. Classic case of "if it ain't broke..." Will happily stick with FSUIPC... and yes, I agree that we don't hear much about the native controller setup options because most of us are likely FSUIPC users or are using other advanced solutions like .bat files. Thanks, guys, for talking me off the ledge.