My goodness, I didn't follow this topic for a few days and now we are at 20 pages and some sort of solution...? Can anyone tell me what exactly is the solution? Should I put that beta dll in my FSX folder or something...? What's the story?

Yes, just replace your version (backup) with the latest beta.Really Pete is a genius.

My goodness, I didn't follow this topic for a few days and now we are at 20 pages and some sort of solution...? Can anyone tell me what exactly is the solution? Should I put that beta dll in my FSX folder or something...? What's the story?

I was about to ask the very same thing lol :-) I got another couple of those darn errors close to eick airport (eiresim) today and if fsuipc does the trick Pete deserves a gold medal !

Thank's Pete. Just had an test flight, PANC-KSEA with NGX and ActiveSky E. in use. Lod 4.5, Mesh set to 5m, Autogen on Very Dense, from Aerosoft scenery with ASE to PNW land, on all previous flight's, CTD at Orcas area, right after passing YYJ. Now with 'c vers. inside i had a nice landing at KSEA without any problems at all.Again, Thank you Pete.

********* FSUIPC4, Version 4.749c by Pete Dowson *********User Name=XXXXXXXXUser Addr=XXXXXXXFSUIPC4 Key is providedWideFS7 Key is providedRunning inside FSX on Windows 7Module base=61000000 16 System time = 29/11/2011 17:39:37 31 FLT UNC path = "\\MASTER\Users\Stein-Ove Rud\Documents\Flight Simulator X Files\" 47 Trying to connect to SimConnect Acc/SP2 Oct07 ... 47 FS UNC path = "\\MASTER\D\Flight Simulator X\" 265 LogOptions=00000000 00000001 265 Wind smoothing fix is fully installed 265 G3D.DLL fix attempt installed ok 265 SimConnect_Open succeeded: waiting to check version okay 265 Trying to use SimConnect Acc/SP2 Oct07 1154 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) 1154 Initialising SimConnect data requests now 1154 FSUIPC Menu entry added 1186 \\MASTER\D\Flight Simulator X\FLIGHTS\OTHER\FLTSIM.FLT 1186 \\MASTER\D\Flight Simulator X\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR 28813 \\MASTER\D\Flight Simulator X\SimObjects\Airplanes\PMDG 737-700NGX WL\B737-700WL.AIR 35225 System time = 29/11/2011 17:40:12, Simulator time = 09:43:56 (18:43Z) 35225 Aircraft="Boeing 737-790NGX Alaska Airlines (Timbers Jet) Winglets" 100465 Sim stopped: average frame rate for last 30 secs = 27.2 fps 104568 Starting everything now ... 106206 Advanced Weather Interface Enabled 133194 Weather Mode now = Global 173442 Weather Mode now = Theme 173910 Weather Mode now = Global 5507927 **** G3D Bad pointer: 0x24759BB2 5507927 Last file="D:\Flight Simulator X\SimObjects\Airplanes\PMDG 737-700NGX WL\model\PMDG_737_700WL" 5508115 **** G3D Bad pointer: 0x25779BB2 5508115 Last file="D:\Flight Simulator X\SimObjects\Airplanes\PMDG 737-700NGX WL\model\PMDG_737_700WL" 5508224 **** G3D Bad pointer: 0x09321FF3 5508224 Last file="D:\Flight Simulator X\SimObjects\Airplanes\PMDG 737-700NGX WL\model\PMDG_737_700WL" 5508349 **** G3D Bad pointer: 0x26CF9BB2 5508349 Last file="D:\Flight Simulator X\SimObjects\Airplanes\PMDG 737-700NGX WL\model\PMDG_737_700WL" 6625160 Sim stopped: average frame rate for last 6522 secs = 27.3 fps 6629543 Weather Mode now = Theme 6629543 \\MASTER\Users\Stein-Ove Rud\AppData\Roaming\Microsoft\FSX\Previous flight.FLT 6648341 System time = 29/11/2011 19:30:25, Simulator time = 13:52:01 (21:52Z) 6648341 *** FSUIPC log file being closedAverage frame rate for running time of 6554 secs = 27.3 fpsG3D fix: Passes 141401, Null pointers 0, Bad pointers 4Memory managed: 12230 Allocs, 12230 Freed********* FSUIPC Log file closed ***********

You can add me to the list of people who think this fix should be in the registered version of FSUIPC only, you really do deserve recompense for finding this work-around Pete, it's been plaguing FSX users for many years and it seems you finally may have cracked it.

All I want to know is where I buy a registered version and how to install this working beta fix afterward. Pete, you are a real hero if this pans out as well as it seems to be at this point. We won't be able to say enough how much difference you will make.Kind regards,

In case you want to buy (recommended, it offers so much more), maybe get it here. http://secure.simmar...n-fsuipc4.phtml The link is from Pete's site, so it should be ok. Available since: 10/14/2006. To clarify, the fix works in the free version, so buying the soft would just show your attitude towards Pete's very noble one.

Where does it go? In the FSX root file?Kind regards,

Get the main installer first (FSUIPC4 4.70b), then replace the FSUIPC4.DLL in the modules folder with the one from the fix.As always, 'run as admin'.

Where does it go? In the FSX root file?Kind regards,

Stephen, You just need to make sure you have at least version 4.7 of the fsuipc.dll in your Modules folder. Then you need to download and copy the fsuipc4749c.dll to the Modules folder and overwrite the version there. Go fly. The fsuipc4749c.dll is located in one of Pete's posts on page 18 or 19 of this thread. If this works like he was hoping it would, he will probably come up with a new version you can download on his site. I just purchased a license.Best regards,Jim

I've been seeing a lot of MyTrafficX aircraft showing up after the bad pointer. I just upgraded to their latest version and wondering if something is wrong with their aircraft.

No I doubt it. The data being processed at the time of the crash may originate from the file logged, but I am pretty sure it isn't the cause of the corruption -- something else is. I was hoping to be able to pinpoint it and so get closer to the cause, but the damage done leaves no useful clues I'm afraid. To find out what is actually corrupting them one would have to protect the data in such a way that the error occurred when it was trampled on, not when the trampled data is used. I can do that sort of testing with a debugger and the source of the program to manipulate, but of course I don't have the latter.I'm going to revise the logging so that is logs close-timed groups of such errors as one, and doesn't include either the bad pointer value or the misleading filename.RegardsPete

Yes, just replace your version (backup) with the latest beta.

Currently the only link to the beta is somewhere backwards in this thread. The version needed at present is FSUIPC 4.749c.Later on if I'm awake enough I'll build one with better logging and put it up in the Download Links subforum over in my Support Forum. It'll be 4.749d as I'm not quite ready yet to move on to 4.75 (that will be a new release with updated documentation and installer, but probably not till January).Note that when a d update is available in the Support Forum the links in this thread to the c version will no longer work.RegardsPete

What would it take to get a source file from Microsoft? I mean, is it really that hard? Not getting the whole sim as a source code, but only the needed part.Wouldn't Microsoft see that as a show of good faith towards FSX users, maybe in light of making them "believe" towards their new simulator... I don't want to start a debate now (wrong forum for that), but only wanted to point out if getting a source file is that hard?

well i normaly dosent get problems whit 4.5000 (default) and as i test lowi whit lod at 8.500000 no crash so it seems to work now whit the higher lod. as i was testing for some on aerosoft site and seemed to be texture and plane there was to bussy at 0.5nm from oev16. but whit this fix it just runs so far

What would it take to get a source file from Microsoft? I mean, is it really that hard? Not getting the whole sim as a source code, but only the needed part.Wouldn't Microsoft see that as a show of good faith towards FSX users, maybe in light of making them "believe" towards their new simulator... I don't want to start a debate now (wrong forum for that), but only wanted to point out if getting a source file is that hard?

Not a chance in hell.

Get the main installer first (FSUIPC4 4.70b), then replace the FSUIPC4.DLL in the modules folder with the one from the fix.As always, 'run as admin'.

If we already have fsuipc4, we can simply just replace. Is that correct?Pete, this is a fine accomplishment for which we are all grateful. You should see an increase in sales too.