Jump to content
The simFlight Network Forums
Sign in to follow this  
SirPres

I'm Really Stomped

Recommended Posts

I haven't been able to figure this out.  Since I've upgraded to P3D v2.3, I have not been able to use FSUIPC.  When I use any version of FSUIPC, Prepar3D would load up to "100% complete!" and then promptly crash with the window "Prepar3D has stopped working".  I've checked the Windows event viewer logs and it always traces back to MSVCR100.dll.  I had hoped that upgrading to P3D v2.4 would solve the problem, but it remains.  I've used different MSVCR100.dll files, started with clean Prepar3D.cfg and scenery.cfg files, but no luck.  When I remove FSUIPC.dll, P3D loads up without any problem.  FSUIPC has worked fine with my previous versions of P3D with all the addons, and it still works fine with FSX, which is still on my machine.  Any ideas anyone?  Here's a copy of the Windows event log...

 

Prepar3D.exe       2.4.11570.0       542314d3       MSVCR100.dll       10.0.40219.332       4e1a9f56       c0000417       0008af3e       158c       01cfe3f5b987c601       I:\Lockheed Martin\Prepar3D v2\Prepar3D.exe       C:\WINDOWS\SYSTEM32\MSVCR100.dll       c98def37-4fea-11e4-be8b-74d4359c69ce                

 

Share this post


Link to post
Share on other sites

I haven't been able to figure this out.  Since I've upgraded to P3D v2.3, I have not been able to use FSUIPC.  When I use any version of FSUIPC, Prepar3D would load up to "100% complete!" and then promptly crash with the window "Prepar3D has stopped working".  I've checked the Windows event viewer logs and it always traces back to MSVCR100.dll.  I had hoped that upgrading to P3D v2.4 would solve the problem, but it remains.  I've used different MSVCR100.dll files, started with clean Prepar3D.cfg and scenery.cfg files, but no luck.  When I remove FSUIPC.dll, P3D loads up without any problem.  FSUIPC has worked fine with my previous versions of P3D with all the addons, and it still works fine with FSX, which is still on my machine.  Any ideas anyone?  Here's a copy of the Windows event log...

 

Prepar3D.exe       2.4.11570.0       542314d3       MSVCR100.dll       10.0.40219.332       4e1a9f56       c0000417       0008af3e       158c       01cfe3f5b987c601       I:\Lockheed Martin\Prepar3D v2\Prepar3D.exe       C:\WINDOWS\SYSTEM32\MSVCR100.dll       c98def37-4fea-11e4-be8b-74d4359c69ce                

 

Well, FSUIPC doesn't need MSVCR1000.dll and doesn't use it at all, so I think that's misleading. I suspect you are not updating FSUIPC to keep up with P3D changes. The current version of FSUIPC is 4.937 which was released to work with P3D 2.4. Every time you update P3D you will need to look for the subsequent matching update to FSUIPC.

 

Please, in future, ALWAYS state the version number of FSUIPC you have installed. Without such information diagnosis is not possible in any case.

 

Pete

Share this post


Link to post
Share on other sites

Sorry about that, Pete.  I am using the current version (4.937).  I have kept the FSUIPC version current through all updates of P3D.  I still don't know why the combination of FSUIPC and MSVCR100.dll would cause P3D to crash if they are not interactive.  Maybe there's another file in the Modules folder that I need to check.  And since I just checked... tell me, are the FSUIPC.dll and FSUIPC4.dll files both needed in the modules folder?  The FSUIPC.dll file has a 2002 date.  Maybe an addon put it there.

Share this post


Link to post
Share on other sites

Sorry about that, Pete.  I am using the current version (4.937).  I have kept the FSUIPC version current through all updates of P3D.  I still don't know why the combination of FSUIPC and MSVCR100.dll would cause P3D to crash if they are not interactive.  Maybe there's another file in the Modules folder that I need to check.  And since I just checked... tell me, are the FSUIPC.dll and FSUIPC4.dll files both needed in the modules folder?  The FSUIPC.dll file has a 2002 date.  Maybe an addon put it there.

 

FSUIPC.DLL would probably be FSUIPC version 2 or 3 or before, not for FSX or P3D, only for old versions of FS. And it won't be used or touched in any case.

 

You'll need to check the other add-ons you are using, do a process of elimination.

 

Pete

Share this post


Link to post
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
Sign in to follow this  

×

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.