1 minute ago, Woozie said:

Stand alone entry? Its not part of a default prepar3d.cfg and needs to be added manually under the [MAIN] section, if thats what you meant. If there's no entry it will default to 0.33

Thanks, I appreciate your help.  I am about to update to P3D4.5 and I'm gathering as much info as I can. Fingers crossed!

Just now, TomCYYZ said:

Thanks, I appreciate your help.  I am about to update to P3D4.5 and I'm gathering as much info as I can. Fingers crossed!

Anytime!

Good luck then! From which version are you coming from? Major step or just simply applying the hotfix? If you skip multiple versions i would advise to refrain from manual CFG tweaks until you run into any issues that would need a manual tweak. Many of those that were deemed as mandatory for older versions are no longer necessary imho

3 hours ago, Bert Pieke said:

Just did the exact same test, flew at 3000 feet all the way and worked great.

FFTF set to 0.15 since the fftf dynamic app is MIA at present..

Just updated it too :

AGL : 

0 = 0.01

4000 = 0.2

Edited May 14, 20197 yr by GSalden

7 hours ago, simbol said:

Thanks guys, in that case @vbazillio, you might want to confirm you really installed the latest hotfix and actually deleted you P3D config file.

I do have 4.5.12.30293 client installed and I made a mistake looking correctly in the Prepar3D.cfg: I can confirm I do have the UIHardwareAcceleration=True in [USERINTERFACE] section.

Sorry for the inconvenience.

Quote

I'm still curious why people clean out the compiled shaders folder on a version upgrade.

There are times when I have to delete the contents of the Shaders folder (and indeed the Scenery Indexes x64 folder for good measure) without having upgraded anything. If I notice a degradation in performance, cleaning out those folders generally corrects the issue. Don't ask me how. It just does.

Edited May 14, 20197 yr by Christopher Low

OK, I'm good now - managed to get the hotfix running perfectly.  The issue - at least, I think this was the issue - was a scenery.cfg conflct.  I found and removed a stray entry for Turbulent's Terraflora tree set, which I thought I'd uninstalled, but apparently there were traces left behind.  I'm guessing that created problems (conflicting calls?) with the Orbx trees.  Or maybe this was coincidence and something else fell into place.  But for whatever reason, I've now got smooth performance locked at 30 in all the scenarios that were giving me trouble yesterday. Wondering if that might have been my problem with the original 4.5 as well.  I could find out - I've still got the installer - but I'm not going to.  Enough with the agonies - off to fly.

2 hours ago, ZLA Steve said:

Because remnant data is leftover and can cause glitches and issues.

Think of shaders like a glass of wine. It has unique flavors and properties. An update (be it new drivers/version/graphics add-ons) is akin to a new bottle.

You want to rinse out the glass so the old stuff doesn't influence or corrupt the taste of the new stuff.

Is that why poppet was obessed with telling people to delete them? 😏

7 hours ago, simbol said:

Shaders were probably rebuilding..

S.

Not a pause in waiting for shaders to rebuild it was during taxi and take off and flight (dropping frames if you will). 2nd run of P3D was smooth in all afore-mentioned phases.

Testing out true earth GB with Ultra 4096 texture and use high resolution textures  and getting some startling results . Better performance than 1024 texture and fantatic graphics and reasonable fps . I have a high end machine but before hot fix no chance . Other than that same settings as JV recommended ones for TE on orbx website . graphics fantastic.

5 minutes ago, cannow said:

Testing out true earth GB with Ultra 4096 texture and use high resolution textures  and getting some startling results . Better performance than 1024 texture and fantatic graphics and reasonable fps . I have a high end machine but before hot fix no chance . Other than that same settings as JV recommended ones for TE on orbx website . graphics fantastic.

define "reasonable fps" in case of TE GB please 😉 Are you saying you see double digits when flying over London?

no seriously, are we talking about 30+?

37 minutes ago, tooting said:

Is that why poppet was obessed with telling people to delete them? 😏

No, it's because it is one of the recommendations from LM to avoid issues. If you are having issues they recommend you follow a specific procedure, among which is deleting the shaders.

 

Vic

Here I am less happy.

The framerates are good and to make it even less taxing I use Vsync  @ 25 hertz.

With all sliders at medium core 0 is 100%, even with fair weather .

i do use TE NL + FT Amsterdam + PTA, but with 4.5 I did too and core 0 was always 60-95%.

38 over Southampton and smooth DA62 airplane last time I tried London getting some judder more testing to do to find a good setting for london

The Hot Fix has worked a dream for me  .... My P3D using True Earth South was an absolute slideshow until I applied the fix

This is what I did

1. Uninstalled old Client

2. Installed new Client

3. Deleted P3D CFG (For some reason I had 2 ... both deleted)

4. Deleted Shaders Folder

Started P3D 

5. Closed down P3D and went to newly compiled P3D CFG and added the line ...  UIHardwareAcceleration=True under [USERINTERFACE] section.

6. Re-instated all my settings and now it is running like a dream  ...... WELL PLEASED

Paul 

OK, this is odd - today, when I reinstalled the hotfix, the UIHardwareAcceleration=True line was added to the USERINTERFACE section.  Yesterday it wasn't.  I have no idea why.  

Maybe that and not the tree conflict (the one I mentioned in my last post) was the issue.

P3D is a mystery...