Jump to content
The simFlight Network Forums
wlix261

Crash Loading P3Dvhttp://forum.simflight.com/topic/82599-crash-loading-p3dv34-reporte-fsuipc4dll/3.4 reporte FSUIPC4.dll

Recommended Posts

Too add to the confusion, after I reinstall fsuipc, at times I can start P3D normally 5 or 6 times, both with and without a computer restart before suddenly it starts and disappears to the task bar thus forcing me to reinstall fsuipc again. Yes I do have LINDA installed as well. 

Share this post


Link to post
Share on other sites

There have been two distinct possible solutions now found, but perhaps not yet proven.

The first appears to be to do with LINDA, as described in  the messages above.

The second has been posted by gypsyczar obver in the L-M forum, as follows:

I just did a reinstall of GSX using the 1/4/17 version (download from the FSDT website). I have now restarted P3D multiple times without a crash both with a reboot before restart or restarting without a reboot. The reinstall of GSX was the only change made from the configuration that resulted in the repetitive P3D CTDs. Anyone else having this problem may want to try a GSX reinstall

I added my own observation to this:

Odd that I'm using GSX without that update (I have one from mid-December I think). The AddonManager install puts the COUATL.EXE into the EXE.XML, and the BGLMANX.DLL into the DLL.XML files, both on the ProgramData folder I think.

I expect this would be the same, then, for any DreamFleet install.

Can others here confirm or deny either of these?

Pete

Share this post


Link to post
Share on other sites
3 minutes ago, B773ER said:

suddenly it starts and disappears to the task bar

If it goes to the task bar it simply means that something else has stolen the focus. There are lots of addons which can do that. It is still running!

All you would need to do is click it on the task bar to return the focus and it would re-open its screen!

Pete

 

Share this post


Link to post
Share on other sites
1 hour ago, Pete Dowson said:

Ah, so could the apparently successful sessions actually be crashing on exit without you noticing? Can you check the Event Viewer logs in Windows to see? On a successful run, is the FSUIPC log file complete with the end summaries?

The crash on exit is always noticed. On closure of P3D it takes a couple of seconds before a Windows dialog is popping up stating that prepar3d.exe stopped working. It's the closing issue you're discussing with the LINDA Dev in another thread which you already referenced above.

FSUIPC log however is complete with end summaries.

1 hour ago, Pete Dowson said:

Try a re-boot instead of an FSUIPC reinstall.

re-boot does not help in the case we discuss. FSUIPC reinstall seems so far to be the only thing to allow P3D to start again. As reported by other users as well. So it must change something to the good. Maybe a changed timestamp on a file or advanced file attributes?

btw other things noticed related to this crash (not the crash on exit)

- prepar3d.exe remains running (with 100% utilization of 1 core)

- dxdiag seems to be called producing a dxdiag log file in AppData Roaming

Joerg

P.S: would like to help analyze further, but won't be available to do so before sunday.

 

Share this post


Link to post
Share on other sites
28 minutes ago, Joerg Alvermann said:

re-boot does not help in the case we discuss. FSUIPC reinstall seems so far to be the only thing to allow P3D to start again. As reported by other users as well. So it must change something to the good. Maybe a changed timestamp on a file or advanced file attributes?

Well, yes, the timestamp on the DLL.XML file will be different. But that's all. Nothing else at all will be different. The timestamp on the DLL is set by the installer and is related to creation time here on my system.

30 minutes ago, Joerg Alvermann said:

tw other things noticed related to this crash (not the crash on exit)

- prepar3d.exe remains running (with 100% utilization of 1 core)

- dxdiag seems to be called producing a dxdiag log file in AppData Roaming

You mean the "crash" which is actually a "minimise" action? Won't it restore if you click it?

Those points need reporting to L-M please.

I've not heard of any "minimise" problem before. The 100% core utilisation sounds very odd indeed, and the DXDiag does seem related to devices -- back to LINDA I suppose. Maybe a process of elimination on what LINDA is doing would be useful? I know L-M were making quite a lot of changes to the way they were handling devices, even with choices between DirectX use and the older style device driving.

Pete

 

Share this post


Link to post
Share on other sites
2 minutes ago, Pete Dowson said:

You mean the "crash" which is actually a "minimise" action? Won't it restore if you click it?

Those points need reporting to L-M please.

I've not heard of any "minimise" problem before. The 100% core utilisation sounds very odd indeed, and the DXDiag does seem related to devices -- back to LINDA I suppose. Maybe a process of elimination on what LINDA is doing would be useful? I know L-M were making quite a lot of changes to the way they were handling devices, even with choices between DirectX use and the older style device driving.

Pete

 

There is no GUI element left to klick on after the 'crash' or 'minimise'. i.e. there is only the process, but no app listed in the task manager. Will report to LM after this weekend.

On the GSX Topic:

I just tested an can confirm:

- LINDA only (i.e. no COUATL.exe, no AddOnManager): NO P3D crash on exit. NO subsequent failure on P3D start

- LINDA and COUATL but No AddOnManager:     NO P3D crash on exit. NO subsequent failure on P3D start

- LINDA and COUATL and AddOnManager:    P3D crash on exit. Subsequent failure on P3D start

- NO LINDA, but COUATL and AddOnManager:  NO P3D crash on exit. NO subsequent failure on P3D start

Reinstallation of the FSDreamTeam AddOnManager resolves the issue. Just like the installation Routine of FSUIPC.

Could it be that the P3D crash on exit leaves one/some files in a unclean state which causes the subsequent failure (i.e. crash or minimize during start), and any installation routine touching this file / those files with a complete open, read/write, close brings them back in a normal state?

Joerg

Share this post


Link to post
Share on other sites
37 minutes ago, Joerg Alvermann said:

There is no GUI element left to klick on after the 'crash' or 'minimise'. i.e. there is only the process, but no app listed in the task manager.

Sorry, I thought you said it minimised to the task bar. That means it reduces to an icon in the task bar which should certainly be clickable.

So you really mean is closed completely except for some hung thread. It would be good to identify that thread. You'd need something like Process Explorer for that I think.

41 minutes ago, Joerg Alvermann said:

LINDA and COUATL and AddOnManager:    P3D crash on exit. Subsequent failure on P3D start

Is that with the very latest Addon Manager, released this week?

41 minutes ago, Joerg Alvermann said:

Could it be that the P3D crash on exit leaves one/some files in a unclean state which causes the subsequent failure (i.e. crash or minimize during start), and any installation routine touching this file / those files with a complete open, read/write, close brings them back in a normal state?

Well, yes to the former (though it may be devices or drivers rather than files per se) but I don't know what files "touched" by the FSUIPC Installer could affect anything. It's only the timestamp on he DLL.XML as I said. Maybe the Addon Manager checks that and does something different when it changes. It might be worth asking Virtuali about that.

Pete

 

 

Share this post


Link to post
Share on other sites
5 hours ago, Pete Dowson said:

If it goes to the task bar it simply means that something else has stolen the focus. There are lots of addons which can do that. It is still running!

All you would need to do is click it on the task bar to return the focus and it would re-open its screen!

Pete

 

My error, task manager, not bar.

Share this post


Link to post
Share on other sites

Ok,

 

I'll add my findings here too and hope it helps to resolve the error.

 

I have also since version 4959 (P3D 3.4.) the issue that the sim starts and then "vanishes" into nowhere. Task Manager shows P3D running, all other tools, which are related to P3D do also behave normal as P3D is running. It is not possible to restore the window - even not with ALT+Arrow to move a window, there is no window.

When I reinstall FSUIPC, then it works till I restart my computer, or better said, I send him to sleep mode (energy saving). Can't currently say if the issue persists also, when I shut down the PC completely as I normaly use energy saving (sleep). Once the issue comes up and I reinstall FSUIPC it is gone till the next sleep.

 

I have removed everything LINDA related from the modules folder --> issue persists

I have disabled any other addon in the exe.xml and dll.xml --> issue persists

deleted FSUIPC.ini --> issue persists

disabled FSUIPC in the dll.xml --> issue solved

 

Tried to start with simStarter (what I normally use) and also without simStarter. Tried several saved flights and created new saved flights --> issue persists

 

I have now reverted to FSUIPC v 4949f and have no problems. (I haven't had access to possible version between, just had the 4949f stored somewhere, so couldn't test later ones between 4949f and 4959)

 

 

many thanks!

Share this post


Link to post
Share on other sites
12 hours ago, guenseli said:

I have now reverted to FSUIPC v 4949f and have no problems.

That's an interesting find. 4.949f should crash P3D 3.4 with HotFix2. Are you using Hot Fix 2? 4.949f is not compatible with it -- at least one link is wrong. Can you show me your FSUIPC4.LOG please?

Pete

 

Share this post


Link to post
Share on other sites

Hello,

 

yes, I have HF2 and it runs without problems. I get one red line in the LINDA console (which shows the FSUIPC.log in case of an error), can't remember which. (edit: the friction line) But it runs

 

********* FSUIPC4, Version 4.949f by Pete Dowson *********
Prepar3D.exe version = 3.4.18.19475
Reading options from "F:\Prepar3D v3\Modules\FSUIPC4.ini"
Running inside Prepar3D v3 on Windows 8.0
Module base=24ED0000
User Name="Günter Steiner"
User Addr="-"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
     1250 System time = 07/01/2017 00:22:33
     1250 FLT path = "V:\OneDrive\Dokumente\Prepar3D v3 Files\"
     1250 ------ Module Version Check ------
     1250        acontain.dll: 3.4.18.19475
     1250             api.dll: 3.4.18.19475
     1250        controls.dll: 3.4.18.19475
     1250      fs-traffic.dll: 3.4.18.19475
     1250             G3D.dll: 3.4.18.19475
     1250        language.dll: 3.4.18.19475
     1250            sim1.dll: 3.4.18.19475
     1250        visualfx.dll: 3.4.18.19475
     1250         weather.dll: 3.4.18.19475
     1250          window.dll: 3.4.18.19475
     1250 ----------------------------------
     1250 Trying F:\Prepar3D v3\Modules\SimConnectP3D2.dll
     1250 Found it: trying to connect
     1265 FS path = "F:\Prepar3D v3\"
     1359 ---------------------- Joystick Device Scan -----------------------
     1359 Product= BU0836X Interface
     1359    Manufacturer= Leo Bodnar
     1359    Vendor=1DD2, Product=1001 (Version 1.35)
     1359    Serial Number= B10304
     1359 Product= Saitek Pro Flight Rudder Pedals
     1359    Manufacturer= Saitek
     1359    Vendor=06A3, Product=0763 (Version 1.0)
     1359    Serial Number= Saitek
     1359 Product= Throttle - HOTAS Warthog
     1359    Manufacturer= Thrustmaster
     1359    Vendor=044F, Product=0404 (Version 1.0)
     1359    Serial Number= Thrustmaster
     1359 Product= CH THROTTLE QUADRANT
     1359    Manufacturer= CH PRODUCTS
     1359    Vendor=068E, Product=00FA (Version 0.0)
     1359    Serial Number= CH PRODUCTS
     1359 Product= Joystick - HOTAS Warthog
     1375    Manufacturer= Thustmaster
     1375    Vendor=044F, Product=0402 (Version 1.0)
     1375    Serial Number= Thustmaster
     1375 Product= �
     1375    Manufacturer= �
     1375    Vendor=06A3, Product=0762 (Version 0.48)
     1375    Serial Number= �
     1375 -------------------------------------------------------------------
     1375 LogOptions=00000000 00000001
     1375 -------------------------------------------------------------------
     1375 ------ Setting the hooks and direct calls into the simulator ------
     1375 Failed to find CONTROLS timer memory location!
     1375 ### Failed to obtain SIM1 Frictions access: no frictions facilities available!
     1375     Reason 6: SIM1 base=534F0000
     1375     FrictionAddr=53617220 contains FC000000
     1375     BrakingAddr=536184E0 contains 65776F50
     1375 --- FS Controls Table located ok
     1375 --- Installed Mouse Macro hooks ok.
     1375 --- Wind smoothing fix is installed
     1375 --- All links okay (except older global weather setting method)
     1375 -------------------------------------------------------------------
     1375 SimConnect_Open succeeded: waiting to check version okay
     1375 Trying to use SimConnect Prepar3D
     1390 VRI port 1 "com3" opened
     3093 VRI MCP2B ("MCP2 Boeing") detected on port com3
     3422 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.4.18.19475 (SimConnect: 3.4.0.0)
     3422 Initialising SimConnect data requests now
     3422 FSUIPC Menu entry added
     3437 C:\Users\Guens\Documents\Prepar3D v3 Files\SIMstarter NG.fxml
     3437 F:\Prepar3D v3\SimObjects\Airplanes\WoP3_Spitfire\spitIIa.air
    52078 System time = 07/01/2017 00:23:24, Simulator time = 10:05:36 (09:05Z)
    52078 Aircraft="Spitfire Mk IIa Red Bull"
    58078 Starting everything now ...
    58078 LUA.0: beginning "F:\Prepar3D v3\Modules\ipcReady.lua"
    58078 LUA.0: ended "F:\Prepar3D v3\Modules\ipcReady.lua"
    58093 LUA.1:  *************************** STARTING LINDA **************************
    58093 LUA.1: LINDA:: [START] Loading System Configuration files
    58125 LUA.1: LINDA:: [START] VRInsight MCP Set = mcp2
    58140 LUA.1: LINDA:: [START] System Configuration files loaded
    58140 LUA.1: LINDA:: [START] Aircraft found: A2A B17
    58140 LUA.1: LINDA:: [START] Aircraft found: A2A B377
    58156 LUA.1: LINDA:: [START] Aircraft found: A2A Cessna 172R
    58156 LUA.1: LINDA:: [START] Aircraft found: A2A P40B
    58156 ASN active function link set
    58156 Ready for ASN WX radar
    58156 LUA.1: LINDA:: [START] Aircraft found: A2A Spitfire
    58156 LUA.1: LINDA:: [START] Aircraft found: A2A_C182
    58172 LUA.1: LINDA:: [START] Aircraft found: A2A_Connie_L049
    58172 LUA.1: LINDA:: [START] Aircraft found: A2A_Piper_PA24_250_Comanche
    58172 LUA.1: LINDA:: [START] Aircraft found: A2A_Piper_PA28_180_Cherokee
    58187 LUA.1: LINDA:: [START] Aircraft found: A2A_T6_Texan
    58187 LUA.1: LINDA:: [START] Aircraft found: Aerosoft Airbus
    58187 LUA.1: LINDA:: [START] Aircraft found: Aerosoft Catalina
    58187 LUA.1: LINDA:: [START] Aircraft found: Aerosoft_DHC6
    58203 LUA.1: LINDA:: [START] Aircraft found: Beech King Air 350
    58203 LUA.1: LINDA:: [START] Aircraft found: DA Dornier 27
    58203 LUA.1: LINDA:: [START] Aircraft found: DodoSim_206
    58218 LUA.1: LINDA:: [START] Aircraft found: Douglas DC3 C47
    58218 LUA.1: LINDA:: [START] Aircraft found: Douglas_C-47_V3
    58218 LUA.1: LINDA:: [START] Aircraft found: F1_Kingair B200
    58234 LUA.1: LINDA:: [START] Aircraft found: IRIS PC-21 2014
    58234 LUA.1: LINDA:: [START] Aircraft found: IRIS PC9A
    58234 LUA.1: LINDA:: [START] Aircraft found: Lotus L-39
    58234 LUA.1: LINDA:: [START] Aircraft found: Majestic Dash 8 Q-400
    58250 LUA.1: LINDA:: [START] Aircraft found: MILVIZ_Bell_UH1
    58250 LUA.1: LINDA:: [START] Aircraft found: PMDG 737NGX
    58250 LUA.1: LINDA:: [START] Aircraft found: PMDG 777
    58265 LUA.1: LINDA:: [START] Aircraft found: RealAir B60T
    58265 LUA.1: LINDA:: [START] Aircraft found: RealAir Duke B60 V2
    58265 LUA.1: LINDA:: [START] Aircraft found: T-38A_ADV_MilViz
    58265 LUA.1: LINDA:: [START] Aircraft found: WoP3_P47D
    58281 LUA.1: LINDA:: [START] Aircraft found: WoP3_P51D_civ
    58281 LUA.1: LINDA:: [START] Library found: lib-a2amap.lua
    58281 LUA.1: LINDA:: [START] Library found: lib-aivlasoft.lua
    58297 LUA.1: LINDA:: [START] Library found: lib-ATC.lua
    58297 LUA.1: LINDA:: [START] Library found: lib-fallback.lua
    58297 LUA.1: LINDA:: [START] Library found: lib-FS2Crew.lua
    58312 LUA.1: LINDA:: [START] Library found: lib-fsx.lua
    58312 LUA.1: LINDA:: [START] Library found: lib-IVAO.lua
    58312 LUA.1: LINDA:: [START] Library found: lib-realityxp.lua
    58312 LUA.1: LINDA:: [START] Library found: lib-saitek.lua
    58328 LUA.1: LINDA:: [START] Library found: lib-user.lua
    58328 LUA.1: LINDA:: [START] Library found: lib-VATSIM.lua
    58328 LUA.1: LINDA:: [START] Library found: lib-vrinsight.lua
    58343 LUA.1: LINDA:: [START] Library found: lib-weather.lua
    58359 LUA.1: LINDA:: [START] Airplane Set event caught!
    58359 LUA.1: LINDA:: [START] *************************************************************
    58375 LUA.1: LINDA:: [START] New Aircraft Selected - restarting...
    58375 LUA.1: LINDA:: [START] *************************************************************
    58375 LUA.1: LINDA:: [START] Current Aircraft: Spitfire Mk IIa Red Bull
    58375 LUA.1: LINDA:: [START] Air file: F:\Prepar3D v3\SimObjects\Airplanes\WoP3_Spitfire\spitIIa.air
    58484 LUA.1: LINDA:: [START] Aircraft module detected: A2A Spitfire
    58484 LUA.1: LINDA:: [START] *************************************************************
    58515 LUA.0: LINDA:: [INIT] Starting Initialisation...
    58547 LUA.0: LINDA:: [INIT] Loading Libraries...
    58547 LUA.0: LINDA:: [INIT] loading optional library: linda/libs/lib-aivlasoft
    58562 LUA.0: LINDA:: [LIB]  AivlaSoft library loaded...
    58562 LUA.0: LINDA:: [INIT] loading optional library: linda/libs/lib-ATC
    58562 LUA.0: LINDA:: [LIB]  ATC library loaded...
    58562 LUA.0: LINDA:: [INIT] loading optional library: linda/libs/lib-fallback
    58562 LUA.0: LINDA:: [LIB]  FSX standard library loaded...
    58578 LUA.0: LINDA:: [INIT] loading optional library: linda/libs/lib-FS2Crew
    58578 LUA.0: LINDA:: [LIB]  FS2Crew library loaded...
    58578 LUA.0: LINDA:: [INIT] loading optional library: linda/libs/lib-fsx
    58578 LUA.0: LINDA:: [LIB]  FSX Functions loaded...
    58593 LUA.0: LINDA:: [INIT] loading optional library: linda/libs/lib-IVAO
    58593 LUA.0: LINDA:: [LIB]  IVAO library loaded...
    58593 LUA.0: LINDA:: [INIT] loading optional library: linda/libs/lib-realityxp
    58593 LUA.0: LINDA:: [LIB]  RealityXP library loaded...
    58593 LUA.0: LINDA:: [INIT] loading optional library: linda/libs/lib-saitek
    58609 LUA.0: LINDA:: [LIB]  Saitek Functions loaded...
    58609 LUA.0: LINDA:: [INIT] loading optional library: linda/libs/lib-user
    58609 LUA.0: LINDA:: [LIB]  User Library loaded...
    58609 LUA.0: LINDA:: [INIT] loading optional library: linda/libs/lib-VATSIM
    58609 LUA.0: LINDA:: [LIB]  VATSIM library loaded...
    58625 LUA.0: LINDA:: [INIT] loading optional library: linda/libs/lib-vrinsight
    58625 LUA.0: LINDA:: [LIB]  VRInsight Function Library loaded...
    58625 LUA.0: LINDA:: [INIT] loading optional library: linda/libs/lib-weather
    58625 LUA.0: LINDA:: [LIB]  Weather library loaded...
    58625 LUA.0: LINDA:: [INIT] loading optional library: linda/libs/lib-a2amap
    58640 LUA.0: LINDA:: [LIB]  A2A MAP library loaded...
    58640 LUA.0: LINDA:: [INIT] Initializing Common Variables...
    58640 LUA.0: LINDA:: [COMM] Saitek GUI in use ..
    58687 LUA.0: LINDA:: [INIT] User GLOBAL config loaded...
    58687 LUA.0: LINDA:: [USER] User's modifications script is loaded...
    58687 LUA.0: LINDA:: [INIT] User FUNCTIONS loaded...
    58703 LUA.0: LINDA:: [INIT] VRI MCP config loaded...
    58703 LUA.0: LINDA:: [START] A2A detected
    58718 LUA.0: LINDA:: [START] Prepar3D found
    58718 LUA.0: LINDA:: [INIT] Finalising Initialisation...
    58734 LUA.0: LINDA:: [INIT] Initialising HID devices...
    58984 LUA.0: LINDA:: [INIT] Loading a fallback joysticks config...
    59015 LUA.0: LINDA:: [COMM] DSP Mode 2
    59547 LUA.0: LINDA:: [START] A2A detected
    59547 LUA.0: LINDA:: [START] Prepar3D found
    59547 LUA.0: LINDA:: [COMM] Checking VRI
    59547 LUA.0: LINDA:: [COMM] Enabling VRI
    59562 LUA.0: LINDA:: [COMM] ConnectMCP - Connecting to MCP Panel...
    59562 LUA.0: LINDA:: [COMM] ConnectMCP completed - 618942892
    59562 LUA.0: LINDA:: [COMM] InitMCP - Initialising MCP...
    60031 LUA.0: LINDA:: [COMM] Initializing MCP2 (Boeing)...
    66422 LUA.0: LINDA:: [COMM] InitMCP - completed
    67437 LUA.0: LINDA:: [COMM] MCP Started...
    67437 LUA.0: LINDA:: [COMM] Starting Saitek Panels ..
    67437 LUA.0: LINDA:: [COMM] Saitek Switch Panel available!
    67437 LUA.0: LINDA:: [COMM] Connecting Saitek Switch Panel
    67484 LUA.0: LINDA:: [COMM] Initializing Saitek Switch Panel
    67484 LUA.0: LINDA:: [INIT] Module: A2A Spitfire Started...
    67500 LUA.0: LINDA:: [INIT] Initiating Autosave true
    67687 LUA.0: LINDA:: [INIT] Ready to go, Captain!
    67687 LUA.0: LINDA:: [INIT] ***************************************************************
    67703 LUA.0: LINDA:: [EVNT] Airborne ...
    71578 Sim stopped: average frame rate for last 20 secs = 33.3 fps
    78109 Advanced Weather Interface Enabled
   129078 Sim stopped: average frame rate for last 54 secs = 33.6 fps

 

Share this post


Link to post
Share on other sites
1 hour ago, guenseli said:

yes, I have HF2 and it runs without problems. I get one red line in the LINDA console (which shows the FSUIPC.log in case of an error), can't remember which. (edit: the friction line) But it runs

The frictions cannot be set because of this, shown in the FSUIPC log:

1375 ### Failed to obtain SIM1 Frictions access: no frictions facilities available!
     1375     Reason 6: SIM1 base=534F0000
     1375     FrictionAddr=53617220 contains FC000000
     1375     BrakingAddr=536184E0 contains 65776F50
     

Evidently the friction tables moved in the later P3D. Also  this "controls timer" link doesn't work. 

So, could you try the latest FSUIPC again but with this in the [General] section of the FSUIPC4.INI file, please?

P3dhacks=36

That will eliminate those two "hacks". 

If that works, please split them:

P3dhacks=32

eliminates the controls timer one, and

P3dhacks=4

eliminates the friction tables one.

This will help me enormously track the problem down. Without being able to reproduce it here I have to rely on user results.

Thanks!

Pete

 

Share this post


Link to post
Share on other sites

Hello Pete,

 

ok, now I have made my test run. (nothing disabled, nothing changed)

 

- Installed 4959

- started sim twice without problems, made also a flight, everything normal

- shut down computer in sleep state for a minute, woke it up again

- started P3D again twice, works

 

- shut down computer for about one hour (also sleep state)

- started P3D again several times, error is present: P3D vanishes into the background tasks. Have to kill P3D in task manager background tasks.

(and this is now the very obscure thing, that it just happens after some time the PC was sent to energy saving state (sleep). I have observed this very often with 4959)

No FSUIPC.log is produced

 

- added  P3dhacks=36 as you said - no difference unfortunately. Tried it also several times.

 

- then copied back the FSUIPC.dll 4949 (which I have saved before), but P3D vanishes also into the background task. This is sth. I observed also before. I have to reinstall FSUIPC now with 4959 (have no older installation file, from 4949 I just have the FSUIPC.dll) and then copy back the FSUIPC.dll 4949.

 

- ok, then re-installed with Install FSUIPC4.exe to version 4549 again ---> P3D is working as it should.

 

will copy back then the FSUIPC.dll with 4949. 

 

Hope this helps.

I can assume it must be a horrible scenario for you, sorry ;)

 

Share this post


Link to post
Share on other sites

With really good and intense help from gypsyczar, we've possibly narrowed the crash at start down to one facility FSUIPC offers. the one to display windows on the P3D screen -- those provided for Lua displays and for some other program displays like the Radar Contact menu.

I don't know if these are used by those reporting here with the crash problem, so information about that would be useful.

To prevent FSUIPC providing this facility you can add:

P3dhacks=x80

to the [General] section of the FSUIPC4.INI file.

Currently, if you do this it will also stop traffic deletion working for those traffic management programs -- and FSUIPC's new Traffic Limiter -- but if you no longer can make P3D crash on start with that option added, I'll provide a version early next week with that additional problem fixed whilst I'm investigating why the display facility doesn't work correctly, the way I use it, in 3.4 HF2.

Those who don't get the problem so often, or not at all on old versions of FSUIPC, are probably just lucky. It seems very timing dependent. gypsyczar found that sometimes all was well for several P3D reloads after each other.  And I and Thomas can't make it happen at all. so it is very variable indeed.

Feedback here, please, as and when you can test this. I really need to know if it is something I can solve or something we need L-M to look at.

Pete

 

Share this post


Link to post
Share on other sites

Hello Pete,

I just tested your solution after a fresh re install of FSUIPC. And It works. I started P3D several times. I rebooted my PC and started again P3D in order to confirm.

In fact, I modified FSUIPC4.INI just after a crash of P3D and it did not work. So I decided to try by reinstalling FSUIPC as I have been doing so before each session of P3D. And then it worked.

Bruno

Share this post


Link to post
Share on other sites
17 hours ago, Pete Dowson said:

 

To prevent FSUIPC providing this facility you can add:

P3dhacks=x80

 

Hello,

unfortunately this isn't working here for me.

Share this post


Link to post
Share on other sites
1 hour ago, guenseli said:

unfortunately this isn't working here for me.

I didn't think it was a solution. It was only a test.

We only arrived at that with a series of eliminations of bits in the “P3dhacks” value (there are 14 active bits, each suppressing one set of hacks into P3D). With all of them set my test volunteer could reboot P3D several times without problem, so we moved on to eliminations. With any one or combination, P3D could still be rebooted, but the number of times varied before it crashed (2-5). Only this one, to do with Lua displays, lasted 8 times, as many as all bits set, and he didn’t take it further. I’ve asked him (and now others here, too) to run with it set that way because i still didn’t think this is the problem.

I know you say it fails consistently with 4.959 but not at all with 4.949f, which dates back to early 2016 and was built for P3D 3.1 (15831)! That makes no sense to me at all – if anything that should be worse. It does stop a couple of features working (friction tables and the controls timer, used to let separated Control+1,2,3,4 actions work even with intervening controls from advanced panels) but otherwise is really identical..

So, I think it’s very timing critical, and the differences in the timings of events is making the differences. Even recompiling a module with small changes can change such things. I’ve no idea how to go about “fixing” it, or whether I have anything to actually fix or it’s completely down to L-M.

FSUIPC itself really doesn’t change very much – I may add new facilities, and of course they are changes – but 99% is unchanged from release to release. Even the differences between FSX and P3D are very minor, just different addresses mostly. And they change from each version of P3D to the next, even between Beta releases sometimes. And now, gypsyczar and yourself, between you, have proven that stopping ALL of the special changes in FSUIPC peculiar to P3D doesn't help. There's nothing else to change.

It certainly seems to be some sort of interaction between add-ons, whether only DLLs or EXE's or add-on aircraft (which use DLLs too, either by name or as GAU files). But it is so variable, so time critical, I think, that narrowing it down is going to be well nigh impossible.

I'm wondering if this is specific to P3D3.4 HF2, so I'd welcome feedback from earlier P3D version users to tell us their results with 4.959, which after all is my only supported version. I can't go backwards.

16 hours ago, frenchsimmer said:

just tested your solution after a fresh re install of FSUIPC. And It works. I started P3D several times. I rebooted my PC and s tarted again P3D in order to confirm.

gypsycar was able to restart P3D after with most of the different options removed, one at a time.  Unfortunately it has to be so on EVERY time, not just once, 6 or 50 times. One excption, as we have already, shows it isn't a solution.

I also now think that those who find that reinstalling FSUIPC helps are just seeing the results of a different timing, resulting from the DLL file remaining cached. You could probably do something similar in other ways, like copying it or looking at its properties.

Pete

 

Share this post


Link to post
Share on other sites
Quote

gypsycar was able to restart P3D after with most of the different options removed, one at a time.

 

But be careful as I could also restart P3D several times also with 4959!

The issue begins when I send my computer to sleep or shut down for some time, hope you've taken this into account with your tests. (But I don't know if thats the case with others, too. But it is here a 100% reproduceable thing)

 

As you talk about versions:

the 4949f is just one I have had saved. I used another, more actual version before I have updated to 4959, but can't remember the number. But normaly I keep FSUIPC relatively updated. So, 4949f is just the last backup I had unfortunately. maybe you could provide me the last version before 4959 and I could try this also?

Share this post


Link to post
Share on other sites
1 minute ago, guenseli said:

But be careful as I could also restart P3D several times also with 4959!

Exactly. Hence the rest of my explanation, if you read further.

2 minutes ago, guenseli said:

So, 4949f is just the last backup I had unfortunately. maybe you could provide me the last version before 4959 and I could try this also?

But I don't think any will help. The differences are so minor. And without the P3D-specific differences, they are zero except for the additional facilities which may or may not be used. Like the Traffic Limiter.

And we've now proven that the P3D specific differences are not relevant.

Pete

 

Share this post


Link to post
Share on other sites

Hi,

I also have same issue with P3D v3.4.18.19475 the issue that the sim starts and then "vanishes"
into nowhere. Task Manager shows P3D running, all other tools, which are related to P3D do
also behave normal as P3D is running. It is not possible to restore the window -
even not with ALT+Arrow to move a window, there is no window.  
= My computer behavoir exactly as this.

- The 100% core utilisation sounds very odd indeed
= same behavior here on my computer

I'm wondering if this is specific to P3D3.4 HF2, so I'd welcome feedback from earlier
P3D version users to tell us their results with 4.959, which after all is my only
supported version.
= I ran with P3D v3.4.18.19475 (not hf2)


To Info:
- complete new win10/64 computer installed.
- Complete new P3D installed v3.4.18.19475.
- Addons used Aerosoft-airbus/ezdok-v2/PMDG737-base/ORBX/Linda-v2.8.7 and fsuicp v4959 installed.
- no other flightsim installed, like fsx/FSX-steam..
- uac is completely disable
- run p3d as administrator, and also all installation was done with "right click" and run as administrator
- P3D and all addons installed on dedicate hard-drive and all virusscan(both inline/path) disabled for these folders.
- win10 updated with all win-updates/.net
- lastest nvidia driver (GTX980)

To fix:
- Reinstall fsuicp v4959
- P3D will then start nicely on first atempt, but if i close P3D and want to start P3D again
  it fail as stated above. (even a computer reboot will not solve my issue, need to reinstall fsuicp and then
  p3d will start again.)

To info:
- during first time P3D installation, I used FSUIPC4 4.955 and didnt have any issue, after upgrade to 4959
issue started as descriped above.
- If I remove FSUIPC4.DLL from the modules folder p3d start nicely.


Hope this info can be to some help and diag this issue further.

My log-files =  https://rushfiles.one/client/publiclink.aspx?id=4BYFiK
(if more info/logs needed let me know and I can send)


Brgds
Søren O.

Share this post


Link to post
Share on other sites
56 minutes ago, zoro67 said:

complete new win10/64 computer installed.

I'm starting to think it is a problem with Win10 compatibility, but whether it is P3D or FSUIPC I cannot determine and won't be able to, as it can still occur even if I stop all P3D-specific things from being active in FSUIPC. Also it is suspicious that it only started with 3.4HF2. Maybe users of earlier versions get it too, but no reports so far!

I use it on two Win7 systems with no problems. So far, where I've been told or can deduce it from logs supplied, all folks with this problem are on Win10. I'm still waiting to hear from 5 folks who haven't said and haven't provided logs. I even posted a separate thread asking the Question, but no replies -- yet.

I do know there are dome subtle changes in Win10 which make quite a few programs which are very stable on Win7 crash. Some of my favourite programs (not related to fS) crash randomly, and several of my own cockpit drivers crash or won't even run. This is why I'm sticking with Win7, even to the extent of returning one new PC built for me because it and the supplier wouldn't support Win7 properly. (I found an alternative supplier who could and did provide a similar spec PC with Win7 installed and working fine).

Pete

 

Share this post


Link to post
Share on other sites

can confirm i'm on Windows 10

19 hours ago, guenseli said:

The issue begins when I send my computer to sleep or shut down for some time, hope you've taken this into account with your tests. (But I don't know if thats the case with others, too. But it is here a 100% reproduceable thing)

i can't second that. I have no issues after sending my computer to sleep. P3D start is normal.

==

Let me try to summarize my view:

On my system,

- the P3D crash on startup (i.e. the main issue reported with 4.959 & HF2, were discussing here) is ONLY happening, once i had an P3D "crash on exit" (i.e. the Windows Dialog stating that prepar3d.exe stopped working, when closing P3D).

- It requires GSX (i.e. couatl.exe and bglman.exe, latest versions here) AND linda.lua to be active to reproduce this "crash on exit"

- i don't recall when this 'crash on exit' has been introduced, but it's happening for quite some time (i.e. also monitored with previous versions of FSUIPC, LINDA, GSX. I also I think i monitored it on Win7 already, but am not sure on this) Difference to previous versions however: It's only now (i.e. with 4.959 & HF2) that this 'crash on exit' it's really affecting subsequent starts of P3D

Would be interesting to hear from others affected by the Topic issue, whether they as well have P3D 'crash on exit' after a fresh FSUIPC install.

Pete, you probably did test this when trying to reproduce, but out of curiosity: You mentioned GSX present on your system. Did you also have LINDA installed & active during your tests?

Joerg

P.S. Some spare time to help further analyzing. PM me if i can help

Edited by Joerg Alvermann

Share this post


Link to post
Share on other sites
26 minutes ago, Joerg Alvermann said:

can confirm i'm on Windows 10

That makes 6 out of 10 so far ... the other 4 are as yet unknown.

26 minutes ago, Joerg Alvermann said:

i don't recall when this 'crash on exit' has been introduced, but it's happening for quite some time (i.e. also monitored with previous versions of FSUIPC, LINDA, GSX.

The majority of "crash on exit" problems earlier, with or without LINDA, were probably related to a problem with SimConnect Close, which I provided an INI parameter to avoid -- it was defaulted to avoid it in the FSUIPC releases for P3D3.0-.32 (I think), but 3.3 and certainly 3.4 seemed fine with that function being called, so it was defaulted the other way. It was the same on Win7.

You could try avoiding it again, as a test. Add this to the [General] section of FSUIPC4.INI (or change it if already there).

CallSimconnectEnd=No

26 minutes ago, Joerg Alvermann said:

Did you also have LINDA installed & active during your tests?

No, but neither did other reporters here who experiences the same problems. I don't have LINDA and wouldn't know what to do with it. If it is a possible cause I suspect you'd need to configure it to do something.

26 minutes ago, Joerg Alvermann said:

Some spare time to help further analyzing. PM me if i can help

Thanks. When I have something else to try I'll let you know.

Pete

 

Share this post


Link to post
Share on other sites

Not getting a crash on exit but getting P3D stalled in background on startup.
This only happens with FSUICP 4959.
If I remove FSUICP completely problem goes away.
If I install FSUICP 4958 the problem also goes away.
Tried six or so P3D shut downs and restarts with 4958 and all seems well.
With 4959 P3D will hang on startup with the first or second start after install of 4959.

All this with a fresh install of Win10 and latest P3DV3 full install.

Addons include Orbx FTX AU, A2A planes, PMDG 737, Majestic Dash8.
I usually use LINDA but I have removed it for the above tests.
 

gb.
 

Share this post


Link to post
Share on other sites
57 minutes ago, Pete Dowson said:

You could try avoiding it again, as a test. Add this to the [General] section of FSUIPC4.INI (or change it if already there).

CallSimconnectEnd=No

Tested. With or without that entry, results are the same. P3D crash on exit under certain circumstances:

My assumption is still: The P3D crash on exit is the root cause for the reported failures on subsequent P3D starts. And since I can reproduce the P3D crash on exit with LINDA in place I tried to eliminate that LINDA function which might cause P3D to crash on exit. 

At the end I found 'ipc.display()' at least suspicious. If I eliminate (i.e. comment out)  all 'ipc.display()' function calls in the LUA scripts provided by LINDA, P3D closes normal, and i have no issues on following P3D starts.

As soon as ipc.display() is called only one time,  and I close P3D afterwards, I get the "prepar3d.exe stopped working" message, i.e. P3D crash on exit.

Joerg

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

×

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.