Jump to content
The simFlight Network Forums

FSUIPC Side By Side Errors


Recommended Posts

I noticed that in the "Event Viewer", I was constantly getting "Side By Side" errors. I uninstalled everything and so far have a clean re-install of of FSX (SP1 only) and TrackIR 4. Everything is fine until I install the first addon. Radar Contact 4 (for FSX). RC4 automatically installs a now older version of FSUIPC (4.1.5.2). Anyway, I'm getting the "Side By Side" errors again. So I install the latest FSUIPC 4.5.0.0. Open FSX (no need to open RC4), close FSX, look in "Event Viewer" and sure enough, the Side By Side Errors" are still there. I'm getting about six error lines each time I open FSX.

When I right click on the error, I see error messages like....

1)......Dependant Assembly Microsoft Flight Simulator. Simconnect could not be found and last error was the referenced assembly is not installed on your system.

2)......Generate Activation context for J:/Program Files/Micrososoft Games/Microsoft Flight Simulator X/Modules/FSUIPC.dll. Referenced error message the operation completed successfully.

I can see in the "winsxs" folder that there are two Simconnect d.lls there. One for the base FSX ( 10.00 60905.0) and one from the SP1 update..(10.061355.0).

If I delete the FSUIPC 4.1.5.2 from the modules folder, then I don't get any errors when looking in the "Event Viewer" after running FSX. Replace the FSUIPC, and the "Side By Side" errors of the kind mentioned above re-appear.

I would be grateful for you advice as to what I can do to stop this because otherwise I cannot play FSX otherwise I'll get CTD and screen freezes etc. It was dues to the screen freezes that prompted me to look in the "Event Viewer" which is how I first discovered this problem.

Many thanks.

Graham.

Link to comment
Share on other sites

I noticed that in the "Event Viewer", I was constantly getting "Side By Side" errors. I uninstalled everything and so far have a clean re-install of of FSX (SP1 only) and TrackIR 4. Everything is fine until I install the first addon. Radar Contact 4 (for FSX). RC4 automatically installs a now older version of FSUIPC (4.1.5.2).

Does it? It's never done that to me. It should be checking the version!

Anyway, I'm getting the "Side By Side" errors again. So I install the latest FSUIPC 4.5.0.0. Open FSX (no need to open RC4), close FSX, look in "Event Viewer" and sure enough, the Side By Side Errors" are still there. I'm getting about six error lines each time I open FSX.

Of course. They are not only spurious, but they are fully explained in the documentation so that they wouldn't worry you. There's even a listing in the Contents.

I would be grateful for you advice as to what I can do to stop this because otherwise I cannot play FSX otherwise I'll get CTD and screen freezes etc.

Nonsense! They are absolutely nothing to do with CTD and Screen freezes. They occur when FSUIPC initially runs whilst it is checking for the version of SimConnect it can use best. Please read what I write about these. There is no way you can stop them and they do absolutely no harm at all. There is no way I can program around them -- I complained to Microsoft about it three years ago and they confessed it was a weakness in Windows, which throws the error when a program "probes" for a side-by-side library to see if it can be used, even though such probing is the official way of doing it and provided in the Windows SDK.

t was dues to the screen freezes that prompted me to look in the "Event Viewer" which is how I first discovered this problem.

It is nothing to do with your problem. You need to look elsewhere.

Pete

Link to comment
Share on other sites

Pete...

Thanks very much for your reply. Guess I'll have to live with it I suppose. Had a little time in the Sim this evening for about 40 odd minutes. When I finnished and closed down FSX, I looked in the "Event Viewer", and there they were, as aslways, my few lines of "Side By Side" errors with great big white Crosses in red circles making it seem more unerving than it already is.

Link to comment
Share on other sites

Thanks very much for your reply. Guess I'll have to live with it I suppose. Had a little time in the Sim this evening for about 40 odd minutes. When I finnished and closed down FSX, I looked in the "Event Viewer", and there they were, as aslways, my few lines of "Side By Side" errors with great big white Crosses in red circles making it seem more unerving than it already is.

But you could look and find the side-by-side errors directly after FSX is fully started, as they occur when FSUIPC is initialised, right at the start. They are not real errors. I don't know why you don't believe me... what on Earth have I done to deserve it? What's all this about "living with it? What the blazes is it costing you? A few bytes of disk space in a log file? complain to MS about their stinking systems if you really feel so angry, but I would suggest you just ignore them as they are of absolutely no consequence!

Gee. If you don't like the look of them, don't ***** look at them!!! :-(

Pete

Link to comment
Share on other sites

I don't know why you don't believe me... what on Earth have I done to deserve it? What's all this about "living with it? What the blazes is it costing you? A few bytes of disk space in a log file? complain to MS about their stinking systems if you really feel so angry,e!

Gee. If you don't like the look of them, don't ***** look at them!!! :-(

Pete

WOA....Hold the reins there my Son!! I've been polite but there's no need for this attitude! I'm not angry, who said I don't believe you? I don't know what you are getting at when you say things like.."What have I done to deserve this"?, and..."What the blazes is it costing you"? Cripes Pete, your a tetchy fellow. :?

Link to comment
Share on other sites

Cripes Pete, your a tetchy fellow. :?

I'm sorry, it's been one of those days. People moaning and saying nasty things. I must admit it makes one "tetchy" sometimes.

I still don't understand where you are coming from with this, but i did overreact. Apologies.

Please take my word for it. As Documented, no harm is being done. I wrote it all up in the documentation especially to avoid rather inane exchanges like this one.

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.