FSUIPC not communicating with P3d after migration to new PC

GLC · June 12, 2021

Hello,

I have used FSUIPC v 5 with P3d 4.5 on my old computer with no problems. I bought a new computer and did not want to reprogram all my settings, so I reinstalled P3d and all my addons, and updated to the newest version FSUIPC 5.157 and followed Pete's instructions I found on the web to migrate FSUIPC to my new computer. I was able to get all the controllers to show up, and then relabeled them after copying my old FSUIPC to the new setup, and eliminating the Joy sticks not found. My controllers show up in the device manager. I am able to program some buttons on one of the Saitek Controllers with Chase Plane, indicating that Chase Plane can see them. I have disabled controllers in P3d V4.5. Yet when I load my PMDG planes which worked before, absolutely none of the buttons or axes work on my Saitek Controllers. Again they all show up in the Human Interface on Device Manager and are listed as working. When i Look at the log, everything seems normal and it records actions and seems ok. Lack of function might happen before if I added a new livery for PMDG plane, and would respond to my adding the new livery to FSUIPC profile. I tried adding a new livery and it did not work. I am mystified, and must be doing something wrong, but despite a lot of troubleshooting, I cannot figure it out.

I am including my FSUIPC.ini and a recent log.

Your help would be appreciated.

Greg

FSUIPC5.ini FSUIPC5.log

Pete Dowson · June 12, 2021

5 hours ago, GLC said:

I am mystified, and must be doing something wrong, but despite a lot of troubleshooting, I cannot figure it out.

When changing PCs the "GUID"s, which are guaranteed unique but which are generated afresh on your new PC, will be different.

This section of your new INI defines which device each of your letters actually now refer to:

[JoyNames]
AutoAssignLetters=Yes
0=Controller (Gamepad F310)
0.GUID={AEE20C10-C9DC-11EB-8002-444553540000}
1=Flight Yoke System
1.GUID={FE9129C0-CA9B-11EB-8001-444553540000}
2=Saitek Pro Flight Rudder Pedals
2.GUID={FE9150D0-CA9B-11EB-8002-444553540000}
3=Saitek Pro Flight Quadrant
3.GUID={FE9BB110-CA9B-11EB-8003-444553540000}

A=Controller (Gamepad F310)
A.GUID={AEE20C10-C9DC-11EB-8002-444553540000}
B=Saitek Pro Flight Yoke << MISSING JOYSTICK >>
B.GUID={FE9129C0-CA9B-11EB-8001-444553540000}
C=Saitek Pro Flight Rudder Pedals
C.GUID={FE9150D0-CA9B-11EB-8002-444553540000}
D=Saitek Pro Flight Quadrant
D.GUID={FE9BB110-CA9B-11EB-8003-444553540000}
E=Flight Yoke System
E.GUID={FE9129C0-CA9B-11EB-8001-444553540000}

If you can recognise which should be which you merely need to change the letters accordingly. I can see two which should be easy to change, but you first need to delete the two lines starting "B", as that one doesn't exist now.

It would be much easier if you still had a copy of the INI file from your previous PC. Then the changes would be easy t do as you could match one to the other (or I could do it for you). I can do a little -- according to your [Axes] assignments A should be your Yoke and B your pedals, so instead of E:

A=Flight Yoke System
A.GUID={FE9129C0-CA9B-11EB-8001-444553540000}

and instead of C

B=Saitek Pro Flight Rudder Pedals
B.GUID={FE9150D0-CA9B-11EB-8002-444553540000}

that leaves just:

A=Controller (Gamepad F310)
A.GUID={AEE20C10-C9DC-11EB-8002-444553540000}
D=Saitek Pro Flight Quadrant
D.GUID={FE9BB110-CA9B-11EB-8003-444553540000}

Strangely you don't seem to have any Throttle assignments for the quadrant -- only one throttle on the Yoke system. Aren't you using the quadrant?

So, that just leaves some button assignments. Those appear to be either on the yoke system (already sorted), or device C. So:

C=Controller (Gamepad F310)
C.GUID={AEE20C10-C9DC-11EB-8002-444553540000}

And that completes it, giving:

A=Flight Yoke System
A.GUID={FE9129C0-CA9B-11EB-8001-444553540000}
B=Saitek Pro Flight Rudder Pedals
B.GUID={FE9150D0-CA9B-11EB-8002-444553540000}
C=Controller (Gamepad F310)
C.GUID={AEE20C10-C9DC-11EB-8002-444553540000}
D=Saitek Pro Flight Quadrant
D.GUID={FE9BB110-CA9B-11EB-8003-444553540000}

Try replacing the contents of the [JoyNames] section with that.

Pete

GLC · June 12, 2021

Hi Pete,

You hit the nail on the head for me. When I looked at the new ini file for the new computer, I later realized that the order of the controllers had changed from the old PC, but it did not dawn on me that was significant or how to resolve it.

With your help I was able to reassign the letters and now almost everything is working well.

My old PC controller assignments, which I did not think to include were:

[JoyNames]

AutoAssignLetters=Yes

A=Saitek Pro Flight Yoke

A.GUID={6F8F70D0-72C9-11E1-8001-444553540000}

B=Saitek Pro Flight Rudder Pedals

B.GUID={9AC30D60-72CA-11E1-8001-444553540000}

C=Saitek Pro Flight Throttle Quadrant

C.GUID={CEE817B0-72CB-11E1-8001-444553540000}

D=Controller (Gamepad F310)

D.GUID={3598A1D0-95B6-11E5-8001-444553540000}

0=Saitek Pro Flight Yoke

0.GUID={6F8F70D0-72C9-11E1-8001-444553540000}

1=Saitek Pro Flight Rudder Pedals

1.GUID={9AC30D60-72CA-11E1-8001-444553540000}

2=Saitek Pro Flight Throttle Quadrant

2.GUID={CEE817B0-72CB-11E1-8001-444553540000}

3=Controller (Gamepad F310)

3.GUID={3598A1D0-95B6-11E5-8001-444553540000}

Your guesses were almost correct, but I was able to re-label as follows with your direction:

[JoyNames]

AutoAssignLetters=Yes

A=Flight Yoke System

A.GUID={FE9129C0-CA9B-11EB-8001-444553540000}

B=Saitek Pro Flight Rudder Pedals

B.GUID={FE9150D0-CA9B-11EB-8002-444553540000}

C=Saitek Pro Flight Quadrant

C.GUID={FE9BB110-CA9B-11EB-8003-444553540000}

D=Controller (Gamepad F310)

D.GUID={AEE20C10-C9DC-11EB-8002-444553540000}

0=Controller (Gamepad F310)

0.GUID={AEE20C10-C9DC-11EB-8002-444553540000}

1=Flight Yoke System

1.GUID={FE9129C0-CA9B-11EB-8001-444553540000}

2=Saitek Pro Flight Rudder Pedals

2.GUID={FE9150D0-CA9B-11EB-8002-444553540000}

3=Saitek Pro Flight Quadrant

3.GUID={FE9BB110-CA9B-11EB-8003-444553540000}

One thing that I cannot get to work now is assigning panning [POV] to my Saitek Flight Yoke Hat button. It worked before but won't work now. Nothing happens when I move the HAT switch.

I heard to reduce judderniness one can assign the POV to an axis:

Quoting from the web:

The way I do it is set my POVs on my Fighterstick and ProThrottle as Pan View in the Axis Assignments tab.

1. Rescan in Axis Assignments.

2. Push "down" on the POV, it should register with FSUIPC.

3. Select "Send to FS as normal axis" (paraphrasing here, I'm at work. Don't worry about your P3D controllers being disabled in P3D, it does not matter).

4. Select Pan View in the axis assignments drop down box.

5. Save and go back to P3D and it should smooth pan with or without the controllers being enabled in the P3D options.”

This results in the following entry in the ini file

[Axes]
PollInterval=10
RangeRepeatRate=10
0=AX,256,F,65763,0,0,0   -{ TO SIM: AXIS_AILERONS_SET }-
1=AY,256,F,65762,0,0,0   -{ TO SIM: AXIS_ELEVATOR_SET }-
2=AZ,256,F,65765,0,0,0   -{ TO SIM: AXIS_THROTTLE_SET }-
3=AV,256,F,66534,0,0,0   -{ TO SIM: AXIS_FLAPS_SET }-
4=AP,0,F,66416,0,0,0   -{ TO SIM: PAN_VIEW }-
5=BX,256,F,66387,66388,0,0   -{ TO SIM: AXIS_LEFT_BRAKE_SET, AXIS_RIGHT_BRAKE_SET }-
6=BY,256,F,66388,66387,0,0   -{ TO SIM: AXIS_RIGHT_BRAKE_SET, AXIS_LEFT_BRAKE_SET }-
7=BR,256,F,65764,0,0,0   -{ TO SIM: AXIS_RUDDER_SET }-

But again the switch movement does nothing.

I cannot attach any further files due to size limitations, but new .ini contents are at the end of this reply

RE: Quadrant with only one throttle assigned, I am using it but never got around to assigning all the throttles, which is unrealistic, but maybe some day in the future.

I do have one last question. The FSUIPC interface is very small and hard for me to see on 1440p resolution. I do not like to change screen resolutions, because that rearranges all my icons. Can the size of the interface be programmed to be bigger for those of us with poor vision?

Thanks for all of your help.

Greg

[General]
UpdatedByVersion=5157
History=DE8ZZT15O9E4VI0CUB4PN
InitDelayDevicesToo=No
PMDG737offsets=Auto
PMDG747offsets=Auto
PMDG777offsets=Auto
Annotate=Yes
UseSystemTime=No
UseMidMouseBtn=Yes
MouseWheelMove=No
MouseWheelTrim=No
MouseWheelTrimSpeed=1
JoystickTimeout=20
RestoreSimcWindows=No
FixMachSpeedBug=No
AutoScanDevices=Yes
DisconnTrimForAP=No
ZeroElevForAPAlt=No
ThrottleSyncAll=No
WhiteMessages=No
ShowPMcontrols=No
SpoilerIncrement=512
MagicBattery=No
RudderSpikeRemoval=No
ElevatorSpikeRemoval=No
AileronSpikeRemoval=No
ReversedElevatorTrim=No
ClockSync=No
ClockSyncMins=5
ClearWeatherDynamics=No
TimeForSelect=4
LoadFlightMenu=No
LoadPlanMenu=No
PauseAfterCrash=No
BrakeReleaseThreshold=75
SaveDataWithFlights=No
ZapSound=firework
ShortAircraftNameOk=Substring
UseProfiles=Yes
EnableMouseLook=No
DelayedMouseLookZoom=No
WideLuaGlobals=Yes
AxesWrongRange=No
TCASid=Flight
TCASrange=40,3
AxisCalibration=No
DirectAxesToCalibs=No
ShowMultilineWindow=Yes
SuppressSingleline=No
SuppressMultilineFS=No
AxisIntercepts=No
DontResetAxes=No
ThreadAffinityMask=x0
LuaAffinityMask=x0
InitDelay=0
GetNearestAirports=Yes
LogOptionProtect=Yes
TimeForLuaClosing=2
WeatherReadFactor=2
WeatherRewriteSeconds=1
TrafficStallTime=1
InitialStallTime=10
NormalStallTime=1
LuaRerunDelay=66
Console=No
ControlsListBuild=34698
ZapAirRange=1.50
ZapGroundRange=0.25
ZapCylinderAltDiff=0
ComReadLoopTime=20
ConsoleWindowTopMost=No
LogAxes=Yes
LogButtonsKeys=Yes
FSVersionUsed="Lockheed Martin® Prepar3D® v4",4.5.14.34698
SimConnectUsed=4.5.0.0

[Traffic Limiter]
AirportPreference=50
PlannedAirportsPreference=50
GroundPreference=50
NearerPreference=50
TargetFrameRate=0
TrafficLimit=0

[JoystickCalibration]
RudderBlendLowest=1
AllowSuppressForPFCquad=Yes
ExcludeThrottleSet=Yes
ExcludeMixtureSet=Yes
ExcludePropPitchSet=Yes
SepRevsJetsOnly=No
ApplyHeloTrim=No
UseAxisControlsForNRZ=No
FlapsSetControl=0
FlapDetents=No
ReverserControl=66292
Reverser1Control=66422
Reverser2Control=66425
Reverser3Control=66428
Reverser4Control=66431
MaxThrottleForReverser=256
AileronTrimControl=66731
RudderTrimControl=66732
CowlFlaps1Control=66162
CowlFlaps2Control=66163
CowlFlaps3Control=66164
CowlFlaps4Control=66165
SteeringTillerControl=0
MaxSteerSpeed=60
Flaps=-16384,16255/16
FlapStarts=-16384,1,16255
LeftBrake=-16384,16383/16
Rudder=-16319,128,512,16191
RightBrake=-16384,16383/16
Aileron=-16159,-512,-193,16383
Elevator=-16384,0,512,16255
Throttle=-16384,16255
FlapEnds=-16384,1,16255
SlopeRudder=4
SlopeElevator=15

[Axes]
PollInterval=10
RangeRepeatRate=10
0=AX,256,F,65763,0,0,0   -{ TO SIM: AXIS_AILERONS_SET }-
1=AY,256,F,65762,0,0,0   -{ TO SIM: AXIS_ELEVATOR_SET }-
2=AZ,256,F,65765,0,0,0   -{ TO SIM: AXIS_THROTTLE_SET }-
3=AV,256,F,66534,0,0,0   -{ TO SIM: AXIS_FLAPS_SET }-
4=AP,0,F,66416,0,0,0   -{ TO SIM: PAN_VIEW }-
5=BX,256,F,66387,66388,0,0   -{ TO SIM: AXIS_LEFT_BRAKE_SET, AXIS_RIGHT_BRAKE_SET }-
6=BY,256,F,66388,66387,0,0   -{ TO SIM: AXIS_RIGHT_BRAKE_SET, AXIS_LEFT_BRAKE_SET }-
7=BR,256,F,65764,0,0,0   -{ TO SIM: AXIS_RUDDER_SET }-

[Buttons]
PollInterval=25
ButtonRepeat=20,10
1=RA,20,C65602,0 -{THROTTLE_DECR}-
2=UA,20,C65604,0 -{THROTTLE_CUT}-

[AutoSave]
Next=1
Interval=60
Files=10
SaveOnGround=No
AutoSaveEnabled=No

[GPSout]
GPSoutEnabled=No

[GPSout2]
GPSoutEnabled=No

[WideServer]
WideFSenabled=Yes

[Sounds]
Path=D:\Program Files\Lockheed Martin\Prepar3D v4\Sound\
Device1=Primary Sound Driver
Device2=Speakers (Realtek(R) Audio)
Device3=DELL U3415W (NVIDIA High Definition Audio)
Device4=Realtek Digital Output (Realtek(R) Audio)

[Profile.PMDG 737 NGX]
1=Boeing 737-924 United Airlines (Merger) Winglets
2=Boeing 737-823NGX American Airlines (OC) Winglets
3=Boeing 737-990NGX Alaska Airlines Winglets
4=Boeing 737-824NGX United Airlines (Merger) Winglets
5=Boeing 737-824NGX Continental Airlines Winglets
6=Boeing 737-832NGX Delta Air Lines Winglets
7=Boeing 737-890NGX Alaska Airlines (Lei) Winglets
8=Boeing 737-890NGX Alaska Airlines (alaskaair.com) Winglets
9=Boeing 737-890NGX Alaska Airlines (Spirit of Seattle) Winglets
10=Boeing 737-890NGX Alaska Airlines Winglets
11=Boeing 737-836NGX British Airways Virtual Winglets
12=Boeing 737-8H4NGX Southwest Airlines (Warrior One) Winglets
13=PMDG P-8A Poseidon
14=Boeing 737-900NGX Alaska USA
15=Boeing 737-85PNGX ALASKA N560AS Winglets
16=Boeing 737-890(WL) Alaska Airlines 'New Livery' N563AS
17=Boeing 737-990/ER Alaska Airlines N248AK
18=Boeing 737-990/ER Alaska Airlines N495AS
19=PMDG 737-900NGX PMDG House Winglets
20=Boeing 737-86NNGX Norwegian Air Shuttle Winglets
21=Boeing 737-924NGX Continental Airlines Winglets

[Buttons.PMDG 737 NGX]
0=PA,0,C66416,0    -{PAN_VIEW}-
1=PA,1,K83,8    -{Key press: S}-
2=RA,2,C65607,0    -{ELEV_TRIM_DN}-
3=RA,3,C65615,0    -{ELEV_TRIM_UP}-
6=PA,6,K189,8    -{Key press: -_key}-
7=PA,7,K187,8    -{Key press: =+key}-
8=PC,0,C65570,0    -{GEAR_TOGGLE}-
10=PC,2,C65861,0    -{AUTO_THROTTLE_TO_GA}-
11=PC,4,K75,9    -{Key press: shft+K}-
12=PC,5,C65860,0    -{AUTO_THROTTLE_ARM}-
13=PC,1,C65752,0    -{PARKING_BRAKES}-
14=RA,20,C65602,0    -{THROTTLE_DECR}-
15=PA,22,C65603,0    -{FLAPS_DOWN}-
17=UA,20,C65604,0    -{THROTTLE_CUT}-
18=PA,4,K81,9    -{Key press: shft+Q}-
19=PA,5,K84,9    -{Key press: shft+T}-
20=PC,6,K84,10    -{Key press: ctl+T}-
21=PC,3,K68,11    -{Key press: ctl+shft+D}-

[Window.Message Window]
NewDocked=27, 47, 3386, 17

[Window.SimConnectWindow]
NewDocked=1290, 540, 860, 344

[Profile.F-22 Raptor]
1=F-22 Raptor - 525th Fighter Squadron

[Buttons.F-22 Raptor]
0=PC,0,K71,8 -{Key press: G}-

[Profile.PMDG 747 400]
1=PMDG 747-451 Delta Air Lines (N661US | 2015)

[Buttons.747]
0=PA,0,C66416,0    -{PAN_VIEW}-
1=PA,1,K83,8    -{Key press: S}-
2=RA,2,C65607,0    -{ELEV_TRIM_DN}-
3=RA,3,C65615,0    -{ELEV_TRIM_UP}-
6=PA,6,K189,8    -{Key press: -_key}-
7=PA,7,K187,8    -{Key press: =+key}-
8=PC,0,C65570,0    -{GEAR_TOGGLE}-
10=PC,2,C65861,0    -{AUTO_THROTTLE_TO_GA}-
11=PC,4,K75,9    -{Key press: shft+K}-
12=PC,5,C65860,0    -{AUTO_THROTTLE_ARM}-
13=PC,1,C65752,0    -{PARKING_BRAKES}-
14=RA,20,C65602,0    -{THROTTLE_DECR}-
15=PA,22,C65603,0    -{FLAPS_DOWN}-
17=UA,20,C65604,0    -{THROTTLE_CUT}-
18=PA,4,K81,9    -{Key press: shft+Q}-
19=PA,5,K84,9    -{Key press: shft+T}-
20=PC,6,K84,10    -{Key press: ctl+T}-
21=PC,3,K68,11    -{Key press: ctl+shft+D}-
22=PA,19,C65561,0    -{PAUSE_TOGGLE}-

[Profile.747]
1=747

[Profile.PMDG 737 NGXu]
1=PMDG 737 NGXu

[Buttons.PMDG 737NGXu]
0=PA,0,C66416,0    -{PAN_VIEW}-
1=PA,1,K83,8    -{Key press: S}-
2=RA,2,C65607,0    -{ELEV_TRIM_DN}-
3=RA,3,C65615,0    -{ELEV_TRIM_UP}-
6=PA,6,K189,8    -{Key press: -_key}-
7=PA,7,K187,8    -{Key press: =+key}-
8=PC,0,C65570,0    -{GEAR_TOGGLE}-
10=PC,2,C65861,0    -{AUTO_THROTTLE_TO_GA}-
11=PC,4,K75,9    -{Key press: shft+K}-
12=PC,5,C65860,0    -{AUTO_THROTTLE_ARM}-
13=PC,1,C65752,0    -{PARKING_BRAKES}-
14=RA,20,C65602,0    -{THROTTLE_DECR}-
15=PA,22,C65603,0    -{FLAPS_DOWN}-
17=UA,20,C65604,0    -{THROTTLE_CUT}-
18=PA,4,K81,9    -{Key press: shft+Q}-
19=PA,5,K84,9    -{Key press: shft+T}-
20=PC,6,K84,10    -{Key press: ctl+T}-
21=PC,3,K68,11    -{Key press: ctl+shft+D}-
22=PA,19,C65561,0    -{PAUSE_TOGGLE}-

[JoyNames]
AutoAssignLetters=Yes
A=Flight Yoke System
A.GUID={FE9129C0-CA9B-11EB-8001-444553540000}
B=Saitek Pro Flight Rudder Pedals
B.GUID={FE9150D0-CA9B-11EB-8002-444553540000}
C=Saitek Pro Flight Quadrant
C.GUID={FE9BB110-CA9B-11EB-8003-444553540000}
D=Controller (Gamepad F310)
D.GUID={AEE20C10-C9DC-11EB-8002-444553540000}

0=Controller (Gamepad F310)
0.GUID={AEE20C10-C9DC-11EB-8002-444553540000}
1=Flight Yoke System
1.GUID={FE9129C0-CA9B-11EB-8001-444553540000}
2=Saitek Pro Flight Rudder Pedals
2.GUID={FE9150D0-CA9B-11EB-8002-444553540000}
3=Saitek Pro Flight Quadrant
3.GUID={FE9BB110-CA9B-11EB-8003-444553540000}

Pete Dowson · June 13, 2021

16 hours ago, GLC said:

One thing that I cannot get to work now is assigning panning [POV] to my Saitek Flight Yoke Hat button. It worked before but won't work now. Nothing happens when I move the HAT switch.

Does it not register in FSUIPC's Axis Assignments tab? If not, check if it works in Windows own game controller. Calibrate it there first to make sure it is registered correctly in Windows.

16 hours ago, GLC said:

4=AP,0,F,66416,0,0,0 -{ TO SIM: PAN_VIEW }-

That looks okay. If you enable axis logging in FSUIPC does it log the PAN VIEW control? If so it is definitely getting sent to P3D (the log is from notifications by P3D's SimConnect).

16 hours ago, GLC said:

I cannot attach any further files due to size limitations

Just ZIP them! They are simple text files and ZIP up really small!

16 hours ago, GLC said:

The FSUIPC interface is very small and hard for me to see on 1440p resolution. I do not like to change screen resolutions, because that rearranges all my icons. Can the size of the interface be programmed to be bigger for those of us with poor vision?

Not for FSUIPC5, for which development has ended. You could put a request in to John for such an enhancement in FSUIPC6 or FSUIPC7, but I know for FSUIPC6 at least it is not a trivial job. The options screen is a standard Windows tabbed dialogue and it appears as that facility dictates. You could possibly try increasing the font scaling in Windows, making the text larger, but that might result in text partly disappearing outside its confining box. I know it used to on Windows 7 but Windows 10 may handle it better.

I have a similar problem in that I have a 7680x2160 display on a large curved screen. The size is good enough, but the curving and the blending in the centre makes dialogues hard to use with mouse positioning. What I do is have another cheap small monitor to the side and have the options (and other things) positioned on that. If it a normal 1920 x 1080 monitor. FSUIPC will remember the position.

Pete

GLC · June 14, 2021

Hi Pete,

It turns out that when I originally set up FSUIPC for P3D up years ago on my old PC, I also was also learning to use Chaseplane, and somehow set up the HAT switch on the Flight Sim yoke using its Controller interface, while doing everything else in FSUIPC. I had competely forgotten that. I think that leads to a conflict with FSUIPC. In any event the HAT switch is working in Chaseplane, so I will just leave it that way, for the sake of time. I figured that out by looking at my old PC ini in detail and not finding any entries at all relating to PAN.

Thanks for the information on limitations of creating the interface for higher resolution displays. At least I understand it. I did just discover the Windows 10 Magnifier, which is slightly clunky but definitely works for me now in a circumstance like visualizing the FSUIPC interface.

Greg

Sign In

FSUIPC not communicating with P3d after migration to new PC

Recommended Posts

GLC

Pete Dowson

GLC

Pete Dowson

GLC

Create an account or sign in to comment

Create an account

Sign in

Browse

Activity

Important Information