Jump to content
The simFlight Network Forums

Recommended Posts

Posted

I installed the latest build from Pete D  ( oct 4 )of fsuipc and my p3d v3 is crashing giving me a fatal error every time I start the program and load a flying "free flight "session

I get a " not responding " then a crash then a fatal error message 

 

I deleted the fsuipc and all associated fsuipc files and the sim works again without crashing

 

Any ideas ???

my machine   w7x64 p3d  v3.0 ( fully licensed fsuipc)

 

 

Peter

Posted

I installed the latest build from Pete D  ( oct 4 )of fsuipc and my p3d v3 is crashing giving me a fatal error every time I start the program and load a flying "free flight "session

I get a " not responding " then a crash then a fatal error message 

 

I deleted the fsuipc and all associated fsuipc files and the sim works again without crashing

 

Any ideas ???

 

No ideas at all because there's no information here.

 

Is a Log produced? If so I need to see it. At what exact stage does it crash -- i.e. what is on the screen? What is the actual version number of FSUIPC (I always need this)? And please show me the Windows crash details from the Windows event viewer.

 

Also it might help to have a list of other add-ons you are running at the same time. It may be some clash. Have you tried stopping everything else BUT FSUIPC, just to be sure?

 

Pete

Posted

No ideas at all because there's no information here.

 

Is a Log produced? If so I need to see it. At what exact stage does it crash -- i.e. what is on the screen? What is the actual version number of FSUIPC (I always need this)? And please show me the Windows crash details from the Windows event viewer.

 

Also it might help to have a list of other add-ons you are running at the same time. It may be some clash. Have you tried stopping everything else BUT FSUIPC, just to be sure?

 

Pete

 

Ok .. thanks for the guidance. Ill round up some info and report back

what i can tell you so far is that im running FSUIPC4 4.946

I am running w7 x64 p3d v3

I have no add ons as of yet , stock p3dv3

I was waiting for fsuipc to be compatible with this p3d version

P3d v3 starts, I get the splash screen). I load a stock aircraft.

I experimented with different airports, aircraft , scenarios .. same result every time per below ( tried about 10 scenarios )

The program bar at the top immediatly after load goes to " not responding "

The in a about 5 sec's goes to  " stopped due to a fatal error "

I removed the fsuipc dll and associated files in the modules folder, restarted and the program worked again with not further crashes.

I will run a log and send it.

Thank you

 

Pete

Posted

I removed the fsuipc dll and associated files in the modules folder, restarted and the program worked again with not further crashes.

 

The only other reports of crashes on loading have all turned out to be bad installations of P3D, especially ones which have been altered by migration tools. But I cannot guess anything. I need to see the FSUIPC4.LOG after such a crash, and the Windows crash data. It may even be a bad joystick driver.

 

I will run a log and send it.

 

 

You don't need to "run a log". FSUIPC always automatically makes a Log when it runs. And don't try sending anything. You'll need to paste the text into a message.

 

Pete

Posted

The only other reports of crashes on loading have all turned out to be bad installations of P3D, especially ones which have been altered by migration tools. But I cannot guess anything. I need to see the FSUIPC4.LOG after such a crash, and the Windows crash data. It may even be a bad joystick driver.

 

 

You don't need to "run a log". FSUIPC always automatically makes a Log when it runs. And don't try sending anything. You'll need to paste the text into a message.

 

Pete

 

Pete here is the info requested... let me know if this is helpful or if you need to me to get additional info

I actually thought i had it working last night . I uninstalled and reinstalled the most recent v. of fsuipc 

I ran for while and then i shut it off

I restarted p-v3 this morning and it crashed with the stock mooney acclaim

Here is the info i was able to extract from the log and windows error report

 

les that help describe the problem:

  C:\Users\fsx\AppData\Roaming\Lockheed Martin\Prepar3D v3\Prepar3D.cfg.txt
  C:\Users\fsx\AppData\Roaming\Lockheed Martin\Prepar3D v3\dxdiag.txt
  C:\Users\fsx\AppData\Roaming\Lockheed Martin\Prepar3D v3\fdr.dat
  C:\Users\fsx\AppData\Roaming\Lockheed Martin\Prepar3D v3\DLL.XML
  C:\Users\fsx\AppData\Local\Temp\WER19A7.tmp.WERInternalMetadata.xml
  C:\Users\fsx\AppData\Local\Temp\WER2E51.tmp.appcompat.txt
  C:\Users\fsx\AppData\Local\Temp\WER517B.tmp.mdmp
 
Read our privacy statement online:
 
If the online privacy statement is not available, please read our privacy statement offline:
 
 
 
 
fsuipc log
 
 
********* FSUIPC4, Version 4.946b by Pete Dowson *********
Reading options from "G:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Modules\FSUIPC4.ini"
Running inside Prepar3D v3 on Windows 7
Module base=5B8B0000
User Name="peter kofman"
User Addr="pkofman@rogers.com"
FSUIPC4 Key is provided
WideFS7 Key is provided
      125 System time = 08/10/2015 08:24:41
      125 FLT UNC path = "\\AVIATION-PC\fsx\Documents\Prepar3D v3 Files\"
      125 Trying G:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D2.dll
      140 Found it: trying to connect
      140 FS UNC path = "\\AVIATION-PC\G\Program Files (x86)\Lockheed Martin\Prepar3D v3\"
      281 LogOptions=00000000 00000001
      281 -------------------------------------------------------------------
      281 ------ Setting the hooks and direct calls into the simulator ------
      281 --- CONTROLS timer memory location obtained ok
      281 --- SIM1 Frictions access gained
      281 --- FS Controls Table located ok
      281 --- Installed Mouse Macro hooks ok.
      281 --- Wind smoothing fix is installed
      281 --- All links checked okay
      281 -------------------------------------------------------------------
      281 SimConnect_Open succeeded: waiting to check version okay
      281 Trying to use SimConnect Prepar3D
    15288 Running in "Lockheed MartinÆ Prepar3DÆ v3", Version: 3.0.3.0 (SimConnect: 3.0.0.0)
    15288 Initialising SimConnect data requests now
    15288 FSUIPC Menu entry added
    15319 \\AVIATION-PC\fsx\Documents\Prepar3D v3 Files\ykz.fxml
    15319 \\AVIATION-PC\G\Program Files (x86)\Lockheed Martin\Prepar3D v3\SimObjects\Airplanes\Carenado A36 BONANZA P3D\A36.air
    80434 System time = 08/10/2015 08:26:01, Simulator time = 08:15:37 (12:15Z)
    80449 Aircraft="Carenado A36 Bonanza Deep Green"
    81463 Starting everything now ...
    82774 Advanced Weather Interface Enabled
   110433 \\AVIATION-PC\G\Program Files (x86)\Lockheed Martin\Prepar3D v3\SimObjects\Airplanes\Mooney_Acclaim\Mooney_Acclaim.air
   110760 Aircraft="Mooney Acclaim With G1000 4"
Posted

 

Pete here is the info requested... let me know if this is helpful or if you need to me to get additional info

 

Here is the info i was able to extract from the log and windows error report

 

Okay. There's no Windows crash information here at all. The crash information gives the following sorts of data. I've no idea what you picked up instead:

 

Faulting application name: uedit32.exe, version: 22.10.0.12, time stamp: 0x5589b3ca
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x10a9fd24
Faulting process id: 0xe18
Faulting application start time: 0x01d10120300477fa
Faulting application path: C:\ULTRAEDT\uedit32.exe
Faulting module path: unknown
Report Id: b7f7805e-6d4f-11e5-a1ed-74d435ed54d3
 
With the correct Windows crash data the offending module can usually be identified, and even the location within. There's little can be done without this data.
 
The FSUIPC log shows everything is fine ... it set everything up correctly and there's really nothing to go wrong after that. Running for 110 seconds and crashing when you load an aircraft suggests something else is going on. Unless the Windows crash data actually points to FSUIPC4.DLL then I am afraid your recourse must be to Lockheed-Martin support. But first i suggest you try a reinstall of P3D, as it sounds very much to me like a corrupt installation.
 
Before trying again to get a proper Windows crash report, please install 4.947, just released. In case the crash report does point to FSUIPC4 I would need to match the data to my current version. Thanks.
 
Pete
Posted

HI Pete

I am not sure exactly where to get the windows crash log ( maybe you can point me to it  , using w7 ).... but i can report the following 

I installed the later version 4.947

after removing  the fsuipc files from the modules folder

I was then able to fly with p3d v3 for about 25 mins without a crash

a36 and mooney

I then shut down the sim and restarted

I flew for a while 10 min and then i went into the fsuipc program and did one simple thing

I checked under "clouds" allow "changes to fs wx program " .... maybe not the exact working but you know what i mean

I unpaused the sim and it crashed in 10 seconds

I restarted the sim and then it would crash in about 10 seconds

( generally i click on something and it crashes the sim )

I went back an unchecked the wx setting and it did not crash again

 

I was not sure if this was an actual issue so i uninstalled the fsuipc program reinstalled and went through it all again with exactly the same result

Maybe this helps

 

Here is the log

 

Reading options from "G:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Modules\FSUIPC4.ini"
Running inside Prepar3D v3 on Windows 7
Module base=5E110000
User Name="peter kofman"
User Addr="pkofman@rogers.com"
FSUIPC4 Key is provided
WideFS7 Key is provided
       94 System time = 08/10/2015 10:40:17
      109 FLT UNC path = "\\AVIATION-PC\fsx\Documents\Prepar3D v3 Files\"
      109 Trying G:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D2.dll
      109 Found it: trying to connect
      109 FS UNC path = "\\AVIATION-PC\G\Program Files (x86)\Lockheed Martin\Prepar3D v3\"
      234 ---------------------- Joystick Device Scan -----------------------
      234 Product= Saitek X52 Flight Control System
      234    Manufacturer= Saitek
      234    Vendor=06A3, Product=075C (Version 1.0)
      234    Serial Number= 
      234    Using existing joystick id:  0
      250 -------------------------------------------------------------------
      250 LogOptions=00000000 00000001
      250 -------------------------------------------------------------------
      250 ------ Setting the hooks and direct calls into the simulator ------
      250 --- CONTROLS timer memory location obtained ok
      250 --- SIM1 Frictions access gained
      250 --- FS Controls Table located ok
      250 --- Installed Mouse Macro hooks ok.
      250 --- Wind smoothing fix is installed
      250 --- All links checked okay
      250 -------------------------------------------------------------------
      250 SimConnect_Open succeeded: waiting to check version okay
      250 Trying to use SimConnect Prepar3D
     3853 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.0.3.0 (SimConnect: 3.0.0.0)
     3853 Initialising SimConnect data requests now
     3853 FSUIPC Menu entry added
     3884 \\AVIATION-PC\fsx\Documents\Prepar3D v3 Files\ykz.fxml
     3884 \\AVIATION-PC\G\Program Files (x86)\Lockheed Martin\Prepar3D v3\SimObjects\Airplanes\Carenado A36 BONANZA P3D\A36.air
    24523 System time = 08/10/2015 10:40:42, Simulator time = 08:15:37 (12:15Z)
    24539 Aircraft="Carenado A36 Bonanza Deep Green"
    25537 Starting everything now ...
    25678 Advanced Weather Interface Enabled
    56223 Weather Mode now = Theme
    74725 \\AVIATION-PC\G\Program Files (x86)\Lockheed Martin\Prepar3D v3\SimObjects\Airplanes\Mooney_Acclaim\Mooney_Acclaim.air
    75037 Aircraft="Mooney Acclaim With G1000 4"
   152819 Sim stopped: average frame rate for last 77 secs = 31.9 fps
   152819 Average weather filter write interval in that time = 77111.0 msecs
 
   303297 Sim stopped: average frame rate for last 114 secs = 32.0 fps
 
 
Here is a log that was in the event log but not sure if it is what you are looking for
Log Name:      Application
Source:        Application Error
Date:          10/8/2015 10:39:56 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      aviation-PC
Description:
Faulting application name: Prepar3D.exe, version: 3.0.10.14945, time stamp: 0x560b4abe
Faulting module name: MSVCR120.dll, version: 12.0.21005.1, time stamp: 0x524f7ce6
Exception code: 0xc0000005
Fault offset: 0x000182a4
Faulting process id: 0x122c
Faulting application start time: 0x01d101d6e15de03e
Faulting application path: G:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe
Faulting module path: C:\Windows\system32\MSVCR120.dll
Report Id: 71457d04-6dca-11e5-894b-60a44c6492d1
Event Xml:
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-10-08T14:39:56.000000000Z" />
    <EventRecordID>29051</EventRecordID>
    <Channel>Application</Channel>
    <Computer>aviation-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Prepar3D.exe</Data>
    <Data>3.0.10.14945</Data>
    <Data>560b4abe</Data>
    <Data>MSVCR120.dll</Data>
    <Data>12.0.21005.1</Data>
    <Data>524f7ce6</Data>
    <Data>c0000005</Data>
    <Data>000182a4</Data>
    <Data>122c</Data>
    <Data>01d101d6e15de03e</Data>
    <Data>G:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe</Data>
    <Data>C:\Windows\system32\MSVCR120.dll</Data>
    <Data>71457d04-6dca-11e5-894b-60a44c6492d1</Data>
  </EventData>
</Event>
Posted

I am not sure exactly where to get the windows crash log ( maybe you can point me to it  , using w7 ).... but i can report the following 

 

The Windows Event Viewer (enter event viewer into the Start/Search edit area) has logs for system and application problems. Check the latter.

 

I flew for a while 10 min and then i went into the fsuipc program and did one simple thing

I checked under "clouds" allow "changes to fs wx program " .... maybe not the exact working but you know what i mean

I unpaused the sim and it crashed in 10 seconds

I restarted the sim and then it would crash in about 10 seconds

( generally i click on something and it crashes the sim )

I went back an unchecked the wx setting and it did not crash again

 

 

 

I don't think any of the Weather facilities should be used with P3Dv3 -- I can check, but generally everyone these days uses a decent weather program, so none of those have been thortoughly tested. Maybe P3D doesn't support the changes those entail -- I'd need to check.

 

Maybe you should delete your FSUIPC4.INI file, please and start with default settings? I hadn't realised you'd changed things. Show me a copy of an FSUIPC4.INI file which regularly crashes, please.

 

Here is a log that was in the event log but not sure if it is what you are looking for

 

 

 
Well it is certainly in P3D.  I am suspecting that there are bugs in the weather setting facilities in P3Dv3. I'd need to do more testing in that area and report to Lockheed-Martin.
 
I don't think, in these days of ASN and the like, that anyone uses the older FS2000-compatible FSUIPC weather filters, but I'll check them -- not at present though. Too busy.
 
Pete
Posted

Ok...Pete.... Ill just leave those unchecked and use opus or some other wx program...

Glad we could narrow the issue down a bit

I will also send you the ini file

Thanks for all of your assistance.....

BTW... as always thanks for you continued support of your products and the community.

Pete

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.