Problem with FSUIPC4 DLL version 4.90

[remelco]

Hi, FSX has a problem with the latest software of FSUIPC4. It says Flight simulator has detected a problem with a third-party software. Name FSUIPC4 DLL: FS new universal IPC interface. Version 4.90 File Modules\FSUIPC4.dll. Do you want to run this software? When I said Yes FSX stopped working. What can I do to solve this problem? Thanks advance. Rene Potter

[Pete Dowson]

When I said Yes FSX stopped working. What can I do to solve this problem?

It's a rare timing bug in SimConnect. Please read the FAQ subforum thread on the subject:

http://forum.simflight.com/topic/68382-fsx-fails-to-run-after-fsuipc4-first-installed/

Pete

[USA4321]

I have done everything on the support forum,Peter, and the error still shows

[remelco]

It's a rare timing bug in SimConnect. Please read the FAQ subforum thread on the subject:

http://forum.simflig...irst-installed/

Pete

Thanks its working now

[Funkster39]

I am also having this issue and have tried all methods prescribed in the linked thread.

I did get some success with using the DLL loader and this resolved the initial error but them caused freezes when ever I clicked a button on the main screen ??? Can any one help? Did anyone else get this?

[Pete Dowson]

I did get some success with using the DLL loader and this resolved the initial error but them caused freezes when ever I clicked a button on the main screen ??? Can any one help? Did anyone else get this?

Nothing in either Loader or the FSUIPC proper can affect whether FSX freezes later -- once FSUIPC is actually loaded and running the problems of FSX crashing when it is started are long past -- the initial crash is not even in any Loader or FSUIPC code, it is in SimConnect when it is trying to load it.

The odd thing is that this problem is rare -- out of all the thousands of users it only affects a few -- so it is a very complicated timing glitch (which explains why Microsoft never managed to fix it -- though they did lessen its likelihood in SP2/Acceleration. In the original and SP1 releases it was much worse). I would be delighted to try to fix it once and for all, but I have to actually be able to reproduce it. It has never once been a problem on any of the 6 systems I've installed it on, whether XP, Vista, Win7 or Win8.

Since the exact cause is indeterminate and it isn't within the code I have control over, the solution is only that already proposed in that FAQ thread -- persistence. In all the cases I'm aware of, persistence has paid off. Once it is loaded ands registed in FSX.CFG as Trusted, it doesn't recur.

Regards

Pete