John Fee

Thanks again. It's the Aeroworx King Air. I'm not sure I understand your last two sentences. I run FS9. In FS9 'S' is 'Views (cycle)'. I have used this assignment for button 2 for close on ten years without problems. I do not get an AP disconnect when I use button 2 on any other plane, be it default, Level D 767, or one of many other addons. When I open FSUIPC the number 24 is in the Btn# box. I think it ought not to be there. I cannot remove it except by un-checking the checked boxes. Then it reverts to 0. However, if I return to the opening panel to make some other adjustment, the 24 is always back. I do not know if this is relevant. Thanks for your help.

Events included this time, my mistake. ********* FSUIPC, Version 3.999z9a by Pete Dowson ********* Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL) User Name="John Fee" User Addr="gooneybird@yankeedodge.com" FSUIPC Key is provided WideFS Key is provided [Continuation log requested by user] Module base=61000000 WeatherReadInterval=4 LogOptions=00000001 4729358 System time = 09/09/2014 16:25:25, FS2004 time = 15:07:43 (19:07Z) 4729405 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4729405 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4729405 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4729405 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4729405 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4729405 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4729405 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4729405 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4729405 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4729405 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4729405 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4729405 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4729405 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4729405 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4729405 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4729405 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4729405 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4729405 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4729529 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4729576 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4729607 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4729701 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4729732 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4729779 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4729810 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4729888 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4729935 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4730013 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4730091 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4730138 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4730185 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4730216 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4730263 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4730341 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4730372 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4730419 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4730543 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4730575 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4730621 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4730668 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4730746 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4730777 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4730824 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4730855 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4730949 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4731027 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4731058 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4731136 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4731183 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4731230 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4731261 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4731339 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4731386 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4731433 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4731542 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4731589 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4731620 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4731667 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4731713 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4731791 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4731823 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4731869 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4731947 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4731994 Button changed: bRef=0, Joy=2, Btn=0, Pressed 4731994 [Buttons] 11=P2,0,K83,8 4731994 SendKeyToFS(00000053=[S], KEYDOWN) ctr=0 4731994 Sending WM_KEYDOWN, Key=83 (Scan code 31), Ctr=1 4731994 KEYDOWN: VK=83, Waiting=0, Repeat=N, Shifts=0 4731994 .. Key not programmed -- passed on to FS 4731994 *** EVENT: Cntrl= 65567 (0x0001001f), Param= 0 (0x00000000) VIEW_MODE 4732103 *** EVENT: Cntrl= 66104 (0x00010238), Param= 0 (0x00000000) AP_PANEL_ALTITUDE_OFF 4732103 *** EVENT: Cntrl= 65816 (0x00010118), Param= 0 (0x00000000) AP_ALT_HOLD_OFF 4732103 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 0 (0x00000000) AP_BC_HOLD_OFF 4732103 *** EVENT: Cntrl= 65814 (0x00010116), Param= 0 (0x00000000) AP_APR_HOLD_OFF 4732103 *** EVENT: Cntrl= 65815 (0x00010117), Param= 0 (0x00000000) AP_HDG_HOLD_OFF 4732103 *** EVENT: Cntrl= 65819 (0x0001011b), Param= 0 (0x00000000) AP_NAV1_HOLD_OFF 4732103 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 0 (0x00000000) AP_BC_HOLD_OFF 4732103 *** EVENT: Cntrl= 65791 (0x000100ff), Param= 0 (0x00000000) AUTOPILOT_OFF 4732103 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4732135 SendKeyToFS(00000053=[S], KEYUP) ctr=0 4732135 Sending WM_KEYUP, Key=83 (Scan code 31), Ctr=1 4732135 Button changed: bRef=0, Joy=2, Btn=0, Released 4732135 [Buttons] 11=P2,0,K83,8 4732135 KEYUP: VK=83, Waiting=0 4732181 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4732213 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4732306 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4732337 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4732384 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4732415 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4732540 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4732587 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4732618 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4732696 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4732743 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4732790 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4732821 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4732868 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4732946 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4733024 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4733071 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4733149 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4733180 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4733227 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4733273 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4733351 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4733383 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4733429 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4733554 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4733585 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4733632 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4733663 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4733741 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4733788 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4733835 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4733866 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4733944 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4733991 Button changed: bRef=0, Joy=2, Btn=0, Pressed 4733991 [Buttons] 11=P2,0,K83,8 4733991 SendKeyToFS(00000053=[S], KEYDOWN) ctr=0 4733991 Sending WM_KEYDOWN, Key=83 (Scan code 31), Ctr=1 4733991 KEYDOWN: VK=83, Waiting=0, Repeat=N, Shifts=0 4733991 .. Key not programmed -- passed on to FS 4733991 *** EVENT: Cntrl= 65567 (0x0001001f), Param= 0 (0x00000000) VIEW_MODE 4734038 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4734085 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4734116 SendKeyToFS(00000053=[S], KEYUP) ctr=0 4734116 Sending WM_KEYUP, Key=83 (Scan code 31), Ctr=1 4734116 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4734116 KEYUP: VK=83, Waiting=0 4734194 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4734241 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4734241 Button changed: bRef=0, Joy=2, Btn=0, Released 4734241 [Buttons] 11=P2,0,K83,8 4734272 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4734319 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4734397 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4734443 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4734521 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4734599 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4734646 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4734677 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4734724 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4734755 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4734755 Button changed: bRef=0, Joy=2, Btn=0, Pressed 4734755 [Buttons] 11=P2,0,K83,8 4734755 SendKeyToFS(00000053=[S], KEYDOWN) ctr=0 4734755 Sending WM_KEYDOWN, Key=83 (Scan code 31), Ctr=1 4734755 KEYDOWN: VK=83, Waiting=0, Repeat=N, Shifts=0 4734755 .. Key not programmed -- passed on to FS 4734755 *** EVENT: Cntrl= 65567 (0x0001001f), Param= 0 (0x00000000) VIEW_MODE 4734802 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4734896 SendKeyToFS(00000053=[S], KEYUP) ctr=0 4734896 Sending WM_KEYUP, Key=83 (Scan code 31), Ctr=1 4734896 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4734896 KEYUP: VK=83, Waiting=0 4734927 Button changed: bRef=0, Joy=2, Btn=0, Released 4734927 [Buttons] 11=P2,0,K83,8 4734927 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4735005 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4735083 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4735130 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4735177 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4735208 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4735255 Button changed: bRef=0, Joy=2, Btn=0, Pressed 4735255 [Buttons] 11=P2,0,K83,8 4735255 SendKeyToFS(00000053=[S], KEYDOWN) ctr=0 4735255 Sending WM_KEYDOWN, Key=83 (Scan code 31), Ctr=1 4735255 KEYDOWN: VK=83, Waiting=0, Repeat=N, Shifts=0 4735255 .. Key not programmed -- passed on to FS 4735255 *** EVENT: Cntrl= 65567 (0x0001001f), Param= 0 (0x00000000) VIEW_MODE 4735364 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4735395 SendKeyToFS(00000053=[S], KEYUP) ctr=0 4735395 Sending WM_KEYUP, Key=83 (Scan code 31), Ctr=1 4735395 Button changed: bRef=0, Joy=2, Btn=0, Released 4735395 [Buttons] 11=P2,0,K83,8 4735395 KEYUP: VK=83, Waiting=0 4735442 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4735520 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4735567 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4735645 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4735676 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF 4735723 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 1 (0x00000001) AP_BC_HOLD_OFF

Thank you, Pete. The same thing happens with the FS keyboard command (S). I've checked for duplicate assignments several times and could find none. I've attached a log file and would be grateful if you could take a look at it. Regards, John FSUIPC_joy2.txt

I run FS9 in W7x64. I have button 2 on CH Eclipse mapped to Views/cycle using FSUIPC v.3.999z9a. In cockpit view when I click this button (taking me into Virtual Cockpit or Spot views) the Collins AP Power switches off. As can be seen, the Collins, unusually for most FS9 autopilots, has separate Power ON/OFF switches and AP engage/disengage switches. I am not sure how to separate commands for View/Cycle and Power ON/OFF with this particular autopilot using FSUIPC and would be grateful for advice. BTW, I cannot Power ON the Collins again until I return to Cockpit View. Thanking you. John

In my system I have made two small amendments for FS9.1. To get virtual radar altitudes showing in the Sky Demon Navigation Page (i.e. the 'in flight' page), set this in GPSOut.ini: [GPSout] Sentences=RMC,PGRMZ,GGA,GSA Remember that altitudes will not show in the Navigation page until the aeroplane is moving. The default settings for sentences are sufficient in my FSX system. I have also set Speed=19200 in the GPSOut.ini, and in the /GPS Navigation options I have set baud=19200.

I have managed to link FS9.1 with SkyDemon using the GPSOut program. I run W7 x64. SkyDemon is a real world VFR flightplanner and moving map display with extensive European, US, Australia/NZ coverage. Being designed for real world navigation with Garmin receivers it is regularly updated. It is not cheap but can be used both in the aeroplane and in a simulator under the same licence. http://www.skydemon.aero/ My method: 1. Install SkyDemon and run the program. Install maps. Exit the program. 2. Create a pair of virtual serial ports using Eltima software - there is a free trial period. I tried other software including the MixW program included in the GPSOut.zip without success. The Eltima program involved 4 clicks and worked first time. Download the VSP driver to a temp folder. 3. Run the downloaded Eltima virtual serial port driver - vspd.exe. Select two pairs of COM ports - I chose COM8 and COM9. Click 'Add pair.' 4. Run FS9.1 and create a test flight using the MS flightplanner i.e. a GPS flight. Make sure this shows in the GPS as a purple track. 5. Open SkyDemon. Under SetUp/Device Connectivity Options, check 'I have a Garmin handheld device'. Set port to COM8 (the first of the pair in your VSP setup). Do not change anything else. 6. Still under Setup, go to /GPS Navigation options in the drop down menu. Set port to COM9 (the second of the pair in your VSP setup). I left the other options at default values. 7. Close SkyDemon and FS9.1. 8. Install GPSOut 2.61 - available for download from http://www.schiratti.com/dowson.html - follow install instructions carefully. 9. Open GPSOut.ini and scroll down to Port. Set this to Port=8 or whatever was the first of your pair of virtual ports. Save. 10. Run FS9.1 and open at the departure airport for your test flight. 11. Open SkyDemon and click on 'Start GPS' top right. I've tested this GPSOut program with the default GPS and the RealityXP GNS500 units. Not surprisingly they both work although the default unit lacks many RNAV funtions including the LPV function. For the benefit of less experienced users, if you are running Windows 7 you can avoid trouble by installing all programs on the root folder e.g. C:\SkyDemon. It is usually best to avoid using the C:\Program Files or C:\Program Files (x86) folder. Also, in W7 best to run all programs as administrator (right click). I do not know about Windows 8. Thanks for another gem, Pete. I've looked at this GPSOut for many years wondering.... [Addendum by Pete: thanks for posting your solution. I should also add that registered users of FSUIPC4 can also do this with FSX or P3D using the GPSout facility built in]

[EDIT by Pete: moved from original thread in support forum so it is retained for others to benefit] Sky Demon is a real world VFR flightplanner which creates a moving map display using GPS data. In FSX it is relatively easy to set this up using a virtual serial port and OpusFSX (primarily an FSX weather program). The RealityXP GNX500 together with OpusFSX provide the GPSOut data for Sky Demon. I would like to use Sky Demon with FS9 but am not sure how to proceed. From the FSUIPC Advanced Guide it seems that FSUIPC GPSOut is designed for VRInsight devices via WideFS. I run a multi-monitor system with Sky Demon and FS9 on the same PC. So I need to send GPS data from the PC via VSP to Sky Demon. In the first instance I will use the default GPS rather than Reality XP GNX500. I'd welcome your views on the feasilbility of this, and if feasible, the best way of setting it up. Thanks and regards, John

Never mind. I got it sorted. John

Pete I run the old Digital Aviation Fokker 70/100 in FSX/Win7 x64. Panel changes (i.e. overhead, pedestal, radios etc) are effected by clickspots - ten in all - narrow bars at the top, side, or bottom of each panel. They are a pain in the bum. Panels can also be changed in the usual way using SHIFT+1 etc key-presses but with so many different panels I soon forget which number does what. Is it possible to assign simicons to the key-presses in the panel.cfg? I can easily delete the clickspots with FSPanel Studio. Or can the keypresses be re-assigned to the numeric part of the keyboard? Perhaps I need one of them new fangly gadgets. Best regards John

I quote your guide: 'The 256 is the increment and 16383 is the limit. This will give 128 steps between -16383 and 16383 inclusive (32768/256 = 128)....' The word 'steps' is how I got the wrong idea. I understand now that my interpretation was incorrect. John

Thanks. Am using x0BC0 as per the Advanced Users guide. I thought by reducing the number of increments/decrements this would make matters worse - dividing the same range into fewer, and thus larger, segments. Worth a try. I don't want to reduce button scanning rate if that's going to affect rotary buttons as well. Thanks again for prompt support. Hope all well with you. John

I'm using 'Offset SWord Increment/Decrement' to control elevator trim buttons on a yoke in both FSX and FS9 (Windows 7 x64). In the parameter box I set 256/16383 for increment and 256/-16383 for decrement. I allow the control to repeat when the (trim) buttons are held. My problem is that the resulting trim control is very fierce - it is as though the button was controlling the elevator directly and not just trim tabs. I don't know the correct word for it but I suspect the 'frequency' of signals sent by the button is very fast and that this gives an exaggerated effect. Could this be so? If it could be, is there a way of adjusting the rate at which the button sends its signals when held? Thanks. John

Thanks, Pete, This was exactly the information I needed. I hadn't tried offsets before - scared off by the terminology. I now have the most balanced trim function I've ever had in half a lifetime of using FSUIPC. I traced the original problem though. In the photo Button 24 points up at the green LED. This button is permanently active and in some way had become set to keypress 'Home'. This resulted in continuous trim inputs. I removed the key/button assignment - I hope permanently. I would like to disable this button but am not sure how. Just one thing, Pete, I've not set these trim offsets to be 'profile specific'. Does that mean that these settings are active for any plane unless over-ridden by a 'profile specific' setting? I wasnt' sure exactly what the User Guide meant. John PS I set up the same trim offsets in FSX :)

Pete I'm using FSUIPC 3.999w 12 Aug 2012 and FS2004. For longer than I care to remember I've been using FSUIPC button assignments to control elevator trim via a rocker switch on a CH Eclipse yoke. This worked very nicely until recently after I deliberately deleted FSUIPC ini. I've got everything back the way it was except for elevator trim up/down. Under Buttons and Switches, I assign 'Home' key for trim down, and 'End' key for trim up, but this produces erratic responses to the rocker switch. I have tried this with 'key press to be repeated when held', and not; and I have tried it with 'profile specific' checked, and not. I ended up re-enabling FS9 joystick and reverted to FS control. The upside is that I can now use the FS 'Hat' control. EDIT: This failed after a re-start and I was back to square one. I was getting full trim up or trim down no matter what I did. Is there something about elevator trims (they are axes after all) which makes them tricky to set up using FSUIPC keypress assignments? Or have I, as is often the case, missed something obvious? Thanks as always for your continuing development of FSUIPC. I've been following the FSX friction discussions with interest. John

Many thanks, Pete. Spot on as usual :) . John

Pete I'm running FSX with FSUIPC 4.839b in W7 x64. Forgive me if I missed this in the docs, but what parameters should I set for Traffic Zapall and Traffic Zapper in the Key Presses dialogue? I wish to be able to remove AI planes that are in my way on short finals, and also when they are about to taxi through me on the ground. So, a narrow beam with a range of 1-2 miles extending around 800ft QNH would seem about right. Having said that, your default values for most things in FSX usually fit the bill. I know I should not mix topics but I read a lot now on these boards about Lua. Is this a language the inquisitive but poorly informed sim pilot should learn? Best regards John

Problem solved. It was a livery problem. The JU52 profile was for one repaint only. I was doing my checking with a different repaint loaded. I'm not sure why this second repaint chose to be a DC-3 and not something else though. Thanks for help, Pete. As I suspected, I missed something obvious. Regards John

No joy, it is still doing it. It is convinced it's a DC3. FS9 is installed in the root directory for that very reason. All very odd, I admit.

No, I never tweak settings with FS running. I saved the .ini and rebooted each time. Will do.

Hmm...not so simple. I already tried removing the profile name from under DC-3. What happens is that when I then attempt to assign the JU52 profile it again shows as DC-3. [Profile.Junkers 52] 1=Junkers 52/3m D-ASIS 2=AC520 Pegasus [JoystickCalibration.Junkers 52] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No MapThr12to123=Yes FlapsSetControl=0 FlapDetents=No ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=0 RudderTrimControl=0 CowlFlaps1Control=0 CowlFlaps2Control=0 CowlFlaps3Control=0 CowlFlaps4Control=0 MaxSteerSpeed=60 Rudder=-16190,-1355,1408,16192 Throttle=-16209,16383 PropPitch=-16380,16380 Mixture=-16380,16380 LeftBrake=-15104,16384/16 SlopeLeftBrake=5 RightBrake=-14848,16384/16 SlopeRightBrake=5 Throttle1=-15877,-9290,-5067,16216 Throttle2=-15694,-10003,-4829,16042 PropPitch1=-16035,-9760,-5926,16039 PropPitch2=-16384,-10082,-7382,16383 Spoilers=-16209,16211/16 Flaps=-16201,16383/16 Reverser=-16380,16380 [Profile.DC3] 1=Douglas DC-3 BEA 2=Junkers 52/3m G-AHOF //this line reappears under DC3 when I check profile specific and select Junkers 52 Presumably I am missing something obvious.

I'm running version 3.999 in FS9. I set up a triple engined JU52 as a profile. When I load the JU52 and check the FSUIPC settings it shows as DC-3. Obviously, the same profile will not work for these two aircraft. I would do a fresh set up of the JU52 but I cannot uncheck the 'profile specific' box (greyed out). I guess I need to amend the .ini file but what to do exactly? Thanks. John

I tried it, Ed, but it didn't work. Since #21 I have mapped both my FSX (W7) and FS9 (XP) drives to my client. This has speeded up access. Also, WideFS opens automatically when connecting to FSX and FS9. I'm not sure why it does this but I like it :) John

Pete Joy! :grin: After much head-scratching and experimentation I eventually decided to take a look at the client PC registry. I should have done that sooner because the ASE paths to FSX and FS9 were in a mess. I fixed these, but still no joy.... Changed port from 500 to 4506 (supposedly unused) - success at last! Also, I had to rewrite the paths in the dll.xml to get the tools showing as you said. Nope. But I gotta admit this darned Simconnect thing very nearly had me beat. MS made a very big mistake when they passed you up, Pete. Thanks again for your help and encouragement. John

Ok. Just one last question. When you run FSX how many tools show in your Tools menu? I have only the OPT. I read somewhere that there are 3 in-game tools, OPT, Effects, and another. Regards John