Everything has been deleted

[urgeboc]

So i fired up the newest version of P3D and got into the 737 just to discover that all the my bindings had been deleted. Found out it had happen to all the profiles.

But it looks like all the settings are still there when looking at the config file. To use my KingAir profile as a example:

But when using the assigned throttle inside fsuipc itself nothing comes up.

What could have caused this?

 

Quote

[Profile.KingAir]
1=F1_Kingair_B200

[JoystickCalibration.KingAir]
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
Spoilers=-16380,16380
Aileron=-16384,0,0,16383
Elevator=-16384,0,512,16383
Rudder=-16384,0,0,16383
Throttle=-16384,16128
LeftBrake=-16384,16383/16
RightBrake=-16384,16380/16
SlopeLeftBrake=3
SlopeRightBrake=3

[Axes.KingAir]
RangeRepeatRate=10
0=0X,256,D,7,8,0,0
1=0Y,256,D,8,7,0,0
2=0U,256,D,5,0,0,0
3=0V,256,D,6,0,0,0
4=1X,256,D,1,0,0,0
5=1Y,256,D,2,0,0,0
6=1Z,256,D,4,0,0,0
7=1U,256,D,5,0,0,0
8=1V,256,D,6,0,0,0
9=1P,0,F,66416,0,0,0

[Buttons.KingAir]
0=P0,17,C66080,0
1=P0,16,C66079,0
2=P1,17,C66080,0
3=P1,16,C66079,0

 

Edited October 24, 2016 by urgeboc

[Pete Dowson]

24 minutes ago, urgeboc said:

So i fired up the newest version of P3D and got into the 737 just to discover that all the my bindings had been deleted. Found out it had happen to all the profiles.

But it looks like all the settings are still there when looking at the config file. To use my KingAir profile as a example:

But when using the assigned throttle inside fsuipc itself nothing comes up.

What could have caused this?

You only showed part of the INI file, just for the KingAir, which seems unlikely to be a 737! You'll need to show the complete INI file, and the FSUIPC4.LOG, please. The LOG would show me whether FSUIPC loaded okay and was the correct version, and also what the Aircraft name was, and the rest of the INI would show the Profile allocations.

Be sure you updated to the latest version (4.957c at least) of FSUIPC, as earlier ones will not work with P3D 3.4.

The usual reasons folks find assignments not working are:

* The profile where the assignments are made does not include the aircraft you loaded,
* The control devices have been removed and reconnected, causing the Joystick ID numbers to change.

Pete

 

[urgeboc]

2 hours ago, Pete Dowson said:

You only showed part of the INI file, just for the KingAir, which seems unlikely to be a 737! You'll need to show the complete INI file, and the FSUIPC4.LOG, please. The LOG would show me whether FSUIPC loaded okay and was the correct version, and also what the Aircraft name was, and the rest of the INI would show the Profile allocations.

Be sure you updated to the latest version (4.957c at least) of FSUIPC, as earlier ones will not work with P3D 3.4.

The usual reasons folks find assignments not working are:

* The profile where the assignments are made does not include the aircraft you loaded,
* The control devices have been removed and reconnected, causing the Joystick ID numbers to change.

Pete

 

Will post it.

I dont remember which version i've been using, but FSUIPC has been working all the time, even when i updated to newest version of P3D.

Only changes i have made lately is that i have plugged in a gamepad, but P3D and FSUIPC has been working with it (i unplugged it before starting P3D). I also disconnected my pedals when i have been using the gamepad, but i havent used my pedals in FSUIPC. After every flight i disconnect my yoke+throttler so that cant be the reason either.

I have assigned new controllers to the PMDG today so it should be ok for now (i also updated FSUIPC today).

Quote

 

[General]
UpdatedByVersion=4957b
History=U94HMM9L6HSVV31A30UFJ
InitDelayDevicesToo=No
NewInterceptTextMenu=No
UseSystemTime=No
UseMidMouseBtn=Yes
MouseWheelMove=No
MouseWheelTrim=No
MouseWheelTrimSpeed=1
JoystickTimeout=20
PollGFTQ6=Yes
BlankDisplays=No
FixControlAccel=No
FixMachSpeedBug=No
DeleteVehiclesForAES=Yes
AutoScanDevices=Yes
AssignJoystickIDs=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=No
ShowPMcontrols=No
SpoilerIncrement=512
MagicBattery=No
RudderSpikeRemoval=No
ElevatorSpikeRemoval=No
AileronSpikeRemoval=No
ReversedElevatorTrim=No
ClockSync=No
ClockSyncMins=5
ClearWeatherDynamics=No
OwnWeatherChanges=No
TimeForSelect=4
LoadFlightMenu=No
LoadPlanMenu=No
PauseAfterCrash=No
BrakeReleaseThreshold=75
SaveDataWithFlights=No
ZapSound=firework
ShortAircraftNameOk=Substring
UseProfiles=Yes
EnableMouseLook=No
DelayedMouseLookZoom=No
AxesWrongRange=No
TCASid=Flight
TCASrange=40
AxisCalibration=No
DirectAxesToCalibs=No
ShowMultilineWindow=Yes
SuppressSingleline=No
SuppressMultilineFS=No
AxisIntercepts=No
DontResetAxes=No
InitDelay=0
GetNearestAirports=No
OOMcheck=Yes
OOMcheckInterval=10
WeatherReadFactor=2
WeatherRewriteSeconds=1
CustomWeatherModify=No
SimConnectStallTime=1
InitialStallTime=10
NormalStallTime=1
LuaRerunDelay=66
Console=No
Annotate=Yes
NewDeleteVehiclesForAES=No
LogOptionProtect=Yes
TimeForLuaClosing=1
FSVersionUsed="Lockheed Martin® Prepar3D® v3",3.4.9.18400
SimConnectUsed=3.4.0.0

[JoyNames]
AutoAssignLetters=No
0=Pro Flight Cessna Rudder Pedals
0.GUID={CBD93CA0-D99E-11E5-8002-444553540000}
2=Saitek Pro Flight Yoke
2.GUID={93076130-D99F-11E5-8003-444553540000}

[Axes]
PollInterval=10
RangeRepeatRate=10

[Buttons]
PollInterval=25
ButtonRepeat=20,10
1=P1,15,C65758,0     -{FLAPS_INCR}-
2=P1,14,C65759,0     -{FLAPS_DECR}-
3=P1,19,C65752,0     -{PARKING_BRAKES}-
4=P1,16,C66079,0     -{GEAR_UP}-
5=P1,17,C66080,0     -{GEAR_DOWN}-
7=R1,2,C65607,0     -{ELEV_TRIM_DN}-
8=R1,3,C65615,0     -{ELEV_TRIM_UP}-

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

[GPSout]
GPSoutEnabled=No
Port=COM1
Speed=4800
Interval=2000
PosTo6Decimal=No
SimModeIndicator=No
Sentences=

[GPSout2]
GPSoutEnabled=No
Port=<none set>
Speed=4800
Interval=2000
PosTo6Decimal=No
SimModeIndicator=No
Sentences=

[WideServer]
WideFSenabled=Yes

[Sounds]
Path=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Sound\
Device1=Primær lyddriver
Device2=Hodetelefoner (Xonar U7)
Device3=SPDIF Out (Xonar U7)

[Profile.PMDG]
1=Boeing 737-683NGX SAS Scandinavian Airlines
2=Boeing 737-773NGX SAS Scandinavian Airlines
3=Boeing 737-883NGX SAS Scandinavian Airlines (Saga Viking)
4=Boeing 737-6CTNGX WestJet
5=Boeing 737-86NNGX Norwegian Air Shuttle Winglets
6=PMDG P-8A Poseidon
7=PMDG 777-FS2 FedEx Express
8=PMDG 777-21HLR Emirates
9=PMDG 737-700NGX PMDG House
10=Boeing 737-9K2NGX KLM Royal Dutch Airlines Winglets
11=Boeing 737-883NGX SAS Scandinavian Airlines (Freja Viking) Winglets
12=Airbus A320 Wizz Air UR-WUC
13=Learjet 35A N925DM GTN
14=F-35A Lightning II

[Buttons.PMDG]
0=P0,17,C66080,0     -{GEAR_DOWN}-
1=P0,16,C66079,0     -{GEAR_UP}-
2=P1,16,C66079,0     -{GEAR_UP}-
3=P1,17,C66080,0     -{GEAR_DOWN}-
4=P2,19,C65752,0     -{PARKING_BRAKES}-
5=P2,17,C66080,0     -{GEAR_DOWN}-
6=P2,16,C66079,0     -{GEAR_UP}-
7=P2,15,C65758,0     -{FLAPS_INCR}-
8=P2,14,C65759,0     -{FLAPS_DECR}-
10=P2,2,C65607,0     -{ELEV_TRIM_DN}-
11=P2,3,C65607,0     -{ELEV_TRIM_DN}-

[JoystickCalibration]
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
Spoilers=-16380,16380
Aileron=-16384,0,0,16383
Elevator=-16384,0,0,16383
PropPitch=-16384,16128
Mixture=-16384,16383
Rudder=-16384,0,0,16383
LeftBrake=-16383,16384/16
RightBrake=-16383,16384/16
SlopeRightBrake=-4
Throttle=-16384,16383/8
SlopeLeftBrake=-4

[Axes.PMDG]
RangeRepeatRate=10
0=0X,256,D,7,8,0,0    -{ DIRECT: LeftBrake, RightBrake }-
1=0Y,256,D,8,7,0,0    -{ DIRECT: RightBrake, LeftBrake }-
2=0V,256,D,22,0,0,0    -{ DIRECT: Spoilers }-
3=1X,256,D,1,0,0,0    -{ DIRECT: Aileron }-
4=1Y,256,D,2,0,0,0    -{ DIRECT: Elevator }-
5=1Z,256,D,4,0,0,0    -{ DIRECT: Throttle }-
6=1V,256,D,22,0,0,0    -{ DIRECT: Spoilers }-
7=1P,0,F,66416,0,0,0    -{ TO SIM: PAN_VIEW }-
8=2X,256,D,1,0,0,0    -{ DIRECT: Aileron }-
9=2Y,256,D,2,0,0,0    -{ DIRECT: Elevator }-
10=2Z,256,D,4,0,0,0    -{ DIRECT: Throttle }-
11=2V,256,D,22,0,0,0    -{ DIRECT: Spoilers }-

[JoystickCalibration.PMDG]
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
Spoilers=-16384,16383
Aileron=-16384,0,0,16383
Elevator=-16384,0,0,16383
LeftBrake=-16384,16383/16
RightBrake=-16384,16383/16
SteeringTiller=-16384,2304,2304,16383
SlopeLeftBrake=-5
SlopeRightBrake=-5
Throttle=-16384,16383

[Profile.KingAir]
1=F1_Kingair_B200

[JoystickCalibration.KingAir]
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
Spoilers=-16380,16380
Aileron=-16384,0,0,16383
Elevator=-16384,0,512,16383
Rudder=-16384,0,0,16383
Throttle=-16384,16128
LeftBrake=-16384,16383/16
RightBrake=-16384,16380/16
SlopeLeftBrake=3
SlopeRightBrake=3

[Axes.KingAir]
RangeRepeatRate=10
0=0X,256,D,7,8,0,0
1=0Y,256,D,8,7,0,0
2=0U,256,D,5,0,0,0
3=0V,256,D,6,0,0,0
4=1X,256,D,1,0,0,0
5=1Y,256,D,2,0,0,0
6=1Z,256,D,4,0,0,0
7=1U,256,D,5,0,0,0
8=1V,256,D,6,0,0,0
9=1P,0,F,66416,0,0,0

[Buttons.KingAir]
0=P0,17,C66080,0
1=P0,16,C66079,0
2=P1,17,C66080,0
3=P1,16,C66079,0

[Profile.Carenado]
1=Carenado F406 Caravan II White

[Axes.Carenado]
0=0U,256,D,5,0,0,0
1=0V,256,D,6,0,0,0
RangeRepeatRate=10

[Profile.Duke v2]
1=RealAir Beech Duke Turbine V2 G-BXTR
2=RealAir Beech Duke Turbine V2 N626N
3=RealAir Beech Duke Turbine V2 DNSYR

[Axes.Duke v2]
RangeRepeatRate=10
0=0U,256,D,5,0,0,0
1=0V,256,D,6,0,0,0
2=1X,256,D,1,0,0,0
3=1Y,256,D,2,0,0,0
4=1U,256,D,5,0,0,0
5=1V,256,D,13,14,0,0

[Profile.Q400]
1=MJC8Q400_WIF
2=MJC8Q400_BTI

[Axes.Q400]
RangeRepeatRate=10
0=0X,256,D,7,8,0,0
1=0Y,256,D,8,7,0,0
2=0U,256,D,17,0,0,0
3=0V,256,D,18,0,0,0
4=1X,256,D,1,0,0,0
5=1Y,256,D,2,0,0,0
6=1Z,256,D,4,0,0,0
7=1U,256,D,17,0,0,0
8=1V,256,D,18,0,0,0

[JoystickCalibration.Q400]
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
Aileron=-16384,0,0,16383
Elevator=-16384,0,0,16383
Mixture=-16384,16383
Throttle=-16384,9344
PropPitch1=-16384,-16384,-16384,16383/32
PropPitch2=-16384,0,512,16383/32
LeftBrake=-16383,16384/16
SlopeLeftBrake=-6
RightBrake=-16383,16384/16
SlopeRightBrake=-6

[LuaFiles]
1=Q400VSpeeds

[Keys.Q400]
1=86,8,L1:R,0

[Window.LUA display]
Docked=7347, 2457, 3575, 1941

[Buttons.Q400]
2=P0,17,C66080,0
3=P0,16,C66079,0

[Buttons.Duke v2]
0=P0,14,C66079,0
1=P0,17,C65570,0
2=P1,17,C66080,0
3=P1,16,C66079,0

[Profile.A2A]
1=Piper Pa-24-250 Comanche N6229P
2=Maule M7 260C Ski
3=Lockheed L049_4
4=P-38Jg
5=Mooney Acclaim With G1000 2
6=P-38F "Beautiful Lass"
7=Piper Pa-24-250 Comanche N8665R
8=Piper Pa-24-250 Comanche N822JH
9=Milviz Baron 55_1
10=Piper Pa-24-250 Comanche N59250
11=F-22 Raptor - 525th Fighter Squadron
12=Lockheed C69B
13=C182_VH-DLL
14=C182_N516DM

[Buttons.A2A]
0=P0,17,C66080,0
1=P0,16,C66079,0
2=P1,17,C66080,0
3=P1,16,C66079,0

[Axes.A2A]
RangeRepeatRate=10
0=0X,256,D,7,8,0,0
1=0Y,256,D,8,7,0,0
2=0U,256,D,6,0,0,0
3=0V,256,D,5,0,0,0
4=1X,256,D,1,0,0,0
5=1Y,256,D,2,0,0,0
6=1Z,256,D,4,0,0,0
7=1U,256,D,5,0,0,0
8=1V,256,D,6,0,0,0

[Profile.T-38]
1=T38A_ADV NATO
2=T38A_ADV NASA
3=Virtavia Blackhawk 160thSOAR
4=T-6 SP2 #0

[Axes.T-38]
RangeRepeatRate=10
0=1X,256,D,1,0,0,0
1=1Y,256,D,2,0,0,0

[Buttons.T-38]
0=P1,2,C66079,0
1=P1,3,C66080,0
2=P1,13,C65752,0

[Profile.CJ2]
1=Carenado 5252A CJ2 OY-CTB

[Axes.CJ2]
RangeRepeatRate=10
0=0X,256,D,7,8,0,0
1=0Y,256,D,8,7,0,0
2=1X,256,D,1,0,0,0
3=1Y,256,D,2,0,0,0
4=1Z,256,D,4,0,0,0

[Buttons.CJ2]
0=P1,16,C66079,0
1=P1,17,C66080,0
2=P1,18,C66065,0
3=P1,19,C66064,0

[Profile.Airbus]
1=Airbus A320 IAE Scandinavian OY-KAS

[Buttons.Airbus]
0=P0,17,C66080,0
1=P0,16,C66079,0
2=P1,16,C66079,0
3=P1,17,C66080,0

[Axes.Airbus]
0=0X,256,D,7,8,0,0
1=0Y,256,D,8,7,0,0
2=0V,256,D,22,0,0,0
3=1X,256,D,1,0,0,0
4=1Y,256,D,2,0,0,0
5=1Z,256,D,4,0,0,0
6=1V,256,D,22,0,0,0
RangeRepeatRate=10

[JoystickCalibration.Airbus]
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
Aileron=-16384,0,0,16383
Elevator=-16384,0,0,16383
Throttle=-16384,16383
LeftBrake=-16384,16383/16
SlopeLeftBrake=-5
RightBrake=-16384,16383/16
SlopeRightBrake=-5
Spoilers=-16384,16383
SteeringTiller=-16384,1677,1677,16383

[Profile.B55]
1=Milviz Baron E55
2=Virtavia Blackhawk USA
3=Carenado 500S Aero Commander C-GAFA
4=Carenado 500S Aero Commander N120ET
5=Carenado 500S Aero Commander VH-MIO
6=Piper Pa-24-250 Comanche N7791P
7=Beech Baron 58

[Buttons.B55]
0=P0,17,C66080,0
1=P0,16,C66079,0
2=P1,17,C66080,0
3=P1,16,C66079,0

[Axes.B55]
RangeRepeatRate=10
0=0X,256,D,7,8,0,0
1=0Y,256,D,8,7,0,0
2=0U,256,D,6,0,0,0
3=0V,256,D,5,0,0,0
4=1X,256,D,1,0,0,0
5=1Y,256,D,2,0,0,0
6=1Z,256,D,4,0,0,0
7=1U,256,D,5,0,0,0
8=1V,256,D,6,0,0,0
9=1P,0,F,66416,0,0,0

[Monitor]

 

 

Quote

********* FSUIPC4, Version 4.957b (26th September 2016) by Pete Dowson *********
Windows version reported as 6.1.?.7601
Prepar3D.exe version = 3.4.9.18400
Reading options from "C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Modules\FSUIPC4.ini"
Running inside Prepar3D v3 on Windows 7
Module base=53A80000
User Name="J**** G****"
User Addr="j***************@hotmail.com"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
       16 System time = 24/10/2016 14:36:00
       16 FLT path = "C:\Users\Min\Documents\Prepar3D v3 Files\"
       16 ------ Module Version Check ------
       16        acontain.dll: 3.4.9.18400
       16             api.dll: 3.4.9.18400
       16        controls.dll: 3.4.9.18400
       16      fs-traffic.dll: 3.4.9.18400
       16             G3D.dll: 3.4.9.18400
       16        language.dll: 3.4.9.18400
       16            sim1.dll: 3.4.9.18400
       16        visualfx.dll: 3.4.9.18400
       16         weather.dll: 3.4.9.18400
       16          window.dll: 3.4.9.18400
       16 ----------------------------------
       16 Trying C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D3.dll
       16 Found it: trying to connect
       31 FS path = "C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\"
      156 ---------------------- Joystick Device Scan -----------------------
      156 Product= Pro Flight Cessna Rudder Pedals
      156    Manufacturer= Mad Catz
      156    Vendor=06A3, Product=0765 (Version 1.9)
      156    Serial Number= Example#
      156 Product= Saitek Pro Flight Yoke
      156    Manufacturer= Saitek
      156    Vendor=06A3, Product=0BAC (Version 3.4)
      156    Serial Number=
      156 -------------------------------------------------------------------
      172 LogOptions=00000000 00000001
      172 -------------------------------------------------------------------
      172 ------ Setting the hooks and direct calls into the simulator ------
      172 --- CONTROLS timer memory location obtained ok
      172 --- SIM1 Frictions access gained
      172 --- FS Controls Table located ok
      172 --- Installed Mouse Macro hooks ok.
      172 --- Wind smoothing fix is installed
      172 --- SimConnect intercept for texts and menus option is off
      172 --- All links okay (except older global weather setting method)
      172 -------------------------------------------------------------------
      172 SimConnect_Open succeeded: waiting to check version okay
      172 Trying to use SimConnect Prepar3D
      172 Opened separate AI Traffic client okay
     3042 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.4.9.18400 (SimConnect: 3.4.0.0)
     3042 Initialising SimConnect data requests now
     3042 FSUIPC Menu entry added
     3058 C:\Users\Min\AppData\Local\Lockheed Martin\Prepar3D v3\Prepar3D_Default.fxml
     3058 C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air
   115332 C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\SimObjects\Airplanes\PMDG 737-600NGX\B737-600.air
   162522 System time = 24/10/2016 14:38:42, Simulator time = 14:37:42 (13:37Z)
   162538 Aircraft="Boeing 737-683NGX SAS Scandinavian Airlines"
   168700 Starting everything now ...
   168778 ASN active function link set
   168778 Ready for ASN WX radar
   169714 Weather Mode now = Theme
   169870 Advanced Weather Interface Enabled
  3393927 Sim stopped: average frame rate for last 3232 secs = 36.5 fps
  3393927              Max AI traffic was 42 aircraft
  4409774 Sim stopped: average frame rate for last 1015 secs = 43.1 fps
  4409774              Max AI traffic was 8 aircraft
  4434968 Sim stopped: average frame rate for last 22 secs = 63.1 fps
  4434968              Max AI traffic was 0 aircraft
  4440038 C:\Users\Min\AppData\Roaming\Lockheed Martin\Prepar3D v3\Temp\RECTMPFLT.fxml
  4710669 C:\Users\Min\AppData\Roaming\Lockheed Martin\Prepar3D v3\Temp\RECBACKUPFLT.fxml
  4804457 Sim stopped: average frame rate for last 72 secs = 76.5 fps
  4804457              Max AI traffic was 2 aircraft
  4832225 === Calling SimConnect_Close ...
  4832412 === SimConnect_Close done!
  4833426 System time = 24/10/2016 15:56:33, Simulator time = 15:56:42 (14:56Z)
  4833426 *** FSUIPC log file being closed
Minimum frame rate was 20.0 fps, Maximum was 95.9 fps
Minimum available memory recorded was 768Mb
Average frame rate for running time of 4341 secs = 38.9 fps
Maximum AI traffic for session was 42 aircraft
Memory managed: 2074 Allocs, 2074 Freed
********* FSUIPC Log file closed ***********

 

 

 

 

Edited October 24, 2016 by urgeboc

[Pete Dowson]

54 minutes ago, urgeboc said:

Only changes i have made lately is that i have plugged in a gamepad, but P3D and FSUIPC has been working with it (i unplugged it before starting P3D). I also disconnected my pedals when i have been using the gamepad, but i havent used my pedals in FSUIPC. After every flight i disconnect my yoke+throttler so that cant be the reason either.

On the contrary, that is probably precisely the reason. Each time to reconnect them it is quite possible that they will be assigned a different ID. FSUIPC relies on the IDs to tie the devices to your assignments.

Windows assigns IDs on some basis depending on which sockets they connect to and what order it sees them.

Looking at your settings:

57 minutes ago, urgeboc said:

[JoyNames]
AutoAssignLetters=No
0=Pro Flight Cessna Rudder Pedals
0.GUID={CBD93CA0-D99E-11E5-8002-444553540000}
2=Saitek Pro Flight Yoke
2.GUID={93076130-D99F-11E5-8003-444553540000}

You have a Yoke as ID 2 and pedals as ID 0.

In your assignments you have many to device 0, which isn't (now) attached. Just for now looking at the profile you used last, PMDG:

59 minutes ago, urgeboc said:

[Buttons.PMDG]
0=P0,17,C66080,0     -{GEAR_DOWN}-
1=P0,16,C66079,0     -{GEAR_UP}-
2=P1,16,C66079,0     -{GEAR_UP}-
3=P1,17,C66080,0     -{GEAR_DOWN}-
4=P2,19,C65752,0     -{PARKING_BRAKES}-
5=P2,17,C66080,0     -{GEAR_DOWN}-
6=P2,16,C66079,0     -{GEAR_UP}-
7=P2,15,C65758,0     -{FLAPS_INCR}-
8=P2,14,C65759,0     -{FLAPS_DECR}-
10=P2,2,C65607,0     -{ELEV_TRIM_DN}-
11=P2,3,C65607,0     -{ELEV_TRIM_DN}-

You have here assignments to devices 0, 1, and 2. Judging by the axis assignments, here:

1 hour ago, urgeboc said:

[Axes.PMDG]
RangeRepeatRate=10
0=0X,256,D,7,8,0,0    -{ DIRECT: LeftBrake, RightBrake }-
1=0Y,256,D,8,7,0,0    -{ DIRECT: RightBrake, LeftBrake }-
2=0V,256,D,22,0,0,0    -{ DIRECT: Spoilers }-
3=1X,256,D,1,0,0,0    -{ DIRECT: Aileron }-
4=1Y,256,D,2,0,0,0    -{ DIRECT: Elevator }-
5=1Z,256,D,4,0,0,0    -{ DIRECT: Throttle }-
6=1V,256,D,22,0,0,0    -{ DIRECT: Spoilers }-
7=1P,0,F,66416,0,0,0    -{ TO SIM: PAN_VIEW }-
8=2X,256,D,1,0,0,0    -{ DIRECT: Aileron }-
9=2Y,256,D,2,0,0,0    -{ DIRECT: Elevator }-
10=2Z,256,D,4,0,0,0    -{ DIRECT: Throttle }-
11=2V,256,D,22,0,0,0    -{ DIRECT: Spoilers }-

You have two assignments to the main aircraft yoke controls -- devices 1 and 2, and 3 assignments to spoilers seemingly on the same device (pedals) as the toe brakes! But no rudder assignment?

If you want to be able to unplug and plug devices in to your heart's conent, you need to tell FSUIPC to use letters instead of numerical IDs. It will then match them up by name -- the only time it would then have trouble is if you had several identically named devices.

There's a chapter in the User Guide about this. Look up Joy Letters.

Oh, and version 4.957b is out of date and unsupported now. Please install the current version, 4.957c.

Pete

 

[urgeboc]

To be honest, i understand probably 50% of what you just said. Not your fault, but mine :)

But i've done this for a year now, always unplugging my yoke + throttle after each flight and never had a problem. I forgot to say that i have assigned my toebrakes in FSUIPC, but the rudder i have assigned in P3D controlsmenu.

So basically what you are telling me is; update FSUIPC, re-assign everything (or is it possible to get the old assignments back?), then look up Joy Letters so i can continue unplugging my yoke after each flight?

[Pete Dowson]

3 hours ago, urgeboc said:

I forgot to say that i have assigned my toebrakes in FSUIPC, but the rudder i have assigned in P3D controlsmenu.

Ah, so you haven't disabled controllers in P3D? It's not a good idea to mix assignments in both FS/P3D and FSUIPC. Both FS and P3D have a habit of making automatic assignments sometimes. Then you'll get two inputs from the same controls and buttons, often conflicting. You should always assign only in one or the other, and if in FSUIPC disable controllers completely in P3D.

If this hasn't affected you before you've been lucky.

The really odd thing, though, is that you have the spoillers assigned to the same device as the toe brakes (as well as on two other devices). Does your pedal set have a spare lever you've assigned for this? Seems rather odd.

3 hours ago, urgeboc said:

So basically what you are telling me is; update FSUIPC, re-assign everything (or is it possible to get the old assignments back?), then look up Joy Letters so i can continue unplugging my yoke after each flight?

You shouldn't need to reassign everything, although seeing that you have so many duplicate assignments, probably unwanted, it might not be a bad idea. However, if you tell FSUIPC to assign letters then it will do, automatically replacing the IDs in at least the assignments to devices 0 and 2, the two you have listed at present. Then, if these are wrong, you only need to change the letters over manually in the [JoyNames] section. 

As it is at present, since there's no known device 1, those assignments won't get lettered. If you only ever have those two devices then you might as well delete those assignment lines.

But implement the lettering first. It's easy to do -- just one line to change:

4 hours ago, Pete Dowson said:

AutoAssignLetters=No

Set that to Yes.

Pete

 

[urgeboc]

Sorry, i dont know how to quote single lines like you do.

But no, i havent disabled it. I use a mix of FSUIPC and the control section in P3D as i found some things hard to assign to FSUIPC. I thought the rudder was assigned to P3D controls only, not FSUIPC aswell. Will have a look at it.

Spoilers and toe brakes assigned to the same device? That cant be right? Im using the Saitek Pro Flight Yoke (This one) and the speed brake for the PMDG is assigned to the red lever. But for propeller planes its assigned for mixture if im not mistaken (probably doesnt matter?).

I think im just gonna go ahead and delete everything FSUIPC related and start over. So basically what you're saying about the JoyNumbers is that it will be ok to unplug both my rudders and yoke and plug it back in the same port when im gonna fly again? And if something goes wrong i just "assign" the correct letter to the usb?

Btw thank you for helping me :)

Edited October 25, 2016 by urgeboc

[Pete Dowson]

7 hours ago, urgeboc said:

I thought the rudder was assigned to P3D controls only, not FSUIPC aswell.

The rudder control isn't assigned in FSUIPC, but the toe brakes are (normally part of the rudder device) AND another Spoiler control to the SAME device. All the rudder devices I know have a rudder input and two toe brake inputs, but not a fourth axis, so it does appear in your assignments as if you have the rudder acting as a spoiler control as well!

7 hours ago, urgeboc said:

Spoilers and toe brakes assigned to the same device? That cant be right

Exactly what I said, but there it is, in black and white:

0=0X,256,D,7,8,0,0    -{ DIRECT: LeftBrake, RightBrake }-
1=0Y,256,D,8,7,0,0    -{ DIRECT: RightBrake, LeftBrake }-
2=0V,256,D,22,0,0,0    -{ DIRECT: Spoilers }-

The 0 directly after the = means device 0, which as you saw in the [Joynames] section, is the rudder.

Also I don't understand why you've assigned both left and right toe brakes to each of the brake pedals!

Really it is all rather a mess.

7 hours ago, urgeboc said:

i found some things hard to assign to FSUIPC.

Can you please elaborate on this. FSUIPC includes ALL of the controls offered by P3D plus many more. P3D only offers a subset. So which controls are difficult for you? And why the rudder, when it is one of the main controls alongside the aileron and yoke?

7 hours ago, urgeboc said:

I think im just gonna go ahead and delete everything FSUIPC related and start over.

Probably a good idea.

7 hours ago, urgeboc said:

So basically what you're saying about the JoyNumbers is that it will be ok to unplug both my rudders and yoke and plug it back in the same port when im gonna fly again?

Better, it won't matter which port you plug them into, as FSUIPC will track them by their names.

7 hours ago, urgeboc said:

And if something goes wrong i just "assign" the correct letter to the usb?

No, you would need to do nothing. What's to go wrong? The only problem you'd be left with is having controllers not disabled in P3D. I won't really be able to help if you continue with that.

Pete

 

[urgeboc]

I saw a tip on a forum once where someone complained that when they used either left or right brake the plane would go in the direction where you applied the brake, and i had the same "problem". So i assigned both left and right brake to the same pedal so the plane would stay straight when applying brake.

Well, i didnt figure out out how to assign reverse thrust and found it easier to do in the controls menu. And with the rudder i didnt find a option to change the sensitivity and dead zone like you can in the controls menu.

 

 

[Pete Dowson]

1 hour ago, urgeboc said:

I saw a tip on a forum once where someone complained that when they used either left or right brake the plane would go in the direction where you applied the brake, and i had the same "problem"

Well that would mean your calibration wasn't very good. with correct calibration you should be able to steer with good sensitivity whilst braking, keeping straight should be easy.

1 hour ago, urgeboc said:

Well, i didnt figure out out how to assign reverse thrust and found it easier to do in the controls menu.

But it was the Spoilers you said you set in P3D, not the Thottle. you do have the throyyle assigned in FSUIPC!  As explained at length in the User Guide, because FS/P3D does not support Reverse Thrust on its throttle assignments, FSUIPC does it using older controls which are only availble for separate throttles for each engine. You'd need to map the single throttle to multiple throttles, a simple checkbox on the calibration page.

Mind you, PMDG's 737 and 777 add-ons don't work with FSUIPC calibrated throttles, and you cannot assign directly but only to the FS Axis controls. I see you have that wrong too.

1 hour ago, urgeboc said:

And with the rudder i didnt find a option to change the sensitivity and dead zone like you can in the controls menu.

That is all done by proper calibration! You shouldn't be using P3Ds sensitivity or dead zones, they really just limit the precision of your devices. The main reason folks use FSUIPC for their devices is for the far better calibration and results. You can even apply different sensitivity curves. P3D's sliders simply make it ignore more of the inputs from the device so gives less precision.

It would really be worth your while reading at least some of the User Guide, especially the chapter on calibration. I think you are rather wasting your money on FSUIPC the way you are using it.

Pete

 

[urgeboc]

Thanks for all your help Pete. Will start configuring everything today.

One question though, i recently bought a gamepad that is plugged in all the time. If i have my rudders connected and opens a game (FIFA17) it scrolls automatically through the menus and its because of the rudder for some strange reason.

So i have to ask, will it cause problem to have the gamepad plugged in while the yoke and rudder is connected?

[Pete Dowson]

26 minutes ago, urgeboc said:

So i have to ask, will it cause problem to have the gamepad plugged in while the yoke and rudder is connected?

Is the gamepad seen as a joystick in FS or FSUIPC? If so, isn't it a separate device? Why would it cause a problem in FS or FSUIPC if it isn't assigned to anything?

The problem with FIFA is probably that it sees the rudder as another valid input, and accepts that too. I don't know if FIFA has control facilities so you can unuassign it, but certainly both FS and FSUIPC allow you to pick and choose what controllers you use.

Pete

 

[urgeboc]

33 minutes ago, Pete Dowson said:

Is the gamepad seen as a joystick in FS or FSUIPC? If so, isn't it a separate device? Why would it cause a problem in FS or FSUIPC if it isn't assigned to anything?

The problem with FIFA is probably that it sees the rudder as another valid input, and accepts that too. I don't know if FIFA has control facilities so you can unuassign it, but certainly both FS and FSUIPC allow you to pick and choose what controllers you use.

Pete

 

It might be because of the last thing you said, that FIFA see the rudder as a valid input. So if FS or FSUIPC doesnt see it like that, then no problem :)

[urgeboc]

Hello again Pete. I went into the config file and edited AutoAssignLetters to =Yes.

Now its like this:

[JoyNames]
AutoAssignLetters=Yes
0=Pro Flight Cessna Rudder Pedals
0.GUID={CBD93CA0-D99E-11E5-8002-444553540000}
1=Controller (XBOX One For Windows)
1.GUID={1706B0B0-8CC1-11E6-8001-444553540000}
2=Saitek Pro Flight Yoke
2.GUID={93076130-D99F-11E5-8003-444553540000}
A=Pro Flight Cessna Rudder Pedals
B=Controller (XBOX One For Windows)
C=Saitek Pro Flight Yoke

 

Is thats how it supposed to be? The example shown in User Guide is not like that, so i want to make sure if its correct or not.

[Pete Dowson]

28 minutes ago, urgeboc said:

Is thats how it supposed to be? The example shown in User Guide is not like that, so i want to make sure if its correct or not.

The GUIDs should be duplicated with A, B, C as well, but they're not essential when all the devices have different names in any case. What's more important is that the assignments have been correctly automatically lettered in place of the numbers.

Pete

 

[urgeboc]

15 minutes ago, Pete Dowson said:

The GUIDs should be duplicated with A, B, C as well, but they're not essential when all the devices have different names in any case. What's more important is that the assignments have been correctly automatically lettered in place of the numbers.

Pete

 

Alright, i replaced the numbers with the letters shown for each hardware, so im guessing im good to go!

[Pete Dowson]

9 hours ago, urgeboc said:

i replaced the numbers with the letters shown for each hardware, so im guessing im good to go!

Not "replace" so much as "copy and replace". You need the number lines there too -- i.e. 4 lines for each device, two numbered, two lettered. The idea is that FSUIPC matches them up on each new session in case the ID has changed.

Pete

 

[urgeboc]

4 hours ago, Pete Dowson said:

Not "replace" so much as "copy and replace". You need the number lines there too -- i.e. 4 lines for each device, two numbered, two lettered. The idea is that FSUIPC matches them up on each new session in case the ID has changed.

Pete

 

Oh. So this is wrong then?

Quote

[JoyNames]
AutoAssignLetters=Yes
A=Pro Flight Cessna Rudder Pedals
0.GUID={CBD93CA0-D99E-11E5-8002-444553540000}
B=Controller (XBOX One For Windows)
1.GUID={1706B0B0-8CC1-11E6-8001-444553540000}
C=Saitek Pro Flight Yoke
2.GUID={93076130-D99F-11E5-8003-444553540000}
A=Pro Flight Cessna Rudder Pedals
B=Controller (XBOX One For Windows)
C=Saitek Pro Flight Yoke
0=Pro Flight Cessna Rudder Pedals
1=Controller (XBOX One For Windows)
2=Saitek Pro Flight Yoke

 

[Pete Dowson]

3 hours ago, urgeboc said:

Oh. So this is wrong then?

Well, yes in two ways:

1. You have two identrical lines for the names of A, B and C. Does no harm, but only one is read.
2. You have no A.GUID, B.GUID or C.GUID lines.

The example in the User guide is clear in this. All you needed to do was make a copy all the lines, and replace 0, 1, 2 by A, B, C in the copies, thus getting this:

0=Pro Flight Cessna Rudder Pedals
0.GUID={CBD93CA0-D99E-11E5-8002-444553540000}
1=Controller (XBOX One For Windows)
1.GUID={1706B0B0-8CC1-11E6-8001-444553540000}
2=Saitek Pro Flight Yoke

A=Pro Flight Cessna Rudder Pedals
A.GUID={CBD93CA0-D99E-11E5-8002-444553540000}
B=Controller (XBOX One For Windows)
B.GUID={1706B0B0-8CC1-11E6-8001-444553540000}
C=Saitek Pro Flight Yoke

Actually, I see you have no GUID recorded for the Saitek Yoke -- seems that wasn't connected, or not seen last time you ran FS?

Pete

 

[urgeboc]

5 hours ago, Pete Dowson said:

Well, yes in two ways:

1. You have two identrical lines for the names of A, B and C. Does no harm, but only one is read.
2. You have no A.GUID, B.GUID or C.GUID lines.

The example in the User guide is clear in this. All you needed to do was make a copy all the lines, and replace 0, 1, 2 by A, B, C in the copies, thus getting this:

0=Pro Flight Cessna Rudder Pedals
0.GUID={CBD93CA0-D99E-11E5-8002-444553540000}
1=Controller (XBOX One For Windows)
1.GUID={1706B0B0-8CC1-11E6-8001-444553540000}
2=Saitek Pro Flight Yoke

A=Pro Flight Cessna Rudder Pedals
A.GUID={CBD93CA0-D99E-11E5-8002-444553540000}
B=Controller (XBOX One For Windows)
B.GUID={1706B0B0-8CC1-11E6-8001-444553540000}
C=Saitek Pro Flight Yoke

Actually, I see you have no GUID recorded for the Saitek Yoke -- seems that wasn't connected, or not seen last time you ran FS?

Pete

 

 

Trying to get my head around this, but it aint easy. Can i just copy/paste what you just wrote into the config and i will be good to go?

Isnt this the GUID for the Yoke?

2=Saitek Pro Flight Yoke
2.GUID={93076130-D99F-11E5-8003-444553540000}

[Pete Dowson]

1 hour ago, urgeboc said:

Isnt this the GUID for the Yoke?

2=Saitek Pro Flight Yoke
2.GUID={93076130-D99F-11E5-8003-444553540000}

Oh yes. Sorry. I missed that.

1 hour ago, urgeboc said:

Trying to get my head around this, but it aint easy. Can i just copy/paste what you just wrote into the config and i will be good to go?

There was nothing for you to "get your head around" originally. You have just made it seem complicated. When you set "AutoAssignLetters=Yes" that was ALL you needed to do. I did say in my first reply to that that you could leave it at that, it would work fine.

Anyway, now, either just delete the duplicate lines you've inexplicably added, or replace it all with what I give above plus, yes, that 2.GUID line.

The only time you really ever needed to edit this section would be if you wanted more sensible letters assigned than A, B, C. For instance P for pedals, Y for yoke and T for Throttle.  That would be without "Auto" assigning letters. The autoassignletters method means you just change one "No" to a "Yes" and have done with it.

This whole subject takes only one page in the user guide and has always been adequate. What was there not to understand there?

Pete

 

[urgeboc]

9 minutes ago, Pete Dowson said:

Oh yes. Sorry. I missed that.

There was nothing for you to "get your head around" originally. You have just made it seem complicated. When you set "AutoAssignLetters=Yes" that was ALL you needed to do. I did say in my first reply to that that you could leave it at that, it would work fine.

Anyway, now, either just delete the duplicate lines you've inexplicably added, or replace it all with what I give above plus, yes, that 2.GUID line.

The only time you really ever needed to edit this section would be if you wanted more sensible letters assigned than A, B, C. For instance P for pedals, Y for yoke and T for Throttle.  That would be without "Auto" assigning letters. The autoassignletters method means you just change one "No" to a "Yes" and have done with it.

This whole subject takes only one page in the user guide and has always been adequate. What was there not to understand there?

Pete

 

Allright, i got it now. And sorry for being a little bit slow!

 

Thanks for your help! Really appreciate it :)