Mapped button press work in P3Dv3.1 but not v3.2

[maximilianchen]

Hello Peter,

 

This question is about the button mapping for PMDG777 in P3D v3.2.3, with FSUIPC4 v4.949h.

 

Back in the P3D v3.1 era (and any version earlier), I mapped a button on my saitek yoke to send ctrl+shift+z when the button is pressed through FSUIPC. This button press is meant to disconnect the autopilot in PMDG777 and it worked flawlessly in previous versions (of P3D and FSUIPC).

 

However since I updated my P3D to v3.2.3 this function seems not working. Strangely enough, all other button assignments that I have in the FSUIPC work as it should (trim up/dn, flaps up/dn...etc), but just this single button.  I checked the "key command" setting in PMDG777 itself and the setting is in agreement bewteen FSUIPC and PMDG777 for disconnecting the autopilot; I checked and confirmed that this button does send out signal when being pressed (through the default device setting in Win7). I wonder if you have received similar user report since the release of P3D v3.2.3?

 

Win7 SP1

P3D v3.2.3

FSUIPC v4.949h

Latest version of PMDG777

 

Thanks.

[Pete Dowson]

Back in the P3D v3.1 era (and any version earlier), I mapped a button on my saitek yoke to send ctrl+shift+z when the button is pressed through FSUIPC. This button press is meant to disconnect the autopilot in PMDG777 and it worked flawlessly in previous versions (of P3D and FSUIPC).

 

However since I updated my P3D to v3.2.3 this function seems not working. Strangely enough, all other button assignments that I have in the FSUIPC work as it should (trim up/dn, flaps up/dn...etc), but just this single button.  I checked the "key command" setting in PMDG777 itself and the setting is in agreement bewteen FSUIPC and PMDG777 for disconnecting the autopilot; I checked and confirmed that this button does send out signal when being pressed (through the default device setting in Win7). I wonder if you have received similar user report since the release of P3D v3.2.3?

 

No. And FSUIPC isn't treating it any differently. But I suspect most PMDG 777 users would be assigning direct to the <custom control> facility, using the PMDG published control numbers for these things. (See the 777 SDK folder, the .h file lists them all, after the data listing).

 

Pete

[maximilianchen]

No. And FSUIPC isn't treating it any differently. But I suspect most PMDG 777 users would be assigning direct to the <custom control> facility, using the PMDG published control numbers for these things. (See the 777 SDK folder, the .h file lists them all, after the data listing).

 

Pete

 

Hi Pete,

 

I had a look at the button setting page in FSUIPC just now and, when the joystick button is pressed FSUIPC definitely picks up the signal; I tested the key command using keyboard input and PMDG777 picks up the key command no problem. It appears the issue is that the FSUIPC is not talking to PMDG when this button is pressed. Do you have any clue on where I can further my investigation on the issue please?

[Pete Dowson]

I had a look at the button setting page in FSUIPC just now and, when the joystick button is pressed FSUIPC definitely picks up the signal

 

 

 

That's not a good check. Didn't you enable Button/Key logging and check in the log that the keypress in being sent okay?

 

It appears the issue is that the FSUIPC is not talking to PMDG when this button is pressed. Do you have any clue on where I can further my investigation on the issue please?

 

FSUIPC doesn't "talk" to PMDG. Key presses are just sent to the main FS Window, effectively emulating the keyboard. And this is the same on all FSUIPC versions and with all Flight Sims.

 

If the keypress is being sent (and I thought you would have checked this), then it sounds like something it intercepting this in P3D, or causing it to be ignored. Why this should happen when keypresses are sent by program instead of from the real keyboard I don't know, but they are distinguishable if something really wants to.

 

Earlier you said 

 

all other button assignments that I have in the FSUIPC work as it should (trim up/dn, flaps up/dn...etc),

 

 

Are you talking there also about assignments to key presses, or to controls? If keypresses, then it definitely seems the key combination you are having trouble with is being singled out. Is it possible to reassign to a different one?

 

If it affects all assignments to keys, and you didn't have this problem in P3D3.1, then something has obviously gone wrong in P3D3.2. I am checking here now (but not with PMDG aircraft, as I have none).

 

Pete

[Pete Dowson]

Okay. tested and working:

 

in P3D3.2, using FSUIPC 4.949k (the latest interim update released on Sunday), I assigned a button to Ctr+Shift+Z, which is assigned by default in P3D to "altitude bug set". That worked fine.

 

Then, again in FSUIPC, I assigned that keypress to "Sound toggle" (so it would be obvious to me when it worked). It did work -- the button toggles the sound.

 

Then, just to be really sure, I unassigned the keypress in FSUIPC and reassigned Ctrl+Shift+Z to Sound on/off in P3D instead.

 

Again the button worked fine, toggling the sound.

 

So, it seems P3D3.2 is fine. There's either something wrong with your assignments, or with the PMDG add-on.

 

Pete

[maximilianchen]

Okay. tested and working:

 

in P3D3.2, using FSUIPC 4.949k (the latest interim update released on Sunday), I assigned a button to Ctr+Shift+Z, which is assigned by default in P3D to "altitude bug set". That worked fine.

 

Then, again in FSUIPC, I assigned that keypress to "Sound toggle" (so it would be obvious to me when it worked). It did work -- the button toggles the sound.

 

Then, just to be really sure, I unassigned the keypress in FSUIPC and reassigned Ctrl+Shift+Z to Sound on/off in P3D instead.

 

Again the button worked fine, toggling the sound.

 

So, it seems P3D3.2 is fine. There's either something wrong with your assignments, or with the PMDG add-on.

 

Pete

 

Bugger....looks like something I need to figure out myself. Thanks for your confirmation Pete, appreciated.