John Veldthuis

Something is really messed up. The altitude says you are skipping just above the ground a long way from your target height. You speed is way below your target and is why the plane it pitching down to speed up. Even your flight FD is telling you to go down. And you fpm gauge is clearly out of whack to give you that sort of figure. Certainly nothing to do with the yoke or FSUIPC (which this forum is for)

Easier way is not to install the Saitek software at all and then just use the compound buttons in fsuipc as has already been discussed on this site.

What do you normally do then? Maybe I can't reproduce the crash because I am doing things in the wrong order? I know you said you ran ASX on a separate PC. Do you usually get it fully running and waiting for FSX first? Maybe the problem is related to the FSX/FSUIPC4 initialisation phases only? Possibly I've not been testing that part in the same way. Please let me know and I'll re-run the testing on my one and only FSX SP2 PC. Regards Pete I normally load ASX on the remote PC and let it grab its weather. Once it is done I load the flight plan into ASX so that it knows where I am going from/to and can grab the VatSim data as well for the online flight. I then let it transfer its theme over and once it is complete only then do I start FSX up, select the plane, load the flight plan, set date/time, fuel, weight and then click fly. The crash would happen just after the first green bar starts to scroll across the screen. Good news is that I installed the 4.2.5.2 FSUIPC.dll and the ASX SP3 beta and this combo seems to have fixed the issue. I can again turn on all the suppression check boxes with no crashes. It certainly had some issue with ASX as it was okay with the internal FSX weather downloads. Anyway whatever it was seemed to be cured for the present.

Okay thanks, Will grab the ASX SP3 tonight when I get home from my meeting. I tried smoothing both on/off in ASX and also some other changes but no result. Will redo everything with the SP3 version. Will also try loading FSX 1st and then letting ASX run as well.

My reason is that there is nothing below the detents to use except the buttons. There is no calibration down there so if you wish to use some of the throttle as reverser then you have to be very careful when bringing the throttles back to zero thrust. It is far easier to bring them back to their detent and when you want reverse just pull them down into the buttons and let FSUIPC do the work. It was not hard at all to set up. Just set a button press for the lever to decrease the engine (DECR from memory) and then I also add set throttle to 0 when released to ensure that it goes to zero.

One thing occurs to me. When you are doing these tests, are you always starting with FSX in the same place, or close, when ASX is initialising the weather? Could it possibly be something in the ASX data itself which is acting as the trigger, something which possibly was different when you were testing the earlier Betas? Could you try tests where you move your aircraft a long way from your normal starting position before starting up ASX? Maybe even a sampling of different locations throughout the World? Pete I have tried it starting at NZAA, KLAX, KSFO and get the same result every time.The way I start it up is to load up ASX on the remote machine and let it get the weather, select the flight plan I am going to use and load that and transfer over the theme from ASX. Once complete I go and start FSX, select the aircraft, flight planner and select same plan again, Set date/time, fuel and weight and then click Fly Now. FSX loads up and if any of the selections noted are active it starts to display the green line saying ASX is starting its weather update and then promptly crashes. If I have none of them turned on I can let it load the weather and all is fine and it will run for ages but if I go into FSUIPC and turn one on after about 20-40 seconds I get a crash.

The 3 seconds per Knot/Degree means that sudden wind changes should only happen at 1 degree per 3 seconds as I understand and is what I have seen. This works okay. However if I turn on any of the suppression stuff, even just say gusts, then I get crashes. Any one of the suppression ones by itself is enough to trigger the crash. I will grab the newer beta version and give that a try and get back to you. Oh the other thing is that it works fine with the standard FSX weather. It is only an issue when using ASX. Okay, Just tried the 4.2.5.1 version and same result. Works okay with FSX internal downloaded weather but crashes with ASX putting weather in. I have to say that this is a completely fresh install with no add ons except PMDG 744X on the PC and ASX on the remote PC. I installed FSX RTM and SDK, then SP1 and SDK SP1, and then finally SP2 and SDK SP2. All the updates to windows have been done and latest video drivers installed. I got the same results before the re-install just when the final 4.2.5 went out. The betas before that worked 100% fine.

Have done some more testing. I can turn on OwnWeatherChanges=Yes if I don't turn on any of the things below. On the Winds tab. "Suppress these wind effects" turbulence, gusts, variance On the Clouds tab. Suppress all Cloud Turbulence. I can turn on Smooth Wind changes near aircraft and have it set for 3 seconds per knot/degree.

Okay I have found the line that certainly turns the crash on. If I change OwnWeatherChanges=No to OwnWeatherChanges=Yes Then I get the crash. I would assume turning this to No turns off any weather changes that FSUIPC makes to FSXs weather.

Whoops, Must ensure spell checker is on next time. It usually picks them up. Made it worse actually. Did not crash but hung the program so that in the end I had to log out to kill it off. Task Manager did not even stop it. Yes I am running the SP2 version and I know I did have it fully installed at one point because I remember checking. I had an idea though and I took the fsuipc.ini file out and made it rebuild itself. I started it up and everything works. I then added my button section back in and tried again and still works. So added the joystick calibration section back and still works. I am going through the rest adding them back in a bit at a time to find the cause but as I have to shut down and restart the program each time it is taking time. Below is what I still have to check out. Maybe something stands out? [General] History=MU39GQN3WVU9MXQ79SL6S FixControlAccel=No GraduatedVisibility=No LowerVisAltitude=0 UpperVisAltitude=0 UpperVisibility=0 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=Yes MaxIce=-4 MinIce=-4 UpperWindGusts=No SuppressWindTurbulence=Yes SuppressWindVariance=Yes WindTurbulence=No TurbulenceRate=1.0 SuppressAllGusts=Yes MaxSurfaceWind=0 WindLimitLevel=200 WindDiscardLevel=400 WindAjustAltitude=No WindAjustAltitudeBy=2000 WindSmoothing=Yes WindSmoothness=-3 WindSmoothAirborneOnly=Yes PressureSmoothness=0 TemperatureSmoothness=0 DisconnTrimForAP=No ZeroElevForAPAlt=No ThrottleSyncAll=No WhiteMessages=No ShowPMcontrols=No SpoilerIncrement=512 MagicBattery=No RudderSpikeRemoval=No ElevatorSpikeRemoval=No AileronSpikeRemoval=No ReversedElevatorTrim=No ClockSync=No ClockSyncMins=5 ClearWeatherDynamics=No OwnWeatherChanges=Yes TimeForSelect=4 LoadFlightMenu=No LoadPlanMenu=No PauseAfterCrash=No ZapSound=firework ShortAircraftNameOk=No TCASid=Flight TCASrange=40 AxisCalibration=No DirectAxesToCalibs=No ShowMultilineWindow=Yes SuppressSingleline=No SuppressMultilineFS=No AxisIntercepts=No WeatherReadFactor=2 WeatherRewriteDelay=10 SimConnectStallTime=1 [AutoSave] AutoSaveEnabled=No [GPSout] GPSoutEnabled=No Port= Speed=4800 Interval=1000 PosTo6Decimal=Yes Sentences= [WideServer] WideFSenabled=Yes AdvertiseService=1 Port=8002 Port2=9002 [Axes] 0=0X,256,D,7,0,0,0 1=0Y,256,D,8,0,0,0 2=1Z,256,D,22,0,0,0 3=1U,256,D,9,0,0,0 4=1V,256,D,10,0,0,0 5=2X,256,D,11,0,0,0 6=2Y,256,D,12,0,0,0 7=2Z,256,D,23,0,0,0 [ClientNames] 1=TOWER5

Okay, have rebuilt my PC and installed everything from fresh so there is no possible way of outside things affecting it. Have ASX running on a remote PC. Everything works 100% without ASX running no issues. Load ASX weather and as soon as it starts injecting it into FSX, FSX will crash with the following Problem signature: Problem Event Name: APPCRASH Application Name: fsx.exe Application Version: 10.0.61472.0 Application Timestamp: 475e17d3 Fault Module Name: StackHash_c709 Fault Module Version: 6.0.6000.16386 Fault Module Timestamp: 4549bdc9 Exception Code: c0000374 Exception Offset: 000af1c9 OS Version: 6.0.6000.2.0.0.256.1 Locale ID: 5129 Additional Information 1: c709 Additional Information 2: 0f892d40c3ecb9688ec909cc1e5a061b Additional Information 3: c2fb Additional Information 4: 1fc67a5fcf98239a45d2aae228698c39 The reason why I think it is a FSUIPC fault is that everything was working fine with the exact same ASX setup until I installed version 4.2.5.0 of FSUIPC. all the betas before it worked fine. I was about to try out a previous version but I had deleted them when the final came out. The computer crash meant I had to reinstall so that was a chance to find out that. If I remove FSUIPC.DLL from the modules folder and let ASX run it injects the weather fine and I get no crash. Put it back in and bang straight away. FSUIPC log up until crash ********* FSUIPC4, Version 4.25 by Pete Dowson ********* Reading options from "G:\Microsoft Flight Simulator X\Modules\FSUIPC4.ini" User Name="John Veldthuis" User Addr="xxxx" FSUIPC4 Key is provided WideFS7 Key is provided Running inside FSX on Windows Vista (SimConnect Acc/SP2 Oct07) Module base=61000000 Wind smoothing fix is fully installed DebugStatus=255 78 System time = 12:30:42 94 FLT UNC path = "\\TOWER7\MSPLANS\" 94 FS UNC path = "\\TOWER7\G\Microsoft Flight Simulator X\" 1217 LogOptions=00000001 1217 SimConnect_Open succeeded: waiting to check version okay 2886 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0) 2886 Initialising SimConnect data requests now 2886 FSUIPC Menu entry added 2933 G:\Microsoft Flight Simulator X\FLIGHTS\OTHER\FLTSIM.FLT 2933 G:\Microsoft Flight Simulator X\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR 12917 G:\Microsoft Flight Simulator X\SimObjects\Airplanes\feelThere pic 737-300\B737-3A00A.AIR 23104 C:\Users\John Veldthuis\Documents\Flight Simulator X Files\fp_NZAA-NZWN.PLN 44913 System time = 12:31:26, FSX time = 07:30:45 (20:30Z) 45069 Aircraft="feelThere Boeing 737-300 Hooters Air" 45553 Weather Mode now = Custom Does not matter which aircraft I use they all do the same.

Well I am going to have to wait a bit now. I just updated my BIOS and it decided it wipe out one of the members of my RAID0 array so looks like I am going to have to rebuild it as I cant get it back without deleting the other. It may fix the issue by itself anyway as my FSX stuff was not backed up.

FSX has suddenly started crashing on me and the only change has been FSUIPC from the last beta and the final version. It appears to crash just as ASX starts to inject the weather into the sim as I get the first part of the message. If I restart it then the program will work but I cannot get my own program to connect via simconnect but programs using FSUIPC dont seem to be affected. The weather does not get inkected the second time around so it looks like ASX cant connect either. If I reboot the machine then I get exactly the same result over again. Anyone else seeing this problem?

Works well for me most of the tie as well with just the odd little increase/decrease in plane IAS and small deviations to the left right but nothing the AP cant handle. I have noticed however that the pressure seems to jump wildly that never used to be there. Just sitting at the airport you can hear the engines changing speeds on idle. Look at the altitude indicator and it jumps nearly 1000-2000 feet and then short time later drops back. This is with the PMDG744X as well. Have turned on pressure smoothing to see if this helps with the default value of 20.

I'm planning a new PC at present, and I'm looking at overclocking -- not by me, mind. I want it done by the supplier so I can blame them! ;-). What's the clock speed you got up to, then? The supplier I'm looking at uses water cooling and gets a Quad up to 3.75. I've read you can push to 4 GHz. Is the 4Gb memory fully used? I thought you could only use 3 Gb with 32-bit windows -- 2Gb for programs and the rest for Windows? I'm seriously thinking of asking for Vista64. I don't much like Vista, but reports seem to suggest that the 64-bit version is solid. It'd be up to my supplier to make sure they had the drivers, obviously. Best Regards Pete I am using a Q6700 Quad at standard and get good rates. Have it locked at 26FPS and get that all the time in the dropping to around 18 on the ground. Have everything nearly full including water 2.x, autogen, etc. I have just now put in another 2GB memory and with Vista Ultimate it is reporting as having 3.58GB memory. I have a 8800GTX card.

Okay that seemed to do it for me. Did a flight from SBNT to FHAW and while there was a couple of jumps in airspeed while climbing the cruise was fine. Descent was also fine with a couple of small pushes of to either side but barely noticeable. Had all three suppressions on in the winds and turb in the clouds.

Yes I had both turbulence and gusts suppressed in the winds tab but not in the clouds tab. Will try that and see what happens. Currently running 4.2.3.1 and did not try it before that.

I have no trouble at all unless I use ASX with real weather and then only when descending. Once I get down to around 14,000 the plane seems to have a mind of its own and even the autopilot can not keep it straight. Have attached a screen shot. To me winds were steady from one direction, I had suppress gusts on and 1degree/3secs. After this screen shot I tried to get back on track but went one way then the next. As soon as I turned off the wind smoothing all was well again. As I said, Everything thru takeoff, climb and cruise and only on descent did this happen. Had it happen two for two now.

Thanks Pete, I had not thought about using the logging but it is obvious now you mention it. I checked and the VIEW_MODE and VIEW_MODE_REV are the ones I want and now everything is working fine. What I am trying to do is use the B1/B2 switch on my Saitek Yoke to allow me to change views when the mode switch is in mode 1 and as I have my throttle quadrant on the left due to desk space, also use it to control the elevator trim in mode 2 so that I can use 1 hand on the yoke and the other on the throttles and still keep the PMDG 744X trimmed properly on the landing.

I am trying to set up a compound button for my PMDG 744X and cant get one command to work. I want to program a double switch to cycle through Prev/Next View and also to allow Elev Trim Up/Down The Elev Trim Up/Down works fine but the view does not cycle. I think I have the right command but am now not 100% sure. My INI file has the following to allow this 21=CR(+1,9)1,5,C65615,0 ; Trim Up, Mode Button = 2 22=CR(+1,9)1,4,C65607,0 ; Trim Down, Mode Button = 2 23=CP(+1,8)1,5,C65827,0 ; Next View, Mode Button = 1 24=CP(+1,8)1,4,C65828,0 ; Prev View, Mode Button = 1

The mode button just shows up as normal button presses. They just stay on. Read the FSUIPC advanced stuff and look up compound buttons. This is what I am using and you can do wonders with them. The below from the FSUIPC4.ini file maps the left hand button to send either 1, 2, or 3 depending on if mode switch 1=CP(+1,8)1,0,K49,8 2=CP(+1,9)1,0,K50,8 3=CP(+1,10)1,0,K51,8

Yes I have the assignments down in FSUIPC. I have just double checked and the only axis I have enabled in FS are the elevators and ailerons. Everything else is not assigned and in fact the one throttle controller that has the flaps on it is disabled in FS. I did not want to go back to the FS assignments as it does not give me reverse thrust like FSUIPC does.

Sounds like those settings are loading from your "start up" flight. Just set everything they way you want to start, then save a flight flagging it as the start-up one. FSUIPC only acts on axis inputs when they change. Your initial positions are set by your start-up flight. Regards Pete Okay tried this. Loaded the default Cessna and set throttle to zero and flaps to up. Then saved these back as the default flight. However I still have the same issue. The throttles are on and the flaps are about 1/2 way as soon as I load the plane and stay that way until I move any lever. As soon as I do that everything goes back to where it should be. Only have to move 1 lever to affect the lot.

When I start up any plane I find that the throttles are already on and the flaps are also set to a position. If I use the 747 The flaps are at about 10 degrees and enough power to start moving. To get out of this I have to move the levers from their zero position to any setting and then back to the zero position and all is okay till the next time. I have done the calibration through FSUIPC for all the axis but cant find a way to avoid this. If I dont use FSUIPC and use the axis in FSX then it works fine but does not give me what I want in the way of reversers. Anyone know how to force these initial values to zero on startup?

Okay, Can report I have everything back up and running including Active Sky X. Had to do it the hard way though by un-installing everything, removing all traces of files on hard drives in all the various places, manually going through the registry and removing anything with simconnect in any part of it. Then ran CCleaner over the registry a few times and removed all the invalid links and stuff from removing everything. Then a complete re-install of FSX/SDK and then FSX SP1 and SDK SP1A. All up and working. Now only have to go through and add back in all my extra scenery I had installed and the few planes I had. Oh well at least it works again. Cheers from New Zealand