Jump to content
The simFlight Network Forums

Recommended Posts

Posted

Event Viewer reports the following:

 

Faulting application name: Prepar3D.exe, version: 2.2.10438.0, time stamp: 0x53469019
Faulting module name: FSUIPC4.dll, version: 4.9.2.9, time stamp: 0x534ea035
Exception code: 0xc0000005
Fault offset: 0x00028a22
Faulting process id: 0xd08
Faulting application start time: 0x01cf5a01f639b4cd
Faulting application path: V:\Lockheed Martin\Prepar3D v2\Prepar3D.exe
Faulting module path: V:\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.dll
 
The FSUIPC 4.93 install log:
 
INSTALLATION FOR Prepar3D v2:
SetupPath="V:\Lockheed Martin\Prepar3D v2\"
Checking version of the Prepar3D v2 EXE:
... Version 2.2.10438.0  (Need at least 1.0.677.0)
!! WARNING !! This version of Prepar3D is later than any known by this FSUIPC4.
   There may be problems. Please check for a later version of FSUIPC4!
Checking compatibility with installed SimConnect:
    Found SimConnect build 60905 (Original)
    Found SimConnect build 195 (ESP Orig)
    Found SimConnect build 61242 (SP1 May07)
    Found SimConnect build 61259 (Acc/SP2 Oct07)
Checking if there's already a version of FSUIPC4 installed in:
       V:\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.DLL
... Version 4.930 found.
Prepar3D v2 Modules folder already exists.
Okay -- installed FSUIPC4 into "V:\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.DLL"
Looking for the current user's Application Data path: 
... found as "C:\Users\Rob\AppData\Roaming"
Now finding \Lockheed Martin\Prepar3D v2\Prepar3D.CFG for all users, including this one
Looking in "C:\Users\All Users\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Default\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Default User\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Public\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Rob\AppData\Roaming"
Found Prepar3D.CFG in "C:\Users\Rob\AppData\Roaming\Lockheed Martin\Prepar3D v2\Prepar3D.CFG"
Now checking DLL.XML ...
... There is a previous DLL.XML, checking for FSUIPC4 section.
... FSUIPC4 section already exists but will be replaced.
     (for FSUIPC4, without Loader)
... FSUIPC4 section of DLL.XML written okay
Now checking for a SimConnect.XML file ...
... No SimConnect.XML file found. This is okay.
"Modules\FSUIPC Documents" folder already exists.
Now installing the Prepar3D SimConnect interface for FSUIPC4 into the "Modules" folder:
   Installed "SimConnectP3D2.dll" okay
Now installing additional files into the "Modules\FSUIPC Documents" folder:
   Installed "FSUIPC4 User Guide.pdf" okay
   Installed "FSUIPC4 for Advanced Users.pdf" okay
   Installed "FSUIPC4 History.pdf" okay
   Installed "List of FSX and P3D controls.pdf" okay
   Installed "FSUIPC Lua Library.pdf" okay
   Installed "FSUIPC Lua Plug-Ins.pdf" okay
   Installed "Lua License.pdf" okay
   Installed "Lua Plugins for VRInsight Devices.pdf" okay
   Installed "LuaFileSystem.pdf" okay
   Installed "Example LUA plugins.zip" okay
   Installed "ASN WX Radar facilities in FSUIPC4.pdf" okay
   Installed "Offset Mapping for PMDG 737NGX.pdf" okay
   Installed "FSUIPC4 Offsets Status.pdf" okay
===========================================================
 
All installer tasks completed.
Registration check for FSUIPC4 and WideFS was successful! (result code 00)
 
I noticed that the FSUIPC.DLL shows a File Version = 2.9.2.9 but the Product Version is 4.93.
 
post-2996-0-46296300-1397715805_thumb.pn
 
Windows 7 64bit
P3DV2.2 + hotfix  (Professional Plus version)
 
Rob.
 
Posted

 

Event Viewer reports the following:

 

Faulting application name: Prepar3D.exe, version: 2.2.10438.0, time stamp: 0x53469019
Faulting module name: FSUIPC4.dll, version: 4.9.2.9, time stamp: 0x534ea035
Exception code: 0xc0000005
Fault offset: 0x00028a22
Faulting process id: 0xd08
Faulting application start time: 0x01cf5a01f639b4cd
Faulting application path: V:\Lockheed Martin\Prepar3D v2\Prepar3D.exe
Faulting module path: V:\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.dll

 

Ah, thanks! That's the info I need!

 

Working on it now.

 

Oddly it runs perfectly here, 100%

 

Pete

Posted

Working on it now.

 

I think I've fixed it. I'll upload 4.931 soon. But one thing puzzles me. My Prepar3D 2.2 is build 10437, yours (and others I've seen) are 10438. I don't understand that. Has there been a later update to 2.2 since Monday?

 

Pete

Posted

There was a hotfix for a flight planner problem.

 

Since Monday when I downloaded mine? Oh dear. Back to hacking again. It takes hours each time even if they've not changed much -- I still have to verify each hook by disassembling code and coparing locations etc.

 

Pete

Posted

I think I've fixed it. I'll upload 4.931 soon. But one thing puzzles me. My Prepar3D 2.2 is build 10437, yours (and others I've seen) are 10438. I don't understand that. Has there been a later update to 2.2 since Monday?

 

Pete

 

4.931 is working well for me ... including mouse macros.  Thanks for the very prompt response and fix.

 

LM released a HotFix to 2.2 on 4/10.  I am running released version which is 10438 (not Beta).

 

Cheers, Rob.

Posted

4.931 is working well for me ... including mouse macros.  Thanks for the very prompt response and fix.

 

LM released a HotFix to 2.2 on 4/10.  I am running released version which is 10438 (not Beta).

 

Cheers, Rob.

 

The released version is 10437 which I got n the 14th when I returned. The hotfix is 10438, but it is buried deep in the Forums. LM have only just pinned it to stop it sinking without trace.

 

They replaced all of the DLLs even though most were actually not changed. Trouble is I still have to check each one FSUIPC depends on, just in case.

 

Pete

Posted

The released version is 10437 which I got n the 14th when I returned. The hotfix is 10438, but it is buried deep in the Forums. LM have only just pinned it to stop it sinking without trace.

 

They replaced all of the DLLs even though most were actually not changed. Trouble is I still have to check each one FSUIPC depends on, just in case.

 

Pete

 

I don't know if the Hot+Fix for 2.2 also included other items they had been working on or not ... like you said, most DLLs were not changed so I'm guessing they were able to regress back to the 2.2 release build and just implement code changes specific to fixing the Flight Planner issue.

 

Appreciate your work as always Pete.

 

Cheers, Rob.

Posted

I have fsuipc 4.931 and I can't get it to work on 10437 or 10438...  the simulator hung on loading each time.  :/

 

If it makes any difference, I'm using the academic version of P3Dv2

 

Regards,

Joshua Robertson (creator of FS Real Time)

Posted

I have fsuipc 4.931 and I can't get it to work on 10437 or 10438...  the simulator hung on loading each time.  :/

 

If it makes any difference, I'm using the academic version of P3Dv2

 

It works fine here on both Academic and Pro versions. and the problems before weren't hanging but a definite crash (but only on some configurations with registered installs).

 

Can you supply any more details at all? Like whether FSUIPC4 creates a log file? If so please show it to me.

 

Pete

Posted

I re-installed fsuipc 4.931 into 10438 to grab the setup log. However, when I started p3d this second time, I was expecting to see the dreaded hang on loading again -- nope. Murphy's law strikes again. No hang! So I don't know what it could have been. Only thing I did differently this time was to supply my registration key for fsuipc and widefs (which I suspect wouldn't cause a problem if I DIDN'T supply it.)

 

If I get p3d to hang again, i'll be sure to grab the fsuipc log for your reading pleasure. ;)

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.