Sudden Problem with Compound Button

[GCNorth]

Hi Pete,

 

I have been using FSUIPC registered version for about two years now, and it works great.  However, I recently encountered a problem that I don't understand.  I am using version 4944a and have programmed my CH Eclipse yoke using compound key assignments for each plane.  This is the programming i have for the Lancair Legacy:

 

0=CR(+A,24)(-A,0)A,1,C65588,0 ;GREEN-break

1=CU(+A,24)(-A,0)A,1,K116,8 ;GREEN-Retract flaps fully

2=CP(+A,24)(+A,0)A,1,C65589,0 ;GREEN-toggle Spoilers

3=CP(+A,24)(+A,0)A,2,K65,8 ;GREEN-next view

4=CP(+A,24)(-A,0)A,2,K86,11 ;GREEN-view virtual cockpit forward (C+S+V)

5=CP(+A,24)(+A,0)A,3,K83,8 ;GREEN-next category

6=CP(+A,24)(-A,0)A,3,K52,9 ;GREEN-Default GPS 500

7=CP(+A,24)(-A,0)A,4,C66079,0 ;GREEN-gear up

8=CP(+A,24)(+A,0)A,4,K56,9 ;GREEN-ICE Gauge

9=CP(+A,24)(-A,0)A,5,C66080,0 ;GREEN-gear down

10=CP(+A,24)(+A,0)A,5,C1009,0 ;GREEN Traffic Density Toggle

11=CP(+A,24)(-A,0)A,6,C65759,0 ;GREEN-flaps retract

12=CR(+A,24)(+A,0)A,6,C65656,0 ;GREEN-zoom out

13=CP(+A,24)(-A,0)A,7,C65758,0 ;GREEN-flaps extend

14=CR(+A,24)(+A,0)A,7,C65655,0 ;GREEN-zoom in

15=CR(+A,24)(+A,0)A,8,C65607,0 ;Green-Elevator Trim Down  GO UP

16=CP(+A,24)(-A,0)A,8,K87,11 ;GREEN-cycle thru interior views (C+S+W)

17=CR(+A,24)(+A,0)A,9,C65615,0 :GREEN-Elevator Trim Up GO DOWN

18=CP(+A,24)(-A,0)A,9,K50,9 ;GREEN-Default GPS

19=CP(+A,24)(+A,0)A,10,C66530,0 ;GREEN-eyepoint reset

20=CR(+A,24)(-A,0)A,10,K85,8 ;GREEN-next checklist item

21=CR(+A,24)(+A,0)A,11,K73,11 ;GREEN-Insrument Panel (C+S+I)

22=CR(+A,24)(-A,0)A,11,K85,9 ;GREEN-next checklist sublist

23=CR(+A,24)(+A,0)A,12,K83,11 ;GREEN-Radios  (C+S+S)

24=CR(+A,24)(-A,0)A,12,K85,10 ;GREEN-quit checklist

25=CR(+A,24)(+A,0)A,13,K84,11 ;GREEN-VM1000  (C+S+T)

26=CP(+A,24)(-A,0)A,13,CL3:R,0 ;Voice Checklist

27=CP(+A,24)(-A,0)A,14,K75,8 ;GREEN-Kneeboard Show/Hide

28=CP(+A,24)(-A,0)A,15,K112,10 ;GREEN-Kneeboard Switch Document

29=CP(+A,24)(-A,0)A,16,K79,10 ;GREEN-Kneeboard Open Document

30=CP(+A,24)(-A,0)A,17,Cx02000C1A,x0400 ;GREEN Time 4 Speed

31=CP(+A,24)(-A,0)A,18,Cx02000C1A,x0200 ;GREEN Time 2 Speed

32=CP(+A,24)(+A,0)A,20,C65876,0 ;GREEN-kneeboard View

33=CP(+A,24)(-A,0)A,20,K86,10 ;GREEN-Wing Leveler Toggle

34=CP(+A,24)(-A,0)A,21,C65561,0 ;GREEN-pause toggle

35=CP(+A,24)(+A,0)A,21,Cx02000C1A,x0100 :GREEN Normal Time Speed

36=CP(+A,24)(-A,0)A,22,K53,9 ;GREEN-Weather Gauge

37=CP(+A,24)(+A,0)A,22,K90,9 ;GREEN-Frame Rates

 

 

I use the first CH yoke button 0 for compounds. However, in the last two days I've noticed that when I press the 0 button, it releases the parking brake as well as performing a compound command.  For example, in line 3 above, it releases the parking brake as well as going to the next view.  Just pressing the 0 button releases the parking brake.  It appears some value has been assigned to the 0 button.

 

I opened the Lancair flight and just pressed the 0 button four times with the following FSUIPC4.log:

 

  2490010 System time = 08/09/2015 12:16:42, Simulator time = 12:12:19 (19:12Z)

  2490010 FLT path = "C:\Users\Gerry\Documents\Flight Simulator X Files\"

[Continuation log requested by user]

Running inside FSX on Windows 7

Module base=16E20000

  2490010 LogOptions changed, now E0000000 0000000D

  2490010 [buttons] now profile-specific:

  2490010    11=CP(+A,24)(-A,0)A,6,C65759,0

  2490010    13=CP(+A,24)(-A,0)A,7,C65758,0

  2490010    15=CR(+A,24)(+A,0)A,8,C65607,0

  2490010    27=CP(+A,24)(-A,0)A,14,K75,8

  2490010    28=CP(+A,24)(-A,0)A,15,K112,10

  2490010    29=CP(+A,24)(-A,0)A,16,K79,10

  2494003 *** EVENT: Cntrl= 65588 (0x00010034), Param= 0 (0x00000000) BRAKES

  2494035 *** EVENT: Cntrl= 65588 (0x00010034), Param= 0 (0x00000000) BRAKES

  2494081 *** EVENT: Cntrl= 65588 (0x00010034), Param= 0 (0x00000000) BRAKES

  2498372 *** EVENT: Cntrl= 65752 (0x000100d8), Param= 0 (0x00000000) PARKING_BRAKES

  2500088 *** EVENT: Cntrl= 65588 (0x00010034), Param= 0 (0x00000000) BRAKES

  2500134 *** EVENT: Cntrl= 65588 (0x00010034), Param= 0 (0x00000000) BRAKES

  2500166 *** EVENT: Cntrl= 65588 (0x00010034), Param= 0 (0x00000000) BRAKES

  2501632 *** EVENT: Cntrl= 65752 (0x000100d8), Param= 0 (0x00000000) PARKING_BRAKES

  2502942 *** EVENT: Cntrl= 65588 (0x00010034), Param= 0 (0x00000000) BRAKES

  2502989 *** EVENT: Cntrl= 65588 (0x00010034), Param= 0 (0x00000000) BRAKES

  2503020 *** EVENT: Cntrl= 65588 (0x00010034), Param= 0 (0x00000000) BRAKES

  2504268 *** EVENT: Cntrl= 65752 (0x000100d8), Param= 0 (0x00000000) PARKING_BRAKES

  2505626 *** EVENT: Cntrl= 65588 (0x00010034), Param= 0 (0x00000000) BRAKES

  2505672 *** EVENT: Cntrl= 65588 (0x00010034), Param= 0 (0x00000000) BRAKES

  2505704 *** EVENT: Cntrl= 65588 (0x00010034), Param= 0 (0x00000000) BRAKES

  2508402 *** EVENT: Cntrl= 65752 (0x000100d8), Param= 0 (0x00000000) PARKING_BRAKES

  2509214 *** EVENT: Cntrl= 65588 (0x00010034), Param= 0 (0x00000000) BRAKES

  2509245 *** EVENT: Cntrl= 65588 (0x00010034), Param= 0 (0x00000000) BRAKES

  2509292 *** EVENT: Cntrl= 65588 (0x00010034), Param= 0 (0x00000000) BRAKES

  2513519 Sim stopped: average frame rate for last 23 secs = 25.5 fps

  2518371 LogOptions changed, now 00000000 00000001

  2730875 Sim stopped: average frame rate for last 212 secs = 20.9 fps

[Log closed by user request, and continued in new file]

  2747895 System time = 08/09/2015 12:21:00, Simulator time = 12:16:15 (19:16Z)

  2747895 *** FSUIPC log file being closed

Minimum frame rate was 14.9 fps, Maximum was 30.0 fps

Minimum available memory recorded was 32768Mb

Average frame rate for running time of 2450 secs = 27.5 fps

G3D fix: Passes 23281, Null pointers 0, Bad pointers 0, Separate instances 0

Memory managed: 1097 Allocs, 1094 Freed

********* FSUIPC Log file closed ***********

 

  FSUIPC4 has worked flawlessly for several years.  Hope you can help.

 

Regards,

Gerry

 

[Pete Dowson]

What was the previous version of FSUIPC4 you were using?

 

What do you expect to see when pressing the 0 button 4 times? I don't have enough information to understand what you think is wrong.

 

Pete

[GCNorth]

Hi Pete,

 

Basically, the problem was that a number of the buttons on the yolk were screwed up!  I solved the problem when I discovered that the button assignments in fsx had reappeared-don't know why.  I erased them and everything seems to be working well.

 

Thanks,

 

Gerry