Jump to content
The simFlight Network Forums
Sign in to follow this  
Randy Chance

Axes work fine but buttons don't respond in FSUIPCv5.101j

Recommended Posts

I'm using the x55 rhino and on prepar3d v4 with the PMDG 747 v3. I'm able to bind axes but not buttons or keys. I follow the process normally but it just doesn't have any effect in the aircraft. Throttles, rudder, ailerons and elevators all work perfect. Thanks for helping. (I have a registered version of fsuipcv5.101j)

Edited by Randy Chance

Share this post


Link to post
Share on other sites
23 minutes ago, Randy Chance said:

I'm using the x55 rhino and on prepar3d v4 with the PMDG 747 v3. I'm able to bind axes but not buttons or keys. I follow the process normally but it just doesn't have any effect in the aircraft.

Are you sure you aren't trying to use functions which are implemented differently in the PMDG aircraft. Please test with a default aircraft.

The state of buttons is read at the same time as the axes. FSUIPC can't get on without the other.

Pete

 

Share this post


Link to post
Share on other sites

Thanks for the reply Pete.. 

Also does not work for default. What do you mean by "implemented differently in the PMDG aircraft"? I have disabled all controls for the PMDG in Prepar3d v4.

Share this post


Link to post
Share on other sites
56 minutes ago, Pete Dowson said:

Are you sure you aren't trying to use functions which are implemented differently in the PMDG aircraft. Please test with a default aircraft.

The state of buttons is read at the same time as the axes. FSUIPC can't get on without the other.

Pete

 

Thanks for the reply Pete.. 

Also does not work for default. What do you mean by "implemented differently in the PMDG aircraft"? I have disabled all controls for the PMDG in Prepar3d v4.

The buttons and switches work when I assign them to other non aircraft functions like... 'open and closing atc menu'. It just doesn't have any effect on the aircraft functions.

Share this post


Link to post
Share on other sites
19 minutes ago, Randy Chance said:

What do you mean by "implemented differently in the PMDG aircraft"?

For many things you can normally assign to for default and less sophisticated aircraft, PMDG implement their own controls. These are llisted in their SDK. They can be assigned if you work out the number and use the <custom control> facility in FSUIPC.

21 minutes ago, Randy Chance said:

The buttons and switches work when I assign them to other non aircraft functions like... 'open and closing atc menu'. It just doesn't have any effect on the aircraft functions.

Aircraft functions such as?

Perhaps you should show me your FSUIPC5.INI file. You'll find it in the Modules folder.

Looking back, you said:

1 hour ago, Randy Chance said:

I'm able to bind axes but not buttons or keys.

By "bind" do you mean "assign"?  Because if you cn't assign them how did you assign one to opening and closing the ATC menu? Surely that shows that they are being received and sent on.

You could enable Event logging in the FSUIPC Logging menu and see if the correct controls are being sent when you press buttons.

Pete

 

Share this post


Link to post
Share on other sites
17 minutes ago, Pete Dowson said:

For many things you can normally assign to for default and less sophisticated aircraft, PMDG implement their own controls. These are llisted in their SDK. They can be assigned if you work out the number and use the <custom control> facility in FSUIPC.

Aircraft functions such as?

Perhaps you should show me your FSUIPC5.INI file. You'll find it in the Modules folder.

Looking back, you said:

By "bind" do you mean "assign"?  Because if you cn't assign them how did you assign one to opening and closing the ATC menu? Surely that shows that they are being received and sent on.

You could enable Event logging in the FSUIPC Logging menu and see if the correct controls are being sent when you press buttons.

Pete

 

I enabled the 'event logging' and it shows a bunch of events scrolling down continuously without end. 

And by by 'bind' I meant I am able to assign key to functions but when i move to the aircraft those 'assigned' keys do not do anything. 

'733360 *** EVENT: Cntrl= 65701 (0x000100a5), Param= 32 (0x00000020) VIEW_ZOOM_SET' .....  this is a line from the whole lot.

'853828 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE'....... and this line appears anytime I flick the switch assigned to 'atc menu close'

Edited by Randy Chance

Share this post


Link to post
Share on other sites

[General]
UpdatedByVersion=5101j
History=L03C4QNV1V2274JR8E7S9
InitDelayDevicesToo=No
Annotate=Yes
NewInterceptTextMenu=No
UseSystemTime=Yes
UseMidMouseBtn=Yes
MouseWheelMove=No
MouseWheelTrim=No
MouseWheelTrimSpeed=1
JoystickTimeout=20
FixControlAccel=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=0,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
CustomWeatherModify=No
SimConnectStallTime=1
InitialStallTime=10
NormalStallTime=1
LuaRerunDelay=66
Console=No
FSVersionUsed="Lockheed Martin® Prepar3D® v4",4.0.23.21468
SimConnectUsed=4.0.0.0
LogEvents=Yes

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

[JoyNames]
AutoAssignLetters=No
0=Saitek Pro Flight X-55 Rhino Throttle
0.GUID={BB203020-23AE-11E7-8006-444553540000}
2=Controller (Xbox One For Windows)
2.GUID={CA62D2D0-31E7-11E7-8001-444553540000}
1=Saitek Pro Flight X-55 Rhino Stick
1.GUID={BB205730-23AE-11E7-8008-444553540000}

[Axes]
PollInterval=10
RangeRepeatRate=10
0=0X,256,D,4,0,0,0    -{ DIRECT: Throttle }-
1=1X,256,D,1,0,0,0    -{ DIRECT: Aileron }-
2=1Y,256,D,2,0,0,0    -{ DIRECT: Elevator }-
3=1R,256,D,3,0,0,0    -{ DIRECT: Rudder }-

[Buttons]
PollInterval=25
ButtonRepeat=20,10
2=U0,17,C0,0     -{Custom control: <0>}-
4=R1,0,C65588,0     -{BRAKES}-
5=P1,4,C65599,0     -{FLAPS_2}-
6=P0,10,C66513,0     -{ATC_MENU_OPEN}-
7=P0,9,C66514,0     -{ATC_MENU_CLOSE}-
8=P0,8,C65752,0     -{PARKING_BRAKES}-
9=P1,3,C65752,0     -{PARKING_BRAKES}-

[AutoSave]
Next=1
Interval=60
Files=10
SaveOnGround=Yes
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 v4\Sound\
Device1=Primary Sound Driver
Device2=Speakers (Realtek High Definition Audio)
Device3=Realtek Digital Output (Realtek High Definition Audio)
Device4=PLG2773-4 (NVIDIA High Definition Audio)

[Profile.Boeing]
1=Boeing

[Buttons.Boeing]
2=P0,4,C65751,0     -{LANDING_LIGHTS_TOGGLE}-

[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
Throttle=-16159,15935
SlopeThrottle=4

[Axes.Boeing]
RangeRepeatRate=10
0=0X,256,D,4,0,0,0    -{ DIRECT: Throttle }-
1=0R,256,D,23,0,0,0    -{ DIRECT: Flaps }-
2=1X,256,D,1,0,0,0    -{ DIRECT: Aileron }-
3=1Y,256,D,2,0,0,0    -{ DIRECT: Elevator }-
4=1R,256,D,3,0,0,0    -{ DIRECT: Rudder }-

[Profile.747]
1=PMDG 747-406 KLM Royal Dutch Airlines (PH-BFN | 2017)
2=Lockheed Martin F-16C - USAF Gray

[Axes.747]
RangeRepeatRate=10
0=0X,256,D,4,0,0,0    -{ DIRECT: Throttle }-
1=0Y,256,D,4,0,0,0    -{ DIRECT: Throttle }-
2=1X,256,D,1,0,0,0    -{ DIRECT: Aileron }-
3=1Y,256,D,2,0,0,0    -{ DIRECT: Elevator }-
4=1R,256,D,3,0,0,0    -{ DIRECT: Rudder }-

[Buttons.747]
0=P1,4,C65792,0     -{AUTOPILOT_ON}-
 

Share this post


Link to post
Share on other sites
1 hour ago, Randy Chance said:

And by by 'bind' I meant I am able to assign key to functions but when i move to the aircraft those 'assigned' keys do not do anything. 

And what functions are you assigning to which don't appear to be working for you. (I did ask you this before!).

Your INI shows that the ONLY buttons you've assigned are:

PollInterval=25
ButtonRepeat=20,10
2=U0,17,C0,0     -{Custom control: <0>}-
4=R1,0,C65588,0     -{BRAKES}-
5=P1,4,C65599,0     -{FLAPS_2}-
6=P0,10,C66513,0     -{ATC_MENU_OPEN}-
7=P0,9,C66514,0     -{ATC_MENU_CLOSE}-
8=P0,8,C65752,0     -{PARKING_BRAKES}-
9=P1,3,C65752,0     -{PARKING_BRAKES}-

You have an odd custom control of 0 which can't possibly do anything.

If you've loaded one of these aircraft:
1=PMDG 747-406 KLM Royal Dutch Airlines (PH-BFN | 2017)
2=Lockheed Martin F-16C - USAF Gray

you also have this button to use:
0=P1,4,C65792,0     -{AUTOPILOT_ON}-
replacing your FLAPS 2 assignment,

or for other Boeings:

[Profile.Boeing]
1=Boeing

[Buttons.Boeing]
2=P0,4,C65751,0     -{LANDING_LIGHTS_TOGGLE}-

No others. A rather odd lot of assignments really. Very few "normal" assignments I would expect you to use, and two separate assignments to "PARKING BRAKES".

So which don't work?  Without seeing the log I can't help further. 

Pete

 

Share this post


Link to post
Share on other sites
45 minutes ago, Pete Dowson said:

 

So which don't work?  Without seeing the log I can't help further. 

Pete

 

Pete, .. I think i got things figured out now. I went into the SDK, computed the Event ID and set the appropriate parameters in FSUIPC and the buttons are responding. Thanks for your help and time. Much appreciated. 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.