John Fee Posted April 29, 2020 Report Share Posted April 29, 2020 I am running v. 4.974 in FSX-SE. Whn flying in the cruise the landing gear lowers itself - uncommanded by me. At exactly the same time the cockpit view switches itself to locked spot view. This happens with several different aircraft when flying on autopilot. I am completely hands off when it happens. All FSX controls have been checked umpteen times for both axes and buttons in normal and slew modes. There is nothing assigned to FSX control as far as I can see.. I use an FSUIPC axis setting for the HAT view. It works perfectly. Saitek pedals, CH Eclipse Yoke and GF-TQ6. I am at a loss to know as to what is causing this. It is very irritating although easily remedied. It seems only to happen once during a flight although I rarely fly longer than a couple of hours. I wonder if it could be time related. Whatever it is, I've not come across anything similar in 50 years of flightsimming! Regards, John Link to comment Share on other sites More sharing options...
John Fee Posted April 29, 2020 Author Report Share Posted April 29, 2020 log file: ********* FSUIPC4, Version 4.974b (14th March 2018) by Pete Dowson ********* Windows 10 Home 64 Bit reported as Build 18362, Release ID: 1903 (OS 10.0) fsx.exe version = 10.0.62615.0 Reading options from "F:\FSX_Steam\steamapps\common\FSX\Modules\FSUIPC4.ini" Running inside FSX Steam Edition on Windows 10 Module base=56CF0000 User Name="John Fee" User Addr="gooneybird@yankeedodge.com" FSUIPC4 Key is provided WideFS7 Key is provided 0 System time = 29/04/2020 12:18:42 15 ------ Module Version Check ------ 15 acontain.dll: 10.0.62615.0 15 api.dll: 10.0.62615.0 15 controls.dll: 10.0.62615.0 15 fs-traffic.dll: 10.0.62615.0 15 G3D.dll: 10.0.62615.0 422 language.dll: 10.0.62615.0 422 sim1.dll: 10.0.62615.0 422 visualfx.dll: 10.0.62615.0 422 weather.dll: 10.0.62615.0 422 window.dll: 10.0.62615.0 422 ---------------------------------- 437 Trying to connect to SimConnect Steam ... 500 FS UNC path = "\\RUDOLF\FSX\" 562 ---------------------- Joystick Device Scan ----------------------- 562 Product= Saitek Pro Flight Rudder Pedals 578 Manufacturer= Saitek 578 Vendor=06A3, Product=0763 (Version 1.1) 578 GUIDs returned for product: VID_06A3&PID_0763: 578 GUID= {DAA2C6C0-EC02-11E7-8008-444553540000} 578 Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0 578 Product= CH ECLIPSE YOKE 578 Manufacturer= S 578 Vendor=068E, Product=0051 (Version 0.0) 578 GUIDs returned for product: VID_068E&PID_0051: 578 GUID= {DAA25190-EC02-11E7-8006-444553540000} 578 Details: Btns=26, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R895,U1023,V1023,X1006,Y1023,Z1023 593 Product= GF-TQ6 Throttle System 609 Manufacturer= GoFlight 609 Vendor=09F3, Product=0200 (Version 1.0) 609 GUIDs returned for product: VID_09F3&PID_0200: 609 GUID= {DAA29FB0-EC02-11E7-8007-444553540000} 609 Details: Btns=4, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R225,U215,V219,X209,Y220,Z221 672 ------------------------------------------------------------------- 672 Device acquired for use: 672 Joystick ID = 2 (Registry okay) 672 2=Saitek Pro Flight Rudder Pedals 672 2.GUID={DAA2C6C0-EC02-11E7-8008-444553540000} 672 Device acquired for use: 672 Joystick ID = 1 (Registry okay) 672 1=CH ECLIPSE YOKE 672 1.GUID={DAA25190-EC02-11E7-8006-444553540000} 672 Device acquired for use: 672 Joystick ID = 0 (Registry okay) 672 0=GF-TQ6 Throttle System 672 0.GUID={DAA29FB0-EC02-11E7-8007-444553540000} 672 ------------------------------------------------------------------- 703 FSUIPC couldn't run: "F:\FSX-Steam\steamapps\common\Modules\FSX.bat" [Error=2] 703 LogOptions=00000000 00000001 703 ------------------------------------------------------------------- 703 ------ Setting the hooks and direct calls into the simulator ------ 703 --- CONTROLS timer memory location obtained ok 703 --- SIM1 Frictions access gained 703 --- FS Controls Table located ok 703 --- Installed Mouse Macro hooks ok. 703 --- Wind smoothing fix is fully installed 703 --- SimConnect intercept for texts and menus option is off 703 --- All links checked okay 703 ------------------------------------------------------------------- 703 SimConnect_Open succeeded: waiting to check version okay 703 Trying to use SimConnect Steam 703 Opened separate AI Traffic client okay 2468 Running in "Microsoft Flight Simulator X", Version: 10.0.62615.0 (SimConnect: 10.0.62615.0) 2468 Initialising SimConnect data requests now 2468 FSUIPC Menu entry added 2484 \\RUDOLF\FSX\flights\other\FLTSIM.FLT 2484 \\RUDOLF\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.air 6562 Weather Mode now = Theme 14297 \\RUDOLF\Users\howar\AppData\Roaming\Microsoft\FSX\Previous flight.FLT 54968 User Aircraft ID 1 supplied, now being used 54968 Aircraft loaded: running normally now ... 55265 System time = 29/04/2020 12:19:38, Simulator time = 05:32:41 (03:32Z) 55281 Aircraft="Aircreation582SL red" 163922 Starting everything now ... 167093 Advanced Weather Interface Enabled 191672 \\RUDOLF\FSX\SimObjects\Airplanes\Douglas C-47 3.1406-MVC\Douglas_DC3_v1.5.air 192281 Aircraft="Douglas C-47 Piedmont Airlines MVC" 281953 Sim stopped: average frame rate for last 89 secs = 28.1 fps 281953 Max AI traffic was 9 aircraft (Deleted 0) 1132828 Sim stopped: average frame rate for last 735 secs = 28.7 fps 1132828 Max AI traffic was 9 aircraft (Deleted 0) 1134781 === Closing session: waiting for DLLStop to be called ... 1142390 === DLLStop called ... 1142390 === Closing external processes we started ... 1143390 === About to kill any Lua plug-ins still running ... 1143562 === Closing global Lua thread 1144578 === About to kill my timers ... 1144797 === Restoring window procs ... 1144797 === Unloading libraries ... 1144797 === stopping other threads ... 1144797 === ... Button scanning ... 1144922 === ... Axis scanning ... 1145031 === Releasing joystick devices ... 1145031 === Freeing macro memory 1145031 === Removing any offset overrides 1145031 === Closing all WideFS threads 1148468 === Clearing any displays left 1148468 === NOTE: not calling SimConnect_Close ... 1148468 === AI slots deleted! 1148468 === Freeing button memory ... 1148468 === Closing my Windows ... 1148468 === Freeing FS libraries ... 1149484 === Closing devices ... 1149484 === Closing the Log ... Bye Bye! ... 1149484 System time = 29/04/2020 12:37:52, Simulator time = 05:46:48 (03:46Z) 1149484 *** FSUIPC log file being closed Minimum frame rate was 26.0 fps, Maximum was 28.9 fps Minimum available memory recorded was 2146Mb Average frame rate for running time of 846 secs = 28.7 fps Maximum AI traffic for session was 9 aircraft Memory managed: 207 Allocs, 206 Freed ********* FSUIPC Log file closed *********** Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 29, 2020 Report Share Posted April 29, 2020 2 hours ago, John Fee said: Whn flying in the cruise the landing gear lowers itself - uncommanded by me. At exactly the same time the cockpit view switches itself to locked spot view. Well evidently something is sending FSX some command, though how landing gear and views are related is a bit mysterious. Two things to try: firstyou say: 2 hours ago, John Fee said: There is nothing assigned to FSX control as far as I can see.. That really isn't good enough. If you are using FSUIPC for assignments you need to DISABLE controllers, each one (I seem to remember in FSX you had to select controllers separately). It then doesn't matter if there are any assignments, and it prevents FSX from automatically making assignments on a reload, or after a Windows update, or whenever it things there's a new or changed device connected. Second, if after you do that you still get that strange thing happening, use FSUIPC's event logging (not the axes). Best to then stop the session and close FSX immediately the events occur, then the log entries near the end will show what commands were responsible. unfortunately, though, there's no way to trace back). You could also enable button and key logging. That will make the log a lot bigger i expect, so hope that the strange events occur early in the session. With that logging you might see what is triggering it. maybe an unstable button or USB connection. Pete Link to comment Share on other sites More sharing options...
John Fee Posted April 29, 2020 Author Report Share Posted April 29, 2020 Thanks. The FSX controllers are all disabled. This time, (only the second occasion it's done this) when I landed the plane the brakes appeared to come on full without command from me. Whatever way this worked it stopped the plane dead in its tracks as if it landed on glue. Had I done this myself with differential brakes, I'd have tipped the old girl over on her nose and spoiled her day. Log attached with button/key and events log as requested. Seems some problem with toggle engine failure. John FSUIPC4.log Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 29, 2020 Report Share Posted April 29, 2020 13 minutes ago, John Fee said: Log attached with button/key and events log as requested.. There are THREE instances of the same two buttons being pressed, one of which operates "GEAR TOGGLE": #1 186797 Button changed: bRef=0, Joy=1, Btn=9, Pressed 186797 [Buttons] 1=R1,9,Cx32000BC0,x3FFF0100 186797 Repeating flag set: bRef=0, Joy=1, Btn=9 (RepeatDelayCtr=1) 186797 IPC Offsets Control: Ctrl=x3200, Length=2, Offset=0BC0, Param=x3FFF0100 186938 Button changed: bRef=0, Joy=1, Btn=9, Released 191188 Button changed: bRef=0, Joy=1, Btn=5, Pressed 191188 [Buttons] 3=P1,5,C65570,0 191188 FS Control Sent: Ctrl=65570, Param=0 191188 *** EVENT: Cntrl= 65570 (0x00010022), Param= 0 (0x00000000) GEAR_TOGGLE 191453 Button changed: bRef=0, Joy=1, Btn=5, Released#2 337109 Button changed: bRef=0, Joy=1, Btn=9, Pressed 337109 [Buttons] 1=R1,9,Cx32000BC0,x3FFF0100 337109 Repeating flag set: bRef=0, Joy=1, Btn=9 (RepeatDelayCtr=1) 337109 IPC Offsets Control: Ctrl=x3200, Length=2, Offset=0BC0, Param=x3FFF0100 337141 Button changed: bRef=0, Joy=1, Btn=9, Released 353234 Button changed: bRef=0, Joy=1, Btn=5, Pressed 353234 [Buttons] 3=P1,5,C65570,0 353234 FS Control Sent: Ctrl=65570, Param=0 353234 *** EVENT: Cntrl= 65570 (0x00010022), Param= 0 (0x00000000) GEAR_TOGGLE 353328 Button changed: bRef=0, Joy=1, Btn=5, Released #3 497797 Button changed: bRef=0, Joy=1, Btn=9, Pressed 497797 [Buttons] 1=R1,9,Cx32000BC0,x3FFF0100 497797 Repeating flag set: bRef=0, Joy=1, Btn=9 (RepeatDelayCtr=1) 497797 IPC Offsets Control: Ctrl=x3200, Length=2, Offset=0BC0, Param=x3FFF0100 497969 Button held, flags=X05, repeat set: bRef=0, Joy=1, Btn=9, (RepeatOk sets 2) 498250 [Buttons] 1=R1,9,Cx32000BC0,x3FFF0100 498250 Repeating flag set: bRef=0, Joy=1, Btn=9 (RepeatDelayCtr=11) 498250 IPC Offsets Control: Ctrl=x3200, Length=2, Offset=0BC0, Param=x3FFF0100 498250 Button changed: bRef=0, Joy=1, Btn=9, Released 558125 Button changed: bRef=0, Joy=1, Btn=5, Pressed 558125 [Buttons] 3=P1,5,C65570,0 558125 FS Control Sent: Ctrl=65570, Param=0 558125 *** EVENT: Cntrl= 65570 (0x00010022), Param= 0 (0x00000000) GEAR_TOGGLE 558266 Button changed: bRef=0, Joy=1, Btn=5, Released This one: 1=R1,9,Cx32000BC0,x3FFF0100 is "Offset SWord Increment", with 0BC0 which is the Elevator Trim control. (Why are you assigning a button for this instead of using the normal Fs control for trim? Is it that you want a bigger or smaller effect?). That wouldn't be so odd if it wasn't that it is always associated with this button being used: 3=P1,5,C65570,0 which is your Gear operation. Could your device (joy = 1) be playing up and sending button presses by itself? Can happen when they get faulty. Or maybe the Gear assignmnet button fires incidentally when you usae the trim button -- but didn't you say it happens hands off? Don't know about your brakes. There's no brake use in the log at all after the start where you toggle Parking brake and "Antiskid brakes" which is somethnig i don't know.. You do have these at the end: 1377656 *** EVENT: Cntrl= 66313 (0x00010309), Param= 0 (0x00000000) TOGGLE_ENGINE1_FAILURE 1377656 *** EVENT: Cntrl= 66314 (0x0001030a), Param= 0 (0x00000000) TOGGLE_ENGINE2_FAILURE but no FSUIPC assigned button or key press did that. Pete 1 Link to comment Share on other sites More sharing options...
John Fee Posted April 29, 2020 Author Report Share Posted April 29, 2020 Hmm. How interesting! The Gear Down/Up action was unrelated to my use of the elevator trim buttons on the yoke. Yes, it can happen hands off. I began to use the Offset SWord setting because it gave me finer iterations with some plane which I flew in the distant past, probably in FS2002. I just kept using that way of setting up trim with each new simulator that came along. I never had trouble with it. It just worked fine, so why change? I have changed now and it'll be interesting to see if using the normal FS control via FSUIPC will solve the problem. The antiskid brakes thing is a total mystery. Even if I wanted to I have no idea how to set that up. I couldn't find a switch or lever for cockpit activation. I'll run that particular problem past the C-47/DC3 chaps. Some test flying to do before I report back. Thanks again. John Link to comment Share on other sites More sharing options...
John Fee Posted April 29, 2020 Author Report Share Posted April 29, 2020 This time, she did it all - uncommanded Spot view, Gear Down, Brakes set whilst on autopilot, totally hands off. . Log attached. Regards, John FSUIPC4.log Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 29, 2020 Report Share Posted April 29, 2020 3 hours ago, John Fee said: This time, she did it all - uncommanded Spot view, Gear Down, Brakes set whilst on autopilot, totally hands off. . Log attached. You could try looking at these Logs yourself. I can point out where "GEAR TOGGLE" is used. I just search on GEAR. you can do the same. I'll do this just this once more, then I think yo should check for yourself. Here's the first instance. I include a lot because you can see from this that ONE button press (Joy 1 button 5) instigates the GEAR TOGGLE, but there's then a whole lot of other stuff that is most certainly NOT instigated by actions in FSUIPC: 518375 Button changed: bRef=0, Joy=1, Btn=5, Pressed 518375 [Buttons] 3=P1,5,C65570,0 518375 FS Control Sent: Ctrl=65570, Param=0 518375 *** EVENT: Cntrl= 65570 (0x00010022), Param= 0 (0x00000000) GEAR_TOGGLE 518516 Button changed: bRef=0, Joy=1, Btn=5, Released 556453 *** EVENT: Cntrl= 65793 (0x00010101), Param= 1 (0x00000001) YAW_DAMPER_TOGGLE 560203 *** EVENT: Cntrl= 66416 (0x00010370), Param= 90 (0x0000005a) PAN_VIEW 560250 *** EVENT: Cntrl= 66416 (0x00010370), Param= 90 (0x0000005a) PAN_VIEW 560281 *** EVENT: Cntrl= 66416 (0x00010370), Param= -1 (0xffffffff) PAN_VIEW 562859 *** EVENT: Cntrl= 65580 (0x0001002c), Param= 0 (0x00000000) AP_MASTER 563719 *** EVENT: Cntrl= 65798 (0x00010106), Param= 0 (0x00000000) AP_PANEL_HEADING_HOLD 564875 *** EVENT: Cntrl= 65799 (0x00010107), Param= 0 (0x00000000) AP_PANEL_ALTITUDE_HOLD 585484 *** EVENT: Cntrl= 65729 (0x000100c1), Param= 0 (0x00000000) AP_NAV1_HOLD 590594 *** EVENT: Cntrl= 66375 (0x00010347), Param= 0 (0x00000000) TOGGLE_GPS_DRIVES_NAV1 627562 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW 627594 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW 627625 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW 627672 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW 627703 *** EVENT: Cntrl= 66416 (0x00010370), Param= 180 (0x000000b4) PAN_VIEW 627734 *** EVENT: Cntrl= 66416 (0x00010370), Param= -1 (0xffffffff) PAN_VIEW 631500 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC 631531 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC 631609 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC 631641 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC 632125 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC 632156 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC 632187 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC 632234 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC 632750 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC 632750 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC 632812 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC 633578 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC 633656 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC 634375 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC 634453 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC 641391 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW 641422 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW 641453 *** EVENT: Cntrl= 66416 (0x00010370), Param= 0 (0x00000000) PAN_VIEW 641500 *** EVENT: Cntrl= 66416 (0x00010370), Param= -1 (0xffffffff) PAN_VIEW The second seems better. there aree other actions around it seemingly mostly to do with other button and key presses. 1697078 Button changed: bRef=0, Joy=1, Btn=5, Pressed 1697078 [Buttons] 3=P1,5,C65570,0 1697078 FS Control Sent: Ctrl=65570, Param=0 1697078 Button changed: bRef=0, Joy=1, Btn=24, Released .... 1697078 *** EVENT: Cntrl= 65570 (0x00010022), Param= 0 (0x00000000) GEAR_TOGGLE And that was it. I assume the first is the instance which concerns you. You have some add-on which is doing these things you don't like. Whether it's to do with the aircraft, or you have some other add-ons, or perhaps some plug-ins, i don't know. but I think you need to carry out a process of elimiination of those, because it isn't FSUIPC. Attach you FSUIPC.INI file and I'll check that you've not got any rogue assignments. Pete Link to comment Share on other sites More sharing options...
John Fee Posted April 30, 2020 Author Report Share Posted April 30, 2020 Thanks, Pete. FSUIPC.ini attached. I agree that it could be caused by an addon. I have very few of these as FSX-SE has been newly installed on its own HDD on this PC. It could be hardware too, of course. It could be Steam related too I suppose. I have FSX boxed on a separate drive, so I can test the yoke, throttle quad, and rudder pedals in that sim. Regards, John FSUIPC4.ini Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 30, 2020 Report Share Posted April 30, 2020 9 minutes ago, John Fee said: FSUIPC.ini attached. I agree that it could be caused by an addon. I have very few of these as FSX-SE has been newly installed on its own HDD on this PC. It could be hardware too, of course. It could be Steam related too I suppose. Well there's nothing complicated in the INI. It's very simple and straightforward. But in the Logs you have shown the GEAR TOGGLE has always been instigated by a button press -- button 5 on joystick 1 (your yoke). There are no un-requested operation of the GEAR. The odd thing in the log is the other actions which seem to accompany some instances of that occurring, as in the last case: 556453 *** EVENT: Cntrl= 65793 (0x00010101), Param= 1 (0x00000001) YAW_DAMPER_TOGGLE 562859 *** EVENT: Cntrl= 65580 (0x0001002c), Param= 0 (0x00000000) AP_MASTER 563719 *** EVENT: Cntrl= 65798 (0x00010106), Param= 0 (0x00000000) AP_PANEL_HEADING_HOLD 564875 *** EVENT: Cntrl= 65799 (0x00010107), Param= 0 (0x00000000) AP_PANEL_ALTITUDE_HOLD 585484 *** EVENT: Cntrl= 65729 (0x000100c1), Param= 0 (0x00000000) AP_NAV1_HOLD 590594 *** EVENT: Cntrl= 66375 (0x00010347), Param= 0 (0x00000000) TOGGLE_GPS_DRIVES_NAV1 Now none of those actions are commanded by anything in FSUIPC. It looks like either the aircraft you are using does all that (maybe as a service to you, like an "easy" mode where it tries to help), or you have some sort of co-pilot program also running which decides to do all that for you. I'd check through whatever add-on (or add-in) programs you have running. AND try a different aircraft. I'm afraid I can't really see any more I can do to help. It just isn't being caused by FSUIPC. Pete Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now