55 minutes ago, lagaffe said:

Currently, in my opinion, on these DX12 problems, it does not seem to me that it is NVidia that is late but Microsoft/Asobo since the Beta version for Steam works very well.

That’s promising. How is it compared to the previous beta? Does it seem stable? In the last one a lot of users were getting “GPU-related” CTDs.

1 hour ago, lagaffe said:

since the Beta version for Steam works very well.

just like the store version. the code is the same for both branches and we, the store beta people, had version .20 also for a short while until they automatically downgraded us over night back to v.18 when they discovered the add-on and configuration options were gone for the store beta testers. My impression is it was just a matter of authentication server/licensing, that is why the store beta users didn't see their store add-on purchases and until that licensing issue is fixed, probably monday/tuesday, the quick and easy solution for MSFS was to revert the store SU10 beta testers to the previous beta version.

Edited September 11, 20223 yr by turbomax

2 hours ago, lagaffe said:

Currently, in my opinion, on these DX12 problems, it does not seem to me that it is NVidia that is late but Microsoft/Asobo since the Beta version for Steam works very well. I don't believe that NVidia develop many version of its drivers at the same time.

If I understand correctly, the Nvidia driver is to help with the VRAM graphical glitches with DX12, not just the performance.

Edited September 11, 20223 yr by Tuskin38

9 minutes ago, Tuskin38 said:

If I understand correctly, the Nvidia driver is to help with the VRAM graphical glitches with DX12, not just the performance.

It’s all a bit blurry as they haven’t really let us in on the details. There some speculation on the official forums that, as they disabled the “VRAM memory manager on nVidia GPUs” due to the reported visual glitches, they rolled DX12 back to a pre-beta version. This is somewhat consistent with DX12 performance reports after that, as it has been stuttery like in SU9.

EDIT: as I understand it, DX12 is for performance. DX12 was launched back in 2014, and with recent CPUs focusing more and more on cores and threads, now is the time to start using DX12 in a flight sim, due to the potentially amazing multithreading usage.

Edited September 11, 20223 yr by Cpt_Piett

the DX12 Vram memory optimisation feature improved performance and at the same time introduced some graphical glitches (according to Asobo: due to bugs in the current NVidia driver) which obviously have been fixed in the next driver release.

5 minutes ago, turbomax said:

which obviously have been fixed in the next driver release.

Fingers crossed! 

Incidentally, as I’m typing this on my iPad, I have minutes left on my general aviation world tour. As it turned out I’ve been granted a beautiful sunset as I approach Jakarta over the Java Sea 🌅

Surely that’s a sign that we’ll get awesome mouthwatering DX12 performance in less than a week, right?

Edited September 11, 20223 yr by Cpt_Piett

Look ma, am I getting mouth- and ramp watering frame rates of 45 fps, and that is still the "old" v1.27.18.0 - SU10 beta @ 4K resolution RTX3090 and no crash using old NVidia driver 512.15 at Flightbeam KPDX. imagine another staggering 3-5 fps next week. ! increíble ¡

Edited September 11, 20223 yr by turbomax

Good stuff @turbomax! I've had excellent performance with DX11 and (for me) more importantly, crash-free for the duration of .18. Quite sensational in fact. No CTDs from Tokyo to Jakarta in my trusted Chancellor 😎

Edited September 11, 20223 yr by Cpt_Piett

23 minutes ago, turbomax said:

imagine another staggering 3-5 fps next week. ! increíble ¡

I’m not sure if you’re being sarcastic or not. I think you are? Anyways, it’s not about the FPS, it’s about frame timing and smoothness. I’d happily lose a few fps if it were super smooth, and that is what DX12 brings when it’s optimised properly, smoothness! 

10 hours ago, turbomax said:

they mention mostly Vulcan and Linux specific issues, so perhaps those x-anadu 12 users have a 1 week advantage 😊

Vulkan Beta Driver Release Updates

September 1st, 2022 - Windows 517.22, Linux 515.49.15

 

In Xanadu did Kubla Khan

A stately pleasure-dome decree:

Where Alph, the sacred river, ran

Through caverns measureless to man

Down to a sunless sea.

And all should cry, Beware! Beware!

His flashing eyes, his floating hair!

Weave a circle round him thrice,

And close your eyes with holy dread

For he on honey-dew hath fed,

And drunk the milk of Paradise.

 

16 minutes ago, Ianrivaldosmith said:

I’m not sure if you’re being sarcastic or not. I think you are?

I am sure I am.

21 minutes ago, Ianrivaldosmith said:

and that is what DX12 brings when it’s optimised properly, smoothness! 

you are absolutely right. should have said "1-2 fps more". people expect magic wizardry from going to DX12. I was trying to simplify the complex subject of DX12's new optimising scheduler, frame times and circuit breakers for the VFR flyers among us. 😀

Edited September 11, 20223 yr by turbomax

7 minutes ago, turbomax said:

I am sure I am.

Hah! I knew it 😅

Just for fun 😃 Do you know the differences between DX11 and DX12?

Apart from the fact that DX12 is more up-to-date, the main technical points are VRAM management.
a) On DX11, the management of this memory is mainly done by the operating system, whereas on DX12, this management is deferred to the application. This induces a lot more work for the programmers in order to make an efficient port.
On the other hand, DX12 is designed to be much closer to the hardware than DX11 is, which allows, among other things, when the programming is well done, to have a faster rendering.
So yes, a DX12 game will be a bit faster but it will require a lot of work from the developers to ensure this.

b) Another counterpart is a more delicate memory consumption (VRAM) and more often a higher VRAM usage (complexity of management by the programmers).
If you refer to the discussions on Prepar3D during the transition to DX12, you will see that these are the main points that Lockheed Martin had to solve to optimize Prepar3D v5.

The main feedback on Prepar3D in DX12 was that these versions consumed more VRam at identical settings.
Then for the speed, as this API allows many more technical things, it goes without saying that programmers try to use them to enrich the simulator and therefore who says more effects says that the gain in speed is very quickly consumed and therefore in the end we have a more beautiful simulator but not really faster.

References:

- https://docs.microsoft.com/en-us/windows/win32/direct3d12/important-changes-from-directx-11-to-directx-12

- http://prepar3d.com/forum/viewtopic.php?t=138387

- https://prepar3d.com/forum/viewtopic.php?t=144586

Excuse me for my unorthodox English but being French developer, I might make some mistakes in my translations 😉

PS: I have worked for 35 years as a Windows administrator and in application development for PCs

Edited September 12, 20223 yr by lagaffe

6 minutes ago, lagaffe said:

but not really faster.

Just smoother 😄