jordanal

Understand. Do I still do the logging instructions above as well, or just try .236 and see what happens?

Understand all. Will do when I get home from work tomorrow. Bedtime now, can't hang with you 24/7, LOL ;) You never, ever sleep! LOL...

FSUIPC.log at the point of the last crash. I have no proof that this was caused by this FSUIPC beta. This was a new flight to a seldom used airport KORD. ********* FSUIPC4, Version 4.235 by Pete Dowson ********* Reading options from "E:\MS Flight Simulator X\Modules\FSUIPC4.ini" User Name="*** Provided ***" User Addr="*** Provided ***" FSUIPC4 Key is provided WideFS7 Key is provided Running inside FSX (SimConnect Acc/SP2 Oct07) Module base=61000000 Wind smoothing fix is only partially installed DebugStatus=255 47 System time = 17:51:25 47 FLT UNC path = "\\ALCOMP\C\Documents and Settings\jordana\My Documents\Flight Simulator X Files\" 47 FS UNC path = "\\ALCOMP\E\MS Flight Simulator X\" 1000 LogOptions=00000001 1000 SimConnect_Open succeeded: waiting to check version okay 3937 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0) 3937 Initialising SimConnect data requests now 3937 FSUIPC Menu entry added 4015 c:\documents and settings\jordana\my documents\flight simulator x files\Baron - Williamsport - Default.FLT 4015 E:\MS Flight Simulator X\SimObjects\Airplanes\beech_baron_58\FSD_B58TC.AIR 22547 E:\MS Flight Simulator X\SimObjects\Airplanes\PMDG747-400\B747-400.AIR 22547 C:\Documents and Settings\jordana\My Documents\Flight Simulator X Files\KPIT-KORD.PLN 22547 Weather Mode now = Custom 22547 c:\documents and settings\jordana\my documents\flight simulator x files\Pittsburg to Chicago - PMDG 744X KLM - Midflight.FLT 51047 System time = 17:52:16, FSX time = 13:26:03 (18:26Z) 51187 Aircraft="PMDG747-400 KLM" 62297 Advanced Weather Interface Enabled ********* WideServer.DLL Log [version 7.235] ********* Blocksize guide = 4096 (double allowed) Date (dmy): 05/02/08, Time 17:52:23.160: Server name is ALCOMP 15218 Initialising TCP/IP server 15218 Initialising IPX/SPX server 15218 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family 15218 Failed to start IPX/SPX Server 15218 Initialising UDP/IP server 16015 Broadcasting service every 1000 mSecs 17828 Incoming connection Accepted ok (skt=8964) TCP 17828 Connected to computer "MAINCOMP" running WideClient version 6.757 (skt=8964) TCP Correct, crash-to-desktop. Nothing, nada. In less than a second I'm staring at my desktop and taskbar. No error window or report offer. I don't see anything really unusual in the logs above. Mabye you do. I will try the same flight (restart midflight) again tomorrow evening EST after reverting back to prior version to see if the CTD is repeatable. Any particular version? I have most of the recent betas back to the last full version. Regards, Al

Testing v4.235 beta. New flight in PMDG 744X from Pittsburgh (KPIT) to Chicago (KORD) over a cold-front with live ASXsp2. Unfortunitly, I experienced two back-to-back CTDs about 150nm from KORD while cruising @ FL380. No sudden wind-shifts noted or drastic IAS changes from within the 744X up until this point. I don't know what's going on with the two CTDs. It's been ages since I've had any of those. AL

Test FSUIPC4 v4.234 Beta + WeatherSet2 on Wide-client: PMDG Boeing 747-400X - Air France Cruise @ 40K 145nm from destinaion PHNL - Full VNAV descent 1) IAS rapid decrease while passing through 33K (1 time) 2) No Wind speed or direction fluctuations noted from 40K down through 12K (VNAV descent) 3) Wind smoothing (direction) was easily noted (very nice slow change) 4) Rapid fluctuations of wind-speed b/w 5Kts and 12kts; descending final from 1K to 500ft MSL (smoothed before touchdown) 5) Full AP landing was smooth with constand wind direction 6) Conclusions - Good beta version - borometer smoothing needs to be tested by full trans-atlantic crossing (this is where I've always seen this problem) Regards, AL FSUIPC4 v4.234 ini settings: ====================== History=Z3KA5T8JXGGM3VKXUZSD7 GraduatedVisibility=No LowerVisAltitude=0 UpperVisAltitude=25000 UpperVisibility=10000 MinimumVisibility=0 MaximumVisibilityFewClouds=0 MaximumVisibility=0 MaximumVisibilityOvercast=0 MaximumVisibilityRainy=0 SetVisUpperAlt=No VisUpperAltLimit=0 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 WindSmoothing=Yes WindSmoothness=-2 WindSmoothAirborneOnly=No DisconnTrimForAP=No ZeroElevForAPAlt=No ThrottleSyncAll=No WhiteMessages=Yes ShowPMcontrols=No SpoilerIncrement=512 MagicBattery=Yes RudderSpikeRemoval=No ElevatorSpikeRemoval=No AileronSpikeRemoval=No ReversedElevatorTrim=No ClockSync=No ClockSyncMins=5 ClearWeatherDynamics=No FixWindows=No OwnWeatherChanges=Yes TimeForSelect=4 LoadFlightMenu=No LoadPlanMenu=No PauseAfterCrash=No ZapSound=firework ShortAircraftNameOk=Yes TCASid=Flight TCASrange=40 AxisCalibration=No DirectAxesToCalibs=No ShowMultilineWindow=Yes SuppressSingleline=Yes SuppressMultilineFS=No AxisIntercepts=No WeatherReadFactor=2 WeatherRewriteDelay=10 ProcessGlobalWeather=No SimConnectStallTime=1 AdvDisplayHotKey=192,8 FixControlAccel=No ZapAirRange=1.5 ZapGroundRange=0.25 PressureSmoothness=20 TemperatureSmoothness=100 SuppressWindVariance=No TurbulenceRate=1.0 Tested Metar (ASXsp2) Live Download: Default settings +Disable Graduated Visibility +Disable Fog Layer +Max Cloud Layers = 20 ============================================================== PHIK 042253Z 06013KT 10SM FEW029 SCT039 SCT050 24/18 A3009 RMK AO2 SLP188 VCSH RMK INTERPOLATED PHNL 042320Z 050024 06011G17KT P6SM VCSH SCT025 BKN045 FM0500 06010KT P6SM SCT025 BKN050 FM2000 06014G20KT P6SM SCT030 BKN050 Destination (PHNL): PHIK 042253Z 06013KT 10SM FEW029 SCT039 SCT050 24/18 A3009 RMK AO2 SLP188 VCSH RMK INTERPOLATED PHNL 042320Z 050024 06011G17KT P6SM VCSH SCT025 BKN045 FM0500 06010KT P6SM SCT025 BKN050 FM2000 06014G20KT P6SM SCT030 BKN050 No alternate station specified... Winds aloft by waypoint: Winds aloft by waypoint: Waypoint 6K 9K 12K 18K 24K 30K 34K 39K 44K 49K CKH 121@05(14) 116@05(11) 148@06(1) 222@06(-11) 257@11(-23) 238@28(-39) 242@35(-50) 251@67(-55) 256@54(-61) 257@24(-72) HNL 121@05(14) 116@05(11) 148@06(1) 222@06(-11) 257@11(-23) 238@28(-39) 242@35(-50) 251@67(-55) 256@54(-61) 257@24(-72) PHNL 121@05(14) 116@05(11) 148@06(1) 222@06(-11) 257@11(-23) 238@28(-39) 242@35(-50) 251@67(-55) 256@54(-61) 257@24(-72) WeatherSet2 Images During VNAV Descent and full ILS AP landing =======================

Roger that, noted this latest version :!: I hope to test it using the same approach tonight. Pete, Can you reply with the specific settings (names from the GUI) that you would like me to have either on or off? Thanks... AL

My E6700, now somewhat outdated, is running fine at 3.2Ghz with an upgraded HSF. Yea, I've ready plenty of people are overclockin' near 4GHz on air with the new Intel procs. Correct, 3GB seen by WinXP 32bit. But I am running a modified boot.ini and the FSXsp2 exe is now large_address_aware by default, so it does help. I've been running Vista 64bit as my wide-client PC just to get used to it, but I wouldn't run FS on it yet. Maybe after Vista SP1 hits the streets and the knowledgeable hardware guys decide exactly what needs to be stripped out to make it lean, fast processing machine. I think I'm running a total of 22 processes on my WinXPsp2 machine and that it what makes it so fast for FS. Regards, AL

That was by accident. I noticed as I was pasting the ini settings that I didn't have them on. I wish I had for freedback purposes. Too much tweaking today and they got overlooked. I have this Honolulu approach saved so I can restart it anytime. Maybe tomorrow afternoon EST with these settings turned back on. Sure, the FSXsp2 PC is an overclocked E6700 on a Asus P5K-E with 4GB of Corsiar RAM in WinXPsp2 and a EVGA Nvidia 8800GTS (640mb) GPU. Running two Western Digital 10Krpm hard drives, one for FSX dedictated. The addons such as Radar Contact and ActiveSkyX are on a generic AMD PC (Vista) across a Wide-client/Simmconect 1Gb LAN. Scenery addons include XGraphics, GEX, UTX, WoAI and MRAI AI traffic. Regards, AL

Hi Pete, Spent most of the morning tweaking various thing with my FSXsp2 setup along with your latest FSUIPC beta. All seemed to be working well here. No wind fluctuations on this end. This was with ASXsp2 default settings without Graduated Visibility or Fog layer, and max layers set to 20. Below are the pertinent settings I used in FSUIPC and some screenshot that I think came out rather well. Thanks again for your dedication to the hobby. You're scholar and a gent! Regards, Al Jordan ====================================== FSUIPC4.ini (v4.233 beta): ... SuppressCloudTurbulence=Yes MaxIce=-4 MinIce=-4 UpperWindGusts=No SuppressWindTurbulence=Yes WindTurbulence=No SuppressAllGusts=Yes MaxSurfaceWind=0 WindLimitLevel=200 WindDiscardLevel=400 WindAjustAltitude=No WindAjustAltitudeBy=2000 WindSmoothing=Yes WindSmoothness=-2 WindSmoothAirborneOnly=Yes ... WeatherReadFactor=2 WeatherRewriteDelay=10 ... TemperatureSmoothness=0 SuppressWindVariance=Yes TurbulenceRate=1.0 PMDG 744X Approach into Honolulu

Good for you and I'm glad I could help. No problem, take your time with the update.

Nope, nothing special like detents in use. Just reversed axis calibration using my Saitek throttle-quad. Calibraion and axis below. Flaps axis = 1Z. AL [JoystickCalibration] SepRevsJetsOnly=No ApplyHeloTrim=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 Aileron=-16384,-512,512,16383 Elevator=-16384,-512,512,16383 Rudder=-16384,-512,512,16383/16 LeftBrake=-16383,16384/16 RightBrake=-16383,16384/16 Throttle1=-16384,-16384,-16384,16383 Throttle2=-16384,-16384,-16384,16383 Throttle3=-16384,-16384,-16384,16383 Throttle4=-16384,-16384,-16384,16383 Mixture1=-16384,-16384,-16384,16256 Mixture2=-16384,-16384,-16384,16383 PropPitch1=-16384,-16384,-16384,16383 PropPitch2=-16384,-16384,-16384,16383 Flaps=-16383,16384/16 Spoilers=-16384,-14544,-10368,16383/16 SlopeRudder=7 SlopeLeftBrake=5 SlopeRightBrake=5 ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes [Axes.PMDG747-400] 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,11,0,0,0 4=1Y,256,D,12,0,0,0 5=1Z,256,D,23,0,0,0 6=2X,256,D,1,0,0,0 7=2Y,256,D,2,0,0,0 8=2Z,256,D,22,0,0,0 9=2U,256,D,9,0,0,0 10=2V,256,D,10,0,0,0

Seemingly confirmed issue. I dropped back to FSUIPC v4.208 beta (changing nothing else) and restarting the sim with the same PMDG 744X at the same location. I now have full-scale flaps lever travel as depicted visualy on the pedestal. AL

Hi Pete, I think we might have another PMDG unique-coding conflict, specifically between FSUIPC v4.222 and the PMDG 744X. My flaps scale seems to be cut in half. It doesn't matter if I use "Normal" flaps axis or "direct" flaps axis. All other axis seem to be working to full scale and move as expected within the 744X. The flaps calibration "IN" is reads normal +16383 to -16384 and the "OUT" is commanding 0 to 16384 (Rev.) as expected. But, the PMDG flaps lever as drawn on the 744X pedistal, is only moving between flaps 10 and flaps 30 (bottom half travel) along with the ND display showing the same thing, flaps 10 to flaps 30. Something in a recent FSUIPC change seems to affected the PMDG 744X flaps logic. Regards, Al Jordan

Oh yea, I forgot that changed b/w FSUIPC3 and FSUIPC4. That indeed makes sense... AL

Hi Pete, Got a quick question for 'ya. I've noticed something a bit curious about one of the axis letters. I'm just wondering why one of the axis letters is assigned a bit differently in FSUIPC4 than in FSUIPC3? On the same WinXPsp2 machine (simultanious install of both FS9.1 and FSXsp2), the #4 axis (shown below) is assigned a different letter. In FSX it is scanned as "2V". In FS9, it is scanned as "2R". Same hardware (does this for my current Saitek Yoke and my older CH Yoke). All other axis and devices are scanned identically. I disable FS joysticks in both FS menues. Difference has been seen over many different versions of both FSUIPC3 and FSUIPC4. Difference is also noted on weather using FSXsp1 and FSXsp2. Letter was also different wether assigned as Direct or Normal axis. Thinking out-loud, there must be some tiny bit difference in the way FSUIPC4 assigns letters than FSUIPC3. Even axis scanned after this particular one remain the same. The only reason I noticed this is becuase I like to flat-copy the assignments and calibrations sections between FSUIPC4 and FSUIPC3 to quickly keep both FSUIPC.ini files up to date. Everything works great in both versions when I do this, except I have to keep reverting this one axis letter assignment between "R" and "V" and I thought you might find this curious as well. Not a big deal whatsoever, just wanted to mention it. [Axes] 0=2X,256,D,1,0,0,0 ; AILERON_SET 1=2Y,256,D,2,0,0,0 ; ELEVATOR_SET 2=2Z,256,D,9,0,0,0 ; THROTTLE1_SET 3=2U,256,D,10,0,0,0 ; THROTTLE2_SET 4=2R,256,D,17,0,0,0 ; PROP_PITCH1_SET . . . Regards, AL

Ahh, that explains why in works in FSUIPC4 and not in FSUIPC3.... Yup, I got it backwards, not realizing the fix was already in FSUIPC4 and you were migrating the fix back to FSUIPC3.... AL

I just want to add, since Pete helped be get my Saitek Yoke and Throttles working the other day using direct axis for everything, I have been successfully using FSCUIPC direct axis with the LvL-D 767 on FSX (sp1) with no ill affects. The issue described with the inactive AP on the Airleron axis is only a FS9 issue. I too had run into this exact issue a year ago on FS9 and like others, fixed it by assigning LvL-D axis to Normal. I hope none of these recent changes in FSUIPC will adversly affect the 767 in FSX while using direct axis. Downloading 4.212 now to verify with my current FSUIPC4.ini to validate soonest. Regards, AL

That's simple enough, thanks... AL

Good morning Pete, I'm converting my "FS Normal" axis assignments to "Direct" assignemnts. I must be blind this morning but I can't find a list of ID's used in "Direct" mode. For instance, Throttle1_Set appears to be 9, Throttle2_Set appears to be 10, Airleron and Elevator assigned 1 and 2 respectively. Is there a complete list of "Direct" ID's in the Docs and I'm missing it? If not already elsewhere, could such a list be appended to "List of FS Contols" doc? Thank you, AL

LOL, you keep replying before I can decide what I'm gonna test next! Glad you have it figured out. I think at this point, I'm gonna change over to "Direct" axis for now and see if I have any problems with the advance aircraft. I just went back through the Level-D forums and it appears there was an issue a while back but it was reported to be fixed in one of your later FSUIPC updates. Adding the exlude to Mixture and Prop does sound like a good approach though, in case "Direct" remains problematic. BTW, having disabled joysticks within the FS menu, which is the prefered method for axis in FSCUIPC, "Send to FS Normal" or "Direct"? Is one less overhead, or perhaps more efficient, than the other? Thanks again for your help Pete. Happy New Year to you and yours... Regards, Al Jordan

That's because you are using the wrong controls. All the "Axis .... Set" controls only have positive input. They correspond to the controls FS assigns. This is why folks use FSUIPC to get reverse on the axis, as it converts the AXIScontrols into the older, original (FS98) controls which have a reverse range. Try using the controls I suggested. Don't just stop at the "Axis ..." ones. Pete Um, if I'm following you correctly, I'm getting the same results (negetive values issue) using the following: [Axes]...10=2V,256,F,65923,0,0,0 ; PROP_PITCH1_SET[buttons]....89=P2,22,C65923,-4096 ; PROP_PITCH1_SET Rev90=U2,22,C65923,0 ; PROP_PITCH1_SET Idle Regards, AL Ahah! I got it, changed the above axis to "Direct" - "10=2V,256,D,17,0,0,0" and that worked! -4096 reverses the axis. But now I'm gonna have issues as I mostly use the PMDG and Level-D advanced aicraft and I know these don't like direct-mode axis... Al

Hi Bob, Pete provides a good example of panning with the hat switch in the user guide with it's own special Note box on the subject (buttons 32 to 39). If you need further help with it, you might be better off starting a dedicated thread on the subject to get Pete's attention. This will also help keep the subjects a bit seperated and easier to read. Al