Profile Specific data lost

[atrcaptainjohn]

Pete,

 

I have all of my PMDG aircraft set up with a ton of key commands, and this morning I seem to have lost all the profile specific data.  My "General assignments" still appear to work, but none of the profile specific buttons work, and when I go into the FSUPIC control panel and hit one of them they don't show what I had previously assigned to them.  FWIW, earlier this morning I set up the axis controls on a Carenado Bonanza, and when I ticked the profile specific box before I started it asked me if I wanted to save changes before I started, and I selected yes.  Any ideas?  I would rather not have to set them all up again.  I'm using ver 4.949 with FSX Accel boxed version, Windows 7 64bit.

 

Thanks

john croft

 

[Pete Dowson]

I have all of my PMDG aircraft set up with a ton of key commands, and this morning I seem to have lost all the profile specific data.  My "General assignments" still appear to work, but none of the profile specific buttons work, and when I go into the FSUPIC control panel and hit one of them they don't show what I had previously assigned to them.  FWIW, earlier this morning I set up the axis controls on a Carenado Bonanza, and when I ticked the profile specific box before I started it asked me if I wanted to save changes before I started, and I selected yes.  Any ideas?  I would rather not have to set them all up again.  I'm using ver 4.949 with FSX Accel boxed version, Windows 7 64bit.

 

FSUIPC doesn't lose settings. They are stored in your Modules folder, in the FSUIPC4.INI file. You should back it up (make a safe copy somewhere) in case any accident, such as a machine crash, corrupts it, but apeart from that nothing but your own actions should change it. And Profiles can't actually be deleted without editing the file itself.

 

I expect they are still there and you are simply loading an aircraft variant which was not previously registered with a profile. Did you click the Profile option in the Buttons tab to see if you could assign it?

 

If you are still puzzled, show me the INI file. You can paste its contents into a message here. Best to use the <> button just above the edit area to enclose it.

 

Pete

[atrcaptainjohn]

FSUIPC doesn't lose settings. They are stored in your Modules folder, in the FSUIPC4.INI file. You should back it up (make a safe copy somewhere) in case any accident, such as a machine crash, corrupts it, but apeart from that nothing but your own actions should change it. And Profiles can't actually be deleted without editing the file itself.

 

I expect they are still there and you are simply loading an aircraft variant which was not previously registered with a profile. Did you click the Profile option in the Buttons tab to see if you could assign it?

 

If you are still puzzled, show me the INI file. You can paste its contents into a message here. Best to use the <> button just above the edit area to enclose it.

 

Pete

It would appear that they still seem to be there, I will post the contents of the file below.  But I am loading the same aircraft and livery that I always use.  There is only one model/livery of the PMDG 737 that I use, and it is the one that I set up the buttons on.  I also just tried it on the PMDG 777-200 that I always use and they don't work there either.  Have I done something to screw myself up here?

[General]
History=MVS8O0W8X4A3FT5F85ZK9
TCASid=Flight
TCASrange=40
AxisCalibration=No
DirectAxesToCalibs=No
ShowMultilineWindow=Yes
SuppressSingleline=No
SuppressMultilineFS=No
AxisIntercepts=No
WeatherReadFactor=2
WeatherRewriteSeconds=1
SimConnectStallTime=1
UpdatedByVersion=4949
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
DontResetAxes=No
InitDelay=0
GetNearestAirports=Yes
OOMcheck=Yes
OOMcheckInterval=10
CustomWeatherModify=No
LuaRerunDelay=66
Console=No
FSVersionUsed="Microsoft Flight Simulator X",10.0.61637.0
SimConnectUsed=10.0.61259.0

[WideServer]
WideFSenabled=Yes
AdvertiseService=1
Port=8002
Port2=9002

[JoyNames]
AutoAssignLetters=Yes
2=Joystick - HOTAS Warthog
2.GUID={BDF22170-94E2-11E5-8001-444553540000}
3=Throttle - HOTAS Warthog
3.GUID={BDF26F90-94E2-11E5-8002-444553540000}
A=F16 MFD 1
B=F16 MFD 2
C=Joystick - HOTAS Warthog
D=Throttle - HOTAS Warthog
E=Saitek Pro Flight Combat Rudder Pedals
1=F16 MFD 2
1.GUID={F1D2D720-94E0-11E5-8002-444553540000}
4=Saitek Pro Flight Combat Rudder Pedals
4.GUID={F0B2D640-94E2-11E5-8001-444553540000}
0=F16 MFD 1
0.GUID={F1D2B010-94E0-11E5-8001-444553540000}

[Axes]
PollInterval=10
RangeRepeatRate=10
0=CX,256,F,65763,0,0,0
1=CY,256,F,65762,0,0,0
2=EX,256,F,66387,0,0,0
3=EY,256,F,66388,0,0,0
4=ER,256,F,65764,0,0,0

[Buttons]
PollInterval=25
ButtonRepeat=20,10
1=PC,14,C65759,0
2=PC,16,C65758,0
3=PC,18,C65570,0
4=RC,36,C65615,0
5=RC,32,C65607,0

[LuaFiles]
1=Aerosoft_F14AB

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

[GPSout]
GPSoutEnabled=No

[GPSout2]
GPSoutEnabled=No

[Sounds]
Path=Z:\FSX\Sound\
Device1=Primary Sound Driver
Device2=Speakers (Realtek High Definition Audio)
Device3=Speakers (Corsair HS1 USB Headset)
Device4=HF289H-0 (NVIDIA High Definition Audio)
Device5=Realtek Digital Output(Optical) (Realtek High Definition Audio)
Device6=iH282-C (NVIDIA High Definition Audio)
Device7=Realtek Digital Output (Realtek High Definition Audio)

[Monitor]
Display=4
Monitor0=0,024C,4,0

[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
LeftBrake=-16380,16380/16
RightBrake=-16380,16380/16

[Profile.737-800NGX WL]
1=Boeing 737-824NGX Continental Airlines Winglets

[Axes.737-800NGX WL]
RangeRepeatRate=10
0=CX,256,F,65763,0,0,0
1=CY,256,F,65762,0,0,0
2=DZ,256,F,66423,0,0,0
3=DR,256,F,66420,0,0,0
4=EX,256,F,66387,0,0,0
5=EY,256,F,66388,0,0,0
6=ER,256,F,65764,0,0,0

[Window.VAFS Message:]
Docked=262, 2775, 3545, 1010

[Buttons.737-800NGX WL]
0=PD,30,K113,11
1=PD,17,K112,11
2=PD,31,K115,11
3=PD,18,K114,11
4=PB,1,K70,10
5=PB,2,K82,9
6=PB,6,K71,11
7=PB,0,K90,8
8=PB,4,K75,8
9=PB,19,K86,10
10=PB,17,K72,10
11=PB,18,K78,10
12=PB,16,K79,10
13=PB,15,K65,10
14=PB,3,K90,10
15=PB,5,K85,8
16=RA,21,K116,10
17=RA,20,K116,9
18=RA,27,K117,10
19=RA,26,K117,9
20=RB,21,K118,10
21=RB,20,K118,9
22=RB,23,K119,10
23=RB,22,K119,9
24=RB,25,K120,10
25=RB,24,K120,9
26=PD,25,K68,9
27=PD,20,K70,9
28=PB,27,K121,10
29=PB,26,K121,9
30=PA,4,K72,9
31=PA,2,K84,10
32=PA,1,K76,11
33=PA,0,K76,10
34=PB,9,K66,9
35=RA,24,K122,9
36=RA,25,K122,10

[Profile.E175]
1=Embraer 175 United Express Post-Merger

[Axes.E175]
RangeRepeatRate=10
0=CX,256,F,65763,0,0,0
1=CY,256,F,65762,0,0,0
2=DZ,256,F,66423,0,0,0
3=DR,256,F,66420,0,0,0
4=EX,256,F,66387,0,0,0
5=EY,256,F,66388,0,0,0
6=ER,256,F,65764,0,0,0

[Profile.Leodardo Maddog 2008]
1=TWA Spirit of Long Beach

[Axes.Leodardo Maddog 2008]
RangeRepeatRate=10
0=CX,256,F,65763,0,0,0
1=CY,256,F,65762,0,0,0
2=DZ,256,F,66423,0,0,0
3=DR,256,F,66420,0,0,0
4=EX,256,F,66387,0,0,0
5=EY,256,F,66388,0,0,0
6=ER,256,F,65764,0,0,0

[Profile.ERJ145XR]
1=ERJ145LR - United Express

[Axes.ERJ145XR]
RangeRepeatRate=10
0=CX,256,F,65763,0,0,0
1=CY,256,F,65762,0,0,0
2=DZ,256,F,66423,0,0,0
3=DR,256,F,66420,0,0,0
4=EX,256,F,66387,0,0,0
5=EY,256,F,66388,0,0,0
6=ER,256,F,65764,0,0,0

[Profile.Majestic Q400]
1=MJC8Q400_CJC

[Axes.Majestic Q400]
RangeRepeatRate=10
0=CX,256,F,65763,0,0,0
1=CY,256,F,65762,0,0,0
2=DZ,256,F,66423,0,0,0
3=DR,256,F,66420,0,0,0
4=DS,256,F,66382,0,0,0
5=EX,256,F,66387,0,0,0
6=EY,256,F,66388,0,0,0
7=ER,256,F,65764,0,0,0

[Profile.737-900NGX WL]
1=Boeing 737-924NGX Continental Airlines Winglets

[Buttons.737-900NGX WL]
0=PD,30,K113,11
1=PD,17,K112,11
2=PD,31,K115,11
3=PD,18,K114,11
4=PB,1,K70,10
5=PB,2,K82,9
6=PB,6,K71,11
7=PB,0,K90,8
8=PB,4,K75,8
9=PB,19,K86,10
10=PB,17,K72,10
11=PB,18,K78,10
12=PB,16,K79,10
13=PB,15,K65,10
14=PB,3,K90,10
15=PB,5,K85,8
16=RA,21,K116,10
17=RA,20,K116,9
18=RA,27,K117,10
19=RA,26,K117,9
20=RB,21,K118,10
21=RB,20,K118,9
22=RB,23,K119,10
23=RB,22,K119,9
24=RB,25,K120,10
25=RB,24,K120,9
26=PD,25,K68,9
27=PD,20,K70,9
28=PB,27,K121,10
29=PB,26,K121,9
30=PA,4,K72,9
31=PA,2,K84,10
32=PA,1,K76,11
33=PA,0,K76,10
34=PB,9,K66,9
35=RA,24,K122,9
36=RA,25,K122,10

[Axes.737-900NGX WL]
RangeRepeatRate=10
0=CX,256,F,65763,0,0,0
1=CY,256,F,65762,0,0,0
2=DZ,256,F,66423,0,0,0
3=DR,256,F,66420,0,0,0
4=EX,256,F,66387,0,0,0
5=EY,256,F,66388,0,0,0
6=ER,256,F,65764,0,0,0

[Profile.777-200LR]
1=PMDG 777-224LR Continental Airlines (Fictional)

[Buttons.777-200LR]
0=PD,30,K113,11
1=PD,17,K112,11
2=PD,31,K115,11
3=PD,18,K114,11
4=PB,1,K70,10
5=PB,2,K82,9
6=PB,6,K71,11
7=PB,0,K90,8
8=PB,4,K75,8
9=PB,19,K86,10
10=PB,17,K72,10
11=PB,18,K78,10
12=PB,16,K79,10
13=PB,15,K65,10
14=PB,3,K90,10
15=PB,5,K85,8
16=RA,21,K116,10
17=RA,20,K116,9
18=RA,27,K117,10
19=RA,26,K117,9
20=RB,21,K118,10
21=RB,20,K118,9
22=RB,23,K119,10
23=RB,22,K119,9
24=RB,25,K120,10
25=RB,24,K120,9
26=PD,25,K68,9
27=PD,20,K70,9
28=PB,27,K121,10
29=PB,26,K121,9
30=PA,4,K72,9
31=PA,2,K84,10
32=PA,1,K76,11
33=PA,0,K76,10
34=PB,9,K66,9
35=RA,24,K122,9
36=RA,25,K122,10

[Axes.777-200LR]
RangeRepeatRate=10
0=CX,256,F,65763,0,0,0
1=CY,256,F,65762,0,0,0
2=DZ,256,F,66423,0,0,0
3=DR,256,F,66420,0,0,0
4=EX,256,F,66387,0,0,0
5=EY,256,F,66388,0,0,0
6=ER,256,F,65764,0,0,0

[Profile.CS 757-300]
1=Captain Sim 757-300 FSX 2

[Axes.CS 757-300]
RangeRepeatRate=10
0=CX,256,F,65763,0,0,0
1=CY,256,F,65762,0,0,0
2=DZ,256,F,66423,0,0,0
3=DR,256,F,66420,0,0,0
4=EX,256,F,66387,0,0,0
5=EY,256,F,66388,0,0,0
6=ER,256,F,65764,0,0,0

[Profile.Maddog CAL]
1=Continental

[Axes.Maddog CAL]
RangeRepeatRate=10
0=CX,256,F,65763,0,0,0
1=CY,256,F,65762,0,0,0
2=DZ,256,F,66423,0,0,0
3=DR,256,F,66420,0,0,0
4=EX,256,F,66387,0,0,0
5=EY,256,F,66388,0,0,0
6=ER,256,F,65764,0,0,0

[Profile.Carenado F33 Bonanza]
1=BONANZA F33A BLUERED

[Axes.Carenado F33 Bonanza]
RangeRepeatRate=10
0=CX,256,F,65763,0,0,0
1=CY,256,F,65762,0,0,0
2=DZ,256,F,66421,0,0,0
3=DR,256,F,66420,0,0,0
4=DS,256,F,66422,0,0,0
5=EX,256,F,66387,0,0,0
6=EY,256,F,66388,0,0,0
7=ER,256,F,65764,0,0,0

[Pete Dowson]

It would appear that they still seem to be there, I will post the contents of the file below.  But I am loading the same aircraft and livery that I always use.  There is only one model/livery of the PMDG 737 that I use, and it is the one that I set up the buttons on.  I also just tried it on the PMDG 777-200 that I always use and they don't work there either.  Have I done something to screw myself up here?

 

Well, the way you have it. of all of your PMDG aircraft, only these are assigned to profiles:

 

[Profile.777-200LR]

1=PMDG 777-224LR Continental Airlines (Fictional)

 

[Profile.737-900NGX WL]

1=Boeing 737-924NGX Continental Airlines Winglets

 

[Profile.737-800NGX WL]

1=Boeing 737-824NGX Continental Airlines Winglets

 

Check the FSUIPC4.LOG file to see the actual title of the aircraft you are loading. It is that which it has to match. You've not used any abbreviations in the INI to enable easy matching to any livery. It must match some part of the actual name completely, so the longer the name in the INI, the more restrictive it is.

 

Also remember that whilst Axis assignment and Calibration is all totally either profiled or not, Button and Key assignments in a Profile only override any ones to the same Buutons or Keys in the general assignments. When you look at the Buttons & Switches tab, you switch between the two, to view (or set) by clicking the Profile option.

 

Pete

[atrcaptainjohn]

Here is my log file, it looks to me like the name matches exactly, but maybe I'm seeing it wrong.  What I don't understand is that everything worked fine 2 days ago, which was the last time I flew either the 727 or the 777.

********* FSUIPC4, Version 4.949 by Pete Dowson *********
fsx.exe version = 10.0.61637.0
Reading options from "Z:\FSX\Modules\FSUIPC4.ini"
Running inside FSX on Windows 7
Module base=5EC10000
User Name="John Croft"
User Addr="atrcaptainjohn@yahoo.com"
FSUIPC4 Key is provided
WideFS7 Key is provided
       62 System time = 26/02/2016 12:37:05
       62 FLT UNC path = "X:\Users\John Croft\Documents\Flight Simulator X Files\"
       62 ------ Module Version Check ------
       62        acontain.dll: 10.0.61637.0
       62             api.dll: 10.0.61637.0
       62        controls.dll: 10.0.61637.0
       62      fs-traffic.dll: 10.0.61637.0
       62             G3D.dll: 10.0.61637.0
       62            sim1.dll: 10.0.61637.0
       62        visualfx.dll: 10.0.61637.0
       62         weather.dll: 10.0.61637.0
       62          window.dll: 10.0.61637.0
       62 ----------------------------------
       78 Trying to connect to SimConnect Acc/SP2 Oct07 ...
       78 FS UNC path = "Z:\FSX\"
      171 ---------------------- Joystick Device Scan -----------------------
      171 Product= Joystick - HOTAS Warthog
      171    Manufacturer= Thustmaster
      171    Vendor=044F, Product=0402 (Version 1.0)
      171    Serial Number= 
      171 Product= Throttle - HOTAS Warthog
      171    Manufacturer= Thrustmaster
      171    Vendor=044F, Product=0404 (Version 1.0)
      171    Serial Number= 
      171 Product= Saitek Pro Flight Combat Rudder Pedals
      171    Manufacturer= Saitek
      171    Vendor=06A3, Product=0764 (Version 2.1)
      171    Serial Number= 
      171 -------------------------------------------------------------------
      218 LogOptions=00000000 00000001
      218 -------------------------------------------------------------------
      218 ------ Setting the hooks and direct calls into the simulator ------
      218 --- CONTROLS timer memory location obtained ok
      218 --- SIM1 Frictions access gained
      218 --- FS Controls Table located ok
      218 --- Installed Mouse Macro hooks ok.
      218 --- Wind smoothing fix is fully installed
      218 --- G3D.DLL fix attempt installed ok
      218 --- All links checked okay
      218 -------------------------------------------------------------------
      218 SimConnect_Open succeeded: waiting to check version okay
      218 Trying to use SimConnect Acc/SP2 Oct07
     1076 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)
     1076 Initialising SimConnect data requests now
     1076 FSUIPC Menu entry added
     1092 X:\Users\John Croft\Documents\Flight Simulator X Files\Default Cessna C172.FLT
     1092 Z:\FSX\SimObjects\Airplanes\C172\Cessna172SP.AIR
    27628 System time = 26/02/2016 12:37:32, Simulator time = 12:37:07 (18:37Z)
    27628 Aircraft="Cessna Skyhawk 172SP Paint1"
    28626 Starting everything now ...
    28657 ASN active function link set
    28657 Ready for ASN WX radar
    29968 Advanced Weather Interface Enabled
    61729 Z:\FSX\SimObjects\Airplanes\PMDG 737-800NGX WL\B737-800WL.AIR
    74724 Aircraft="Boeing 737-824NGX Continental Airlines Winglets"
   176671 Sim stopped: average frame rate for last 102 secs = 61.6 fps
   200102 System time = 26/02/2016 12:40:25, Simulator time = 12:38:59 (18:38Z)
   200102 *** FSUIPC log file being closed
Minimum frame rate was 29.7 fps, Maximum was 96.1 fps
Minimum available memory recorded was 1176Mb
Average frame rate for running time of 113 secs = 64.4 fps
G3D fix: Passes 16148, Null pointers 0, Bad pointers 0, Separate instances 0
Memory managed: 56 Allocs, 56 Freed
********* FSUIPC Log file closed ***********

[Pete Dowson]

Here is my log file, it looks to me like the name matches exactly, but maybe I'm seeing it wrong.  What I don't understand is that everything worked fine 2 days ago, which was the last time I flew either the 727 or the 777.

 

Hmm, yes, it does look correct. How are you actually deciding the profile isn't working? Just by pressing the buttons? Have you been to the Buttons & Switches tab, see if clciking the Profile option there displays the correct profile in the title?

 

Are you sure it isn't the buttons themselves not being seen? Try button logging, see what that shows in the Log.

 

Pete

[atrcaptainjohn]

When I go to the FSUPIC interface with the specific aircraft loaded and click "profile specific" and then click one of the buttons, it shows as being pressed, shows which button it is, and says above that "choose the action for this button...".

 

I have a HOTAS Warthog throttle and stick and 2 Thrustmaster MFD Cougars, and this happens regardless of which button I press, except for the ones assigned to non profile specific aircraft, which are gear, flaps, and trim.

 

Like I said before, the ONLY thing that has changed id this morning I set up the throttle, prop, and mixture on a Carenado plane, and when I click on the "profile Specific" button to start assigning it popped up a dialog that asked me if I wanted to save previously made changes.  I hadn't made any changes to that point, but I selected yes.

[Pete Dowson]

When I go to the FSUPIC interface with the specific aircraft loaded and click "profile specific" and then click one of the buttons, it shows as being pressed, shows which button it is, and says above that "choose the action for this button...".

 

Does the button show the joystick number/letter you expected?

 

Like I said before, the ONLY thing that has changed id this morning I set up the throttle, prop, and mixture on a Carenado plane, and when I click on the "profile Specific" button to start assigning it popped up a dialog that asked me if I wanted to save previously made changes.  I hadn't made any changes to that point, but I selected yes.

 

 

Well, FSUIPC hasn't changed, and the INI file you showed me is okay and shows profiles in place, so those actions which you think must have changed things didn't.  Without knowing which buttons you are talking about I can't cross-check, but did you enable button logging as I suggested?  If you temporarily run FS in Windowed mode you can use the Console Log option to see the results in real time.

 

Pete

[atrcaptainjohn]

I'm sorry, I didn't see the suggestion to log.  I started the console log, and loaded the PMDG 737 WL.  The buttons that are not profile specific log just fine, the ones that are profile specific, nothing happens in the log when I press them.

 

And yes, when I am in the FSUPIC interface and press a button, with profile specific checked, the correct stick and button appear to be showing when I press a button.

 

I can just start reassigning things, but I don't want to screw something up if I can get it to work again because I had a lot of buttons assigned.

[Pete Dowson]

I'm sorry, I didn't see the suggestion to log.  I started the console log, and loaded the PMDG 737 WL.  The buttons that are not profile specific log just fine, the ones that are profile specific, nothing happens in the log when I press them.

 

And yes, when I am in the FSUPIC interface and press a button, with profile specific checked, the correct stick and button appear to be showing when I press a button.

 

I can just start reassigning things, but I don't want to screw something up if I can get it to work again because I had a lot of buttons assigned.

 

No, let's try to sort it out. I'm puzzled and would like to work out what is happening.

 

First, some more questions and things to do:

 

1. When you are in the Buttons tab and you press one of the buttons which should do something specific to the Profile, and select the Profile option at the top, does the correct Profile name display at the top, in the options title bar?

 

2. Program that button to something, doesn't matter which, so I can see the effect on the INI file. TEll me which button it was (joy,number).

 

Second, please ZIP up your INI file and send it to me at petedowson@btconnect.com. I'm now wondering whether there are some addition characters in the file, unprintable ones, which are not visible or lost when pasting into the message here. I've seen such corruption happen before, a couple of times over the years.

 

Include a log too please, a complete one.

 

Pete

[atrcaptainjohn]

OK, I think we found the issue.  I never looked at the name that popped up at the top when I click the "profile specific" button.  It says "Maddog CAL" when I have the PMDG 737 loaded.  I still had the console log opened when I loaded the aircradt and I did notice that the log said the right aircraft when it was loading, but once loaded withe the FSUPIC intercafe open, on Buttons + Switches and I click "profile preficid" it is definitely showing "Maddog CAL".

 

Regardless, I have programmed Joystick A, Button 0 to send the command "L".  The .ini file and the log file are on the way to you.

 

I appreciate your assistance with this.  :)

 

john

[Pete Dowson]

OK, I think we found the issue.  I never looked at the name that popped up at the top when I click the "profile specific" button.  It says "Maddog CAL" when I have the PMDG 737 loaded.  I still had the console log opened when I loaded the aircradt and I did notice that the log said the right aircraft when it was loading, but once loaded withe the FSUPIC intercafe open, on Buttons + Switches and I click "profile preficid" it is definitely showing "Maddog CAL".

 

Regardless, I have programmed Joystick A, Button 0 to send the command "L".  The .ini file and the log file are on the way to you.

 

Yes. II just looked and saw this. You have defined a Profile "Maddog CAL" with this aircraft defined:

 

[Profile.Maddog CAL]

1=Continental

 

So all aircraft with "Continental" in their name will use this profile. Before you added the assignment for button A,0 there was no buttons defined.

 

It looks like all of your PMDG aircraft have Continental in the title. That's the only problem I think.

 

If your Maddog has only got "Continental" as a name, then you'd either need to rename it (in its Aircraft.CFG file), or change one of the options in the [General] section -- ShortAircraftNameOk. Here's an extract from the FSUIPC Advanced User's Guide:

 

If the [General] parameter ShortAircraftNameOk is set to Yes or Substring, the <aircraft name> part of the section

heading can be abbreviated (manually, by editing the INI file) so that it applies to more than one aircraft. With the ‘Yes’

option, FSUIPC4 will automatically select the section with the longest match. The ordering of sections in the INI file is

not relevant. However, with the ‘Substring’ option it will select the first section with a substring match – there’s no

concept of “longest match” in this case.

 

The parameter defaults to Substring -- note well the last sentence in this extract.

 

You can change that to Yes instead, in which case it will work with that very short aircraft title.

 

Note that you could make your PMDG profiles apply to more than one aircraft variant by shortening the titles used by FSUIPC.  In fact, all three PMDG profiles have EXACTLY the same assignments for buttons and axes, so it would be much more efficient and sensible to replace all of the Profile, Keys and Axes sections for those aircraft by one set, i.e:

[Profile.PMDG 2 engine]
1=Boeing 737-824NGX
2=Boeing 737-924NGX
3=PMDG 777

[Buttons.PMDG 2 engine]
0=PD,30,K113,11
1=PD,17,K112,11
2=PD,31,K115,11
3=PD,18,K114,11
4=PB,1,K70,10
5=PB,2,K82,9
6=PB,6,K71,11
7=PB,0,K90,8
8=PB,4,K75,8
9=PB,19,K86,10
10=PB,17,K72,10
11=PB,18,K78,10
12=PB,16,K79,10
13=PB,15,K65,10
14=PB,3,K90,10
15=PB,5,K85,8
16=RA,21,K116,10
17=RA,20,K116,9
18=RA,27,K117,10
19=RA,26,K117,9
20=RB,21,K118,10
21=RB,20,K118,9
22=RB,23,K119,10
23=RB,22,K119,9
24=RB,25,K120,10
25=RB,24,K120,9
26=PD,25,K68,9
27=PD,20,K70,9
28=PB,27,K121,10
29=PB,26,K121,9
30=PA,4,K72,9
31=PA,2,K84,10
32=PA,1,K76,11
33=PA,0,K76,10
34=PB,9,K66,9
35=RA,24,K122,9
36=RA,25,K122,10

[Axes.PMDG 2 engine]
RangeRepeatRate=10
0=CX,256,F,65763,0,0,0
1=CY,256,F,65762,0,0,0
2=DZ,256,F,66423,0,0,0
3=DR,256,F,66420,0,0,0
4=EX,256,F,66387,0,0,0
5=EY,256,F,66388,0,0,0
6=ER,256,F,65764,0,0,0

 

Finally, why is every single button assignment only to a keyboard press? In FS keyboard presses are assigned to FS controls, so your assignment is pretty inefficient -- FSUIPC looking up a table to find a key to press which is later picked up by FS which then looks up that key assignment and converts it to a key which it then sends to itself.

 

FSUIPC's assignment facilities offer ALL of the controls which FS can offer, and many more too. Have you ever looked at those?

 

Pete

[atrcaptainjohn]

Yes, that makes sense.  So can I just delete the [Maddog CAL] section from the .ini file, rename the a/c in the aircraft config file and reassign the maddog?

 

And no, I have never looked at the other assignment options.  I figured that because PMDG used keyboard presses for assigning button presses in the FMC setup that I needed to assign key presses and the map the stick buttons to those presses.  Is there a toturoal somewhere on how to make that more efficient?  Because I have essentially run out of keyboard options to assign to things, and there are more assignments that I would like to make, and I certainly have more joystick buttons that I could use.

[Pete Dowson]

Yes, that makes sense.  So can I just delete the [Maddog CAL] section from the .ini file, rename the a/c in the aircraft config file and reassign the maddog?

 

Yes you could -- though there's more than one section. You'd be better just keeping the existng sections and just edit the name in the [Profile.Maddog CAL] section, i.e change "1=Continental2 to the new name, or a unique part of that name.

 

I'm surprised they gave a title like just "Continental" to an aircraft, without even indicating what sort of aircraft it is! It must look a bit strange in the FS Aircraft Selection menu.

 

I figured that because PMDG used keyboard presses for assigning button presses in the FMC setup that I needed to assign key presses and the map the stick buttons to those presses

 

Yes, true, for FMC programming you'd need keypresses (though their SDK probably lists controls for those too, but they won't be FS controls).

 

Is there a toturoal somewhere on how to make that more efficient?  Because I have essentially run out of keyboard options to assign to things, and there are more assignments that I would like to make, and I certainly have more joystick buttons that I could use.

 

No. You assign buttons to functions you need, rather than find functions and assign just for fun. Decide what you want the buttons to do, then find the appropriate control.

 

PMDG aircraft like the 737NGX and 777X are notoriously non-standard so there will be lots of things in the cockpit which are simply NOT controlled by FS controls or keypresses. They are all accessible using "custom controls" added by PMDG. Those are documented in the SDKs they install.

 

Pete

[atrcaptainjohn]

OK I renamed the section you mentioned and the aircraft in the aircraft.cfg file and that fixed it, thank you so much!

 

One more question on the PMDG stuff though.  Let's say I can figure out how to assign, lets say the heading knob up/down through the PMDG sdk stuff.  How would I reassign it is FSUPIC so it wouldn't send the current keypresses but whatever new command that it needed to send?  Would that happen automatically when I reassigned it?

 

Thank you again!

 

john

[Pete Dowson]

One more question on the PMDG stuff though.  Let's say I can figure out how to assign, lets say the heading knob up/down through the PMDG sdk stuff.  How would I reassign it is FSUPIC so it wouldn't send the current keypresses but whatever new command that it needed to send?  Would that happen automatically when I reassigned it?

 

Yes.

 

There was another question recently which related to PMDG's custom controls. I think you'll find the thread useful:

 

efis tfc button

 

Read from 4th post on.

 

Pete

[atrcaptainjohn]

Thanks so much Pete! You're a lifesaver :)