FSUIPC 4.70 crashing FSX

[hastings]

Hi Pete!

Just wanted to alert you to a problem that I had with the new version of FSUIPC (my prior version was 4.53). I installed to FSX SP1 and FSX crashed during initial loading giving simconnect.dll as the culprit. Initially thinking it was simconnect, I reinstalled it from the SDK 1A and got the same error. Figuring I now had a corrupted FSX, I went and did a Norton Ghost PC restore to get back to the prior state. I then reinstalled only version 4.70 (nothing else) and got the same error. Reverting to version 4.53 took care of the problem.

I'm pretty sure I can repeat this, and will get a log file to you when I can. If there is any additional information that I need, please let me know.

Cheers,

Mike T.

[Pete Dowson]

Just wanted to alert you to a problem that I had with the new version of FSUIPC (my prior version was 4.53). I installed to FSX SP1 and FSX crashed during initial loading giving simconnect.dll as the culprit. Initially thinking it was simconnect, I reinstalled it from the SDK 1A and got the same error. Figuring I now had a corrupted FSX, I went and did a Norton Ghost PC restore to get back to the prior state. I then reinstalled only version 4.70 (nothing else) and got the same error. Reverting to version 4.53 took care of the problem.

4.53 is actually far less trolerant of SimConnect inconsistencies than 4.70. But both would work far more effectively with SP2 SimConnect. Why are you only at SP1 level in FSX?

The main problem with SimConnect which can cause crashes during loading is an error which was known to Microsoft, and is related to the Trust mechanism. It's a timing problem which they tried to fix and failed to do so before disbanding Aces, but it was much improved in SP2. The reason you aren't having it happen in 4.53 is undoubtedly simply because it's already got past the "trust" checking on that one so doesn't run in to the timing clash.

I believe there might be two ways around the problem, judging by other reports. (It's never happened to me or many others so it isn't easy to be definitive):

1. Persist: Keep re-running FSX and telling it to continue until it does. Thereafter it isn't a problem.

2. Find your DLL.XML file (in the same folder as the FSX.CFG file. If you have difficulty show me the FSUIPC install log and I'll point out the correct path), and temporarily re-name it, e.g. to DLL1.XML. Then re-run the FSUIPC 4.70 installer. It will make a new DLL.XML which loads only FSUIPC4. Run FSX. That should get past this glitch. Then you can delete the new DLL.XML and rename the older one back.

Note that you might need to run Windows Explorer "as administrator" to achieve #2.

Regards

Pete

[hastings]

Hi Pete,

Thanks for responding to my post.

To answer your question - the reason I was at FSX SP1 was the fact that there are several FS9 New England Airports that displayed fine with SP1 but not with SP2. This was the only reason I had not installed SP2 until now.

Since this amounted to only a few sceneries, I decided to install FSX SP2 "for the greater good", and get the benefits of both the latest FSUIPC and FSX SP2.

All works properly now with the latest FSUIPC.

Appreciate your assistance!

Cheers,

Mike T.

[Pete Dowson]

To answer your question - the reason I was at FSX SP1 was the fact that there are several FS9 New England Airports that displayed fine with SP1 but not with SP2. This was the only reason I had not installed SP2 until now.

There is a program called "AddonConverter" ( http://www.flightsimtools.com/adconvx/ ) which you might want to investigate.

Since this amounted to only a few sceneries, I decided to install FSX SP2 "for the greater good", and get the benefits of both the latest FSUIPC and FSX SP2.

All works properly now with the latest FSUIPC.

Good! Thanks for getting back on this.

Regards

Pete