Did you do a complete fresh install or update Gerard?

Imho too 4.3 looks better. But if the improvements cause more load on the pc ....

 

43 minutes ago, Nyxx said:

Did you do a complete fresh install or update Gerard?

Only the Cliënt Update. I always do that.

 

I did a full 4.3 install fresh on a new Win10, then added the 1b+ usual stuff. I observe a slightly lower FPS with a little more blurries in congested areas, due to the increased load I guess (FSL A319-320). But overall it's acceptable on my hardware, flying between EGLL and EHAM back and forth. P3Dv4.3 looks better.

([email protected], HT On, 16Gb RAM@3000Mhz, GTX 1080Ti)

 

I don’t fly more than 2 hour flights but with a clean full install all is good.

No real idea why but full clean install is always seems better imo.

I always encounter problems with client only etc

Edited July 23, 20187 yr by Nyxx

 

8 hours ago, GSalden said:

Hopefully it is not because of the Shaders as with V4.2 it all worked well.

LM can and do change shader files on release, so if any product is working the shaders they'll need to update and/or be aware also ... I had a similar issue with ENVSHADE but it was resolved by developer soon after V4.3 release.  If you remove PTA does it attempt to restore a backup of the older V4.2 shader files?  If so, this might cause a problem as you'll be operating V4.3 core code expecting V4.3 shaders but you've restore V4.2 shaders from a PTA restore and/or uninstall ... I'm guessing because I don't know how or what PTA does for backing up original shader files and/or how it restores them (if it restores them).

I'm pretty sure the shader files were changed from V4.2 to V4.3 (base clean installs).

Not suggesting that IS the problem, but it's where you might want to start to look.  In my testing V4.3 with a base install (with very limited add-ons, usually a DL aware airport or two) produced slight better results than V4.2 base install with the same airports.  However, I don't use surround or wideview and I would imagine distortion correct is not "free" in terms of FPS and PTA might be an additional burden on that correction process.

Cheers, Rob.

Hi Rob,

With PTA the original Shaders are being backed up and can be restored. I will try with the default Shaders. However I doubt that the Shaders are the cause.

YesterdayI landed at Schiphol Amsterdam , coming from Frankfurt and at the tarmac the framerate was 13-14 fps.

I closed P3D V4.3 and restarted it. With the same addon programs still running ( ASP4 / Live Traffic ) the framerate was 20-22 ....

 

Does perhaps V4.3 let go of flown over scenery less well as V4.2 did ?

1 hour ago, GSalden said:

YesterdayI landed at Schiphol Amsterdam , coming from Frankfurt and at the tarmac the framerate was 13-14 fps.

I always observe exactly this. But this was already the case back in my FSX days and through all P3D versions I used. Starting in LSZH i get 25FPS, flying out of it to EDDF (both AS sceneries with AI traffic), I have 15FPS when touching down in EDDF. Vice versa, starting in EDDF I get about 25FPS, flying out of it to LSZH, I have 15FPS when touching down in LSZH. Always. Since years. I got used to it, but know if you talk about this again, I am curious if there is a fix for this...

i have another point of view for you Gerard,

could this variation you are seeing and trying to compare between versions has to do with features and bugs corrected?
this could mean an elements or effect earlier not expressed are now properly expressed and thus require adjustments?

if you run a feature that's not working; than fixed later in new version how do you expect the same outcome still?
instead you should  first factor which functionality been restored and evaluate how it should be effecting you now vs "i have more frame impact" route

I know that P3D has a tree construction. Every object  scenery around you is attached to a branch. After some time the tree gets too big is slowing down performance.

With each new version LM was able to have branches to let go of objects/scenery after they were passed by.

As Chris stated it might be that new features are improving quality but also a little heavier on the system. Perhaps now the tree construction is letting go of objects/scenery slower than before and when using high settings it might be too much.

Left or right : something is different and people like me , pushing the system to its bounderies will see the framerate loss first..

things better be different in a new version release! 

the guys at LM receive allot of feedback from us during beta sessions,
they are constantly tweaking things internally; each release could effect previous static settings,

sometime we report bugs that result in performance increases as they are fixed,
and some time we report feature not rendering properly and those fixed result in increased performance requirement that fix now chips away from the relieve we got from the other fix, and so on,

new features are constantly added, new autogen added; each build is not static and only address previous build bug fixes; it also introduces new features and new data in many cases; which again could effect the static balance in your area,

That might explain what multiple users are experiencing including myself.

P3D is letting go objects/scenery slower with the same settings/scenery than V4.2 because of all fixes/inprovements that require performance...

Like a Bucket : 3 drops in - 2 drops out ..

that's just natural progression as each release pushes the boundaries of the one preceded it,
in peoples mind LM is only fixing a static build to perfection,

its not office 2018 where you have a bug and report it MS; they release a fix for the bug end of story,
P3D is an ongoing development; meaning its keeps growing and expanding its capabilities with each new release,

we know its not the most comfortable situation; but that's really a small price we have to pay to get more out of our sim's,
im sure no one wishes the old no development FSX days back!?

 

As a final resort I uninstalled Orbx FTX Global , OpenLC , TU Netherlands , FTX Germany , PTA and V4.3 .  

I deleted the appropriate folders that were left by P3D.

After that I uninstalled the Nvidia driver. Then a register clean-up. Ran W10 update , but there were none.

Installed the latest Nvidia driver ( I had the one before ) and reinstalled P3Dv4.3. Then FSUIPC and calibrated the controls.

Reinstalled FTX Global , OpenLC , FTX Germany , TU Netherlands , reinstalled AS Frankfurt Pro and FT Amsterdam Schiphol.

ASP4 is running on a cliënt so just the Simconnect file had to be installed.

 

Theh I tried a flight from Frankfurt to Amsterdam ( 3 seperate views , no Wideview correction ) :

LOD high

SC Dense

AG Normal/Dense

AG radius Medium

Water Low

Cloudshadows quality Low

Cloudshafows distance High

( I use the above settings more than a year and with 3 seperate views compared to 2 views over the last 2 months . )

 

Departing FPS ; 44

Arrivival FPS : 26

No PTA , no AI aircraft , no FFTF Dynamic.

 

Saved the flight at Schiphol, shut down P3Dv4.2 and restarted the saved flight. FPS : 37 

Same behavior as before and I did not even use Live Traffic yet....   

 

 

 

Edited July 25, 20187 yr by GSalden

After reading this thread allthough Denmark is exceeding 30c outside temperature and making it almost impossible to fly (wife controlling our portabel aircondition ) i started to play a little with blurr and DL. I like aircraft lights alot as the immersion for me is not present without so i just disable airport lights if possible. 

I did a flight as BAW203 from EGLL to KBOS using a lower LOD (5.5) and it did help alot with blurrys on my SLI 970.

I hate compromising Scenery Complexity and hasnt tested if there is any performance of relevants with that slider. I recall FSX had some specific settings related to this and it was in general advised to leaving it at max, but that proberly has a different meaning now. 

Thanks Michael Moe