Hey guys

I cannot figure out as to why P3d hangs on close?

chaseplane and P3d closes from taskbar.

but still running in task manager.

sometimes 2 instances of P3d  exe running.

Thanks

mike

It is normal for my P3D to still appear as running in Process Explorer (more powerful version of a task manager) for up to 90 sec after I close it.  If it is lasting longer than that then it is probably because of a child process (an add-on that uses a dll) is not closing and is keeping the parent process (P3D) open.

 

23 minutes ago, downscc said:

It is normal for my P3D to still appear as running in Process Explorer (more powerful version of a task manager) for up to 90 sec after I close it.  If it is lasting longer than that then it is probably because of a child process (an add-on that uses a dll) is not closing and is keeping the parent process (P3D) open.

 

It is in fact a dll ,thanks for the response.

How do i fix that?

thanks 

mike

47 minutes ago, mikeymike said:

It is in fact a dll ,thanks for the response.

How do i fix that?

I've been seeing this as long as I've had v5.x installed.  Seems that if I'm at airports where the ORBX module(s) are loaded, it pretty consistently does it, but I see the phantom process other times as well.  Usually I can tell, because my auto-run executables like FFTF Dynamic don't terminate when the sim window closes, but other times it's just P3D hanging out in the running process list.  I don't know of a way to troubleshoot it, short of running a debugger and some very time intensive investigative work.  It's mostly just a nuisance.

I've taken to checking in Process Lasso and manually terminating Prepar3D.exe, or just rebooting between sim sessions.

The problem is thou, well with me anyways. I notice if I have to close the exe via process lasso more than a few times it seems to corrupt the P3d cfg and I get poor fps and I have to rebuild it and all is well again.

cheers

mike

4 minutes ago, mikeymike said:

The problem is thou, well with me anyways. I notice if I have to close the exe via process lasso more than a few times it seems to corrupt the P3d cfg and I get poor fps and I have to rebuild it and all is well again.

If you're seeing config file corruption, I would strongly advise using something like the Lorby-SI P3D Addon Manager to take and keep a current snapshot of your config files.  It's a one-click deal to restore them...much less risky than having to rebuild them after an abnormal termination.  If something were to booger-up your scenery.cfg or add-ons.cfg files, for example, it'll be a whole lot more trouble than just letting P3D rebuild a default one.

Just now, w6kd said:

If you're seeing config file corruption, I would strongly advise using something like the Lorby-SI P3D Addon Manager to take and keep a current snapshot of your config files.  It's a one-click deal to restore them...much less risky than having to rebuild them after an abnormal termination.  If something were to booger-up your scenery.cfg or add-ons.cfg files, for example, it's be a whole lot more trouble than just letting P3D rebuild a default one.

Interesting, thanks.

I do use lorby addon manager.

I haven’t noticed the restore button.

I’ll have to look into it again.

cheers

mike

It's in a "Backup/Restore" tab that you may not see unless you scroll the tabs to the right.  There's a very handy one-click backup that will save (or restore) all your important config info.