baw19

Hi Pete, I realise I asked this a while back but I was wondering if you'd had any access to the new MSFlight team since then? I hear it's allegedly due out in Feb - are there any plans to support it with FSUIPC? Cheers Ian

Hi Pete, just to let you know I've been using the v4.731 on full flight cycles for a couple of days now with no problems (I noticed the word Beta on the download link and thought I should update you). All the best Ian

Aha! Think we have a result Pete. I've been taxiing around with v4.731 the for a while now - both 737 and 747 with filters on. Even completed a quick hop from Gatwick to Heathrow in the 747 and no reversers deploying and no FSX hangs. Shall we call that a fix or would you rather I tested for a few more days? Many thanks for the efforts you've put in to this one Pete, very much appreciated. All the best Ian

Yes, sorry, clumsy terminology. FSX hangs and I have to End Task it. Yes No - in fact I switched off the MapThr12to34 option and taxied the 747 around quite happily, albeit mostly to the right. However when I turned the option back on the sim hanged as soon as the FSUIPC dialog closed. FSX then had to be end tasked. Latest log is at www.ianniblo.pwp.blueyonder.co.uk/FSUIPC4_hang_after_setting_map12to34.zip All the best Ian

Hi Pete, I've set all the Deltas to 512, switched filtering back on, added large 'buffers' zones at each end of the calibration ranges and removed the spurious entries in my INI file. Using v4.729 I reliably get FSX abends when I throttle up though it must be said that so far I've not had any rogue reverser deployments. To replicate the abend I start at EGKK using the 737-100 (see note later). Then I change to the 747-100, taxi to the runway and line up. I ramp up the thrust to check the engines are stable then open them fully but FSX freezes before I get to 100%. This happens with the new version of FSUIPC immediately after a full PC reboot. If I restore the original v4.278 I don't get the abend. Please note that with the 747 I currently use throttle lever 1 to control engines 1 & 2 and throttle lever 2 to control engines 3 and 4. Sorry this is all rambling along so much! Both logs are here (one for each version of FSUIPC) www.ianniblo.pwp.blueyonder.co.uk/FSUIPC4_FSX_Abend.zip Ian Note: The 747-100 and 737-100 are actually the default 747-400 and 737-800 FSX models but I've had to segregate them and rename them for quite complicated reasons revloving around dual log ons in VATSIM and me trying to avoid seeing my own plane when I fly online. Apart from the name and the paint job the planes are the defaults in all other respects.

Righto, I'll monitor all the offsets and controls that affect reversers to see if anything's firing them. Here you go, the reverser zone is deliberately narrow to try to minimize any chance of deployment:- Throttle2=-16383,0,1,16125/32 All the best Ian ps The full INI file follows, if it's any use to you. By the way, it's Saturday night and I'm sure you have better things to do than debug someone else's problem - I really appreciate all the work you've put in and I'm quite happy to leave this till it's convenient with you, just let me know. [General] Debug=Please LogExtras=x8 History=NXHU1AMHIUE2GCVOI93O3 TCASid=Tail TCASrange=160 AxisCalibration=No DirectAxesToCalibs=No ShowMultilineWindow=No SuppressSingleline=No SuppressMultilineFS=No WeatherReadFactor=2 SimConnectStallTime=1 GraduatedVisibility=No LowerVisAltitude=0 UpperVisAltitude=25000 UpperVisibility=10000 MinimumVisibility=200 MaximumVisibilityFewClouds=0 MaximumVisibility=0 MaximumVisibilityOvercast=0 MaximumVisibilityRainy=0 SetVisUpperAlt=No VisUpperAltLimit=60000 ExtendMetarMaxVis=No OneCloudLayer=No CloudTurbulence=No CloudIcing=No GenerateCirrus=No SuppressCloudTurbulence=No MaxIce=-4 MinIce=-4 UpperWindGusts=No SuppressWindTurbulence=No WindTurbulence=No SuppressAllGusts=No MaxSurfaceWind=0 WindLimitLevel=200 WindDiscardLevel=400 WindAjustAltitude=No WindAjustAltitudeBy=2000 DisconnTrimForAP=No ZeroElevForAPAlt=No ThrottleSyncAll=No WhiteMessages=No ShowPMcontrols=No MagicBattery=Yes RudderSpikeRemoval=No ElevatorSpikeRemoval=No AileronSpikeRemoval=No ReversedElevatorTrim=No ClockSync=No ClockSyncMins=5 ClearWeatherDynamics=No OwnWeatherChanges=No TimeForSelect=4 LoadFlightMenu=Yes LoadPlanMenu=No PauseAfterCrash=No ShortAircraftNameOk=No AxisIntercepts=No SpoilerIncrement=512 WindSmoothing=No WindSmoothness=2 WindSmoothAirborneOnly=Yes ZapSound=firework FixControlAccel=No SuppressWindVariance=No TurbulenceRate=1.0,5.0 PressureSmoothness=20 TemperatureSmoothness=0 MouseWheelTrim=No VisibilityOptions=Yes TurbulenceDivisor=20,20,40,40 WeatherRewriteSeconds=1 MouseWheelTrimSpeed=1 FixMachSpeedBug=Yes CustomWeatherModify=No Console=No SaveDataWithFlights=No UseProfiles=No UpdatedByVersion=4728 SmoothBySimTime=No BrakeReleaseThreshold=75 DontResetAxes=No JoystickTimeout=20 PollGFTQ6=Yes BlankDisplays=No GetNearestAirports=No LuaRerunDelay=66 EnableMouseLook=No LogAxes=Yes [AutoSave] AutoSaveEnabled=No Next=1 Interval=60 Files=10 SaveOnGround=No [GPSout] GPSoutEnabled=No Port=<none set> Speed=4800 Interval=1000 PosTo6Decimal=Yes Sentences= [WideServer] WideFSenabled=Yes AdvertiseService=1 Port=8002 Port2=9002 [ClientNames] 1=MUSICPC 2=FLTSIM2 3=LAPTOP1 4=SIDEVIEWS [Buttons] :: EliminateTransients=Yes :: PollInterval=25 1=R2,2,C1017,0 2=R2,3,C1016,0 3=R2,4,C65607,0 4=R2,5,C65615,0 5=P2,7,C66530,0 6=R3,2,C1017,0 7=R3,3,C1016,0 8=R3,4,C65607,0 9=R3,5,C65615,0 10=P3,7,C66530,0 11=P158,0,C65906,0 12=P4,28,C65561,0 13=P158,11,C65859,0 14=P158,12,C65725,0 15=P158,13,C65726,0 18=P174,10,C66616,0 ButtonRepeat=20,10 21=R2,0,K116,8 22=R3,0,K116,8 25=P174,9,C66615,0 26=P158,9,C65722,0 [Axes] 0=0X,256,D,7,0,0,0 1=0Y,256,D,8,0,0,0 2=0Z,256,D,3,0,0,0 3=1X,256,D,7,0,0,0 4=1Y,256,D,8,0,0,0 5=1Z,256,D,3,0,0,0 6=2X,256,D,1,0,0,0 7=2Y,256,D,2,0,0,0 8=3X,256,D,1,0,0,0 9=3Y,256,D,2,0,0,0 10=5X,256,D,9,0,0,0 11=5Y,256,D,10,0,0,0 12=5Z,256,D,22,0,0,0 13=5R,256,D,23,0,0,0 [ fCalibration] ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No FlapsSetControl=0 FlapDetents=Yes ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=66731 RudderTrimControl=66732 CowlFlaps1Control=66162 CowlFlaps2Control=66163 CowlFlaps3Control=66164 CowlFlaps4Control=66165 SteeringTillerControl=0 MaxSteerSpeed=60 Spoilers=-15234,-11210,-5174,16384/16 LeftBrake=-16380,16380/16 RightBrake=-16380,16380/16 AllowSuppressForPFCquad=Yes UseAxisControlsForNRZ=No MapThr1to234=Yes MapThr12to34=Yes MapThr12to123=Yes Throttle1=-16383,0,0,16382/32 [Keys] 1=1,8,65865,0 2=187,8,65656,0 4=189,8,65655,0 5=109,8,65656,0 6=107,8,65655,0 7=37,8,65671,0 8=39,8,65672,0 9=49,8,65734,0 [JoyNames] AutoAssignLetters=No 2=Saitek Pro Flight Yoke 3=Saitek Pro Flight Yoke 4=Plasma-Lite 0=CH PRO PEDALS USB 1=CH PRO PEDALS USB 0.GUID={7C4FD0D0-9889-11DD-8002-444553540000} 1.GUID={7C4FD0D0-9889-11DD-8003-444553540000} 2.GUID={7C4FD0D0-9889-11DD-8004-444553540000} 3.GUID={7C4FD0D0-9889-11DD-8005-444553540000} 4.GUID={7C4FD0D0-9889-11DD-800C-444553540000} 5=IOCa 5.GUID={55C60700-18B6-11DF-8001-444553540000} [LuaFiles] 1=display vals 2=liar 3=MenuDemo 4=TripleUse [GPSout2] GPSoutEnabled=No Port=<none set> Speed=4800 Interval=2000 PosTo6Decimal=No Sentences= [Sounds] Path=C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\Sound\ Device1=Primary Sound Driver Device2=SB Live! 24-bit Device3=USB Sound Device [Axes.FA-18 Hornet] 0=0X,256,D,7,0,0,0 1=0Y,256,D,8,0,0,0 2=0Z,256,D,3,0,0,0 3=1X,256,D,7,0,0,0 4=1Y,256,D,8,0,0,0 5=1Z,256,D,3,0,0,0 6=2X,256,D,1,0,0,0 7=2Y,256,D,2,0,0,0 8=3X,256,D,1,0,0,0 9=3Y,256,D,2,0,0,0 10=5X,256,D,9,0,0,0 11=5Y,256,D,10,0,0,0 12=5Z,256,D,22,0,0,0 13=5R,256,D,23,0,0,0 [Monitor] Display=1 Monitor3=0,0BD0,5,0 [JoystickCalibration.Boeing 747-400 BA] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=Yes FlapStarts=-16384,-12177,-7085,-443,5314,9299,12840 FlapEnds=-13284,-7528,-4207,2214,8635,11513,16384 ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=66731 RudderTrimControl=66732 CowlFlaps1Control=66162 CowlFlaps2Control=66163 CowlFlaps3Control=66164 CowlFlaps4Control=66165 SteeringTillerControl=0 MaxSteerSpeed=60 Spoilers=-16384,-9629,-5145,16383/8 Flaps=-13284,12841 MapThr12to34=Yes Throttle1=-16380,0,1,16380/32 Throttle2=-16380,0,1,16380/32 LeftBrake=-16380,16380/16 RightBrake=-16380,16380/16 [JoystickCalibration.FA-18 Hornet] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=Yes FlapStarts=-16384,-7970,1328,11733 FlapEnds=-14391,-4871,5092,16384 ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=66731 RudderTrimControl=66732 CowlFlaps1Control=66162 CowlFlaps2Control=66163 CowlFlaps3Control=66164 CowlFlaps4Control=66165 SteeringTillerControl=0 MaxSteerSpeed=60 Throttle1=-13256,0,1,16073/32 Throttle2=-13520,0,1,16036/32 Spoilers=-16384,-11244,-6746,16383 Flaps=-14391,11734 LeftBrake=-16380,16380/16 RightBrake=-16380,16380/16 [JoystickCalibration] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=No ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=66731 RudderTrimControl=66732 CowlFlaps1Control=66162 CowlFlaps2Control=66163 CowlFlaps3Control=66164 CowlFlaps4Control=66165 SteeringTillerControl=0 MaxSteerSpeed=60 LeftBrake=-16380,16380/16 RightBrake=-16380,16380/16 [JoystickCalibration.Boeing 747-100 BA] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No MapThr12to34=Yes FlapsSetControl=0 FlapDetents=Yes FlapStarts=-16384,-13284,-7306,-886,5535,9963,12176 FlapEnds=-14170,-11070,-4428,1328,9077,11513,16384 ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=66731 RudderTrimControl=66732 CowlFlaps1Control=66162 CowlFlaps2Control=66163 CowlFlaps3Control=66164 CowlFlaps4Control=66165 SteeringTillerControl=0 MaxSteerSpeed=60 LeftBrake=-16380,16380/16 RightBrake=-16380,16380/16 Throttle1=-13547,0,1,16074/32 Throttle2=-13522,0,1,16029/32 Spoilers=-16381,-9637,-5140,16383 Flaps=-14170,12177 [JoystickCalibration.Boeing 737-100 BA] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=Yes FlapStarts=-16384,-12840,-9962,-6863,-3321,0,6199,9520,14937 FlapEnds=-14169,-10848,-7969,-4428,-443,2878,8856,12398,16384 ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=66731 RudderTrimControl=66732 CowlFlaps1Control=66162 CowlFlaps2Control=66163 CowlFlaps3Control=66164 CowlFlaps4Control=66165 SteeringTillerControl=0 MaxSteerSpeed=60 Throttle1=-16383,0,1,16074/32 Throttle2=-16383,0,1,16125/32 Spoilers=-16381,-11243,-5779,16383 Flaps=-13284,12841 LeftBrake=-16380,16380/16 RightBrake=-16380,16380/16 SyncSlopeThrottle2=57/55

Hi Pete Right, I've re-tested using the original FSUIPC v4.278 and with no filtering on any axis and I still get random reverser deployments. I copied the new log pretty shortly after getting one of those events so the axis info at the end of the log should be round about the same time. Looking at this and the earlier logs I noticed an awful lot of -96 entries springing up on Throttle2 but I've no idea if that's interesting or a red herring! The new log is here: www.ianniblo.pwp.blueyonder.co.uk/FSUIPC4278_No_Filtering_Delta_256.zip All the best Ian

Ah, OK, I was searching for "Calibrated=-...". So if the axiis are sending correctly calibrated values and I have NRZ switched I wonder why the reversers are deploying, seemingly at random, when I'm idling or taxiing? Is there anything I can turn on to trap those events? For info the only thing I use to command the reversers is a switch that sends either -4096 or zero to offsets x088C, x0924, x09BC, x0A54 (all 2 byte VB6 integers). As before there is nothing set up in FSX to activate these. Cheers Ian [Later] Ah, wait - I'm probably missing something but there are loads of negatives in the FSUIPC4728c_To_FSUIPC_Calib_No_Filter_Delta_512.log file. This one's on a throttle but there are countless negs on the spoiler, flaps, rudder and brake axiis) 253688 *** AXIS: Cntrl= 65821 (0x0001011d), Param= -96 (0xffffffa0) THROTTLE2_SET compare this to one from the extract you listed above and they look identical but for the negative value 253594 *** AXIS: Cntrl= 65821 (0x0001011d), Param= 704 (0x000002c0) THROTTLE2_SET Sorry to confuse matters! [still later!] I just spotted that the line I pulled out is actually in your extract list! I'll restore the previous version of FSUIPC and see if I can reproduce the spoiler issue with no filtering... Ian

Hi Pete, I've run some more tests using the replacement DLL and the new logs can be found at http:/www.ianniblo.pwp.blueyonder.co.uk/FSUIPC4728c_Logs_For_Pete_Dowson.zip* however there are several more logs that yesterday as the plot thickens! Yesterday I think we figured that the rogue reverser deployment could be elliminated simply by removing the axis filters but with the test DLL and using 512 as a Delta I'm getting the problem even with no Filter on any axiis. The log FSUIPC4728c_To_FSUIPC_Calib_No_Filter_Delta_512.log is littered with negatives and I wonder if that's symptomatic? Let me know if I can do anything more to help! All the best Ian * Sorry - can't seem to get the forum Linking to work!

Hi Pete, Yes - although I left the throttles alone for much of the test I deliberately moved them around to try to get the reversers to deploy. This is why the logs are so large - I felt it important to leave them idling for a long time as well as including some range of manual changes. Usually this would be a slow throttle-up in the lower ranges (I only notice the reverser problem when idling or taxiing) though occasionally I'd close the throttles quite rapidly to see if that had an effect. So all the major ranges of movement will be me not the jitters. Thanks, I'll give this a try and let you know if it helps, in the meantime do let me know if you need anything else. Ian

I'm using the USBAxes card by Manuel Velez but I've ordered the BU0836 to see if that helps (thanks for the tip!). I've done this though I didn't get the same problem with negatives. Curiously all three logs have one negative value on the axis right at the top. However it's only the session "To FSUIPC Calibrated with Filtering" that gave subsequent negatives. In that session I was still getting the rogue Reverser deployment though I probably should have said that it's only a gentle amount - from the outside you can barely see the cowl open. All the same I've got NRZ selected so I guess any amount is bad! (Sorry, forgot to drop that in last time.) Just the default value - 256 Okay - done that and you can review the logs here: http:/www.ianniblo.pwp.blueyonder.co.uk/FSUIPIC_Logs_For Pete_Dowson.zip. Hopefully the file names are meaningful enough. Please let me know if I can be of any more help - appreciate you looking at this! All the best Ian

Hi Pete, I think you may be right about the Filter - I've turned it off and I'm not getting negatives now, thanks! For the sake of anyone else who finds themselves here I'll post the answers to your questions: It's a home-made throttle quadrant using 10k linear pots plugged into a board that's plugged into a USB port on the back of my PC (to elliminate potential hub issues). The pots were replaced with new ones last week in an attempt to suppress the flutter but it didn't make much difference. Mind you they're Maplin pots so I shouldn't really expect flawless performance! Someone else has since suggested getting a better power supply which I may yet do. For info the pots show no flutter at all when connected to a voltmeter, it's only the software that shows flutter (including the Windows XP Game Controllers control panel). Yes, it does look a lot like that's the culprit. Having repeated the tests long and hard I'm not seeing negatives with Filter turned off. The axiis are assigned in FSUIPC "Send direct to FSUIPC calibration" - each axis to it's appropriate function eg Flap lever axis to Flaps. I don't use 3rd party software between the hardware and FSUIPC and I've thoroughly checked that no axis assignments have been made and forgotten about in the FSX Controls dialog. Interestingly the latest log shows a fairly reliable pattern of zero then value for each axis (presumably this is why the logs grow so large). I might expect this on the yoke axiis as they're dual control but the throttles have no other form of input so I'm not sure why I'm seeing these alternate values (see sample below). One thing that does occur to me is that I recently changed from using the single Throttle control (tab 1 in FSUIPC) to the individual throttle setting on tab 3. Although I've deselected the tab 1 stuff I wonder if it's possible that FSUIPC is now getting confused between the two? Just a thought. Anyway, there you go - I'm not getting the reversers kicking in so I think I'm sorted. Thanks for your help again, All the best Ian ********* FSUIPC4, Version 4.728 by Pete Dowson ********* User Name="Ian Niblo" User Addr="my.shopping@blueyonder.co.uk" FSUIPC4 Key is provided WideFS7 Key is provided [Continuation log requested by user] Running inside FSX (using SimConnect Acc/SP2 Oct07) Module base=61000000 Wind smoothing fix is fully installed 161750 System time = 15/09/2011 14:01:48, Simulator time = 16:09:22 (15:09Z) 161750 LogOptions changed, now 10000000 00000001 163188 *** AXIS: Cntrl= 65820 (0x0001011c), Param= 318 (0x0000013e) THROTTLE1_SET 163188 *** AXIS: Cntrl= 65821 (0x0001011d), Param= 131 (0x00000083) THROTTLE2_SET 163235 *** AXIS: Cntrl= 65820 (0x0001011c), Param= 0 (0x00000000) THROTTLE1_SET 163235 *** AXIS: Cntrl= 65821 (0x0001011d), Param= 0 (0x00000000) THROTTLE2_SET 163875 *** AXIS: Cntrl= 65821 (0x0001011d), Param= 131 (0x00000083) THROTTLE2_SET 163907 *** AXIS: Cntrl= 65821 (0x0001011d), Param= 0 (0x00000000) THROTTLE2_SET 164016 *** AXIS: Cntrl= 65820 (0x0001011c), Param= 159 (0x0000009f) THROTTLE1_SET 164047 *** AXIS: Cntrl= 65820 (0x0001011c), Param= 0 (0x00000000) THROTTLE1_SET 164360 *** AXIS: Cntrl= 65821 (0x0001011d), Param= 131 (0x00000083) THROTTLE2_SET 164391 *** AXIS: Cntrl= 65821 (0x0001011d), Param= 0 (0x00000000) THROTTLE2_SET 164922 *** AXIS: Cntrl= 65820 (0x0001011c), Param= 159 (0x0000009f) THROTTLE1_SET 164954 *** AXIS: Cntrl= 65820 (0x0001011c), Param= 0 (0x00000000) THROTTLE1_SET 165125 *** AXIS: Cntrl= 65820 (0x0001011c), Param= 159 (0x0000009f) THROTTLE1_SET 165157 *** AXIS: Cntrl= 65820 (0x0001011c), Param= 0 (0x00000000) THROTTLE1_SET 165235 *** AXIS: Cntrl= 65820 (0x0001011c), Param= 159 (0x0000009f) THROTTLE1_SET 165266 *** AXIS: Cntrl= 65820 (0x0001011c), Param= 0 (0x00000000) THROTTLE1_SET 166266 *** AXIS: Cntrl= 65820 (0x0001011c), Param= 159 (0x0000009f) THROTTLE1_SET 166266 *** AXIS: Cntrl= 65821 (0x0001011d), Param= 131 (0x00000083) THROTTLE2_SET 166297 *** AXIS: Cntrl= 65820 (0x0001011c), Param= 0 (0x00000000) THROTTLE1_SET 166297 *** AXIS: Cntrl= 65821 (0x0001011d), Param= 0 (0x00000000) THROTTLE2_SET 166672 *** AXIS: Cntrl= 65820 (0x0001011c), Param= 159 (0x0000009f) THROTTLE1_SET 166704 *** AXIS: Cntrl= 65820 (0x0001011c), Param= 0 (0x00000000) THROTTLE1_SET 166782 *** AXIS: Cntrl= 65820 (0x0001011c), Param= 159 (0x0000009f) THROTTLE1_SET 166813 *** AXIS: Cntrl= 65820 (0x0001011c), Param= 0 (0x00000000) THROTTLE1_SET

Hi Peter, I recently got a new flightsim PC and am having huge flutter problems on my axis inputs. I've found that the Filter option on the FSUIPC axis tabs helps a great deal to supress these but I'm still getting a peculiar problem that you may be able to help with? I'm using FSUIPC v4.728 and have used it to calibrate my axiis (Spoilers, Flaps and Throttles 1 and 2). All axiis have the Filter option switched on and none are using the Slope option. Both throttles have the No Reverser Zone option selected but the reversers randomly deploy even when I'm idling the engines at the gate. I've tried tweaking the FSUIPC.INI file, setting the reverser zone to 0,1 even though No Reverser Zone is still selected, but I'm still getting the reversers deploying now and then while I'm taxiing, even after a full FSX restart. I took a look at the FSUIPC log and was surprised to see negative values on all the axiis - I'd assumed that once I'd calibrated these FSUIPC would only send positive values to FSX. I'm wondering if the flutter is so wild that it's causing negatives to slip through the net and wondered if you could add a further filter option to completely suppress any negative values that might be triggering the reversers? Here's an extract from the log, it shows only the axis activity and because of the flutter problem it was originally quite long so I've cut it down to highlight the bad values (at least what I'm assuming are bad values!). Many thanks for anything you can suggest or do to help. My best as always, Ian

Ah, that's a shame. Guess it's a dead end then! Yes that's the very field I'm talking about - I was hoping it could be expanded to offer both callsigns and tail numbers but from you've just said that sounds quite pointless! Sadly (for me at least) FSInn is dead in the water! Will have a sniff around Squawkbox to see what it can offer... Thanks Pete, Ian

Hi Peter, I use WideTraffic to display VATSIM planes on two networked FSX PCs, but I've had problems with the wrong liveries or aircraft types appearing on the second machine. The effect is that (for example) a 747 taxis from one monitor onto the next where it appears as a Cessna. All very irritating, especially during Worldflight or big VATSIM events. I've dug around and think the problem lies with the tail number in the TCAS tables. When I'm flying offline the TCAS tables contain tail number from the aircraft.cfg files for each AI plane. However when I'm online with VATSIM the same field appears to contain the call sign of the pilot, not the tail number, which stops Widetraffic from finding a matching plane on my seconds PC (because it uses the tail numbers in the aircraft.cfg files to match planes and liveries on both machines). I've spoken with the author of WT but he's reluctant to help so I've been mulling over what else could be done to make it work. This got me to wondering whether the call sign is actually needed for anything in FSX or FSInn. All my comms are done by voice and I don't display callsigns on my monitors so I wondered if you could expand the dropdown box in FSUIPC to let me put the tail number from the Aircraft.ini file back in the tailnumber slot of the TCAS tables? This may give WT what it needs to work as it should. It's just a thought - I'm at my wit's end trying to work out a fix for this. It may be impossible or it may be that in doing so the rest of the multiplayer logic falls over in FSX or FSInn but I thought I'd ask in case you think it'd work? Cheers Ian

Hi Pete, The viewpoint offsets starting at x05B0 are marked as No-SimC+ in the offsets list (Not working, hoping for additions to SimConnect). Just wondering if they ever became available? Be quite useful to me if they did. Many thanks Ian

Ta-da! That's got it, thanks Pete. With my axis mapped to Throttle 1, calibrated on page 3 of the Joystick Calibration tab (with no reverser zone) and mapped to throttles 2,3 and 4 I can get it's calibrated value from offset x3320, even with the A/T on. Exactly what I need so job done - thanks again! Ian

Hi Pete, appreciate you're busy with the build - no rush on this but I'll leave you with the info so you can mull it over if you get a chance next week. OK, so I'm using v4.70b, built 15/4/11 The Axis assignment is being done via FSUIPC (none of my axiis are assigned via the FSX controls dialog). The throttle axis I'm using is assigned to 'Throttle' in the Axis Assignment tab and is calibrate on the Joystick Calibration Tab using page 1. As for the offset values, I did a thorough test both with and without the axis 'de-activation' switches. During the tests I verified that the throttle was either still controlling the engines or having no effect as specified vai 310A. The results were:- -----+------------------------------------+------------------------------------+ | 310A = 0 | 310A = xC8 | -----+--------------+---------------------+--------------+---------------------+ | A/T Discon | A/T Engaged | A/T Discon | A/T Engaged | =====+==============+=====================+==============+=====================+ 332E | -14k to +14k | -14k to +14k | -14k to +14k | -14k to +14k | -----+--------------+---------------------+--------------+---------------------+ 3330 | Always 0 | Always 0 | Always 0 | Always 0 | -----+--------------+---------------------+--------------+---------------------+ 088C | 0 to 16k | Controlled by A/T | 0 to 16k | Controlled by A/T | | | Axis has no effect | | Axis has no effect | | | Appears to be 0-16k | | Appears to be 0-16k | -----+--------------+---------------------+--------------+---------------------+ 089A | Always 0 | Always 0 | Always 0 | Always 0 | -----+--------------+---------------------+--------------+---------------------+ 3AE8 | 0 - 1.0 | Controlled by A/T | 0 - 1.0 | Controlled by A/T | | | Axis has no effect | | Axis has no effect | | | Appears to be 0-1.0 | | Appears to be 0-1.0 | -----+--------------+---------------------+--------------+---------------------+ From all these tests I think the documentation for 332A should say that it's pre-calibration not post which leaves us without a bona fide post-calibration but pre-FSX offset to read. Also, 310A definitely disconnects the axis from FSX but doesn't appear to alter the data that's read from any of these offsets. I guess third party apps and hardware deal with calibration it internally (?) Anyway, I'll let you get back to the build! Thanks for your input, let's leave it till sometime next week... Best Ian

Hi Pete It looks like 332E is what I need but it's definitely returning pre-calibration data. The initial range I listed (=/- 16k) was what I assumed to be the full range of acceptable values, the +/-14k range is what I'm actually seeing (which is my pre-calibration throttle axis range). Perhaps it's just a documentation error? Anyway, I've thrown some rough and ready calibration code of my own into my PFD and I'm getting approximately what I need - certainly it appears to be close enough but if you ever have a spare moment it'd be nice to get the true post-calibration data from FSUIPC. Thanks for your help, Ian

Hi Pete, no luck I'm afraid. The results of testing various throttle offsets are as follows (don't forget, I'm using a single combined throttle): 088C (2 bytes) Returns the current throttle setting in FSX. It's unaffacted by throttle axis inputs when A/T is engaged. 089A (2 bytes) Always returns 0 when a/t is engaged 332E (2 bytes) Returns -16383 to +16383 and appears to be pre-calibration (documented as post-calibration, interestingly) For my throttle's full range of movement it returns roughly -14,000 to +14,000 and if I manually adjust it to get a 0 to 1 range it shows 0.5 to 0.95, so I can't really use it. 3330 (2 bytes) Always returns 0 when a/t is engaged 3AE8 (8 bytes) Returns the current throttle setting in FSX (post calibtation - 0 to 1). It's unaffacted by throttle axis inputs when A/T is engaged. In an ideal world I need 332E to be the post-calibration value (0 to 1) so that I can pair it with 3AE8 on my display to get the comparison values I need. Best as always, Ian

Hi Pete Is there any way to get the current calibrated throttle axis position while the auto-throttle is engaged (ie 0-1 rather than –4096 to +16384)? I can't see one in the documentation and the various offsets that support the throttle axis seem to report zero when the a/t is on. (I'm using a single throttle to control all engines). I've written my own PFD and want to display my thrust lever's position next to the a/t setting in a spare corner somwhere. This will allow me to match my throttle lever to the a/t's current setting so that when I disengage the a/t there's no sudden drop or surge in power. Do you know of any way to derive this info, or is there a new offset you could introduce to make the info available? Thanks for any insights you can offer! Ian

Hi Pete I'm trying to get Wideview to match the liveries of VATSIM traffic on my second machine to those on my main FSX PC. However from what I can tell Wideview uses tail numbers to uniquely identify aircraft liveries but VATSIM puts callsigns into that bit of storage instead of tail numbers so Wideview hasn't a chance of matching anything while I'm logged into VATSIM (I imagine it works fine off-line but I only fly-off line when I'm testing). I've written some code that reads the AI aircraft title and uses it to look up the relevant tail number from the aircraft's config file but I can't figure out how to push the tail number into the AI stream. I want to be able to over-write the VATSIM callsigns with tail numbers from my main machine so that Wideview can match them up on the second machine (which has a copy of my aircraft folders). If there's already a mechanism in FSUIPC to do this can you give me a bit more info - there's a bit about it in the programmers guide but unless I'm missing something (usually am) I can't make out how to update existing traffic details such as the tail number. If there's nothing currently in place to do this is there any chance you'd consider adding it at some point? It's be so great to finally have VATSIM planes taxiing across the monitors of both machines in the same liveries (not to mention the same aircraft type!!!) Many thanks for any help you can give, Regards Ian