After some testing, something in FSUIPC isn't working well.
First of all, my software system specs:
Prepar3D V2
FSUIPC 4927a
Windows 7 X64 Pro, up to date with the latest updates
Saitek X52 Pro (joy 0), up to date with the latest drivers. No profile loaded at startup
Saitek Pro Flight Rudder Pedals (joy 1), up to date with the latest drivers. No profile loaded at startup
I have backed my INI file, creating a new and fresh one from FSUIPC. Now, I have set a very simple configuration with my axes:
[JoyNames] AutoAssignLetters=No 0=Saitek X52 Pro Flight Controller 0.GUID={2A5298C0-EBAA-11E2-8001-444553540000} 1=Saitek Pro Flight Rudder Pedals 1.GUID={2A5298C0-EBAA-11E2-8002-444553540000}
[Axes] RangeRepeatRate=10 0=0X,256,D,1,0,0,0 1=0Y,256,D,2,0,0,0 2=0Z,256,D,4,0,0,0 3=0U,256,D,6,0,0,0 4=0V,256,D,5,0,0,0 5=0S,256,D,23,0,0,0 6=1X,256,D,7,0,0,0 7=1Y,256,D,8,0,0,0 8=1R,256,D,3,0,0,0
I can speak about two possible scenarios:
1) If I connect my hardware before starting P3D, FSUIPC loads my axes correctly.
2) If I connect my hardware after starting P3D, FSUIPC loads my axes correctly only for the JoyName 0, but not for the JoyName 1. If I push the button "Reload axes" inside FSUIPC axes menu, JoyName 1 still doesn't work (FSUIPC doesn't recognize JoyName 1).
The general options of the INI file are:
[General] UpdatedByVersion=4927a History=AONXYJW2M4O777I9GICX1 InitDelayDevicesToo=No InterceptTextMenu=Yes UseSystemTime=No UseMidMouseBtn=Yes MouseWheelMove=No MouseWheelTrim=No MouseWheelTrimSpeed=1 JoystickTimeout=20 PollGFTQ6=Yes BlankDisplays=No FixControlAccel=No FixMachSpeedBug=Yes DeleteVehiclesForAES=Yes AutoScanDevices=Yes VisibilityOptions=No OneCloudLayer=No CloudTurbulence=No CloudIcing=No GenerateCirrus=No SuppressCloudTurbulence=No MaxIce=-4 MinIce=-4 UpperWindGusts=No SuppressWindTurbulence=No SuppressWindVariance=No WindTurbulence=No TurbulenceRate=1.0,5.0 TurbulenceDivisor=20,20,40,40 SuppressAllGusts=No MaxSurfaceWind=0 WindLimitLevel=200 WindDiscardLevel=400 WindAjustAltitude=No WindAjustAltitudeBy=2000 SmoothBySimTime=No WindSmoothing=No WindSmoothness=2 WindSmoothAirborneOnly=Yes PressureSmoothness=0 TemperatureSmoothness=0 DisconnTrimForAP=No ZeroElevForAPAlt=No ThrottleSyncAll=No WhiteMessages=Yes ShowPMcontrols=No SpoilerIncrement=512 MagicBattery=Yes RudderSpikeRemoval=No ElevatorSpikeRemoval=No AileronSpikeRemoval=No ReversedElevatorTrim=No ClockSync=No ClockSyncMins=5 ClearWeatherDynamics=No OwnWeatherChanges=No TimeForSelect=4 LoadFlightMenu=No LoadPlanMenu=No PauseAfterCrash=Yes BrakeReleaseThreshold=75 SaveDataWithFlights=No ZapSound=firework ShortAircraftNameOk=Yes UseProfiles=Yes EnableMouseLook=No AxesWrongRange=No TCASid=Flight TCASrange=40 AxisCalibration=No DirectAxesToCalibs=No ShowMultilineWindow=Yes SuppressSingleline=No SuppressMultilineFS=No AxisIntercepts=No DontResetAxes=No InitDelay=0 GetNearestAirports=Yes OOMcheck=Yes WeatherReadFactor=2 WeatherRewriteSeconds=1 CustomWeatherModify=No SimConnectStallTime=1 InitialStallTime=10 NormalStallTime=1 LuaRerunDelay=66 Console=No SetSimSpeedX1=76,24 ForceWeatherKey=79,24 PatchSIM1friction=Yes P3Dv2Fiddles=Yes UseASEweather=No FSVersionUsed="Lockheed Martin® Prepar3D® v2",2.0.9448.0 SimConnectUsed=2.0.0.0
I have never had this problem with FSX or P3D V1. I don't know if it is a problem of Windows 7, P3D V2, Saitek drivers, or FSUIPC.