SIMFAN Posted February 4, 2009 Report Posted February 4, 2009 Hi Pete, I have an X52Pro controller, the throttle only of which is inoperative when FSX controller is de-activated and I attempt to operate in FSUIPC4 mode (version 4.26 - registered) only. I have assigned and calibrated the controller in FSUIPC4 and the joystick axes and buttons and throttle buttons and axes all operate perfectly, however the throttle axis will not operate. The throttle axis works just fine when the FSX controller is activated, but only then. The throttle axis appears to be assigned and calibrated ok and reacts to throttle movement on the calibration screen, but has no effect on any aircraft controls. I would be grateful for your assistance. Bill
Pete Dowson Posted February 4, 2009 Report Posted February 4, 2009 I attempt to operate in FSUIPC4 mode (version 4.26 ... Please, before asking for support, always try the current supported version, as noted in the Announcements here. 4.26 is far too old for me to even think about dealing with. 4.40 is the earliest supported version, and it would be worth your while trying the latest increment, 4.427, from the Updates Announcement above -- but be sure to install 4.40 first, please! Once you've done that, then, if you still get the same problem: The throttle axis works just fine when the FSX controller is activated, but only then.The throttle axis appears to be assigned and calibrated ok and reacts to throttle movement on the calibration screen, but has no effect on any aircraft controls. ... I will need more information please. 1. Is this with all aircraft, or a specific add-on aircraft? If an add-on, please test with a default one. 2. When you say calibration screen, you do mean the FSUIPC4 one, yes? 3. Which page of the calibrations are you using -- the single throttle bottom right on the first page (with the aileron, elevator and rudder)? Or the one with the 4 throttle controls on? 4. How have you assigned the throttle in FSUIPC --to an FS control (which one?) or direct to FSUIPC calibration (which one?)? 5. What other options have you set? Maybe the quickest way for me to see what you've done is for you to show me the [Axes] and [JoystickCalibration] sections of your FSUIPC4.INI file, please (in the FSX Modules folder). One other thing to do, to elicit more information, is to enable Axis logging (only) in the FSUIPC4 logging tab, operate the throttle in flight mode, then check the FSUIPC4.LOG file -- show me it. Regards Pete
SIMFAN Posted February 6, 2009 Author Report Posted February 6, 2009 Hi Pete, Thanks for the quick response. I appologise for the delay in getting you requested information; no earlier opportunity. Answers to queries: 1. Problem occurs with all aircraft, however I have done requested retesting with FSUIPC4.427 with the Bell 206 default helicopter. 2. FSUIPC4 calibration screen used. 3. Used single bottom right on the first page. 4. Assigned throttle to FSUIPC direct - Throttle/Slew Alt. 5. Not sure what you mean by 'other options', but all joystick and throttle axes, buttons and rotaries are set to various other options. Pete, I have tried to attach the throttle log and calibration details as a .txt and also a .doc fle, however I get the message that neither extension is allowed. As this is the first time for me on this forum I hope you won't mind instructing me as to how I can get this info. to attach to my replies. Thanks and regards, Bill
Pete Dowson Posted February 6, 2009 Report Posted February 6, 2009 1. Problem occurs with all aircraft, however I have done requested retesting with FSUIPC4.427 with the Bell 206 default helicopter. Best to test with a normal aircraft first, please -- helicopter throttles are different. I need to know explicitly whether you see the throttle lever on the aircraft throttle quadrant moving. Pete, I have tried to attach the throttle log and calibration details as a .txt and also a .doc fle, however I get the message that neither extension is allowed. As this is the first time for me on this forum I hope you won't mind instructing me as to how I can get this info. to attach to my replies. I'd rather they weren't attached (if you do attach, ZIP them in any case). For ordinary text files, if not too big, you can paste them into your message here. If you mark the inserts as "List" (see the button above?) the formatting will be retained. If the files are huge (they shouldn't be if you keep the test short and to the point) then I'll give you an email address to send them to (but still ZIPped). Please don't send or post anything will you are using the updated FSUIPC. Regards Pete
SIMFAN Posted February 7, 2009 Author Report Posted February 7, 2009 Hi Pete, I have re-tested using the default FSX 'Extra' aircraft, with axes assigned direct to FSUIPC4.427 There was no movement of the throttle lever when the control was exercised. Mixture and prop. pitch both showed normal movement ( they are they other two rotaries on the X52Pro throttle lever) Logs etc. requested follow below. Regards, Bill ********* FSUIPC4, Version 4.428 by Pete Dowson *********Reading options from "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.ini"NOTE: SimConnect Acc/SP2 Oct07 is supported, but it isn't installed.User Name="William Kingwell"User Addr="vpile@bigpond.net.au"FSUIPC4 Key is providedWIDEFS7 not user registered, or expiredRunning inside FSX (SimConnect SP1 May07)Module base=61000000Wind smoothing fix is fully installedDebugStatus=15 266 System time = 14:48:06 266 FLT UNC path = "C:\Documents and Settings\BKingwell.VIBROPILE\My Documents\Flight Simulator X Files\" 266 FS UNC path = "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\" 2125 LogOptions=00000000 00000001 2125 SimConnect_Open succeeded: waiting to check version okay 16125 Running in "Microsoft Flight Simulator X", Version: 10.0.61355.0 (SimConnect: 10.0.61242.0) 16125 Initialising SimConnect data requests now 16125 FSUIPC Menu entry added 16281 c:\documents and settings\bkingwell.vibropile\my documents\flight simulator x files\Cross country YMMB-YSWH-YMMB.FLT 16281 C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\C172\Cessna172SP.AIR 62203 C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Extra300\Extra300S.AIR 172266 System time = 14:50:58, FSX time = 14:48:24 (05:48Z) 173109 Aircraft="Extra 300S Paint1" 174516 Advanced Weather Interface Enabled 181953 PFC Menu entry added 207531 Sim stopped: average frame rate for last 25 secs = 14.5 fps 224828 LogOptions changed, now 10000000 00000001 225453 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 7568 (0x00001d90) AXIS_PROPELLER_SET 225453 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 7584 (0x00001da0) AXIS_MIXTURE_SET 225484 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 3514 (0x00000dba) AXIS_PROPELLER_SET 225484 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 3416 (0x00000d58) AXIS_MIXTURE_SET 225656 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 1650 (0x00000672) AXIS_PROPELLER_SET 225656 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 1500 (0x000005dc) AXIS_MIXTURE_SET 225734 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 792 (0x00000318) AXIS_PROPELLER_SET 225734 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 618 (0x0000026a) AXIS_MIXTURE_SET 225781 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 398 (0x0000018e) AXIS_PROPELLER_SET 225781 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 212 (0x000000d4) AXIS_MIXTURE_SET 225938 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 9100 (0x0000238c) AXIS_PROPELLER_SET 225938 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 9088 (0x00002380) AXIS_MIXTURE_SET 225984 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 13104 (0x00003330) AXIS_PROPELLER_SET 225984 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 13170 (0x00003372) AXIS_MIXTURE_SET 226031 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 14944 (0x00003a60) AXIS_PROPELLER_SET 226031 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 15046 (0x00003ac6) AXIS_MIXTURE_SET 226109 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 15790 (0x00003dae) AXIS_PROPELLER_SET 226109 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 15910 (0x00003e26) AXIS_MIXTURE_SET 226156 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16180 (0x00003f34) AXIS_PROPELLER_SET 226156 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 16308 (0x00003fb4) AXIS_MIXTURE_SET 226422 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16358 (0x00003fe6) AXIS_PROPELLER_SET 226422 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 16384 (0x00004000) AXIS_MIXTURE_SET 226469 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16384 (0x00004000) AXIS_PROPELLER_SET 230938 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 15054 (0x00003ace) AXIS_PROPELLER_SET 231063 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 10982 (0x00002ae6) AXIS_PROPELLER_SET 231172 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 9110 (0x00002396) AXIS_PROPELLER_SET 231250 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 4224 (0x00001080) AXIS_PROPELLER_SET 231391 *** AXIS: Cntrl= 66291 (0x000102f3), Param= -702 (0xfffffd42) AXIS_PROPELLER_SET 231453 *** AXIS: Cntrl= 66291 (0x000102f3), Param= -2968 (0xfffff468) AXIS_PROPELLER_SET 231547 *** AXIS: Cntrl= 66291 (0x000102f3), Param= -8452 (0xffffdefc) AXIS_PROPELLER_SET 231578 *** AXIS: Cntrl= 66291 (0x000102f3), Param= -10974 (0xffffd522) AXIS_PROPELLER_SET 231672 *** AXIS: Cntrl= 66291 (0x000102f3), Param= -13896 (0xffffc9b8) AXIS_PROPELLER_SET 231719 *** AXIS: Cntrl= 66291 (0x000102f3), Param= -15240 (0xffffc478) AXIS_PROPELLER_SET 231813 *** AXIS: Cntrl= 66291 (0x000102f3), Param= -15858 (0xffffc20e) AXIS_PROPELLER_SET 231875 *** AXIS: Cntrl= 66291 (0x000102f3), Param= -16144 (0xffffc0f0) AXIS_PROPELLER_SET 231938 *** AXIS: Cntrl= 66291 (0x000102f3), Param= -16274 (0xffffc06e) AXIS_PROPELLER_SET 232000 *** AXIS: Cntrl= 66291 (0x000102f3), Param= -16334 (0xffffc032) AXIS_PROPELLER_SET 232078 *** AXIS: Cntrl= 66291 (0x000102f3), Param= -16362 (0xffffc016) AXIS_PROPELLER_SET 232141 *** AXIS: Cntrl= 66291 (0x000102f3), Param= -15528 (0xffffc358) AXIS_PROPELLER_SET 232203 *** AXIS: Cntrl= 66291 (0x000102f3), Param= -15144 (0xffffc4d8) AXIS_PROPELLER_SET 232469 *** AXIS: Cntrl= 66291 (0x000102f3), Param= -8552 (0xffffde98) AXIS_PROPELLER_SET 232516 *** AXIS: Cntrl= 66291 (0x000102f3), Param= -5520 (0xffffea70) AXIS_PROPELLER_SET 232609 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 618 (0x0000026a) AXIS_PROPELLER_SET 232641 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 3442 (0x00000d72) AXIS_PROPELLER_SET 232734 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 9044 (0x00002354) AXIS_PROPELLER_SET 232766 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 11620 (0x00002d64) AXIS_PROPELLER_SET 232828 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 14260 (0x000037b4) AXIS_PROPELLER_SET 232891 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 15476 (0x00003c74) AXIS_PROPELLER_SET 232953 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16034 (0x00003ea2) AXIS_PROPELLER_SET 233203 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16292 (0x00003fa4) AXIS_PROPELLER_SET 233313 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16384 (0x00004000) AXIS_PROPELLER_SET 234516 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 13408 (0x00003460) AXIS_MIXTURE_SET 234563 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 11920 (0x00002e90) AXIS_MIXTURE_SET 234609 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 8718 (0x0000220e) AXIS_MIXTURE_SET 234719 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 7246 (0x00001c4e) AXIS_MIXTURE_SET 234813 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 2410 (0x0000096a) AXIS_MIXTURE_SET 234859 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 188 (0x000000bc) AXIS_MIXTURE_SET 234938 *** AXIS: Cntrl= 66292 (0x000102f4), Param= -4728 (0xffffed88) AXIS_MIXTURE_SET 235078 *** AXIS: Cntrl= 66292 (0x000102f4), Param= -10954 (0xffffd536) AXIS_MIXTURE_SET 235125 *** AXIS: Cntrl= 66292 (0x000102f4), Param= -13816 (0xffffca08) AXIS_MIXTURE_SET 235266 *** AXIS: Cntrl= 66292 (0x000102f4), Param= -15486 (0xffffc382) AXIS_MIXTURE_SET 235313 *** AXIS: Cntrl= 66292 (0x000102f4), Param= -16254 (0xffffc082) AXIS_MIXTURE_SET 235359 *** AXIS: Cntrl= 66292 (0x000102f4), Param= -16384 (0xffffc000) AXIS_MIXTURE_SET 235672 *** AXIS: Cntrl= 66292 (0x000102f4), Param= -11940 (0xffffd15c) AXIS_MIXTURE_SET 235734 *** AXIS: Cntrl= 66292 (0x000102f4), Param= -9670 (0xffffda3a) AXIS_MIXTURE_SET 235797 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 2098 (0x00000832) AXIS_MIXTURE_SET 235859 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 7510 (0x00001d56) AXIS_MIXTURE_SET 235938 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 9998 (0x0000270e) AXIS_MIXTURE_SET 236000 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 13588 (0x00003514) AXIS_MIXTURE_SET 236063 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 15240 (0x00003b88) AXIS_MIXTURE_SET 236125 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 15998 (0x00003e7e) AXIS_MIXTURE_SET 236203 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 16348 (0x00003fdc) AXIS_MIXTURE_SET 236344 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 16384 (0x00004000) AXIS_MIXTURE_SET 246203 LogOptions changed, now 00000000 00000001[JoystickCalibration]ExcludeThrottleSet=YesExcludeMixtureSet=YesExcludePropPitchSet=YesSepRevsJetsOnly=NoApplyHeloTrim=NoFlapsSetControl=0FlapDetents=NoReverserControl=66292Reverser1Control=66422Reverser2Control=66425Reverser3Control=66428Reverser4Control=66431MaxThrottleForReverser=256AileronTrimControl=66731RudderTrimControl=66732CowlFlaps1Control=66162CowlFlaps2Control=66163CowlFlaps3Control=66164CowlFlaps4Control=66165SteeringTillerControl=0MaxSteerSpeed=60LeftBrake=-16380,16380/24RightBrake=-16380,16380/24Throttle1=-16127,-15360,-15360,15871/8Aileron=-16383,0,0,16383/8Elevator=-16383,0,0,16383/8Rudder=-16380,-257,256,16380/8PropPitch=-16383,16256/8Mixture=-15871,16127/24Throttle2=-8447,-8447,-8447,16127/8Mixture1=-16127,-16127,-16127,16127/8PropPitch1=-16127,-16127,-16127,16127/8PropPitch2=-15359,-15359,-15359,15871/8Mixture2=-16127,-16127,-16127,15871/8SlewAlt=-16384,-9622,8960,16383SlewSide=-16384,-512,512,16383SlewAhead=-16384,-512,512,16383SlewHeading=-16319,-1217,1397,16383Throttle=-16380,16380/24SlopeAileron=3SlopeElevator=3SlopeRudder=3[Axes]0=0X,256,D,45,0,0,01=0Y,256,D,46,0,0,02=0Z,260,D,48,0,0,03=0U,256,D,6,0,0,04=0V,256,D,5,0,0,05=1X,256,D,7,0,0,06=1Y,256,D,8,0,0,07=1R,256,D,47,0,0,0[Axes.Extra 300S Paint1]0=0X,256,D,45,0,0,01=0Y,256,D,46,0,0,02=0Z,260,D,48,0,0,03=0U,256,D,6,0,0,04=0V,256,D,5,0,0,05=1X,256,D,7,0,0,06=1Y,256,D,8,0,0,07=1R,256,D,47,0,0,08=16Y,512,D,2,0,0,0
Pete Dowson Posted February 7, 2009 Report Posted February 7, 2009 I have re-tested using the default FSX 'Extra' aircraft, with axes assigned direct to FSUIPC4.427 There was no movement of the throttle lever when the control was exercised. Mixture and prop. pitch both showed normal movement ( they are they other two rotaries on the X52Pro throttle lever) Logs etc. requested follow below. Aha! The crucial information! The main thing I note which is probably different from most folks is the assignment to the Throttle/Slew combination, not the usual throttles. I'll check that now. Incidentally, I also note two things: 1. You aren't calibrating a reverse zone on any of the throttle/mix/pitch axes, but you are doing this by simply calibrating a zero reverse zone. You'd find it easier to simply set the option for no reverse zone which is added on the multiple engine pages in the recent updates for FSUIPC4, including the one you are using. 2. You appear to be checking the "filter" option on all of the axes in the calibration section. Why? Are you experiencing jitter? Filtering has disadvantages as well as advantages -- it slows the response, sometimes quite noticeably. Best not to use it blindly, only if needed. I'll get back about the como Throttle/Slew axis, later ... Regards Pete
Pete Dowson Posted February 7, 2009 Report Posted February 7, 2009 I'll get back about the como Throttle/Slew axis, later ... Well, using your settings EXACTLY (merely changing the joystick numbers to match mine, I cannot make it go wrong. Works fine. Question: you HAVE disabled the joystick with the throttle on it in FSX itself, haven't you? If not, then the reason it could be failing is that your are Reversing the throttle lever in FSUIPC4 (presumably your lever is mounted backwards?) and I suspect the two values from the two sources are cancelling each other out quite well! If you assign in FSUIPC you MUST be sure not to also assign in FS, unless you realy want some unpredictable behavious. Looking in more detail at the parameters in your file, these lines: Throttle1=-16127,-15360,-15360,15871/8Throttle2=-8447,-8447,-8447,16127/8 Mixture1=-16127,-16127,-16127,16127/8 PropPitch1=-16127,-16127,-16127,16127/8 PropPitch2=-15359,-15359,-15359,15871/8 Mixture2=-16127,-16127,-16127,15871/8 show that you are calibrating two separate throttles, mixtures and levers in the other pages, as well as using the single all-engine values, yet you made no assignments to the separate ones! I would be concerned about what that might be doing to the path taken by the axis values, it already being rather circuitous because of the filtering. I would advise you to go through the Calibration pages and "Reset" all those places which are shoing as calibrated (ie have the Reset button on the left) which are not in fact being assigned in FSUIPC. Or just delete all the above lines before loading FSX. One lesser thing, in your Extras-specific assignments: [Axes.Extra 300S Paint1]0=0X,256,D,45,0,0,0 1=0Y,256,D,46,0,0,0 2=0Z,260,D,48,0,0,0 3=0U,256,D,6,0,0,0 4=0V,256,D,5,0,0,0 5=1X,256,D,7,0,0,0 6=1Y,256,D,8,0,0,0 7=1R,256,D,47,0,0,0 8=16Y,512,D,2,0,0,0 You appear to have a spurious extra assignment to the elevator, from an axis "16Y". There is something happening in FSUIPC4 which does seem to occasional spot an axis on non-existent joystick #16, I am still looking for the reason***. But you shouldn't assign to it, and certainly not an axis already being used. Let me know how you get on after checking these things and having a tidy up. Regards Pete *** P.S. Just found the reason for odd Joystick 16,17 or 18 axes appearing. It'll be fixed in the next update. ;-)
SIMFAN Posted February 8, 2009 Author Report Posted February 8, 2009 Hi Pete, I've made all the setting alterations and double checked that FSX controller is de-activated. Un-checking 'filter' speeded things up noticeably (thanks for all the tips). Unfortunately the throttle problem stll persists and I've run another test and have attached the new log and .INI settings below. I have included the 'General' settings as well this time on the offchance that you might notice something amiss there. The No. 16 joystick issue was actually caused by my PFC yoke which I had also assigned to elevator control in FSUIPC4 at some stage and forgotten about it. That is now un-assigned and no longer shows up. I should have mentioned earlier that I run a PFC "Cirrus" yoke and throttle quadrant in conjunction with the Saitek joystick. Is there a problem with doing this? I seem to recall that FSUIPC4 assigned controls will overide other controls not assigned in FSUIPC4. Regards, Bill ********* FSUIPC4, Version 4.428 by Pete Dowson *********Reading options from "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.ini"NOTE: SimConnect Acc/SP2 Oct07 is supported, but it isn't installed.User Name="William Kingwell"User Addr="vpile@bigpond.net.au"FSUIPC4 Key is providedWIDEFS7 not user registered, or expiredRunning inside FSX (SimConnect SP1 May07)Module base=61000000Wind smoothing fix is fully installedDebugStatus=15 156 System time = 14:13:07 156 FLT UNC path = "C:\Documents and Settings\BKingwell.VIBROPILE\My Documents\Flight Simulator X Files\" 156 FS UNC path = "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\" 1984 LogOptions=00000000 00000001 1984 SimConnect_Open succeeded: waiting to check version okay 6328 Running in "Microsoft Flight Simulator X", Version: 10.0.61355.0 (SimConnect: 10.0.61242.0) 6328 Initialising SimConnect data requests now 6328 FSUIPC Menu entry added 6484 c:\documents and settings\bkingwell.vibropile\my documents\flight simulator x files\Cross country YMMB-YSWH-YMMB.FLT 6484 C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\C172\Cessna172SP.AIR 20515 C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Extra300\Extra300S.AIR 68672 System time = 14:14:15, FSX time = 14:13:15 (05:13Z) 69500 Aircraft="Extra 300S Paint1" 70953 Advanced Weather Interface Enabled 78406 PFC Menu entry added 185656 Sim stopped: average frame rate for last 107 secs = 23.3 fps 233968 LogOptions changed, now 10000000 00000001 234375 *** AXIS: Cntrl= 66292 (0x000102f4), Param= -132 (0xffffff7c) AXIS_MIXTURE_SET 234375 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 62 (0x0000003e) AXIS_PROPELLER_SET 237078 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 16384 (0x00004000) AXIS_MIXTURE_SET 237078 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 10986 (0x00002aea) AXIS_PROPELLER_SET 237265 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 5974 (0x00001756) AXIS_PROPELLER_SET 237703 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 12270 (0x00002fee) AXIS_PROPELLER_SET 237859 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16384 (0x00004000) AXIS_PROPELLER_SET 239547 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 14914 (0x00003a42) AXIS_MIXTURE_SET 239703 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 11186 (0x00002bb2) AXIS_MIXTURE_SET 239906 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 8524 (0x0000214c) AXIS_MIXTURE_SET 240125 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 5060 (0x000013c4) AXIS_MIXTURE_SET 240297 *** AXIS: Cntrl= 66292 (0x000102f4), Param= -1574 (0xfffff9da) AXIS_MIXTURE_SET 240484 *** AXIS: Cntrl= 66292 (0x000102f4), Param= -1050 (0xfffffbe6) AXIS_MIXTURE_SET 240672 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 12252 (0x00002fdc) AXIS_MIXTURE_SET 240828 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 16384 (0x00004000) AXIS_MIXTURE_SET 256015 LogOptions changed, now 00000000 00000001[General]History=QZBT5QGOHOKT1JDPPJCX1TCASid=FlightTCASrange=40AxisCalibration=NoDirectAxesToCalibs=NoShowMultilineWindow=YesSuppressSingleline=NoSuppressMultilineFS=NoAxisIntercepts=NoWeatherReadFactor=2WeatherRewriteSeconds=1SimConnectStallTime=1MouseWheelTrim=NoFixControlAccel=NoVisibilityOptions=NoOneCloudLayer=NoCloudTurbulence=NoCloudIcing=NoGenerateCirrus=NoSuppressCloudTurbulence=NoMaxIce=3MinIce=-1UpperWindGusts=NoSuppressWindTurbulence=NoSuppressWindVariance=NoWindTurbulence=NoTurbulenceRate=1.0,5.0TurbulenceDivisor=20,20,40,40SuppressAllGusts=NoMaxSurfaceWind=0WindLimitLevel=200WindDiscardLevel=400WindAjustAltitude=NoWindAjustAltitudeBy=2000WindSmoothing=NoWindSmoothness=2WindSmoothAirborneOnly=YesPressureSmoothness=0TemperatureSmoothness=0DisconnTrimForAP=NoZeroElevForAPAlt=NoThrottleSyncAll=NoWhiteMessages=NoShowPMcontrols=NoSpoilerIncrement=512MagicBattery=NoRudderSpikeRemoval=NoElevatorSpikeRemoval=NoAileronSpikeRemoval=NoReversedElevatorTrim=NoClockSync=NoClockSyncMins=5ClearWeatherDynamics=NoOwnWeatherChanges=NoTimeForSelect=4LoadFlightMenu=NoLoadPlanMenu=NoPauseAfterCrash=NoZapSound=fireworkShortAircraftNameOk=NoMouseWheelTrimSpeed=1FixMachSpeedBug=NoSaveDataWithFlights=NoCustomWeatherModify=NoConsole=NoUseProfiles=No[Axes]0=0X,256,D,45,0,0,01=0Y,256,D,46,0,0,02=0Z,260,D,48,0,0,03=0U,256,D,6,0,0,04=0V,256,D,5,0,0,05=1X,256,D,7,0,0,06=1Y,256,D,8,0,0,07=1R,256,D,47,0,0,0[Axes.Extra 300S Paint1]0=0X,256,D,45,0,0,01=0Y,256,D,46,0,0,02=0Z,260,D,48,0,0,03=0U,256,D,6,0,0,04=0V,256,D,5,0,0,05=1X,256,D,7,0,0,06=1Y,256,D,8,0,0,07=1R,256,D,47,0,0,0
Pete Dowson Posted February 8, 2009 Report Posted February 8, 2009 I've made all the setting alterations and double checked that FSX controller is de-activated. Un-checking 'filter' speeded things up noticeably (thanks for all the tips). Unfortunately the throttle problem stll persists Hmm. That's weird -- you say you can see the throttle axis operating in both the Axis assignments and in the calibrations? It shouldn't have an effect, but just in case, check in the FSX Control Assignments settings that none of the sensitivity sliders are below maximum and none of the null zone sliders above minimum. I should have mentioned earlier that I run a PFC "Cirrus" yoke and throttle quadrant in conjunction with the Saitek joystick. Is there a problem with doing this? Probably, if the PFC driver is also trying to drive the same throttle. Have you disabled the throttle action in the PFC driver? You shouldn't have separate sources for the same controls. That's akin to letting FSX operate the controls at the same time as FSUIPC. The only way to have both FSUIPC and PFC axes working is to disable the axes in the PFC driver and assign those, too, in FSUIPC4. Then for multiple throttles it will arbitrate (using the max setting), or you can make the axis assignments Aircraft or Profile-specific, so loading different aircraft automatically switches to different controls. I seem to recall that FSUIPC4 assigned controls will overide other controls not assigned in FSUIPC4. No, no way. It can't do that. The only types of assignments which FSUIPC can intercept and take over are the Keyboard ones -- a keypress assigned in FSUIPC takes it away from FS. However, even if the PFC driver settings are a problem, what's really puzzling is that your log shows no Throttle axis actions at all. I don't understand that. Note that you omitted to show the Calibration section of the INI file this time, so I couldn't check that. I don't need the [General] section at all. In case it is specific to the actual axis on the device, could you try a test where you assign one of the currently working axes as the throttle and vice versa? Regards Pete
SIMFAN Posted February 9, 2009 Author Report Posted February 9, 2009 Hi Pete, I confirm that the sensitivity and null zone sliders are all set maximum and minimum respectively. I have also disabled the PFC Throttle quadrant and totally disconected 4 to the previous prop pitch axis and the prop pitch to the previous throttle axis. The outcome is that I still don't have the new throttle axis moving the throttle lever although, as before, when the new throttle is operated, the values change in both the assignment and calibration pages. Anyway, I have run a new test and attach the log and .INI sections requested. (sorry I accidentally omitted the calibration section last time). Regards, Bill ********* FSUIPC4, Version 4.428 by Pete Dowson *********Reading options from "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.ini"NOTE: SimConnect Acc/SP2 Oct07 is supported, but it isn't installed.User Name="William Kingwell"User Addr="vpile@bigpond.net.au"FSUIPC4 Key is providedWIDEFS7 not user registered, or expiredRunning inside FSX (SimConnect SP1 May07)Module base=61000000Wind smoothing fix is fully installedDebugStatus=15 453 System time = 20:38:30 453 FLT UNC path = "C:\Documents and Settings\BKingwell.VIBROPILE\My Documents\Flight Simulator X Files\" 453 FS UNC path = "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\" 2375 LogOptions=00000000 00000001 2375 SimConnect_Open succeeded: waiting to check version okay 20422 Running in "Microsoft Flight Simulator X", Version: 10.0.61355.0 (SimConnect: 10.0.61242.0) 20422 Initialising SimConnect data requests now 20422 FSUIPC Menu entry added 20625 c:\documents and settings\bkingwell.vibropile\my documents\flight simulator x files\Cross country YMMB-YSWH-YMMB.FLT 20625 C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\C172\Cessna172SP.AIR 294125 C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Extra300\Extra300S.AIR 435781 System time = 20:45:45, FSX time = 20:38:51 (11:38Z) 436609 Aircraft="Extra 300S Paint1" 438172 Advanced Weather Interface Enabled 444703 PFC Menu entry added 528172 Sim stopped: average frame rate for last 33 secs = 15.4 fps 882125 Sim stopped: average frame rate for last 20 secs = 14.5 fps 1515844 Sim stopped: average frame rate for last 28 secs = 14.7 fps 2350031 Sim stopped: average frame rate for last 725 secs = 23.1 fps 3646250 Sim stopped: average frame rate for last 144 secs = 23.3 fps 3682516 LogOptions changed, now 10000000 00000001 3683016 *** AXIS: Cntrl= 66291 (0x000102f3), Param= -16384 (0xffffc000) AXIS_PROPELLER_SET 3686609 *** AXIS: Cntrl= 66291 (0x000102f3), Param= -14044 (0xffffc924) AXIS_PROPELLER_SET 3686781 *** AXIS: Cntrl= 66291 (0x000102f3), Param= -7802 (0xffffe186) AXIS_PROPELLER_SET 3686922 *** AXIS: Cntrl= 66291 (0x000102f3), Param= -1690 (0xfffff966) AXIS_PROPELLER_SET 3687094 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 5376 (0x00001500) AXIS_PROPELLER_SET 3687234 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 10752 (0x00002a00) AXIS_PROPELLER_SET 3687406 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 15872 (0x00003e00) AXIS_PROPELLER_SET 3687563 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16384 (0x00004000) AXIS_PROPELLER_SET 3687875 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 14208 (0x00003780) AXIS_PROPELLER_SET 3688047 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 7168 (0x00001c00) AXIS_PROPELLER_SET 3688219 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 384 (0x00000180) AXIS_PROPELLER_SET 3688375 *** AXIS: Cntrl= 66291 (0x000102f3), Param= -7152 (0xffffe410) AXIS_PROPELLER_SET 3688516 *** AXIS: Cntrl= 66291 (0x000102f3), Param= -11182 (0xffffd452) AXIS_PROPELLER_SET 3688703 *** AXIS: Cntrl= 66291 (0x000102f3), Param= -14044 (0xffffc924) AXIS_PROPELLER_SET 3688875 *** AXIS: Cntrl= 66291 (0x000102f3), Param= -16384 (0xffffc000) AXIS_PROPELLER_SET 3699094 LogOptions changed, now 00000000 00000001 3985672 Sim stopped: average frame rate for last 286 secs = 23.5 fps[JoystickCalibration]ExcludeThrottleSet=YesExcludeMixtureSet=YesExcludePropPitchSet=YesSepRevsJetsOnly=NoApplyHeloTrim=NoFlapsSetControl=0FlapDetents=NoReverserControl=66292Reverser1Control=66422Reverser2Control=66425Reverser3Control=66428Reverser4Control=66431MaxThrottleForReverser=256AileronTrimControl=66731RudderTrimControl=66732CowlFlaps1Control=66162CowlFlaps2Control=66163CowlFlaps3Control=66164CowlFlaps4Control=66165SteeringTillerControl=0MaxSteerSpeed=60LeftBrake=-16380,16380/16RightBrake=-16380,16380/16Aileron=-16383,0,0,16383Elevator=-16383,0,0,16383Rudder=-16380,-257,256,16380PropPitch=-16383,16256Mixture=-15871,16127/16SlewAlt=-16384,-9622,8960,16383SlewSide=-16384,-512,512,16383SlewAhead=-16384,-512,512,16383SlewHeading=-16319,-1217,1397,16383Throttle=-16380,16380SlopeAileron=3SlopeElevator=3SlopeRudder=3[Axes]0=0X,256,D,45,0,0,01=0Y,256,D,46,0,0,02=0Z,260,D,48,0,0,03=0U,256,D,6,0,0,04=0V,256,D,5,0,0,05=1X,256,D,7,0,0,06=1Y,256,D,8,0,0,07=1R,256,D,47,0,0,0[Axes.Extra 300S Paint1]0=0X,256,D,45,0,0,01=0Y,256,D,46,0,0,02=0Z,260,D,5,0,0,03=0U,256,D,6,0,0,04=0V,256,D,48,0,0,05=1X,256,D,7,0,0,06=1Y,256,D,8,0,0,07=1R,256,D,47,0,0,0
Pete Dowson Posted February 9, 2009 Report Posted February 9, 2009 The outcome is that I still don't have the new throttle axis moving the throttle lever although, as before, when the new throttle is operated, the values change in both the assignment and calibration pages. It is really perplexing then. Did you try, as I asked, using one of the other axes as a throttle, just to eliminate some sort of odd behaviour with that one axis. In other words, one of the axes which work with the mixture or prop pitch control? Also, can you move the throttle via other means -- dragging with the mouse on the throttle quadrant, or using the 9 & 3 keys on the number pad? Anyway, I have run a new test and attach the log and .INI sections requested. (sorry I accidentally omitted the calibration section last time). I notice you always have the Cessna loading as default then change over to the Extra for the test. Could you test with the default loaded Cessna please? 20625 C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\C172\Cessna172SP.AIR <<<<<<<<================ 294125 C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Extra300\Extra300S.AIR I'm trying to simplify things down to the least possibly variation. The log also shows only the Prop axis being moved from one extreme to the other and back. Did you move it, or were you moving what you thought was the throttle? If you are testing the Prop Axis here, why, and why not also the Mixture axis? Finally, I think you should delete this aircraft-specific section from the INI as it is doing nothing different from the generic one and will only complicate the issue: [Axes.Extra 300S Paint1]0=0X,256,D,45,0,0,01=0Y,256,D,46,0,0,02=0Z,260,D,5,0,0,03=0U,256,D,6,0,0,04=0V,256,D,48,0,0,05=1X,256,D,7,0,0,06=1Y,256,D,8,0,0,07=1R,256,D,47,0,0,0 Regards Pete
SIMFAN Posted February 10, 2009 Author Report Posted February 10, 2009 Hi Pete, My last post was incomplete owing I believe to my inexperience in editing on this forum. I had explained that I had swapped axes for the throttle and prop pitch and taken a log. I only operated these two controls and for brevity sake not the mixture control. This time I have used the default Cessna as requested but have interchanged the throttle and mixture axes as the Cessna is fixed pitch. The result is still no throttle response when operating the control, however I can as always, drag the throttle control using the mouse. By the way, I had prior to obtaining FSUIPC4, been profiling the joystick using Saitek's Smart Technology. New info. follows. Regards, Bill ********* FSUIPC4, Version 4.428 by Pete Dowson *********Reading options from "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.ini"NOTE: SimConnect Acc/SP2 Oct07 is supported, but it isn't installed.User Name="William Kingwell"User Addr="vpile@bigpond.net.au"FSUIPC4 Key is providedWIDEFS7 not user registered, or expiredRunning inside FSX (SimConnect SP1 May07)Module base=61000000Wind smoothing fix is fully installedDebugStatus=15 453 System time = 17:38:58 453 FLT UNC path = "C:\Documents and Settings\BKingwell.VIBROPILE\My Documents\Flight Simulator X Files\" 453 FS UNC path = "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\" 2359 LogOptions=00000000 00000001 2359 SimConnect_Open succeeded: waiting to check version okay 26640 Running in "Microsoft Flight Simulator X", Version: 10.0.61355.0 (SimConnect: 10.0.61242.0) 26640 Initialising SimConnect data requests now 26640 FSUIPC Menu entry added 26812 c:\documents and settings\bkingwell.vibropile\my documents\flight simulator x files\C172 G1000 -KSEA default.FLT 26812 C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\C172\Cessna172SP.AIR 2055656 System time = 18:13:14, FSX time = 17:39:26 (01:39Z) 2056468 Aircraft="Cessna Skyhawk 172SP G1000" 2057656 Advanced Weather Interface Enabled 2064515 PFC Menu entry added 2143484 Sim stopped: average frame rate for last 24 secs = 13.8 fps 2574468 Sim stopped: average frame rate for last 34 secs = 13.0 fps 2670171 Sim stopped: average frame rate for last 87 secs = 13.5 fps 3012484 Sim stopped: average frame rate for last 33 secs = 13.3 fps 3102265 Sim stopped: average frame rate for last 80 secs = 12.7 fps 3121218 LogOptions changed, now 10000000 00000001 3121765 *** AXIS: Cntrl= 66292 (0x000102f4), Param= -132 (0xffffff7c) AXIS_MIXTURE_SET 3124609 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 15980 (0x00003e6c) AXIS_MIXTURE_SET 3124750 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 15048 (0x00003ac8) AXIS_MIXTURE_SET 3124953 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 12652 (0x0000316c) AXIS_MIXTURE_SET 3125093 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 7458 (0x00001d22) AXIS_MIXTURE_SET 3125296 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 2398 (0x0000095e) AXIS_MIXTURE_SET 3125500 *** AXIS: Cntrl= 66292 (0x000102f4), Param= -3934 (0xfffff0a2) AXIS_MIXTURE_SET 3125703 *** AXIS: Cntrl= 66292 (0x000102f4), Param= -9570 (0xffffda9e) AXIS_MIXTURE_SET 3125906 *** AXIS: Cntrl= 66292 (0x000102f4), Param= -11012 (0xffffd4fc) AXIS_MIXTURE_SET 3126109 *** AXIS: Cntrl= 66292 (0x000102f4), Param= -15600 (0xffffc310) AXIS_MIXTURE_SET 3126296 *** AXIS: Cntrl= 66292 (0x000102f4), Param= -16384 (0xffffc000) AXIS_MIXTURE_SET 3126781 *** AXIS: Cntrl= 66292 (0x000102f4), Param= -15338 (0xffffc416) AXIS_MIXTURE_SET 3126984 *** AXIS: Cntrl= 66292 (0x000102f4), Param= -12454 (0xffffcf5a) AXIS_MIXTURE_SET 3127187 *** AXIS: Cntrl= 66292 (0x000102f4), Param= -7472 (0xffffe2d0) AXIS_MIXTURE_SET 3127406 *** AXIS: Cntrl= 66292 (0x000102f4), Param= -2360 (0xfffff6c8) AXIS_MIXTURE_SET 3127609 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 3596 (0x00000e0c) AXIS_MIXTURE_SET 3127750 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 8524 (0x0000214c) AXIS_MIXTURE_SET 3127953 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 10654 (0x0000299e) AXIS_MIXTURE_SET 3128109 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 12652 (0x0000316c) AXIS_MIXTURE_SET 3128312 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 16112 (0x00003ef0) AXIS_MIXTURE_SET 3128515 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 16384 (0x00004000) AXIS_MIXTURE_SET 3146515 LogOptions changed, now 00000000 00000001[JoystickCalibration]ExcludeThrottleSet=YesExcludeMixtureSet=YesExcludePropPitchSet=YesSepRevsJetsOnly=NoApplyHeloTrim=NoFlapsSetControl=0FlapDetents=NoReverserControl=66292Reverser1Control=66422Reverser2Control=66425Reverser3Control=66428Reverser4Control=66431MaxThrottleForReverser=256AileronTrimControl=66731RudderTrimControl=66732CowlFlaps1Control=66162CowlFlaps2Control=66163CowlFlaps3Control=66164CowlFlaps4Control=66165SteeringTillerControl=0MaxSteerSpeed=60LeftBrake=-16380,16380/16RightBrake=-16380,16380/16Aileron=-16383,0,0,16383Elevator=-16383,0,0,16383Rudder=-16380,-257,256,16380PropPitch=-16383,16256Mixture=-15871,16127/16SlewAlt=-16384,-9622,8960,16383SlewSide=-16384,-512,512,16383SlewAhead=-16384,-512,512,16383SlewHeading=-16319,-1217,1397,16383Throttle=-16380,16380SlopeAileron=3SlopeElevator=3SlopeRudder=3[Axes]0=0X,256,D,45,0,0,01=0Y,256,D,46,0,0,02=0Z,260,D,6,0,0,03=0V,256,D,48,0,0,04=1X,256,D,7,0,0,05=1Y,256,D,8,0,0,06=1R,256,D,47,0,0,0
Pete Dowson Posted February 10, 2009 Report Posted February 10, 2009 This time I have used the default Cessna as requested but have interchanged the throttle and mixture axes as the Cessna is fixed pitch.The result is still no throttle response when operating the control, however I can as always, drag the throttle control using the mouse. Well, this has got me truly puzzled. The throttle is not treated, inside FSUIPC, any different than any of those other axes. It is just a different number being sent to FS. The code path is the same, Everything else is the same. The values are just interchangeable. Furthermore, with exactly the same settings as you I get good results, so there's nothing hidden in the parameters you have which is doing this. There's just one other facility which can stop FSUIPC sending the results of an axis to FS -- a facility which can be operated by an FSUIPC client application to disconnect the axis. It is used for third party Airbus-style fly-by-wire and auto-throttle actions, for instance So, do you have any other add-ons running or installed? Can you list them, please? Go to FSUIPC's "Logging" page, and on the Right-Hand side, in the Offset column top row enter 310A, and select U16 as the type and check the "Hex" option. Below, check "Normal Log". OK out of there. Then I think it best to close down FSX and start it again, so I can see the log from the beginning. Just run it as far as you can see no throttle response. Close FSX, show me the resulting Log. Thanks, Pete
SIMFAN Posted February 10, 2009 Author Report Posted February 10, 2009 Hi Pete, Not sure if I understand the type of add-ons you refer to, but I do have for instance Wilco's 737 PIC. Have attached the requested log below. Regards, Bill ********* FSUIPC4, Version 4.428 by Pete Dowson *********Reading options from "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.ini"NOTE: SimConnect Acc/SP2 Oct07 is supported, but it isn't installed.User Name="William Kingwell"User Addr="vpile@bigpond.net.au"FSUIPC4 Key is providedWIDEFS7 not user registered, or expiredRunning inside FSX (SimConnect SP1 May07)Module base=61000000Wind smoothing fix is fully installedDebugStatus=15 328 System time = 22:37:42 328 FLT UNC path = "C:\Documents and Settings\BKingwell.VIBROPILE\My Documents\Flight Simulator X Files\" 328 FS UNC path = "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\" 2188 LogOptions=00000000 00000001 2188 SimConnect_Open succeeded: waiting to check version okay 14297 Running in "Microsoft Flight Simulator X", Version: 10.0.61355.0 (SimConnect: 10.0.61242.0) 14297 Initialising SimConnect data requests now 14297 FSUIPC Menu entry added 14438 c:\documents and settings\bkingwell.vibropile\my documents\flight simulator x files\C172 G1000 -KSEA default.FLT 14453 C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\C172\Cessna172SP.AIR 14453 Monitor IPC:310A (U16) = 0x0 123188 System time = 22:39:45, FSX time = 22:37:58 (06:37Z) 124031 Aircraft="Cessna Skyhawk 172SP G1000" 125125 Advanced Weather Interface Enabled 132500 PFC Menu entry added 215172 LogOptions changed, now 10000000 00000001 226766 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 15980 (0x00003e6c) AXIS_MIXTURE_SET 226969 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 15048 (0x00003ac8) AXIS_MIXTURE_SET 227125 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 13584 (0x00003510) AXIS_MIXTURE_SET 227328 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 11052 (0x00002b2c) AXIS_MIXTURE_SET 227531 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 7458 (0x00001d22) AXIS_MIXTURE_SET 227766 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 3730 (0x00000e92) AXIS_MIXTURE_SET 227906 *** AXIS: Cntrl= 66292 (0x000102f4), Param= -1706 (0xfffff956) AXIS_MIXTURE_SET 228109 *** AXIS: Cntrl= 66292 (0x000102f4), Param= -5768 (0xffffe978) AXIS_MIXTURE_SET 228297 *** AXIS: Cntrl= 66292 (0x000102f4), Param= -10488 (0xffffd708) AXIS_MIXTURE_SET 228531 *** AXIS: Cntrl= 66292 (0x000102f4), Param= -14420 (0xffffc7ac) AXIS_MIXTURE_SET 228734 *** AXIS: Cntrl= 66292 (0x000102f4), Param= -16384 (0xffffc000) AXIS_MIXTURE_SET 229031 *** AXIS: Cntrl= 66292 (0x000102f4), Param= -14944 (0xffffc5a0) AXIS_MIXTURE_SET 229250 *** AXIS: Cntrl= 66292 (0x000102f4), Param= -12192 (0xffffd060) AXIS_MIXTURE_SET 229391 *** AXIS: Cntrl= 66292 (0x000102f4), Param= -3672 (0xfffff1a8) AXIS_MIXTURE_SET 229594 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 3064 (0x00000bf8) AXIS_MIXTURE_SET 229766 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 8922 (0x000022da) AXIS_MIXTURE_SET 229984 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 12518 (0x000030e6) AXIS_MIXTURE_SET 230125 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 16384 (0x00004000) AXIS_MIXTURE_SET 244766 LogOptions changed, now 00000000 00000001
Pete Dowson Posted February 10, 2009 Report Posted February 10, 2009 Not sure if I understand the type of add-ons you refer to, but I do have for instance Wilco's 737 PIC. I meant anything at all either added to FSX apart from the FSX SP1/SP2 or Acceleration updates, or anything running on the same PC which works with or into FSX. All such things apart from what Microsoft provides are termed "add-ons". FSUIPC4 is one, but I know you have that! ;-) Anyway, it isn't the 310A throttle inhibitor acting. Three small last tests before I have a long think about what extra code to add to log the path through for the throttle. Can you try changing the throttle assignment in FSUIPC4's axis assignments to (a) The FSUIPC plain "Throttle", the one without the slew action included, but still "direct to FSUIPC calibration. See if that is any different. (b) Select the FS control option instead and assign the "Axis Throttle Set" control. Does that work? © Same but assign the "Throttle Set" control. Depending on what happens to those, I will try to work out a way of narrowing the main problem down more. It might mean running some special test versions of FSUIPC4. Regards Pete
SIMFAN Posted February 11, 2009 Author Report Posted February 11, 2009 Hi Pete, You do recall from my last post that I also have Saitek's Smart Technology programming software, which I de-activate. I also have your PFC software as well. I trust this is not an issue. Regarding your requested tests (a), (b) and ©. Both (a) and (b) gave the previous problem persisting, however © gave a somewhat strange result, in that it did produce throttle movement over the last 50% of throttle control travel i.e. in the range 0 to +1683, but with no reaction in the range -1683 to 0. While these values were dispayed on the assignment page, they were not displayed on the calibration page, which of course prevented (me at least) trying to get full range by re-calibrating. I checked all calibration pages for throttles, but no input/output values were displayed. Hope this is of some use. Regards, Bill
Pete Dowson Posted February 11, 2009 Report Posted February 11, 2009 You do recall from my last post that I also have Saitek's Smart Technology programming software, which I de-activate. I also have your PFC software as well. I trust this is not an issue. I have my PFC software running too. It does not prevent FSUIPC sending the throttle messages on to FS, but possibly you should please just also test with the PFCFSX module temporarily removed from the FSX Modules folder. Let me know. I would have worried that if there's no throttle on the PFC device, the values being passed to FSUIPC for calibration there might be arbitrated in the non-existent PFC throttle favour, but that doesn't look possible from my code, and furthermore another of your tests (see next) really eliminates that as a possibility. Incidentally, after investigating that area, I have to clarify something I said earlier: I said "The only way to have both FSUIPC and PFC axes working is to disable the axes in the PFC driver and assign those, too, in FSUIPC4. Then for multiple throttles it will arbitrate (using the max setting). In fact the only way to disable the throttle axis in PFC is to assign an empty user configuration explicitly to the aircraft. Regarding your requested tests (a), (b) and ©. Both (a) and (b) gave the previous problem persisting Now test (b) was the one where you are assigning the axis IN FSUIPC4, but asking it to send the standard Axis control to FSX, not direct to FSUIPC. This isn't subject to arbitration -- in fact it isn't subject to anything. It is simply sent to FSX and it should then behave exactly as if it were assigned in FSX. So, please re-check test (b) to be sure, and then the next test is obvious. Temporarily delete your throttle assignment in FSUIPC4 and assign it in FSX. Try that with FSUIPC calibration and without. however © gave a somewhat strange result, in that it did produce throttle movement over the last 50% of throttle control travel i.e. in the range 0 to +1683, but with no reaction in the range -1683 to 0. That's normal for the "THROTTLE_SET" control because the negative section is used for reverse thrust, and that isn't supported in the single-throttle calibration sections. With the standard control AXIS_THROTTLE_SET the full range -16384 to +16383 is used for forward thrust only. Hope this is of some use. Not a lot. It deepens the puzzle greatly because your result for test (b) is actually of the shortest possible route through FSUIPC4 for the axis -- detection and sending to FSX. Apart from the extra tests mentioned above (for which let me know please), I need to think how to get more information. Regards Pete
Pete Dowson Posted February 11, 2009 Report Posted February 11, 2009 Apart from the extra tests mentioned above (for which let me know please), I need to think how to get more information. I found a way for your symptom to happen (though it looks very unlikely), but it can only happen for Direct To FSUIPC assigned controls -- so it doesn't explain why test (b) failed which was sending to FSX. It is related to arbitration between axes. I've fixed what I found in versions 4.432 and 3.869, now available in the Updates announcement above. So please use 4.432 in further tests -- which I think will still be needed as in the previous message. I have added some more logging for the "direct" assignment path -- there's really nothing to the one for FS controls to be tracked so that won't log much. After you let me know about the results with 4.432 and the tests above, I'll tell you how to enable the extra logging. For now I don't want to confuse the issue. Regards Pete
SIMFAN Posted February 12, 2009 Author Report Posted February 12, 2009 Hi Pete, I have re-run the previous test as requested with the PFCFSX modules temporarily removed from FSX Modules Folder. Eureka! tests (a) and (b) both had full throttle action and test © was as before in the 0 to +1683 as you expected. Assigning the throttle in FSX while temporarily deleted in FSUIPC4 worked fine also, both with and without FSUIPC calibration. All these tests were conducted without loading the new FSUIPC4.432 as I was not sure if you meant it to be used for these or future tests you may require, e.g. perhaps with PFCFSX re-installed. Let me know if this is not what you meant. Regards, Bill
Pete Dowson Posted February 12, 2009 Report Posted February 12, 2009 I have re-run the previous test as requested with the PFCFSX modules temporarily removed from FSX Modules Folder. Eureka! tests (a) and (b) both had full throttle action and test © was as before in the 0 to +1683 as you expected. Okay. Then it is either (a) The problem of arbitration, which should be fixed in 4.432. However, if it was then the original test (b) should have worked, because sending the FS control rather than using direct FSUIPC calibration doesn't go through the arbitration code, or (b) You had not disabled the PFC throttle quadrant so its settings were always overriding those of FSUIPC or FSX. However, that doesn't make a lot of sense either, because the log definitely showed that no throttle controls were even being sent by FSUIPC -- this could not have been stopped by PFCFSX even if it could override their effect in FS. So, I'm plumping for (a) and the assumption I have to make then is that your report of the outcome of the original test (b) was mistaken. If you were not, then no explanation appears possible. The proof is in the pudding. Try 4.432 with PFCFSX re-installed. It includes extra logging which will show me what happens in the arbitration code. To enable this, before running FSX, add these lines to the FSUIPC4.INI file (in the [General] section): Debug=Please LogExtras=2056 (If you already have these, just change them to match this. You may already have a LogExtras= line). Also, please make sure Filters are off in your FSUIPC calibrations -- those will confuse the logging too much (they lengthen the input to output chain by several cycles). I only want to see the log if there's still a problem. Try with and without the PFC quadrant disabled (you can only do that by enabling and assigning a completely blank User Config to the aircraft, explicitly). Regards Pete
SIMFAN Posted February 13, 2009 Author Report Posted February 13, 2009 Hi Pete, I re-ran the (b) test but it was still the same i.e. no throttle action. I tried it with both the earlier version of FSUIPC4 and then with 4.432 but same result with both. I then made the additions to .INI for the additional log information and ran the test with and without PFC quadrant disabled. The logs appear below. Interesting (to me anyway) but when testing wihout logging, the throttle did not move. However when taking a log, as soon as I closed the logging page, the throttle setting and lever jumped instantly to 50% position, with corresponding engine response. This happened both with and without PFC quadrant disabled. Regards, Bill Test 1. PFC Quadrant disabled.********* FSUIPC4, Version 4.432 by Pete Dowson *********User Name="William Kingwell"User Addr="vpile@bigpond.net.au"FSUIPC4 Key is providedWIDEFS7 not user registered, or expired[Continuation log requested by user]Running inside FSX (using SimConnect Original)Module base=61000000Wind smoothing fix is fully installed 1138750 System time = 18:53:38, Simulator time = 12:28:57 (20:28Z) 1138750 LogOptions changed, now 10000000 00000001 1139266 *** AXIS: Cntrl= 66292 (0x000102f4), Param= -132 (0xffffff7c) AXIS_MIXTURE_SET 1139266 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 62 (0x0000003e) AXIS_PROPELLER_SET 1139266 *** AXIS: Cntrl= 65765 (0x000100e5), Param= 0 (0x00000000) AXIS_THROTTLE_SET 1140641 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 16384 (0x00004000) AXIS_MIXTURE_SET 1140641 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16384 (0x00004000) AXIS_PROPELLER_SET 1140781 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 256 (0x00000100) AXIS_ELEVATOR_SET 1141078 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET 1148172 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 6792 (0x00001a88) AXIS_MIXTURE_SET 1148313 *** AXIS: Cntrl= 66292 (0x000102f4), Param= -9570 (0xffffda9e) AXIS_MIXTURE_SET 1148516 *** AXIS: Cntrl= 66292 (0x000102f4), Param= -14682 (0xffffc6a6) AXIS_MIXTURE_SET 1148656 *** AXIS: Cntrl= 66292 (0x000102f4), Param= -16384 (0xffffc000) AXIS_MIXTURE_SET 1148953 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 3730 (0x00000e92) AXIS_MIXTURE_SET 1149141 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 16384 (0x00004000) AXIS_MIXTURE_SET 1158188 LogOptions changed, now 00000000 00000001Test 2. PFC Quadrant enabled********* FSUIPC4, Version 4.432 by Pete Dowson *********Reading options from "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.ini"NOTE: SimConnect Acc/SP2 Oct07 is supported, but it isn't installed.User Name="William Kingwell"User Addr="vpile@bigpond.net.au"FSUIPC4 Key is providedWIDEFS7 not user registered, or expiredRunning inside FSX (using SimConnect ESP Orig)Module base=61000000Wind smoothing fix is fully installedDebugStatus=15 422 System time = 20:11:35 437 FLT UNC path = "C:\Documents and Settings\BKingwell.VIBROPILE\My Documents\Flight Simulator X Files\" 437 FS UNC path = "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\" 2328 LogOptions=00000000 00000001 2328 Failed on SimConnect_Open, return = 0x80070057: FSUIPC4 cannot operate! 2328check whether you have a SimConnect.dll in your Modules folder. If so remove it! 2328Now trying to connect to another version of SimConnect ... 2328 NOTE: SimConnect SP1 May07 is supported, but it isn't installed. 2343 Now running with SimConnect Original 2343 SimConnect_Open succeeded: waiting to check version okay 16093 Running in "Microsoft Flight Simulator X", Version: 10.0.61355.0 (SimConnect: 10.0.61242.0) 16093 Initialising SimConnect data requests now 16093 FSUIPC Menu entry added 16250 c:\documents and settings\bkingwell.vibropile\my documents\flight simulator x files\C172 G1000 -KSEA default.FLT 16250 C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\C172\Cessna172SP.AIR 16250 Monitor IPC:310A (U16) = 0x0 129656 System time = 20:13:44, Simulator time = 12:22:39 (20:22Z) 130547 Aircraft="Cessna Skyhawk 172SP G1000" 132125 Advanced Weather Interface Enabled 141953 PFC Menu entry added 448937 Sim stopped: average frame rate for last 98 secs = 13.4 fps 493359 Sim stopped: average frame rate for last 38 secs = 15.2 fps 513406 LogOptions changed, now 10000000 00000001 514047 *** AXIS: Cntrl= 66292 (0x000102f4), Param= -132 (0xffffff7c) AXIS_MIXTURE_SET 514047 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 62 (0x0000003e) AXIS_PROPELLER_SET 514047 *** AXIS: Cntrl= 65765 (0x000100e5), Param= 0 (0x00000000) AXIS_THROTTLE_SET 514687 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 16384 (0x00004000) AXIS_MIXTURE_SET 514687 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16384 (0x00004000) AXIS_PROPELLER_SET 518875 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 13850 (0x0000361a) AXIS_MIXTURE_SET 519047 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 4662 (0x00001236) AXIS_MIXTURE_SET 519234 *** AXIS: Cntrl= 66292 (0x000102f4), Param= -4458 (0xffffee96) AXIS_MIXTURE_SET 519422 *** AXIS: Cntrl= 66292 (0x000102f4), Param= -12060 (0xffffd0e4) AXIS_MIXTURE_SET 519625 *** AXIS: Cntrl= 66292 (0x000102f4), Param= -16384 (0xffffc000) AXIS_MIXTURE_SET 520265 *** AXIS: Cntrl= 66292 (0x000102f4), Param= -132 (0xffffff7c) AXIS_MIXTURE_SET 520453 *** AXIS: Cntrl= 66292 (0x000102f4), Param= 16384 (0x00004000) AXIS_MIXTURE_SET 534109 LogOptions changed, now 00000000 00000001pp
Pete Dowson Posted February 13, 2009 Report Posted February 13, 2009 Hi Pete,I re-ran the (b) test but it was still the same i.e. no throttle action. I tried it with both the earlier version of FSUIPC4 and then with 4.432 but same result with both. Well there's no difference in any version of FSUIPC if you assign to FS controls, because it merely sends the AXIS controls to FS as it receives them. The path through FSUIPC is very short. This is completely inexplicable, and there's not really any logging I can add apart from that which I already asked for. I then made the additions to .INI for the additional log information and ran the test with and without PFC quadrant disabled. The logs appear below. Something may be wrong with your INI file editing, then, because the logging you show is just the default + Axis logging you provided before. It certainly is NOT with these lines Debug=Please LogExtras=2056 The lines showing: LogOptions changed, now 10000000 00000001 show that the "2056" value didn't take -- or you cleared it in the Logging options, but why would you do that? Interesting (to me anyway) but when testing without logging, the throttle did not move. However when taking a log, as soon as I closed the logging page ErOuch! Why are you going into the Logging page? I merely asked you to add the above to the INI file before loading FSX, then do the tests. It looks like you pressed some buttons in the Logging page -- at least "New Log". Why? Please, when running tests for me, never push any buttons or change any check marks or numbers unless I ask. There's certainly never a need to Start a New Log as you've done. If you did add those lines before loading FSX, it certainly looks like you then went into the Logging page and turned the Extras logging off that they would have enabled. ... the throttle setting and lever jumped instantly to 50% position, with corresponding engine response. This happened both with and without PFC quadrant disabled. considering the test you accomplished was identical to previous ones, with the same logging exactly, this is rather odd too. This is interesting (I hadn't read this part before): NOTE: SimConnect Acc/SP2 Oct07 is supported, but it isn't installed. Have you not installed FSX SP2 yet? It fixes a lot of SimConnect problems, and is 100% more efficient for programs like FSUIPC -- especially with PFCFSX on top. Do you think you could try updating your FSX? Or is it installed but the SimConnect part broken? This is even more interesting: Running inside FSX (using SimConnect ESP Orig) You have ESP installed? FSUIPC seems to be using the ESP SimConnect in a copy of FSX which hasn't been updated to SP2, probably because the ESP one is more up to date. This same log shows some SimConnect initialisation problems as a result: 2328 Failed on SimConnect_Open, return = 0x80070057: FSUIPC4 cannot operate! 2328check whether you have a SimConnect.dll in your Modules folder. If so remove it! This is a result, I think, of FSUIPC trying to use the ESP SimConnect. Apparently you can use an FSX SimConnect with ESP, but not vice versa. I'll need to look at how to prevent FSUIPC trying, as I didn't realise that. (This wouldn't have noticed before, as this is the first release of FSUIPC4 combining FSX and ESP support). Even stranger, then, but possibly a side effect of the above: 2328Now trying to connect to another version of SimConnect ... 2328 NOTE: SimConnect SP1 May07 is supported, but it isn't installed. 2343 Now running with SimConnect Original 2343 SimConnect_Open succeeded: waiting to check version okay 16093 Running in "Microsoft Flight Simulator X", Version: 10.0.61355.0 (SimConnect: 10.0.61242.0) One of your earlier logs did indicate that at least SP1 was installed and working: ********* FSUIPC4, Version 4.428 by Pete Dowson *********Reading options from "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.ini" NOTE: SimConnect Acc/SP2 Oct07 is supported, but it isn't installed. ... Running inside FSX (SimConnect SP1 May07) Curiouser and curiouser ... I'll investigate the misuse of the ESP SimConnect. Perhaps you could try tests (a), (b) and © again, separately (so separate logs), with the logging I asked for (and no entry into the Logging page please!), and also perhaps contemplate installing SP2. Oh, please include PFCFSX in all tests, but do try disabling the throttle quadrant in the way I suggested for the aircraft in which you are using the Saitek. Regards Pete
Pete Dowson Posted February 13, 2009 Report Posted February 13, 2009 Further to this: Even stranger, then, but possibly a side effect of the above: 2328Now trying to connect to another version of SimConnect ... 2328 NOTE: SimConnect SP1 May07 is supported, but it isn't installed. 2343 Now running with SimConnect Original 2343 SimConnect_Open succeeded: waiting to check version okay 16093 Running in "Microsoft Flight Simulator X", Version: 10.0.61355.0 (SimConnect: 10.0.61242.0) One of your earlier logs did indicate that at least SP1 was installed and working If I remove the SP2 SimConnect, I can reproduce the load and failure of the ESP SimConnect here, so I can certainly stop that by some extra programming, but it recovers okay here and uses SP1, not the Base version: Running inside FSX (using SimConnect ESP Orig)Module base=61000000Wind smoothing fix is fully installedDebugStatus=255 1031 System time = 11:03:12 1047 FLT UNC path = "\\LEFT\FSPLANS\" 1063 FS UNC path = "\\LEFT\G\fsx\" 5000 LogOptions=00000000 00000001 5406 Failed on SimConnect_Open, return = 0x80004005: FSUIPC4 cannot operate! 5406Now trying to connect to another version of SimConnect ... 5563 Now running with SimConnect SP1 May07 5563 SimConnect_Open succeeded: waiting to check version okay 18438 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) So i'm now wondering whether you might have a broken SP1 as well as an uninstalled SP2? Maybe you need to try re-installing SP1 and then adding SP2? Regards Pete
Pete Dowson Posted February 13, 2009 Report Posted February 13, 2009 Running inside FSX (using SimConnect ESP Orig) You have ESP installed? FSUIPC seems to be using the ESP SimConnect in a copy of FSX which hasn't been updated to SP2, probably because the ESP one is more up to date. Whilst I've fixed, here, the problem of FSUIPC4 trying to use an ESP SimConnect on FSX, in the process I also found a new little bug (in the combined FSUIPC4 / ESPIPC which FSUIPC4 has now become) which could mis-identify SP1 as ESP SimConnect, in the absence of SP2. So I won't be surprised to learn that you've never installed ESP! ;-) I will be uploading another increment over the weekend with these things fixed, but as I don't see where to make any changes which affect your throttle problem directly, I would like to see the full logging as requested first. We'll take it from there. Regards Pete
SIMFAN Posted February 14, 2009 Author Report Posted February 14, 2009 Hi Pete, Sorry, but I didn't see your last post until just now; I must have missed the notification. Anyway, in the meantime I installed SP2, not realizing that maybe SP1 is faulty. I then modified the .INI file as requested for extra logging and then restarted FSX. I had also assigned a blank configuration from the PFC quadrant page, to the aircraft explicitly. I then attempted to run test (a) (without going into the Logging page!!!) however this time no axes would register and after a few seconds, a MS message appeared stating that FSX had encounted a problem and needed to shut down. I then shut down and on checking the .INI file noticed that LogExtra=x808 had been substituted for the LogExtra=2056. I repeated the attempt a number of times to ensure that this behaviour was recurring; it was. I then deleted the Debug and LogExtras entries and tried running FSX again. No problems at all were experienced with axes, other than the throttle, which was as before, inoperative. Neither did FSX encounter any problems. I have included below a copy of the log of one of the attempted tests. Pete, as you have no doubt observed, I am struggling a bit with my handling of FSUIPC and am not confident that I always fully understand your instructions and how to effect them, so I hope you won't mind me asking a couple of questions. 1. I note that logs are recorded in the normal log file, however I am not sure as to how to give you separate logs for each of the test as you request. I was intending to copy each test as recorded, shutting down FSX each time between each test. (only way I could see how to do it). How should it be done? 2. Am I using the correct method of disabling the PFC quadrant? I have ticked the enable quadrant box and assigned the blank configuration to the aircraft. Regards, Bill ********* FSUIPC4, Version 4.432 by Pete Dowson *********Reading options from "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.ini"User Name="William Kingwell"User Addr="vpile@bigpond.net.au"FSUIPC4 Key is providedWIDEFS7 not user registered, or expiredRunning inside FSX (using SimConnect Acc/SP2 Oct07)Module base=61000000Wind smoothing fix is fully installedDebugStatus=15 453 System time = 20:19:00 453 FLT UNC path = "C:\Documents and Settings\BKingwell.VIBROPILE\My Documents\Flight Simulator X Files\" 453 FS UNC path = "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\" 2312 LogOptions=00000000 00008091 2312 SimConnect_Open succeeded: waiting to check version okay 8516 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0) 8516 Initialising SimConnect data requests now 8516 FSUIPC Menu entry added 8656 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y 8656 C:\Documents and Settings\BKingwell.VIBROPILE\My Documents\Flight Simulator X Files\Extra 300S KSEA - Default.FLT 8656 C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Extra300\Extra300S.AIR 8656 Monitor IPC:310A (U16) = 0x0 32953 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N 33156 System time = 20:19:33, Simulator time = 12:22:22 (20:22Z) 33953 Aircraft="Extra 300S Paint1" 34922 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y 97656 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y 101984 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N 102391 ExSendEvent(65735, 0, 0) 102391evnum mask=0, preval=0 102391not intercepted or in options 102391 Transmitting "PAN_DOWN" 65735 [0x100C7], Param 0, Group 1 103187 Advanced Weather Interface Enabled 103234 ExSendEvent(65735, 0, 0) 103234evnum mask=0, preval=0 103234not intercepted or in options 103234 Transmitting "PAN_DOWN" 65735 [0x100C7], Param 0, Group 1 103297 ExSendEvent(65735, 0, 0) 103297evnum mask=0, preval=0 103297not intercepted or in options 103297 Transmitting "PAN_DOWN" 65735 [0x100C7], Param 0, Group 1 103359 ExSendEvent(65735, 0, 0) 103359evnum mask=0, preval=0 103359not intercepted or in options 103359 Transmitting "PAN_DOWN" 65735 [0x100C7], Param 0, Group 1 103500 ExSendEvent(65735, 0, 0) 103500evnum mask=0, preval=0 103500not intercepted or in options 103500 Transmitting "PAN_DOWN" 65735 [0x100C7], Param 0, Group 1 103562 ExSendEvent(65735, 0, 0) 103562evnum mask=0, preval=0 103562not intercepted or in options 103562 Transmitting "PAN_DOWN" 65735 [0x100C7], Param 0, Group 1 103641 ExSendEvent(65735, 0, 0) 103641evnum mask=0, preval=0 103641not intercepted or in options 103641 Transmitting "PAN_DOWN" 65735 [0x100C7], Param 0, Group 1 103766 ExSendEvent(65735, 0, 0) 103766evnum mask=0, preval=0 103766not intercepted or in options 103766 Transmitting "PAN_DOWN" 65735 [0x100C7], Param 0, Group 1 104281 ExSendEvent(65735, 0, 0) 104281evnum mask=0, preval=0 104281not intercepted or in options 104281 Transmitting "PAN_DOWN" 65735 [0x100C7], Param 0, Group 1 105469 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y 108250 PFC Menu entry added 108812 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N 109781 ExSendEvent(65735, 0, 0) 109781evnum mask=0, preval=0 109781not intercepted or in options 109781 Transmitting "PAN_DOWN" 65735 [0x100C7], Param 0, Group 1 111047 ExSendEvent(65735, 0, 0) 111047evnum mask=0, preval=0 111047not intercepted or in options 111047 Transmitting "PAN_DOWN" 65735 [0x100C7], Param 0, Group 1 111156 ExSendEvent(66400, 3, 0) 111156evnum mask=0, preval=0 111156not intercepted or in options 111156 Transmitting "MAGNETO1_SET" 66400 [0x10360], Param 3, Group 1 111156 ExSendEvent(65962, 3, 0) 111156evnum mask=0, preval=0 111156not intercepted or in options 111156 Transmitting "FUEL_SELECTOR_SET" 65962 [0x101AA], Param 3, Group 1 111156 ExSendEvent(66523, 3, 0) 111156evnum mask=0, preval=0 111156not intercepted or in options 111156 Transmitting "FUEL_SELECTOR_2_SET" 66523 [0x103DB], Param 3, Group 1 111156 ExSendEvent(66568, 3, 0) 111156evnum mask=0, preval=0 111156not intercepted or in options 111156 Transmitting "FUEL_SELECTOR_3_SET" 66568 [0x10408], Param 3, Group 1 111156 ExSendEvent(66576, 3, 0) 111156evnum mask=0, preval=0 111156not intercepted or in options 111156 Transmitting "FUEL_SELECTOR_4_SET" 66576 [0x10410], Param 3, Group 1 111547 ExSendEvent(65735, 0, 0) 111547evnum mask=0, preval=0 111547not intercepted or in options 111547 Transmitting "PAN_DOWN" 65735 [0x100C7], Param 0, Group 1 112250 ExSendEvent(65735, 0, 0) 112250evnum mask=0, preval=0 112250not intercepted or in options 112250 Transmitting "PAN_DOWN" 65735 [0x100C7], Param 0, Group 1 112609 ExSendEvent(65735, 0, 0) 112609evnum mask=0, preval=0 112609not intercepted or in options 112609 Transmitting "PAN_DOWN" 65735 [0x100C7], Param 0, Group 1 113000 ExSendEvent(65735, 0, 0) 113000evnum mask=0, preval=0 113000not intercepted or in options 113000 Transmitting "PAN_DOWN" 65735 [0x100C7], Param 0, Group 1 114156 ExSendEvent(65671, 0, 0) 114156evnum mask=0, preval=0 114156not intercepted or in options 114156 Transmitting "PAN_LEFT" 65671 [0x10087], Param 0, Group 1 118547 Axis 0Z=-16123: Action=4 (direct to calib) 118547 Direct Axis 4, Ctrl 65765=-16123 : in calibration ... 118547 ###JOY### Event seen, ID=65765 (0x000100E5), Joy=3, value=-16123 (Direct)
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