Performance in DX12 has been spot on here with no loss of performance, But i am on a AMD 6800, Infact despite being in Beta,  i have not had a stutter, or CTD since it was launched. No doubt the upgrade has helped.But it has certainly been far more stable for me.

Edited August 12, 20223 yr by Car147

10 minutes ago, David Mills said:

Here's what I don't understand about the recent DX12 problems: I have a seven-year-old 1070 with only 8GB of memory, which is far less video memory than most of you have. Nonetheless, the release of SU10 brought my system a new level of performance with DX12. I encountered no problems at all with DX12 and gained a great performance boost. I know, however, that others experienced graphics problems with DX12 -- problems which needed to be addressed. Fine. But why remove the DX12 optimizations while working to fix the problems? After all, this is a beta. If the graphics problems that some suffered with DX12 were truly show-stoppers for them, then they could always revert to DX11 until the DX12 fix is finalized.

Most likely, they don't know the circumstances where the performance boost with DX 12 doesn't cause the graphical anomalies from the first beta build. If they could figure out the circumstances and conditions where the graphical anomalies come up, then they could probably use the code that gave the nice performance boost.

My guess is, they will analyze the issue further, and try to figure out how they can add the performance boost back for computers that don't have the graphical anomalies, while trying to avoid the graphical anomalies for others who have a type of computer where those graphical anomalies happen. It probably just takes time for them to figure this out, and the time they had during the open beta test was just not enough time.

7 minutes ago, Car147 said:

Performance in DX12 has been spot on here with no loss of performance, But i am on a AMD 6800, Infact despite being in Beta,  i have not had a stutter, or CTD since it was launched. No doubt the upgrade has helped.But it has certainly been far more stable for me.

word not allowed that's what i wanted to see... It was all quiet in the official forums except for the Xbox guys whose specs amount to a slightly cut down 3700x/6800 equivalent  but i wanted some direct feedback from people in the beta actually using an All AMD PC. Nice to see we didn't get chopped with the DX12 Memory management issue.

10 minutes ago, MarcG said:

Perhaps the performance improvements they gained caused the issues for others, so in trying to fix the issues it then became apparent that the performance was a side effect they couldn't keep (not saying that is the case, just an example).

Software coding item A doesn't always mean it's easy to code item B, especially when for no reason whatsoever item C gets corrupted. 

All true. I just hope they give us the option of choosing whether we want the optimizations or not -- like an option in the graphics settings under DX12. I was really excited today when I saw there was a new beta release. But I was extremely disappointed when the DX12 optimizations were not restored.

2 minutes ago, David Mills said:

All true. I just hope they give us the option of choosing whether we want the optimizations or not -- like an option in the graphics settings under DX12. I was really excited today when I saw there was a new beta release. But I was extremely disappointed when the DX12 optimizations were not restored.

But that's the point I'm trying to make to you, they may not get the optimisations back because of the fixes they have to make elsewhere. 🙂

Therefore they won't include a setting for something that might not exist 😉 again all hypothetical, only they know what's going and we can only guess. DX12 is and will be in beta for some time yet, so IMO there's no rush to "fix" this issue now as now the public SU10 build must take priority with its impending release.

I think this article explains the intricacies of DX12 and the differences between DX11 and 12 quite well.

https://www.hardwaretimes.com/what-is-the-difference-between-directx-11-and-directx-12/

As the author outlines, there are three main advantages with DX12 over DX11:

• Better Scaling with Multi-Core CPUs
• Maximum hardware utilization
• Closer to Metal Support

Despite these potential advantages, the implementation of DX12 requires more from the developer.

“Another major advantage of DirectX 12 is that developers have more control over how their game utilizes the hardware. Earlier this was more abstract and was mostly taken care of by the drivers and the API. Now the task falls to the developers. They have closer to metal access, meaning that most of the rendering responsibilities and resource allocation are handled by the game engines with some help from the graphics drivers. This is a double-edged sword as there are multiple GPU architectures out in the wild and for indie devs, it’s impossible to optimize their game for all of them.”

I think Asobo eventually will be successful in their DX12 implementation. But like others have mentioned, they need more time to do this. For those of us that used XP11 before MSFS, we probably remember that it took Laminar Research quite a while to successfully implement the Vulkan API.

2 hours ago, Cpt_Piett said:

Change drone camera speed to 30

Fixed a scenario where exposure brightness increases too quickly when looking towards instruments

Well these shows that they're listening to user feedback. Both of these have gotten some considerable attention in the official beta forums. 

 

I wish there was an easy way to either adjust or disable the exposure compensation effect entirely. Seems a bit smoother / less jarring now though.

13 minutes ago, Cpt_Piett said:

For those of us that used XP11 before MSFS, we probably remember that it took Laminar Research quite a while to successfully implement the Vulkan API.

and for the rest of us who used P3D before MSFS, we definitely remember that it took LockheedMartin quite a while and several point release updates to successfully implement the DX12 API, without crashing and running out of VRam.

DirectX 12 VRAM Management Recommendations for Prepar3D v5

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

Edited August 12, 20223 yr by turbomax

1 minute ago, turbomax said:

and for those of us who used P3D before MSFS, we definitely remember that it took LockheedMartin quite a while and several point release updates to successfully implement the DX12 API, without running out of VRam.

Yeah, MSFS users definitely don’t want to go through the nightmare that P3D users did with the DX12 VRAM ooms. 

21 minutes ago, Chapstick said:

Yeah, MSFS users definitely don’t want to go through the nightmare that P3D users did with the DX12 VRAM ooms. 

Indeed. VR was rendered virtually useless for me in P3Dv5 on DX12. I ran out of patience, went back to v4 because of it. And by the time they supposedly had fixed the VRAM issues MSFS was out and P3D dead. 😉

People that had performance degradation since the second BETA update, please vote here, so they can give us a feedback in the next Q&A:

https://forums.flightsimulator.com/t/performance-regression-on-pc-from-1-27-9-9-in-the-following-builds/536205?u=cahzito

The latest update looks awful to me in HDR. Looking out of the cockpit is almost completely washed out.  Anyone else seeing this?

Sim looks much better in standard resolution.Non-HDR.

1 hour ago, rjack1282 said:

The latest update looks awful to me in HDR. Looking out of the cockpit is almost completely washed out.  Anyone else seeing this?

Yeah, I guess it looks kinda washed out. 

(taken by my iPhone at the screen as saving HDR screenshots is not really representative of how the sim looks)

 

I've done some more testing in DX11 and the results are good both in terms of fps and very little stuttering. 

Chicago area C172_G1000 (KMDW-KMDW): average fps 60 | 1% low fps 39 | 0.1% low fps 21

London area Bonanza (EGLC-EGLL): average fps 52 | 1% low fps 30 | 0.1% low fps 22

New York area Caravan (KJFK-KJFK): average fps 50 | 1% low fps 30 | 0.1% low fps 20

LA area Caravan (KPSP-KLAX): average fps 55 | 1% low fps 35 | 0.1% low fps 23

The flights were from 25 to 75 minutes, overflying CBD areas in all cases, starting on the runway and ending just after vacating the runway. The worst stuttering was on short final rwy 06L into LAX. On the Palm Springs to LAX flight there was a lot of object (buildings, trees) pop-ins fairly close to the airplane. I didn't notice this on the other flights. 

4K HDR | ultra settings | terrain LOD 200 | vanilla sim | no world updates

Edited August 13, 20223 yr by Cpt_Piett