Jump to content
The simFlight Network Forums

FSUIPC4 Is Killing FSX


Recommended Posts

Hello,

I am having trouble getting FSUIPC4 (v 4.751a) to work on my FSX simulator. The problem is as follows:

I downloaded what I believe is the most recent version of FSUIPC4 from the FSX section of this site: http://www.schiratti.com/dowson.html.

After unzipping the folder and executing the install application I receive a notification that installation has been successful, and am then prompted to register the product. I then press “Cancel” and exit installation without incident.

After opening FSX, the initial boot-up works fine and all aspects of the main menu work smoothly. After going to Free Flight and clicking the “Fly Now!” button, the program loads scenery, etc without incident until roughly five seconds after reaching 100%. At this point, windows tells me that FSX has experienced a fatal error and restarts the simulator.

I am fairly certain FSUIPC4 is causing the problem, as I can go to the FSX/Modules folder and remove the FSUIPC4 dll file and the simulator works fine. Although it sounds like a fix to a different issue, I have also gone to the config file and set initdelay=10000 in the hopes that this would help the problem, but to no effect.

I don’t know if this is related, but I have updated to FSX SP2 since I began looking into this problem; however, the version number that displays when booting up the program and on the install log has not changed to reflect this. I have redownloaded the SP2 patch a couple times and restarted the computer after updating, but also to no effect.

I will post the contents of FSUIPC4 Install.txt and FSUIPC4.txt in separate posts to try and give you more information about the problem.

Thank you for your help, and I hope you’re having happy holidays.

Thomas

Link to comment
Share on other sites

  • 2 weeks later...

After opening FSX, the initial boot-up works fine and all aspects of the main menu work smoothly. After going to Free Flight and clicking the “Fly Now!” button, the program loads scenery, etc without incident until roughly five seconds after reaching 100%. At this point, windows tells me that FSX has experienced a fatal error and restarts the simulator.

I am fairly certain FSUIPC4 is causing the problem, as I can go to the FSX/Modules folder and remove the FSUIPC4 dll file and the simulator works fine. Although it sounds like a fix to a different issue, I have also gone to the config file and set initdelay=10000 in the hopes that this would help the problem, but to no effect.

Three points on this:

1. There's a later update which I'd like you to try first -- 4.754 -- available in the Download Links subforum here. There are usually updates there.

2. The InitDelay is in seconds, with a maximum of 120, so that attempt to change things wouldn't have worked in any case.

3. Crashes and hangs at the point you describe are most usually due to clashes with other add-ons and removing or changing or updating the other will also avoid the problem. One frequent cause is an outdated version of actigate.dll, but also one version of fscopilot.dll caused similar problems. So please make a lit of such add-ons, or show me the DLL.XML and EXE.XML files so I can see what else there is.

The wrong versions being quotes after you installed SP2 are suspicious of a corrupt FSX installation. I assume you did install SP1 first?

I can't really advise further till I see the Install and FSUIPC logs. You can paste them into a message here. don't try attaching them.

Regards

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.