FSUIPC not seeing PFC buttons

[airforce2]

Pete;

Having trouble trying to program my PFC yoke buttons in FSUIPC in a new FSX installation. Programming buttons within the PFC driver works OK, but if I go to FSUIPC Buttons+Switches tab, and press the PFC button, nothing happens. Have repaired SimConnect, and tried 4-5 versions back from 4.03/4.065...same thing each time.

Regards

[Pete Dowson]

Having trouble trying to program my PFC yoke buttons in FSUIPC in a new FSX installation. Programming buttons within the PFC driver works OK, but if I go to FSUIPC Buttons+Switches tab, and press the PFC button, nothing happens. Have repaired SimConnect, and tried 4-5 versions back from 4.03/4.065...same thing each time.

FSUIPC4 recognising PFC buttons is nothing to do with SimConnect, it is a direct call from the PFCFSX.DLL into the FSUIPC4.DLL, which loaded it in the first place.

Could you please do some logging? add

Debug=Please

LogExtras=2

LogButtonsKeys=Yes

to the [General] section of FSUIPC4.INI, run FSX, go into the PFC Test page and check the logging for "only changes to decoded data".

Then operate some PFC buttons (note down which), close FSX, ZIP up the FSUIPC4.LOG and the PFCFSX.LOG and send them to me at petedowson@btconnect.com.

Thanks,

Pete

[airforce2]

Pete;

The electrons are streaking your way now.

Cheers

[Pete Dowson]

The electrons are streaking your way now.

Got them. Thanks. I'll see to this today.

Regards

Pete

[Pete Dowson]

The electrons are streaking your way now.

I've been trying to replicate the problem here, with no success at all I'm afraid. Since the code for that part is pretty much identrical to the way it was in FS2004 this is not surprising (the complete re-write for FSUIPC4 and WideFS7 only applies to the main functions of FSUIPC, the interface to FS itself).

The logs I asked for don't particularly help, as they do show what they should show for use of the buttons EXCEPT in the Options.

Looking at what I asked you to do I realise it was my fault. I forgot to ask you to actually do the thing which you report as not working -- i.e. enter the Buttons options and try to see them pressed there.

If I do that here, with that logging, I get Log entries like this (for the exact sequence you used for your test, as below):

   182110 *** Entered Buttons option page ***
   190188 ButtonCheck dwNow[16]=00210000, dwLast[16]=00200000 (pFirst YES)
   190188 ButtonCheck res=1, *pFirst=4112 (0.16, 16)
   190188 FirstButtonChange res=00001010 (0.16, 16)
   191235 ButtonCheck dwNow[16]=00200000, dwLast[16]=00210000 (pFirst YES)
   200985 ButtonCheck dwNow[16]=00220000, dwLast[16]=00200000 (pFirst YES)
   200985 ButtonCheck res=1, *pFirst=4113 (0.16, 17)
   200985 FirstButtonChange res=00001011 (0.16, 17)
   201938 ButtonCheck dwNow[16]=00200000, dwLast[16]=00220000 (pFirst YES)
   212360 ButtonCheck dwNow[20]=00000400, dwLast[20]=00000000 (pFirst YES)
   212360 ButtonCheck res=1, *pFirst=5130 (0.20, 10)
   212360 FirstButtonChange res=0000140A (0.20, 10)
   213500 ButtonCheck dwNow[20]=00000000, dwLast[20]=00000400 (pFirst YES)
   219907 ButtonCheck dwNow[20]=00001000, dwLast[20]=00000000 (pFirst YES)
   219907 ButtonCheck res=1, *pFirst=5132 (0.20, 12)
   219907 FirstButtonChange res=0000140C (0.20, 12)
   220594 ButtonCheck dwNow[20]=00000000, dwLast[20]=00001000 (pFirst YES)
   227485 ButtonCheck dwNow[28]=00000001, dwLast[28]=00000000 (pFirst YES)
   227485 ButtonCheck res=1, *pFirst=7168 (0.28, 0)
   227485 FirstButtonChange res=00001C00 (0.28, 0)
   228516 ButtonCheck dwNow[28]=00000000, dwLast[28]=00000001 (pFirst YES)
   234860 ButtonCheck dwNow[20]=00000020, dwLast[20]=00000000 (pFirst YES)
   234860 ButtonCheck res=1, *pFirst=5125 (0.20, 5)
   234860 FirstButtonChange res=00001405 (0.20, 5)
   235485 ButtonCheck dwNow[20]=00000000, dwLast[20]=00000020 (pFirst YES)
   244610 *** Exiting Buttons option page ***

To quote from your email:

Button sequence was as follows (all on the left side of the yoke):

Left upper rocker press-release

Left-lower rocker press-release

Right-upper rocker press-release

Right-lower rocker press-release

AP disconnect press-release

Left-fwd button press-release

This is actually the part I need to see on your system.

At present I have no idea whatsoever how the button bits can be changing well (as shown in your log) yet be ignored in the Buttons option dialogue. It makes no sense at present. The Buttons dialogue merely looks through those exact same values for the first change.

Sorry not to be of immediate help.

Regards

Pete

[Pete Dowson]

Hi Bob,

Thanks for the second log. Now this is COMPLETELY different from the first, and shows a serious SimConnect problem. I suspect that it is this which is preventing anything working properly at all. If you look at the FSUIPC4 log yourself you will see what I mean. It is mostly populated by this sequence, repeated:

82125 **** Simconnect Data Stalled! Re-connecting now****

82125 SimConnect_Open succeeded: proceeding to initialise interface!

82125 Initialising SimConnect data requests now

82140 FSUIPC Menu entry added

82171 Running in "Microsoft Flight Simulator X", Version: 10.0.60905.0 (SimConnect: 2.0.60905.0)

83078 System time = 18:25:47, FSX time = 19:24:32 (02:24Z)

Do you have any buttons to press other than the PFC ones? Have you tried any of those?

Because I suspect that no buttons, joysticks, anything, will be seen in FSUIPC4 Options if SimConnect is not cooperating. The PFC buttons scan, although internal between PFCFSX and FSUIPC4, is part of the main button scan which will not occur if Simconnect is not responding to general requests.

I don't understand what has changed between your last log, which showed no signs whatsoever of any Simconnect problem, and this one which shows such serious problems. Have you changed anything else, installed anything else?

I think next we need a SimConnect log -- instructions on producing one of those are given in the "FSX Help" announcement above.

Pleasealso try again (tyhe same test) with the attached interim update of FSUIPC4, version 4.066, which has longer timeouts on initial connections in case some of the errors are simply because your system is so heavily loaded (SimConnect-wise) that it is unable to supply requested data withing the first second or two after connection. (What sort of frame rates are you getting in FSX?).

Regards

Pete

FSUIPC4066.zip