Jump to content
The simFlight Network Forums

Prepar3d, FSUIPC, nVidia Surround - Crash on Launch


Recommended Posts

Hello everyone,

I've a similar problem like some older thread ()

To recap:

-Prepar3d v1.3, installed on C:\Prepar3d, UAC is off

-FSUIPC: 4.80/4.84

-Graphics adapter: nVidia GTX680

-nVidia-driver version: current stable (301....) and beta (304....)

-three projectors merged together with nVidia Surround and the swedish warpalizer-software for image warping

With only Prepar3d and NVS (nVidia Surround), everything runs fine.

As soon as I install FSUIPC, Prepar3d hangs up on the splash screen while the desktop is still visible.

There's no error visible in the windows error log, and no FSUIPC.log is produced.

What I've tried:

-older FSUIPC-version (4.80) - same behavior

-installing the simFlight-cert in the certificate store - same behavior

-workaround with the Launcher.dll - same behavior

-different nVidia-driver versions - same behavior

-disabling the warpalizer by removing the according d3d9.dll - same behavior

-disabling nVidia Surround - Prepar3d launches and supplies the FSUIPC-Connector

I've got the gutt feeling there's something interfering with the new NVS-loading the graphics. It doesn't look like the SimConnect-Auth-bug. Does anyone have any idea what to try next?

Link to comment
Share on other sites

-three projectors merged together with nVidia Surround and the swedish warpalizer-software for image warping

This is most definitely a video driver problem as has now been proven by two or three other separate instances. There is a driver version which appears to work. Please check the other thread(s).

Pete

Link to comment
Share on other sites

I see your point, but the only post I find where there were a "solution" was that a day later, the combo worked. Well, not with me - obviously, there HAS to be a link between the surround graphic initialization and FSUIPC, because it works if I disable either one. Perhaps it's not obvious, but it exists - perhaps somewhere in the order where Prepar3d/FSX is initializing modules, or something like that, that there initates a cross-lock in the module loading routine? I don't see how we could find a solution other way then asking you kindly for debugging, Pete :/

Link to comment
Share on other sites

I see your point, but the only post I find where there were a "solution" was that a day later, the combo worked. Well, not with me - obviously, there HAS to be a link between the surround graphic initialization and FSUIPC, because it works if I disable either one.

It can only be because with FSUIPC loading there s a slight difference in timing elsewhere. There is nothing in FSUIPC in anyway related to video, graphics, or anything like that.

I assume, then, that you've not bothered to try the version of the nVidia drivers which works for others and which therefore does not contain this bug?

I don't see how we could find a solution other way then asking you kindly for debugging,

There's no way I can debug inside video drivers, which is where it is crashing, even if I had the right hardware to generate the problem. The way you must proceed is to install the non-buggy version of the drivers. As reported by others:

Solved it!

Turns out it is directly related to nvidia surround. More importantly to the current beta driver 304.79. Rolling the drivers back to 304.48 (or even the last official 301.42) stops the issue with various .dll files not loading.

Pete

Link to comment
Share on other sites

as I wrote, I tried all nVidia-Versions containing surround - that does include the posted versions. Because of that, I begun the post, because I tried that allready...

Strange, because the specific drivers mentioned fixed exactly the same problem for at least two others. And you did not post precise version numbers, only 301.. and 304.. Each major version has a sub-number too.

Are you using the P3D v1.4 version of FSUIPC (4.852)? Have you tried using the FSUIPC4 Loader to see if it makes any difference?

If none of that works I'm afraid I'm out of ideas. Sorry.

Pete

Link to comment
Share on other sites

  • 1 month later...

Hi,

Fresh install of Windows here, and fresh Prepar3D. I have successfully run Prepar3d in surround to check it was properly set up, I then closed it and the first addon I have attempted to install in FSUIPC 4.853 - I have exactly the same problem - it hangs at the splash screen following the FSUIPC installation.

Please can anyone point me to anywhere that someone has mentioned specific nvidia drivers which worked for them? I have searched the forum in detail, but have been unable to find any post where anyone got it working other than the one NWittje mentioned where it started working without anything having been knowingly changed, and that post did not reference any version numbers. I am currently running 304.79

Thanks

EDIT: Sorry, I just found a post refering to 301.42 working through a google search rather than through the forum. I will try that now and report back.

EDIT 2: Again, sorry for posting too soon. I have indeed got it working in 301.42, however, this is a considerable regression since the 306.x WHQL and their beta versions introduced windowed 3d vision in SLI, which I wanted to use with Prepar3d. At least it's working in 2D, and in full screen 3D.

NWittje - please can you report the problem to nVidia. I am about to do the same. I'd appreciate it if anyone else running surround can try and replicate the problem with the latest drivers then report it also so we can get this fixed.

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.