3 minutes ago, Sesquashtoo said:

I had a locked 30 constant, but now with the same locked 30, I render between 17-30 but mostly see 22-24 FPS.  So, truly it's an apple to apple, as I adjusted nothing in the sim or the nVidia driver app. Again though, I state that even at 17, there is no stutter, chunk, pause..merely very fluid plane animation. So...the FPS number is only now a curiosity, and not a flag to possible sim jag.

Interesting. As long as there is no stutter, I am happy. While I mostly experience smooth aircraft movement below 30 FPS, panning around the cockpit can result in stutter ruining immersion a bit. 

14 minutes ago, Sesquashtoo said:

I had a locked 30 constant, but now with the same locked 30, I render between 17-30 but mostly see 22-24 FPS.  So, truly it's an apple to apple, as I adjusted nothing in the sim or the nVidia driver app. Again though, I state that even at 17, there is no stutter, chunk, pause..merely very fluid plane animation. So...the FPS number is only now a curiosity, and not a flag to possible sim jag.

Interesting.

I noticed that too and first suspected an add-on. But thanks to the XML method I was able to test/deactivate quickly and even at a modest add-on airport I noticed the FPS problem. In 5.2 locked to 29FPS, now with the same settings around 16FPS or worse. And that with the default aircraft. To me, however, it does not seem very fluid. Oh well...

I will now activate Hyperthreading again and see if the automatically set entries are not optimal for my system (7700k, HT still off):

[JobScheduler]
AffinityMask=15
P3DCoreAffinityMask=15
MainThreadScheduler=0
RenderThreadScheduler=2
FrameWorkerThreadScheduler=3

Edited December 2, 20214 yr by Wolkenschreck

48 minutes ago, 737freak said:

How is VRAM usage of 5.3 compared to 5.2 and 5.1? Has it been improved? 

If you have Miami by Latin VFR that would be a very good test of VRAM usage. My 1080Ti ran out with Ultra set in Texture Resolution.

18 minutes ago, Wolkenschreck said:

[JobScheduler]
AffinityMask=15
P3DCoreAffinityMask=15
MainThreadScheduler=0
RenderThreadScheduler=2
FrameWorkerThreadScheduler=3

Mine is:

AffinityMask=21845
P3DCoreAffinityMask=21845
MainThreadScheduler=0
RenderThreadScheduler=2
FrameWorkerThreadScheduler=4

The last three entries determine which of the cores allocated in the core affinity mask do which jobs.

Mine hasn't changed since 5.2HF1

Although more refined control like this is welcome, it does not negate the fact that P3D seems to operate best (for me, YMMV) with 8 separate physical cores, and supporting apps corralled into the last 2 unused cores on my 10850k.

Hardware (to a point) remains king I'm afraid..

Returning briefly to the despicable actions by Aerosoft with regard to support for its P3D aircraft and v5.3, including those it sold to consumers only days ago during its Black Friday sale, I have posted this over on the Aerosoft forum: https://forum.aerosoft.com/index.php?/topic/168506-p3d-version-53/&do=findComment&comment=1064365

And I don't even own any of their aircraft -- came close to buying the A330 during Black Friday, but went with TFDi and Majestic and I'm glad I did.

15 minutes ago, Iadbound said:

Returning briefly to the despicable actions by Aerosoft with regard to support for its P3D aircraft and v5.3, including those it sold to consumers only days ago during its Black Friday sale, I have posted this over on the Aerosoft forum: https://forum.aerosoft.com/index.php?/topic/168506-p3d-version-53/&do=findComment&comment=1064365

And I don't even own any of their aircraft -- came close to buying the A330 during Black Friday, but went with TFDi and Majestic and I'm glad I did.

And now locked, clearly a nerve had been touched there, with the slight backtrack of a commitment to try to ensure it works with 5.3.

MK is wrong that there haven't been any new developments for P3D.  But whatever, he is entitled to upset his customers as much or as little as he wishes.

I feel sorry for the developers of products that he publishes, who may now lose out on revenue as a result of people making an active choice to not buy through Aerosoft, as they will be the unfortunate casualties of MK shooting from the hip as he did.

Edited December 2, 20214 yr by kevinfirth

So it seems performance is better for some and worse for others?  

Gents, whilst I'm aware that Aerosoft products are affected by the v5.3 release it might be better if you created a separate topic with a suitable title. That is likely to attract more attention than discussion in this one.

21 minutes ago, Iadbound said:

Returning briefly to the despicable actions by Aerosoft with regard to support for its P3D aircraft and v5.3, including those it sold to consumers only days ago during its Black Friday sale, I have posted this over on the Aerosoft forum: https://forum.aerosoft.com/index.php?/topic/168506-p3d-version-53/&do=findComment&comment=1064365

And I don't even own any of their aircraft -- came close to buying the A330 during Black Friday, but went with TFDi and Majestic and I'm glad I did.

Right descision!

Topic has already been locked on their site and initial post has been edited to sound less "harmful".

Very "professional"....

With such approach they wont increase their P3D market anymore xD 

(Last post from my site to this aerosoft topic) Sry Ray 🙂  Just want to add this finally

Edited December 2, 20214 yr by Flyinggok

Fly the Maddog X Support & Community Forums

 

I am happy to announce that our latest update (2.1b826) released on 02/12/2021, released as Open Beta, includes compatibility with Prepar3D v5.3 (5.3.12.28072) among some small fixes and "quality of life" updates (see changelog below).

 

Just got via email

29 minutes ago, Iadbound said:

Returning briefly to the despicable actions by Aerosoft with regard to support for its P3D aircraft and v5.3, including those it sold to consumers only days ago during its Black Friday sale, I have posted this over on the Aerosoft forum: https://forum.aerosoft.com/index.php?/topic/168506-p3d-version-53/&do=findComment&comment=1064365

And I don't even own any of their aircraft -- came close to buying the A330 during Black Friday, but went with TFDi and Majestic and I'm glad I did.

That's just a FU to the P3D customers that have supported them over a decade...

Doesn't surprise me though, their attitude is well known. 

Anyway, back to enjoy 5.3. now 🙂

Mike

Edited December 2, 20214 yr by mikealpha

8 minutes ago, Flyinggok said:

Right descision!

Topic has already been locked on their site and initial post has been edited to sound less "harmful".

Very "professional"....

With such approach they wont increase their P3D market anymore xD 

(Last post from my site to this aerosoft topic) Sry Ray 🙂  Just want to add this finally

The initial post can be found on this thread: avsim.com/forums/topic/609800-future-of-p3d/

Perhaps that topic is more appropiate for discussing Aerosofts actions, as its related to the future of P3D and other devs who still develop/don't develop for the platform. 

Will be flying this around today and part of tomorrow to check things out, reinstall went ok with all the standard sceneries that ppl have all installed nicely or resynched.

One thing I have noticed though, the traffic slider for roads which now include additon on ALL roads is an absolute frame rate killer for VR users on only 20% or lower, setting this to 0 and all smooth again

13 minutes ago, Steve_Ellis said:

Will be flying this around today and part of tomorrow to check things out, reinstall went ok with all the standard sceneries that ppl have all installed nicely or resynched.

One thing I have noticed though, the traffic slider for roads which now include additon on ALL roads is an absolute frame rate killer for VR users on only 20% or lower, setting this to 0 and all smooth again

Thank you, Steve!

Same result for me. I used 30% in 5.2 and had no problems. Moreover, I had a Simmershome' tweak in 5.2, which brought back the ORBX Vector traffic to secondary and territory roads. Thus, enabling all roads in 5.3 seemed reasonable to me. But in 5.3, road traffic seems to have an even bigger affect on FPS. My whish for 5.4: RoadTrafficThreadScheduler 

Edited December 2, 20214 yr by Wolkenschreck

40 minutes ago, Ray Proudfoot said:

Gents, whilst I'm aware that Aerosoft products are affected by the v5.3 release it might be better if you created a separate topic with a suitable title. That is likely to attract more attention than discussion in this one.

Could you or another mod kindly hive these comments to another thread, please?

Back OT, has anyone thrown the proverbial kitchen sink at their v5.3, without using any affinity masks?

@Sesquashtoo has said he has lost up to 8 FPS since the move. Stutter in v5.2 is really noticeable below 22 FPS for me, though I can maintain just above that when using Sim-wings EGLL, Orbx TE GB, a complex payware airliner, tons of AI aircraft and inclement weather.
That's not to forget that the Aerosoft Airbii (if they will be made compatible) fall over when FPS drops below 18.

I wouldn't want to switch if there's a significant performance loss.

@Ray Proudfoot, I look forward to hearing the results of your test scenario.