I like more the term "No risk - No fun". :yahoo:

Spirit

I'm all for fun, but flightsims seem to be risk-magnets, in how issues pop up out of nowhere, and dealing with issues is not much fun for me. Rebooting just clears your computer's memory, which is just an additional bit of insurance.

"Obviously P3D v2 won't rebuild the total shader at the 1st start. It will be rebuilt successively. No need to panic."

 

Didn't know that but p3d did not work without a full shader folder - thanks

 

And yes this is the the file location  "C:\Users\[your username]\AppData\Local\Lockheed Martin\Prepar3D v2\Shaders"

Didn't know that but p3d did not work without a full shader folder - thanks

 

Rich, P3D will work fine if you delete the shaders folder ... I've done this a 1000 times.  Just be aware that when P3D starts it will take a while to rebuild and you'll be sitting at a black screen for a few seconds or more, then it will slowly build the scene (can take upto 2 minutes on my system).

 

In fact, if you experience a crash in P3D (especially a g3d.dll crash) it's VERY advisable to delete the entire shaders folder (and there might be other cleanup tasks you need to do before restarting P3D).  Arwen's advice is pretty solid to reboot your PC after a crash if you aren't sure where to look for and what processes to kill that might be still running that could cause P3D crash again on start.  See my tips here: http://forum.avsim.net/topic/441704-recovering-from-g3ddll-crashes-and-tips-to-diagnose/

 

P3D is currently VERY sensitive to 3rd party products that try to do things before those shaders finish building or before the initialization is complete (the joys of threaded applications).  I know any Virtuali items in my DLL.XML or EXE.XML I need to disable when I do a shader rebuild.  In a clean pure P3D I never have a g3d.dll crash, but on a add-on filled P3D with FRAPS and TrackIR and ASN and FS Commander and Lua and FSUIPC etc. etc. all running then things get a little touch and go.  I'm hoping LM will work on "protecting" P3D initialization a little more to make it more resilient to 3rd party add-ons.

 

Cheers, Rob.

Great info Rob - thank you - just installed accu-feel - small edit in p3d xml file - fsuipc was gone and accu-feel was not there - read to re install fsuipc bang worked, maybe this can help someone - I used the fake exe method to install can I use this with other installs - why would I need Estonia tool ?

 

Did not know about the rebuild time involved never noticed that in fsx - as I have a new install I dont think I need to flush it anyway

Great info Rob - thank you - just installed accu-feel - small edit in p3d xml file - fsuipc was gone and accu-feel was not there - read to re install fsuipc bang worked, maybe this can help someone - I used the fake exe method to install can I use this with other installs - why would I need Estonia tool ?

 

Did not know about the rebuild time involved never noticed that in fsx - as I have a new install I dont think I need to flush it anyway

Rich...how did you install Accu-Feel?   Please print Accu-Feel installation into P3D for Dummies...  

 

Thanks..

 

 

I'm hoping LM will work on "protecting" P3D initialization a little more to make it more resilient to 3rd party add-ons.

 

So, when I see the scene building before my eyes...that is a normal P3D occurrence?   I thought it was fatigued G card RAM...  Whew....

One should keep in mind that P3D V2.2 (unlike V1.4) is a new platform. Out of the box it runs quite well.

 

It's up to add-on developers, including ourselves to adjust to the new platform.

 

Therefore don't load your favorite add-on you loved so much under FSX this time in P3D V2.2 and assume the bad performance is down to a flawed sim.

Gerald understood - thanks

 

Mitch just go to a2a forums as I am not home you will get files and directions to do it - but in a nutshell I would just download the latest Accu-feel program - then there is a patch in the forum - you will create a fake fsx.exe - just find a text file or something and rename it and place it into your main P3D folder - route the installer to your main P3D folder it will see fake exe - also you need to edit your xml file - then you need to reload fsuipc after you loaded Accu-feel - I can do a better job for you but that will not be for about 9 hours from now so you may want to go to a2a forums as they explain very well - thanks

Gerald understood - thanks

 

Mitch just go to a2a forums as I am not home you will get files and directions to do it - but in a nutshell I would just download the latest Accu-feel program - then there is a patch in the forum - you will create a fake fsx.exe - just find a text file or something and rename it and place it into your main P3D folder - route the installer to your main P3D folder it will see fake exe - also you need to edit your xml file - then you need to reload fsuipc after you loaded Accu-feel - I can do a better job for you but that will not be for about 9 hours from now so you may want to go to a2a forums as they explain very well - thanks

Thanks rich for that!  It will be another on my to-do P3D evolution walkway...

Thanks again.

Mitch here you go update and instructions - enjoy

 

http://www.a2asimulations.com/forum/viewtopic.php?f=90&t=34173&hilit=2.091

 

 

http://a2asimulations.com/forum/viewtopic.php?f=89&t=33313

Rich, P3D will work fine if you delete the shaders folder ... I've done this a 1000 times.  Just be aware that when P3D starts it will take a while to rebuild and you'll be sitting at a black screen for a few seconds or more, then it will slowly build the scene (can take upto 2 minutes on my system).

 

In fact, if you experience a crash in P3D (especially a g3d.dll crash) it's VERY advisable to delete the entire shaders folder (and there might be other cleanup tasks you need to do before restarting P3D).  Arwen's advice is pretty solid to reboot your PC after a crash if you aren't sure where to look for and what processes to kill that might be still running that could cause P3D crash again on start.  See my tips here: http://forum.avsim.net/topic/441704-recovering-from-g3ddll-crashes-and-tips-to-diagnose/

 

P3D is currently VERY sensitive to 3rd party products that try to do things before those shaders finish building or before the initialization is complete (the joys of threaded applications).  I know any Virtuali items in my DLL.XML or EXE.XML I need to disable when I do a shader rebuild.  In a clean pure P3D I never have a g3d.dll crash, but on a add-on filled P3D with FRAPS and TrackIR and ASN and FS Commander and Lua and FSUIPC etc. etc. all running then things get a little touch and go.  I'm hoping LM will work on "protecting" P3D initialization a little more to make it more resilient to 3rd party add-ons.

 

Cheers, Rob.

 

Rob,

 

One interesting thing I have found is that adding third party scenery takes a couple of further steps in P3D. My ritual now is....after installing third party scenery, go to the Scenery Library, and although the entry is already there and active, simply hit "OK"....it refreshes the scenery library and you can visually see the difference.

 

At that point I like to exit P3D, and refresh the shaders cache folder....next time I load P3D it takes a little while to build the shaders but the results are worth it.