Björn

The return flight went a-ok as well. Looks like the problem is eliminated. Thanks for the help, Pete!

Sorry for the late reply, Pete. With a heavy heart, I've given SP2 another shot. Installed it, defragged the disk and configured it (fresh fsx.cfg). The performance issues seem to be gone and I'm just taking a test flight from EDDV to LKPR with RC4 and ASX running in the background, and so far, it's looking really good, apart from some very short, normal ASX-induced hiccups. It felt really great passing my "dead end" at ERF without a hitch. Ram usage is fairly normal as well. I'm still in the air (it's kind of cool having two PCs... :)) and I'll certainly report back when I'm back on the ground. Maybe I'll even make the return flight right after for testing. - Edit: Parked and secured now. No freeze-up at all, looks like SP2 did the trick. Thank you for your help, Pete!

I thought I was taking away activity by running the tools via network instead of in the background. So basically, increasing the buffer size won't solve my problem. Well, I know about SP2, but it brought me nothing but trouble, even after a veryveryveryvery "by the book" reinstall of everything. I began encountering microstutters when there were none before and, most important of all, I had to disable ground shadowing to make my AI traffic show up at add-on airports - not much of an acceptable solution for me, since AI traffic is one of the most important elements for me in FSX. I still have access to the SP2 SimConnect though (the Installer from the SP2 SDK) as well as an entire zipped up FSX SP2 folder (for backup purposes and/or if I need to cannibalize some SP2 files). I think I'm going to give SP2 SimConnect a try, but I have a bad feeling about ASX. Björn

The thing is, that I haven't done anything regarding adding scenery and changing graphics settings between the pre-WideFS state (which, as I said worked fine) and the current state. I'd like to look into the "TCP/IP buffers" matter. Could you tell me more about it? My page file is set at a fixed 3072Mbytes. I think it's enough. Yes, there are a lot of stations around. I'm going to fly the route without ASX running the next time and report back. Thanks for the help so far, Pete. Björn - Edit: The PC and laptop are connected via wireless LAN. Could this be a factor?

Hello Peter, I'm experiencing a strange problem with FSUIPC 4.306. Every time I get to a certain distance from a certain fix on my flight plan, my FSX crashes displaying the message that my computer has run out of Ram. It's not the first time I've flown on that route, it's one of my favourite airliner routes and I could fly it blindly by now. I've never had problems before flying on it, but after I purchased and installed Radar Contact 4.3 and FSUIPC4 + WideFS7, the troubles started. Not only on this single route, but also before that, on my inaugural flight with RC4 (again, the OOM error, but I blamed it on too much AI traffic when I passed by KORD on approach into KMDW). I think my system is well up to the task (E6600 overclocked, 2Gb PC800 Ram, 8800GTS 640Mb overclocked, XP SP3) and my FSX (SP1) used to show occasional OOM errors, but only without having the "/3GB /Userva=2560" and "FSX can allocate more than 2Gb of Ram" tweaks applied. With those fixes, the sim runs a-ok and error-free. Anyway, upon deciding to purchase RC4.3, I also decided to turn my FSX PC into a WideFS/Simconnect server and let my laptop (also up to the task) run ASX (instead of my main PC) and RC4.3 to free up some more system ressources for FSX. I needed to fiddle quite a bit to get everything running, but everything worked in the end. ASX connected to FSX via SimConnect, like it should and RC4.3 ran via WideFS7 like it should - well, except for the FSX crash. When I first encountered this problem, I suspected it being a driver (running a beta NVidia driver, this was a fairly possible cause) or RC4/ASX error, so I tried again without running those two extra tools and a new graphics card driver...the result was the same - OOM. I then reinstalled FSUIPC4.3, but without registering both FSUIPC and WideFS, and started another try running only ASX via SimConnect - the error didn't occur. Today, I wanted to reproduce the error, but with extensive FSUIPC logging (all options) enabled. I encountered the same error again, but being the idiot I am, I didn't back up the log and started FSX again afterwards (to check something else) - the result: The log vanished. :oops: Yet, since the error is perfectly reproducable, I'm gonna report back in tomorrow with FSUIPC, WideServer and WirdClient logs. Do you need anything else, like a SimConnect log? I hope this posting is already giving you an idea about the nature of the error. Regards, Björn P.S: At the moment of the FSX crash, Ram usage is at 94% - a normal level. P.P.S: The route is from EDDV to LKPR and the crash occurs about 60 miles from the first fix (ERF). P.P.P.S: I've also tried the 4.3 version of FSUIPC - same results.