Sign in to follow this  
Bobsk8

Closing down V3.1, always results in "not responding".

Recommended Posts

Installed V 3.1 today and I have noticed that each time I close P3d, It says that it is not responding and it takes several attempts to close the program rather than just closing like v3.0 and 2.5 did. Anyone else see this?  

Share this post


Link to post
Help AVSIM continue to serve you!
Please donate today!

Have you already tried to run prepar3D.exe with administrator rights?

Share this post


Link to post

Have you already tried to run prepar3D.exe with administrator rights?

 

Always do. I just read a post on the P3D forum where someone else is having the exact same issue. 

Share this post


Link to post

Looked into this some more today and found out this only happens with the PMDG 737 NGX, which didn't do this in V3. All other aircraft allow P3D to shut down normally.  All I changed in P3D was the client when moving to 3.1. 

Share this post


Link to post

Something in your EXE.XML is not unloading and hence is keeping P3D open even if it looks like it shutdown.  I had this issue when my internet connection went down and ASN was running.

 

DLL.XML entries shouldn't stop P3D from unloading ... but you can always disable them and test.

 

Cheers, Rob.

Share this post


Link to post

I actually had this same error today after flying the PMDG NGX with 3.1 and shutting down... oddly, I tried to repeat things and it shut down fine the next few times I tried while flying the NGX. Just a one off wierd thing, dunno.

 

Running great though, no complaints.  This is after a fresh install of 3.1 with only the NGX installed so far.

Share this post


Link to post

Something in your EXE.XML is not unloading and hence is keeping P3D open even if it looks like it shutdown.  I had this issue when my internet connection went down and ASN was running.

 

DLL.XML entries shouldn't stop P3D from unloading ... but you can always disable them and test.

 

Cheers, Rob.

 

That sounds a bit over my head to troubleshoot. What I just tried now, is when I get ready to shut P3D, I switch to another aircraft first, in this case the Airbus 320, and then after that aircraft loads up it shuts down normally. Just doesn't like shutting down with the 737 NGX. 

Share this post


Link to post

That sounds a bit over my head to troubleshoot.

 

DLL.XML and EXE.XML are key files if you use any add-ons at all, like PMDG, ASN, Orbx ... troubleshooting a problem should almost always start by disabling entries in these two files or simply rename the file if you don't want to get into editing.

 

As much as we'd all like to see users completely insulated from everything ... and the user can be insulated if they don't run any 3rd party products (but who does that?) ... then unfortunately will need to get familiar with some basic elements of their flight simulator ... trust me, it'll save you time surfing the web for answers to problems.

 

Of course the other option many like to take is to just blame LM and tell'em to fix it ... but that rarely solves problems and in most cases just ends in frustration.

 

The PMDG will have a couple of entries in the DLL.XML and ASN will have one also ... my hunch is ASN ... like I said earlier, if ASN was in the middle of downloading and I exit P3D while it is downloading, P3D will go away (back to desktop) but the Prepar3D.exe would stay running indefinitely.  Products most likely to keep P3D active (not responding after exit) are any products that "hack" the core P3D files (ASN, ObjectFlow, etc.).

 

I suspect your changing of aircraft was NOT related to the issue, it worked because ASN wasn't downloading at the time.  The inconsistency of it working then not working sometimes also leads me to believe it's ASN.  But to be fair to ASN, their V3.1 build is a BETA build.

 

Cheers, Rob.

Share this post


Link to post

Out of curiosity, while in the middle of my P3Dv3.1 reinstall day (update worked fine, but every so often I like to start fresh and limit what I install) I tried the PMDG 777 as well, and it has the same closing P3D problem.

 

Fresh 3.1 install, then FSUIPC and sim connects, then first addon was NGX, had the close issue once.  Next installed PMDG 777 and sim has the same closing issue.  ASN is not installed yet.

 

Then installed the Iris Grob (fantastic plane, just buy it, LOVE IT!) and sim closes just fine.

 

Not a big deal that I can tell, but something with the PMDG P3D stuff is causing the closing issue with v3.1.  Otherwise, fly and perform as expected.  Sure won't keep me from flying them, but Bob is not alone in this one.

Share this post


Link to post

I unchecked the box in P3D General Settings that says "prompt on exit" .  It then shuts  down instantly. :smile:

  • Upvote 1

Share this post


Link to post

If your only having the "not responding" on the NGX and you have FS2Crew for the 737 its probably the error I see about fs2crew gauge did not unload or something along those lines.  Get appcrashview and you can see the module causing the problem.  Mine happens to be that module.

Share this post


Link to post

I run ASN but not any PMDG stuff and I've had no real issues. I've noticed it takes a few seconds for P3D to unload from task manager ut I don't get any long term hangs.

 

 

Vic

Share this post


Link to post

In similar instances, I open task manager first and take a look at the "processes."  Sometimes an addon program I thought was closed is still running and it hangs P3D when P3D tries to shut down. If you terminate the process, P3D will shut down.  You can then try and find out why the addon is not properly shutting down.  I think in layman's terms this is the EXE.XML business Rob mentioned, but I could be wrong.

Share this post


Link to post

I run ASN but not any PMDG stuff and I've had no real issues. I've noticed it takes a few seconds for P3D to unload from task manager ut I don't get any long term hangs.

 

 

Vic

 

Only happens with PMDG 737 in a couple of cases and PMDG 777 reported by two other people running P3d V 3.1

In similar instances, I open task manager first and take a look at the "processes."  Sometimes an addon program I thought was closed is still running and it hangs P3D when P3D tries to shut down. If you terminate the process, P3D will shut down.  You can then try and find out why the addon is not properly shutting down.  I think in layman's terms this is the EXE.XML business Rob mentioned, but I could be wrong.

 

Tried that. Nothing running except P3D v3.1  When I hit exit, within about 5 seconds task manager says P3D is " not responding".  About 25 seconds later the screen pops up that asks if I am sure I want to exit the program. When I click that, it shuts down instantly. This only happens with PMDG 737 NGX, not other aircraft, and this never happened with Version 3.0. 

Share this post


Link to post

I unchecked the box in P3D General Settings that says "prompt on exit" .  It then shuts  down instantly. :smile:

 

FSUIPC will save a previous flight if you have prompt on exit enabled but it won't with it disabled. I wonder if the hang has something to do with FSUIPC trying to save that flight (with the NGX)?

Share this post


Link to post

FSUIPC will save a previous flight if you have prompt on exit enabled but it won't with it disabled. I wonder if the hang has something to do with FSUIPC trying to save that flight (with the NGX)?

 

Now that's a thought, since it would have to save much more with the PMDG than with some of the other aircraft. I didn't realize it saved anything when I didn't check "auto save" in FSUIPC. I still wonder why this wasn't happening in 3.0, but then this is a new version of FSUIPC which I just downloaded when I installed 3.1. I decided as long as I know it will eventually shut down in 30 seconds, I will just leave the prompt on exit enabled.  

Share this post


Link to post

PMDG 737 and/or 777 will have two entries in your DLL.XML, try to disable them and see if the problem persists.

 

 <Launch.Addon>
    <Name>PMDG Interface</Name>
    <Disabled>True</Disabled>
    <Path>PMDG\DLLs\PMDG_Interface.dll</Path>
    <DllStartName>module_init</DllStartName>
    <DllStopName>module_deinit</DllStopName>
  </Launch.Addon>
 
  <Launch.Addon>
    <Name>PMDG HUD interface</Name>
    <Disabled>True</Disabled>
    <Path>PMDG\DLLs\PMDG_HUD_interface.dll</Path>
    <DllStartName>module_init</DllStartName>
    <DllStopName>module_deinit</DllStopName>
  </Launch.Addon>
 
There are two possible locations of your DLL.XML and EXE.XML -- these are:
 
C:\ProgramData\Lockheed Martin\Prepar3D v3 
C:\Users\Rob\AppData\Roaming\Lockheed Martin\Prepar3D v3
 
These two locations for DLL.XML and EXE.XML get merged (in memory) on loading of P3D.  I believe PMDG update the DLL.XML in "Roaming" path ... but it's good to check both sets of DLL.XML and EXE.XML to make sure you do NOT have duplicate entries.
 
Cheers, Rob.

Share this post


Link to post

 

 


I didn't realize it saved anything when I didn't check "auto save" in FSUIPC.

 

There's a setting in FSUIPC.ini but I hadn't seen it in the GUI. Haven't tried it myself but maybe set this to "No" and turn prompt on exit back on just to see if the hang goes away?

 

[General]
SavePreviousFlight=Yes

  • Upvote 1

Share this post


Link to post

 

PMDG 737 and/or 777 will have two entries in your DLL.XML, try to disable them and see if the problem persists.

 

 <Launch.Addon>
    <Name>PMDG Interface</Name>
    <Disabled>True</Disabled>
    <Path>PMDG\DLLs\PMDG_Interface.dll</Path>
    <DllStartName>module_init</DllStartName>
    <DllStopName>module_deinit</DllStopName>
  </Launch.Addon>
 
  <Launch.Addon>
    <Name>PMDG HUD interface</Name>
    <Disabled>True</Disabled>
    <Path>PMDG\DLLs\PMDG_HUD_interface.dll</Path>
    <DllStartName>module_init</DllStartName>
    <DllStopName>module_deinit</DllStopName>
  </Launch.Addon>
 
There are two possible locations of your DLL.XML and EXE.XML -- these are:
 
C:\ProgramData\Lockheed Martin\Prepar3D v3 
C:\Users\Rob\AppData\Roaming\Lockheed Martin\Prepar3D v3
 
These two locations for DLL.XML and EXE.XML get merged (in memory) on loading of P3D.  I believe PMDG update the DLL.XML in "Roaming" path ... but it's good to check both sets of DLL.XML and EXE.XML to make sure you do NOT have duplicate entries.
 
Cheers, Rob.

 

 

OK, will try it and report back. 

Share this post


Link to post

 

PMDG 737 and/or 777 will have two entries in your DLL.XML, try to disable them and see if the problem persists.

 

 <Launch.Addon>
    <Name>PMDG Interface</Name>
    <Disabled>True</Disabled>
    <Path>PMDG\DLLs\PMDG_Interface.dll</Path>
    <DllStartName>module_init</DllStartName>
    <DllStopName>module_deinit</DllStopName>
  </Launch.Addon>
 
  <Launch.Addon>
    <Name>PMDG HUD interface</Name>
    <Disabled>True</Disabled>
    <Path>PMDG\DLLs\PMDG_HUD_interface.dll</Path>
    <DllStartName>module_init</DllStartName>
    <DllStopName>module_deinit</DllStopName>
  </Launch.Addon>
 
There are two possible locations of your DLL.XML and EXE.XML -- these are:
 
C:\ProgramData\Lockheed Martin\Prepar3D v3 
C:\Users\Rob\AppData\Roaming\Lockheed Martin\Prepar3D v3
 
These two locations for DLL.XML and EXE.XML get merged (in memory) on loading of P3D.  I believe PMDG update the DLL.XML in "Roaming" path ... but it's good to check both sets of DLL.XML and EXE.XML to make sure you do NOT have duplicate entries.
 
Cheers, Rob.

 

 

Tried these suggestions. In program data no entry for PMDG at all.  In users, the only entry was for the HUD, which I disabled. Nothing for interface.  Same problem.   

There's a setting in FSUIPC.ini but I hadn't seen it in the GUI. Haven't tried it myself but maybe set this to "No" and turn prompt on exit back on just to see if the hang goes away?

 

[General]

SavePreviousFlight=Yes

 

There was no entry in the .ini for SavePrevious flight. 

Share this post


Link to post

There was no entry in the .ini for SavePrevious flight. 

 

I believe I may have added that myself now that you mention it, SavePreviousFlight=Yes is apparently default behavior as I don't have it in my FSX version of FSUIPC.ini, yet it still saves the flight. You could put SavePreviousFlight=No anywhere under the [General] section.

Share this post


Link to post

I believe I may have added that myself now that you mention it, SavePreviousFlight=Yes is apparently default behavior as I don't have it in my FSX version of FSUIPC.ini, yet it still saves the flight. You could put SavePreviousFlight=No anywhere under the [General] section.

 

OK, will try that tomorrow. 

Share this post


Link to post

I believe I may have added that myself now that you mention it, SavePreviousFlight=Yes is apparently default behavior as I don't have it in my FSX version of FSUIPC.ini, yet it still saves the flight. You could put SavePreviousFlight=No anywhere under the [General] section.

 

You are genius.  That fixed it.....

Share this post


Link to post

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