Jump to content
The simFlight Network Forums

FSUIPC loading fails in FSX


Recommended Posts

After upgrading fsuipc to 4.961, FSX throws an error when loading (FS has detected a problem with a third party software...FSUIPC4 DLL...FS new universal interface...).

 

I read through some posts discussing the same error, but they were for P3D.  You previously suggested to another user that restarting FSX several times should resolve the problem, and is did for me for a few days.  Got the error again last night (and now) despite no additional changes to FSX or anything else.  Tried reinstalling, and FSX loaded fine on the first try, but failed each subsequent attempt.  I've attached the simconnect log.

 

Previous to this, I had no problems with FSUIPC.

 

Thx,

Dave Skuback

SimConnect0.Log

Link to comment
Share on other sites

25 minutes ago, heightsmite said:

After upgrading fsuipc to 4.961, FSX throws an error when loading (FS has detected a problem with a third party software...FSUIPC4 DLL...FS new universal interface...).

"Throws an error"? Or do you mean it gives a warning where you have the options to run it or not? There's a big difference. You should try running it -- it may just be the annoying FSX SimConnect trust bug (which does NOT apply to P3D!). It might take several attempts.

If there is really an error then I need to see the details, the actual crash report with error type and module offset. However, the current supported version is 4.962, so please update first!

If an FSUIPC4.LOG file is produced before a crash I need to see that.

The SimConnect log isn't much use except possibly to show that, in fact, FSUIPC did not run at all (therefore it can't crash), so it is probably just the trust bug. That log also shows you have the most DLL's loading in FSX I've ever seen. I count 17 actually loading. Your DLL.XML file is in error in any case -- there are THREE attempts to load MV_WXM.DLL (the second two fail, of course!). Also it looks like you have Active Sky installed, but that vital component it needs, as_btstrp.dll isn't listed as loaded.

Pete

 

Link to comment
Share on other sites

The error described above is what happened when I said OK to running it; FSX would when close to the desk top.  If I said no (don't run it) FSX started OK.

 

I did see the multiple Milviz entries; have no idea how that happened.  You think it's safe for me to delete duplicates in the dll.xml?  Can't explain the number of loaded dll's other than the number of add-ons I have installed.

 

At any rate, the trouble I have/had started with a FSUIPC update to 4.961.  Today I saw the next upgrade which I downloaded and installed and, it has worked perfectly through a number of re-starts (of FSX) as well as re-boots fo the PC, so maybe 4.962 has exorcised my FS demon.  So, let me hold this thought & I'll re-post if it comes back.

 

Thanks for your time,

Dave

Link to comment
Share on other sites

55 minutes ago, heightsmite said:

The error described above is what happened when I said OK to running it; FSX would when close to the desk top.

There will almost certainly be a crash report, then. And if there was no log produced (and the SimConnect log actually says it wasn't even loaded), then it most certain was not FSUIPC which crashed. At least on loading.

If there's a Windows crash report for it, then I needed to see it -- check the Windows Event Viewer. If there's no crash report, then it didn't crash.

57 minutes ago, heightsmite said:

You think it's safe for me to delete duplicates in the dll.xml?

Yes.

58 minutes ago, heightsmite said:

Today I saw the next upgrade which I downloaded and installed and, it has worked perfectly through a number of re-starts (of FSX) as well as re-boots fo the PC, so maybe 4.962 has exorcised my FS demon.

That is why FSUIPC 4.962 followed on from 4.961 so quickly. There was a bug in 4.961 which caused crashes ON EXIT from FS (unless you disabled the OOM check). It is those end of session crashes which cause the warning next time you load. There is a writeup about this in the change notes included in the release.

It is always best, before reporting a problem, to see if has been fixed first.

Pete

 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.