8 minutes ago, jcomm said:

I'm on DX12, Nvidia 3060 Ti, Windows 11.

Never had problems with DX12 in SU10 beta, including flights in the Fenix as far as from Frankfurt or London to Lisbon.

How did you get the Fenix to work in SU10 ? When I run the Fenix utility in SU10, nothing happens. Went back to SU9.

Edited August 20, 20223 yr by ZKOKQ

Question to those testing in VR:

Was the testing done with the latest Windows OpenXR Tool (updated yesterday)? Wondering if this would make a difference...

NOTE: Not referring to OPENXR TOOLKIT!

Edited August 20, 20223 yr by tamsini

5 minutes ago, ZKOKQ said:

How did you get the Fenix to work in SU10 ? When I run the Fenix utility in SU10, nothing happens. Went back to SU9.

Simply loaded it ?

I'm sorry to learn you aren't able. It was uneventful in my case.

36 minutes ago, kenny584 said:

Hi Folks.

I am not really a techie, so, are all you folks talking about a beta version that is not yet available as an update? I mean the ones that we all get every so often. Also, if I may. I am assuming that my pc is using DX11 and most posts are mentioning DX12. Is DX12 tied to this beta? Or is it something that I can install? How would I know whether I am using DX11 or 12?

Regards...Kenny.

edit...I just searched online and then ran the dxdiag tool. My pc is using DX12.

If you have not opted into the sim update 10 beta, which you can still join if you wish, you will still using DX11 in fs2020, regardless that your pc is capable of using DX12.

The option to change from DX11 to DX12 is available in tge sim graphics option menu in the beta only at this time, and if you don't want to join the beta you will have to wait for the release of Sim update 10, now likely to release in early September as it has been delayed due to some of the issues discussed around memory management, dx12 and dlss.

I haven't tested the flight itself yet, but I can already see a big improvement on DX11. Yesterday I tested EGAA from Pyreeg on a stand of 26 and on average in Fenix A320 I had 30 FPS, Now after the update I have 40 FPS.

 

4K DLSS

Edited August 20, 20223 yr by rutra

Super smooth in the new V35 and PMDG -700.  4k ultra settings, DX11, DLSS.

The only issue I had was muddy ground textures, like Bing data wasn't loading.  I went to the menu, turned Bing data off, then on again, and now the roads and proper detail ground textures are present once again. 

This remained for a second flight in the 737, so all good.  for once, the small update did not set up a rolling cache of 8GB.  I normally have to de-activate and delete it after an update.

I got this update late last night. I am on climb out now (flying today's Spirit 818 Myrtle Beach to Baltimore) in the Fenix. I switched back to DX11 specifically for the purpose of testing. I am impressed.

A couple of things I noticed. My 1st launch of MSFS after the update was the PMDG 7373-700 sitting at FB KIAD C17, a gate I've been using to learn GSX. The PMDG seemed to recompile it's WASM because I had the extremely long delay like it did the very 1st time I used it. I think that GSX might have also recompiled it's modules as well (and everything else that might use WASM?).

Observations.

• GSX
  • GSX's menus started being more responsive.
  • GSX recognized the list  of excluded airports for jetways, as I had the FB ones back this time (tested FT KBOS later - had the FT jetways there as they should be)
  • Pretty much everything is working as it should with GSX. I'm liking it.
  • My push on this current flight was out of gate A6 at Verticalsim's KMYR and it required a little more than 90 degrees to get the airplane on the CL. GSX is now 5 for 5 in perfect push backs for me. It's great to be able to work with the airplane instead of the tug during push.  
• Fenix
  • This update really made a BIG difference for me (10850K, 2080Ti 12GB, 32Gb, SSD drives) in the overall smoothness, at least from startup to FL330. This is the very 1st time that I've felt the Fenix was as smooth and stutter free as the 737-700, which IMO couldn't be any smoother. It's perfect. 
  • GSX integration is great. GSX opened and closed the doors for catering and baggage and operated the jetway during boarding AND as a bonus, actually boarded the odd number of pax that I used in my Simbrief plan, 137. Either GSX was super lucky, in guessing that number, or the Simbrief integration works like the GSX manual says it does. I did not use the EFB to load the aircraft until the very last minute. For fuel, I called the fuel truck and when GSX told me to input the quantity into the airplane, I used the fuel page under config in the MCDU to do so.  
  • When GSX said it was done boarding, I went into the EFB and did an "instant" load.
• MSFS
  • The whole thing just feels crisper, and more responsive.
  • My usual hit drone cam, go up a couple hundred feet, and spin routine showed significant improvement over the last SU10 update.

Conclusion: I think Asobo found something pretty big and fixed it. This one is not a smoke screen. The results are absolutely noticeable and solid. If I had to guess, I'd say that while they were looking at DX12 with Nvidia, they got a couple of hints for things to do better in the DX11 space. If the Nvidia driver gets fixed, I can only imagine what DX12 will be like.

I will update this after I land. So far, this has been the best flight I've ever had in MSFS.

Edited August 20, 20223 yr by MDFlier

Not mad,  but I have to ROFLMBO that the company who released DX12 officially in July of 2015,  can't figure out how to utilize it in their own code 7 years later.

At least they finally decided to ask Nvidia for help.

 🤡

45 minutes ago, MDFlier said:

The PMDG seemed to recompile it's WASM because I had the extremely long delay like it did the very 1st time I used it.

Yes. Any WASM based aircraft or utility will need to recompile whenever the main flightsimulator.exe file is updated to a new version.

24 minutes ago, Waldo Pepper said:

Not mad,  but I have to ROFLMBO that the company who released DX12 officially in July of 2015,  can't figure out how to utilize it in their own code 7 years later.

At least they finally decided to ask Nvidia for help.

 🤡

The issue appears to be more related towards users who use Nvidia hardware rather than an issue with DX12 on it's own. Which is why AMD GPU users haven't noticed the same sort of issues.

Edited August 20, 20223 yr by Zangoose

Since there weren't many posts in between, I'll just update here instead.

While typing that last entry, I missed TOD. I told the plane to hold at DFORT on short notice (<3 miles from DFORT) and she executed it flawlessly. I exited the hold when I was back on the descent path.

Needless to say, the flight ended perfectly. Smooth as silk right up to the gate and during GSX deboarding as well. I think Asobo can make this one a release candidate. They fixed something big. 

1 minute ago, Zangoose said:

The issue appears to be more related towards users who use Nvidia hardware rather than an issue with DX12 on it's own. Which is why AMD GPU users haven't noticed the same sort of issues.

I agree.   It's just that 3 or 4 patches in a week or two kind of seems like someone throwing darts at a dart board while wearing a blindfold and hoping it sticks.   To me at least.  

It was like,  "Here,  try this!  That didn't work?  Try this one!  That didn't work?  Try this one!".

23 minutes ago, Waldo Pepper said:

Not mad,  but I have to ROFLMBO that the company who released DX12 officially in July of 2015,  can't figure out how to utilize it in their own code 7 years later.

At least they finally decided to ask Nvidia for help.

 🤡

It is probably a problem in the Nvidia driver which only Nvidia can fix. GPU driver updates often contain fixes for known problems/bugs with specific game titles. It will probably mean that once the solution is found, MSFS users with Nvidia GPUs who want to use DX12 will have to update to the latest Nvidia driver. 

So maybe they don`t need the 2 or so weeks delay for SU10, but they hold the delay anyway hoping something fast goes on with Nvidia and DX12 so Asobo can put this also into the update ??

cheers 😉

1 hour ago, Waldo Pepper said:

I agree.   It's just that 3 or 4 patches in a week or two kind of seems like someone throwing darts at a dart board while wearing a blindfold and hoping it sticks.   To me at least.  

It was like,  "Here,  try this!  That didn't work?  Try this one!  That didn't work?  Try this one!".

I don't think they throw darts in the dark randomly. It's just that there are hundreds of different configurations out there and they don't have the time and the hardware to test everything every time. 

I am very happy of the development in the last year or so and I believe that opening beta testing to the public accelerated it.