P3Dv4 switches quit working with FSUIPC5 installed

[fec141]

Let me start by saying this is a clean install of P3Dv4.  Installed a registered copy of FSUIPC5, Version 5.102 and can no longer switch the Nav Radio Frequencies in the default Bonanza A36 between standby and active. I can change the frequency numbers in the standby slot but can not make the frequency active. Removed FSUIPC5 and radio functions fine.

I have attached the log file

Thanks

Dave

 

FSUIPC5.log

[Pete Dowson]

On 6/15/2017 at 7:09 PM, fec141 said:

Installed a registered copy of FSUIPC5, Version 5.102 and can no longer switch the Nav Radio Frequencies in the default Bonanza A36 between standby and active. I can change the frequency numbers in the standby slot but can not make the frequency active. Removed FSUIPC5 and radio functions fine.

Is that using the on-screen radio switches, or some hardware attachment?

Without actually using FSUIPC for something it doesn't really do anything by itself just because it is installed and registered. You don't show your settings (FSUIPC5.INI) file, so I can't check.  The log shows an "Logitech Extreme 3D" device connected. Is that involved?

Pete

 

 

 

[fec141]

Pete

It's using the on screen buttons - just clicking it with a mouse.  the only buttons I have programmed on the Logitech Extreme 3D are basic things like flaps, brakes, etc. nothing to do with avionics like radios, autopilot, etc.

P3D and FSUIPC5 were a clean install and I had not touched any settings in FSUIPC. My only use for it is so that I can run Flight Sim Commander from laptop through WideFS

I disconnected the joystick and went through task manager and shutdown anything else that could be running with P3D and switches still did not work as long as FSUIPC5 is active in P3D.

If I set FSUIPC 5    <Disabled> to True in dll.xml and restart P3Dv4 the switches work fine again.

I have attached all the files - hope they help

additionally, if I set up a key press in FSUIPC5 then the freqs will switch with the key press but will still not work if on screen buttons are clicked with mouse.

Dave

FSUIPC5 Install.log

FSUIPC5.ini

FSUIPC5.JoyScan.csv

FSUIPC5.log

Edited June 20, 2017 by fec141

[Pete Dowson]

Thanks for all the info. My colleague Thomas has been doing some testing and experimenting on this and has confirmed that there's something very off going on just with the SWAP control.  FSUIPC does intercept all controls, just so it can log them, but t doesn't stop them going through. Something odd is happening with that one. It seems to be something odd with P3D4, just with that one control, when it receives it from FSUIPC instead of directly.

I'll be investigating in the morning. I may have to get L-M to look at it, because FSUIPC is certainly not doing anything different than it has always done, with FSX, FSX-SE and all P3D versions. And there are hundreds of other controls all teated the same way, such as those actually used to set the radio frequencies in the first place. in fact every single thing you can assign in P3D or FSUIPC.

Pete

 

[Pete Dowson]

Please download version 5.102a from the Download Links subforum. It fixes this problem by using a work-around.

The problem is that those swap buttons use a sequence of 3 events ending with "FREQUENCY SWAP", which doesn't work. It seems the code is supposed to convert this into the correct specific swap event (as the radios in other aircraft do in the first place)), but for reasons unknown it does not do this if FSUIPC is monitoring events, as it always does so it can log them and provide user facilities through them.

The work-around is for FSUIPC to perform this action if it sees nothing else do it. This does induce a small delay (a third of a second), but it cannot be immediate in case it is fixed elsewhere and you get a double swap action as a result. It has to wait and see if the correct action is taken first.

Note that the proper events when sent using keypresses or buttons do work. You just should not assign to "FREQUENCY SWAP" which seems to be broken.

Pete

 

[fec141]

Pete

installed version 5.102a and everything works fine now.  It would be interesting to know what changed since FSUIPC and the A36 get along fine together in P3Dv3.4

Thanks Again for great support

Dave

[Pete Dowson]

10 minutes ago, fec141 said:

It would be interesting to know what changed since FSUIPC and the A36 get along fine together in P3Dv3.4

I thought I'd explained that.  Seee this, repeated from above:

The problem is that those swap buttons use a sequence of 3 events ending with "FREQUENCY SWAP", which doesn't work. It seems the code is supposed to convert this into the correct specific swap event (as the radios in other aircraft do in the first place)), but for reasons unknown it does not do this if FSUIPC is monitoring events, as it always does so it can log them and provide user facilities through them.

The work-around is for FSUIPC to perform this action if it sees nothing else do it. This does induce a small delay (a third of a second), but it cannot be immediate in case it is fixed elsewhere and you get a double swap action as a result. It has to wait and see if the correct action is taken first.

Note that the proper events when sent using keypresses or buttons do work. You just should not assign to "FREQUENCY SWAP" which seems to be broken.