A320wolf

Hi guys, I'm using Windows 8 Pro 64 and my Logitech G940 system (joy+throttle+pedals) works great within FSX. I install FSUIPC (latest version) and my G940 disappears after some minutes, using both default and payware aircraft. I search the net for a fix and I find a solution: you need to set the compatibility mode for FSX by select WINDOWS XP SP3. In my case the problem goes away! I'm using Windows 8 about from one week now (I need to install and test it due to my work) and I don't think it's so "bad" like someone say. I'm in doubt with the new START INTERFACE... not so good in a business environment. Bye, Max

Hi Pete, I have a problem with my FSX and I suppose it's related with FSUIPC module. I've just reinstall all my pc - so clean installation: Windows 7 Ultimate 64bit, all the drivers and FSX Gold Edition. The problem I have is with the autobrake system both with 3rd party add-ons and with default planes such as the 737-800. Both during take off and landing the autobrakes don't work (they don't engage). After many tests (with and without my Logitech G940 flight controls) I notice that if I use FSUIPC the autobrakes don't work but if I remove your module they work perfectly! I tried to set different values within joystick calibration tab in FSUIPC but without success. I've tried to disable also my joystick - so using only the keyboard - the problem persist. With FSUIPC autobrakes don't work, without it they work. I have this issue both with FSUIPC v4.60, v4.70 and the latest 4.703 Unfortunately I cannot try with version before 4.60 Let me know, please Many thanks! Regards, Massimo

Hi Pete. I press the spacebar because it's the first thing to see if the ctrl+shift is locked. Even if I don't press any keys after turn the switch or other button with the ctrl+shift+any key, this combination produces the "error" Normally when I use my switches or buttons I don't use any other keys so quickly. This is the first time I have this annoying issue but I think it's better to "re-clean" my system, install FSX and FSUIPC with any other add-ons and try with default aircraft. Then I'll let you know. Ok.... for your information I'm using Vista 64bit. Anyway don't worry Pete. I appreciate your help and support. I'll post some news in this topic as soon as my system will be reinstalled. Thanks again and Merry Christmas! Regards, Max

:roll: no... I have to forget the TAB key with this add-on Bye, Max

Good idea but unfortunately the Wilco ERJ doesn't allow the SHIFT+TAB :shock: Well.... I suppose to try a clean installation of my system even if I have installed only FSX. Now I have something to do during my holiday :? Thank for your help! Bye, Max

Ok Pete. I've recreated a new fsuipc.ini but without success. Here is the log. I turn up the goflight t8 switch (ctrl+shif+1). The nav lights switch on the virtual cockpit turn up too. Then I press the space bar on the keyboard to see if the control to move the mouse and look inside the virtual cockpit works. None! It's locked and I have to press ctrl+shift on the keyboard to unlock it. Running inside FSX on Windows Vista (SimConnect Acc/SP2 Oct07) Module base=61000000 Wind smoothing fix is fully installed 175096 System time = 22:43:05, FSX time = 12:20:33 (11:20Z) 175096 LogOptions changed, now 40000000 00000001 184113 Button changed: bRef=0, Joy=109, Btn=0, Pressed 184113 [buttons.Embraer 170 Cirrus new] 0=P109,0,K49,11 184113 SendKeyToFS(00060031=[ctl+shft+1], KEYDOWN) ctr=0 184113 Sending WM_KEYDOWN, Key=16 (Shift) (Scan code 42), Ctr=3 184113 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=3 184113 [buttons.Embraer 170 Cirrus new] 2=U109,0,K49,11 184113 JoystickValues joynum=0, dwCount=1, data[2]={0000006d 00000081} 184113 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 184113 .. Key not programmed -- passed on to FS 184113 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=3 184113 .. Key not programmed -- passed on to FS 184160 Sending WM_KEYDOWN, Key=49 (Scan code 2), Ctr=1 184690 KEYDOWN: VK=32, Waiting=0, Repeat=N, Shifts=3 184690 .. Key not programmed -- passed on to FS 185174 KEYDOWN: VK=32, Waiting=0, Repeat=Y, Shifts=3 185174 .. Key not programmed -- passed on to FS 185189 KEYDOWN: VK=32, Waiting=0, Repeat=Y, Shifts=3 185189 .. Key not programmed -- passed on to FS 185236 KEYDOWN: VK=32, Waiting=0, Repeat=Y, Shifts=3 185236 .. Key not programmed -- passed on to FS 185267 KEYDOWN: VK=32, Waiting=0, Repeat=Y, Shifts=3 185267 .. Key not programmed -- passed on to FS 185283 KEYDOWN: VK=32, Waiting=0, Repeat=Y, Shifts=3 185283 .. Key not programmed -- passed on to FS 185314 KEYDOWN: VK=32, Waiting=0, Repeat=Y, Shifts=3 185314 .. Key not programmed -- passed on to FS 185361 KEYDOWN: VK=32, Waiting=0, Repeat=Y, Shifts=3 185361 .. Key not programmed -- passed on to FS 185392 KEYDOWN: VK=32, Waiting=0, Repeat=Y, Shifts=3 185392 .. Key not programmed -- passed on to FS 185423 KEYUP: VK=32, Waiting=0 192131 LogOptions changed, now 00000000 00000001 200711 System time = 22:43:30, FSX time = 12:20:49 (11:20Z) 200711 *** FSUIPC log file being closed Average frame rate for running time of 71 secs = 56.0 fps Memory managed: 31 Allocs, 31 Freed ********* FSUIPC Log file closed *********** The "bug" happen immediately. Bye, Max

Mmm... thanks Pete. Unfortunatley no, I don't use any other add-ons in the background such as Flight Keeper or similar. In this case I'll try to reinstall all my system because I don't know what happen. I'm asking why if I press the same key combination directly on the keyboard this problem doesn't appear :roll: I'll let you know. Many thanks again for your help, Bye, Max

Hi Pete. Email sent. Thanks! Bye, Max

Simply because many of the complex add-ons for FS9 and FSX don't use the default controls. Someone give you the chance to assign keys combinations. I can say PMDG, LEVEL-D, WILCO-FEELTHERE, DIGITAL AVIATION FOKKER and so on .... In my case I'm using the Wilco ERJ170 www.wilcopub.com who comes with a key assignment control panel. I assign the CTRL+SHIFT+keys to different controls. Anyway I repeat that in FS9 the same situation works without problems. I suppose there's something wrong in FSX + FSUIPC. I'd like to know if someone else has the same issue. Thanks! Bye, Max

Hi Pete. First of all thanks for your great and quick help! Now I try with version 4.111. Ok in the example above I use GoFlight T8 (switches). I assign keys before when I turn the switch up, I have to turn my nav lights on. Then when I turn down the switch I have to turn the nav lights off. Probably it's not the correct way... let me know. In any case the same thing happen also if I assign the ctrl+shift+any keys to a button. I assign the same keys to my VMAX CLOCHE button and the I log the result. Another thing: the ctrl+shift "issue" happens with any add-ons/aircraft. Give me 10 minutes to download and try the FSUIPC 4.111 Bye, Max

Hi Pete. I start FSX with my Embraer 170 add-on, activate the fsuipc log and I move up and down two GoFlight Switches: - turn the nav lights ON and OFF ---- CTRL+SHIFT+1 - turn the beacon lights ON and OFF ---- CTRL+SHIFT+2 Here is the log: ********* FSUIPC4, Version 4.409 by Pete Dowson ********* User Name="Massimo Solimbergo" User Addr="massimo.solimbergo@dreamsky.it" FSUIPC4 Key is provided WIDEFS7 not user registered, or expired [Continuation log requested by user] Running inside FSX on Windows Vista (SimConnect Acc/SP2 Oct07) Module base=61000000 Wind smoothing fix is fully installed 118217 System time = 18:08:01, FSX time = 12:51:08 (11:51Z) 118217 LogOptions changed, now 40000000 00000001 120635 Button changed: bRef=0, Joy=109, Btn=0, Pressed 120635 [buttons.Embraer 170 Cirrus new] 29=P109,0,K49,11 120635 SendKeyToFS(00060031=[ctl+shft+1], KEYDOWN) ctr=0 120635 Sending WM_KEYDOWN, Key=16 (Shift) (Scan code 42), Ctr=3 120635 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=3 120635 [buttons.Embraer 170 Cirrus new] 41=U109,0,K49,11 120635 JoystickValues joynum=0, dwCount=1, data[2]={0000006d 00000081} 120635 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 120635 .. Key not programmed -- passed on to FS 120635 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=3 120635 .. Key not programmed -- passed on to FS 120666 Sending WM_KEYDOWN, Key=49 (Scan code 2), Ctr=1 120666 SendKeyToFS(00060031=[ctl+shft+1], KEYUP) ctr=0 120698 Sending WM_KEYUP, Key=49 (Scan code 2), Ctr=3 120698 KEYUP: VK=49, Waiting=0 120744 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=2 120744 Sending WM_KEYUP, Key=16 (Shift) (Scan code 42), Ctr=2 120744 KEYUP: VK=17, Waiting=0 120744 KEYUP: VK=16, Waiting=0 123318 Button changed: bRef=0, Joy=109, Btn=0, Released 123318 [buttons.Embraer 170 Cirrus new] 29=P109,0,K49,11 123318 [buttons.Embraer 170 Cirrus new] 41=U109,0,K49,11 123318 SendKeyToFS(00060031=[ctl+shft+1], KEYDOWN) ctr=0 123318 Sending WM_KEYDOWN, Key=16 (Shift) (Scan code 42), Ctr=3 123318 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=3 123318 JoystickValues joynum=0, dwCount=1, data[2]={0000006d 00000080} 123318 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 123318 .. Key not programmed -- passed on to FS 123318 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=3 123318 .. Key not programmed -- passed on to FS 123350 Sending WM_KEYDOWN, Key=49 (Scan code 2), Ctr=1 127187 Button changed: bRef=0, Joy=109, Btn=1, Pressed 127187 [buttons.Embraer 170 Cirrus new] 31=P109,1,K50,11 127187 SendKeyToFS(00060031=[ctl+shft+1], KEYUP) ctr=0 127187 Sending WM_KEYUP, Key=49 (Scan code 2), Ctr=1 127187 SendKeyToFS(00060032=[ctl+shft+2], KEYDOWN) ctr=2 127187 [buttons.Embraer 170 Cirrus new] 42=U109,1,K50,11 127187 JoystickValues joynum=0, dwCount=1, data[2]={0000006d 00000082} 127187 KEYUP: VK=49, Waiting=0 127218 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=5 127218 Sending WM_KEYUP, Key=16 (Shift) (Scan code 42), Ctr=5 127218 Sending WM_KEYDOWN, Key=16 (Shift) (Scan code 42), Ctr=5 127218 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=5 127218 SendKeyToFS(00060032=[ctl+shft+2], KEYUP) ctr=1 127218 KEYUP: VK=17, Waiting=0 127218 KEYUP: VK=16, Waiting=0 127218 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 127218 .. Key not programmed -- passed on to FS 127218 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=3 127218 .. Key not programmed -- passed on to FS 127250 Sending WM_KEYDOWN, Key=50 (Scan code 3), Ctr=4 127281 Sending WM_KEYUP, Key=50 (Scan code 3), Ctr=3 127281 KEYUP: VK=50, Waiting=0 127312 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=2 127312 Sending WM_KEYUP, Key=16 (Shift) (Scan code 42), Ctr=2 127312 KEYUP: VK=17, Waiting=0 127312 KEYUP: VK=16, Waiting=0 128123 Button changed: bRef=0, Joy=109, Btn=1, Released 128123 [buttons.Embraer 170 Cirrus new] 31=P109,1,K50,11 128123 [buttons.Embraer 170 Cirrus new] 42=U109,1,K50,11 128123 SendKeyToFS(00060032=[ctl+shft+2], KEYDOWN) ctr=0 128123 Sending WM_KEYDOWN, Key=16 (Shift) (Scan code 42), Ctr=3 128123 Sending WM_KEYDOWN, Key=17 (Control) (Scan code 29), Ctr=3 128123 JoystickValues joynum=0, dwCount=1, data[2]={0000006d 00000080} 128123 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 128123 .. Key not programmed -- passed on to FS 128123 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=3 128123 .. Key not programmed -- passed on to FS 128154 Sending WM_KEYDOWN, Key=50 (Scan code 3), Ctr=1 128154 SendKeyToFS(00060032=[ctl+shft+2], KEYUP) ctr=0 128186 Sending WM_KEYUP, Key=50 (Scan code 3), Ctr=3 128186 KEYUP: VK=50, Waiting=0 128217 Sending WM_KEYUP, Key=17 (Control) (Scan code 29), Ctr=2 128217 Sending WM_KEYUP, Key=16 (Shift) (Scan code 42), Ctr=2 128217 KEYUP: VK=17, Waiting=0 128217 KEYUP: VK=16, Waiting=0 134036 LogOptions changed, now 00000000 00000001 143302 System time = 18:08:26, FSX time = 12:51:23 (11:51Z) 143302 *** FSUIPC log file being closed Average frame rate for running time of 36 secs = 26.4 fps Memory managed: 19 Allocs, 19 Freed ********* FSUIPC Log file closed *********** Thanks for your help! Regards, Max

Hi Pete. Yes... I'm using 4.409. Thanks, bye, Max

Hi Pete! I've just bought FSUIPC 4 from simmarket and installed with the latest version for FSX available on this forum. I start FSX and load the Wilco ERJ170 aircraft. I have the FSUIPC4 correctly installed and registered. All menus are visible and active. I decide to use my goflight P8 module (it has 8 buttons) with this plane and so I go in the FSUIPC Buttons+Switches menu. I start to assign the keyboards shortcuts to each button. The same with my VMAX cloche buttons. Then I close FSUIPC window and try the work. With my surprise I notice a strange problem: each assignment with a CTRL+SHIFT+any keys let FSX to lock any other keyboard input. For example: I use the CTRL+SHIFT+1 assignment to turn on the NAV LIGHTS. If I use this combination directly on the keyboard FSX does it well without any problems. But if I push my button, FSUIPC send this key assignment to FSX, my NAV LIGHT turns ON but it's like the CTRL+SHIFT keys remains locked on the keyboard. I have to push CTRL+SHIFT again on the keyboard to unlock. The strange thing is that on FSUIPC menu I remove these flags: - Key press not to be held (nothing change even if I put the flag on this option) - Key press to repeat while held This issue occurs with any hardware I use (GoFlight or the simple VMAX cloche or any another cloche/throttle and so on). Any other keys combination CTRL+any keys or SHIFT+any keys works perfectly. And for your information I use FSUIPC 3.85 in FS9 in the same manner without problems. I have this "bug" with any aircraft in FSX. I hope you can understand the problem.... my English is not so good :oops: I use FSX SP2 under Windows Vista 64bit Business Edition. Thanks! Bye, Max

Hi Pete and thanks for reply. Well now I post my problem on the 747RFP forum. Anyway I try to explain "better" with my poor English :( The 747RFP has a system called FFRATS which controls the take off power (also power in climb and crz mode) setting the maximum epr value. When you set this system and you are ready to take off you should advance the hardware throttle levers to maximum (as written in the manual) and when epr value reaches 1.1 (I don't remember exactly the value) the FFRATS system is activated and it limits the maximum power to the EPR value set on the FFRATS panel. If I try to move the levers to full power as written in the manual I have my engines at max power thrust. It seems that the ffrats doesn't work. When I in flight the "traditional" a/t works and it maintains the speed selected. Now if I remove the pfc.dll and I use the default keyboard assignments (F1-F4) the FFRATS works great! :unsure: This happen also if i set the levers to idle (and I have not any disalignment or false input from them) The same problem happens when I use the Airbus A310 SSW! On this add-on all the autothrottle system doesn't work but when I remove the pfc.dll (and so disable the console) all work :roll: This happen ONLY with these two add-ons... All others work without any problem and my PFC Console is good! I'd like to know if someone else has this problem.... :oops: PS: I have a friend of mine which use the same add-on which use the MS Force FeedBack throttle and CH Cloche with the throttle lever and all work. Many thanks to all! Best regards, Max

Hi Pete! I have some problems with the pfc.dll v1.90 (I use the Precision Flight Controls Throttle quadrant) and two add-ons: SSW Airbus 310 and Ready for Pushback 747-200. The problem for these 2 add-ons is the same: the autothrottle system on the autopilot (for the SSW310) and the FFRATS (on the 747RFP) don't work! I do some tests but the only way to solve the problem is to remove the pfc.dll from FS9 and use the default F1/F4 key for the throttle. I think there's some incompatibility with the pfc.dll and these add-ons. I think it's strange that both add-ons have the problem. Can you help me? Or is there someone else who have this problem? Thanks! Regards, Max