I agree but one would think that, considering there is only ONE "shaders" folder it would be understood. Somehow I guess people get confused and think ShadersHLSL is the same as Shaders.

 

Better to be safe than sorry.

 

Vic

 

 

Hey Vic, that's a nice system you got there!

Thanx Rick - it seems to be doing the job. I don't think there's a system built yet that will run P3D "perfectly" but I have no complaints.

 

Vic

Richard,

 

In post #21, William states that the shaders folder to be deleted is located in the Appdata/Local/LockheedMartin/Prepar3D folder. If that is the case, then simply stating that the "shaders folder should be dumped" now and again isn't particularly informative. We need to know the exact folder to be deleted, otherwise we may end up getting in a mess.

 

Chris I was at work and after a 2 hour ride home (I live 22 min) 4 hours a day in traffic is awesome lol NOT anyway I could not give you the exact info required - here you go

 

C:\Users\Rich\AppData\Local\Lockheed Martin\Prepar3D v2

 

Delete the entire folder and contents - dont empty reyclebin until you know you have done it right

Thanx Rick - it seems to be doing the job. I don't think there's a system built yet that will run P3D "perfectly" but I have no complaints.

 

Vic

 

Your welcome and you are right about a system - been a long wait and shall be a lot longer

Thanks, Richard. I was just worried that someone might delete the wrong folder!

Wow, thats a lot of to & fro'ing!

Just my suggestion, why not just install the program where it wants to go, obviously drop UAC right down, as all it does is nag! Nothing else!

Then, without tweeking, deleting, modifying anything... Just try & fly the program.

(I installed FS9 (2x), FSX (now dumped) & P3D, in default install paths, after I dropped UAC right down.

Never a days problem or issue.

I have never had a problem with installing FSX or P3D in the Program Files (x86) folder, and with UAC switched off.

Thank you Christopher... Methinks this installing to other directories is actually just an urban legend perpetuated & repeated by so many guys without even trying it.

ALL UAC does is Nag! Nothing else.

The consideration for a separate drive for p3d is a good one. I definitely recommend that simply due to the fact that once you begin amassing scenery files and such. The install can grow rapidly. It is a simple thing to upgrade the Harddrive and copy over the data if it's a separate drive.

Even a better idea that I tried & it works!

I put all my scenery & add-on scenery in separate files on a separate drive & when adding scenery, just told the scenery library to look there.

This way, you can also share scenery betweem FSX & P3D. You can also set up secondary folders for your aircraft as well on other drives.

Thank you Christopher... Methinks this installing to other directories is actually just an urban legend perpetuated & repeated by so many guys without even trying it.

ALL UAC does is Nag! Nothing else.

Wobbie, you can call it whatever you like, but the facts are that over the years having FS9/FSX/P3D installed anywhere other that the default location solves many issues folks have had.

 

Chief among such problems have been third-party gauges and utilities that need to make changes on files while the sim is running (real-time updates). Having the sim installed in the ..\Program Files folder frequently prevents such software from doing its job.

 

In addition, with many computers using small SSD for their operating system, there are potential problems with insufficient space remaining on the drive.

 

Frankly, IMHO having a reasonably short pathname to the sim is also a huge plus... :Whistle:

As for the easiest way to deal with the shader cache, one can simply add this entry to the Prepar3D.cfg file to have them automatically recompile any time a change is made to the Prepar3D.cfg file!

GRAPHICS]
SHADER_CACHE_VERSION=1	

Oh, cool!

Maybe I've been lucky by not having any hassles, not even 1 with both my FS9 installs, FSX as well as P3D. And I have a huge amout of payware palanes & scenery in all my installs. My FSX total file size was about 80 odd Gigs before I deleted it, My P3D, probably the same now, & my 2 FS9's at least double.

So, I cannout buy into 'Gauge'i ssues & such like.

 

Has anyone here had any problems by installing any of the sims into default directories with UAC turned down? No heresay please.

It just cannot be me alone that does not have any hassles doing it that way?

Wobbie - just because you hold a bomb that hasn't exploded, doesn't mean it will not explode.

 

Search through the internet for users who have had issues with the (x86) folder. ANY competent computer consultant knows that the (x86) folder is marked special by Windows. Turning off UAC does NOT affect THIS folder.

 

Developers are becoming wise to Windows foibles and are programming around it but SOONER or LATER - it will get you.

 

If a program tries to write ANYTHING to the (x86) folder without the special permissions enabled, not only will it fail, Windows won't tell you why it failed.

 

Since you have not had any issues, and I know there are many like you - stay with it BUT when you run into a serious issue with the program, you won't be able to eliminate THAT as a cause.

 

You may call it "folklore" but most folklore has been shown to be based upon fact.

 

Let's put it this way - you MAY or may NOT have problems if you install to (x86) but you definitely will NOT if you do not install to (x86).

 

Vic

In 4 years, not one problem. I have also installed & reinstalled on about 20 PC's at our VA. So, not a fairy tale. Anway…
 

Wobbie - just because you hold a bomb that hasn't exploded, doesn't mean it will not explode.

 

Search through the internet for users who have had issues with the (x86) folder. ANY competent computer consultant knows that the (x86) folder is marked special by Windows. Turning off UAC does NOT affect THIS folder.

 

Developers are becoming wise to Windows foibles and are programming around it but SOONER or LATER - it will get you.

 

If a program tries to write ANYTHING to the (x86) folder without the special permissions enabled, not only will it fail, Windows won't tell you why it failed.

 

Since you have not had any issues, and I know there are many like you - stay with it BUT when you run into a serious issue with the program, you won't be able to eliminate THAT as a cause.

 

You may call it "folklore" but most folklore has been shown to be based upon fact.

 

Let's put it this way - you MAY or may NOT have problems if you install to (x86) but you definitely will NOT if you do not install to (x86).

 

Vic

 

I agree with Vic and the other guys. This is a well known issue about not letting our sim install or point to the Programs folder. I have built 3 computers in the past 15 years of siming and along the years, we've come across several issues with said folder; thus, the reason why all the "most developers and know-a lot-sim guys" will caution you not to install the simulator on that folder.

 

Anyway Wobbie, either you are extremely lucky  (1 in a million), or the errors have been there but you did not  realize why they happened.