Still getting Dxgi

[Mb944]

Ok mr tough guy who thinks u know it all. How come I’m
Not getting this error in fs2020? It’s more demanding than p3d with all the details in the scenery’s and the aircrafts. So explain to me why I’m not getting the dxgi in fs2020? If u don’t have an answer for it than my finger is still pointing at LM and they should fix it. So u stop with this nonsense pal.

[Sky_King]

Because the error is related to DX12 and FS2020 is DX11. Other DX12-based games have the same problem.

[JorgenSA]

Thanks for reminding me, Sky, I had forgotten that MSFS2020 is a DX11 application.

I am not much into the games scene, but are you saying that other games using DX12 are having the same issues - and with only AMD cards, or both AMD and nVidia?

Jorgen

[Mb944]

How many games are using dx12?

[Rockwell_Lancer]

Good Morning Folks,

Thank you for your input, Jorgen. You raise a good point. I had never considered there could be an issue with DirectX 12 games and graphics drivers since I don't see this error with other games on my system.

But with that said, looking at this list, my memory was jogged about an incident with a DirectX 12 game I had for PC a few years ago; Battlefield 1. At that time, I would play the game on my GTX 770, and would frequently get a DXGI_ERROR_DEVICE_REMOVED error. It was so frequent that I had to ask for a refund of the game.

I believe the issue was either tied to my specific GPU or the driver, but I can't remember for certain. In any case, I think the issue was eventually resolved, either through a driver update, or a game update. Perhaps this might be a driver issue, though if that is the case, it has been ongoing for quite some time without a patch.

Just out of curiosity, however, do you happen to know when the driver for Nvidia was released that resolved this issue? I had an RTX 2080 in my system until early March 2021, and I was still getting the DXGI error with that card right up until I swapped it out.

Regards,

Dominick

[JorgenSA]

Dominick,

The driver I use now is 466.47, and the version before that was also OK. The problem was with the two driver versions before that one.

I believe (my memory is not too sure about this one) that the driver that fixed the issue - the one version before the present one - was released at the end of April. Probably someone else can provide the exact date. The search function for the forums say that "nvidia driver" is too common words to be used as search criteria.

Jorgen

[Rockwell_Lancer]

Hi Jorgen,

Thank you for checking. Looking at Nvidia's website, I can confirm your statement about the release of the second-to-most-recent driver (466.27): 29 April 2021. Looking at the release dates here, it appears I would have had 461.72 installed when I replaced the GPU, so this is certainly a consideration.

I'll keep an eye out for AMD's patches -- there's a new one that came out on Friday that I've yet to install and try. I'm new to the Radeon ecosystem, but it appears their driver release cycles are less frequent than Nvidia's; if this is indeed GPU-related, and this release does not contain a fix, then it might be a while before we see one that does.

Best,

Dominick

[JorgenSA]

Please post the result of your update here, good, bad or indifferent!

Jorgen

[mpni]

Hi
Here the first feedback with the first nVidia driver fixing the issue :
viewtopic.php?f=6312&t=142203
Regards
Michel

[Sky_King]

Thanks for reminding me, Sky, I had forgotten that MSFS2020 is a DX11 application.

I am not much into the games scene, but are you saying that other games using DX12 are having the same issues - and with only AMD cards, or both AMD and nVidia?

Jorgen

Yes, other games are and are as random as ours. I did a quick Google and here is one as an example (while solved, it illustrates what I am saying): https://www.nvidia.com/en-us/geforce/fo ... g-on-seve/

Also, here is an interesting discussion about DXGI and DX12 --https://stackoverflow.com/questions/524 ... saa-failed. One more link -- here is a link to a blog about enabling DXGI debugging in a project -- https://blogs.msdn.microsoft.com/chuckw ... ug-device/

Personally, I think there is a deep DX12 issue which is Microsoft's to diagnose. However, LM should build in the debugging functionality as described above which would allow better troubleshooting and problem analysis.

Just my 2 cents worth, regards,

SK.

[sportpilot67]

Hello Everyone,

I have made many posts in the past about DXGI Device Hung, which only happened to me on V5 after I purchased an AMD 6800XT. First flight resulted in device hung. Never had the issue with my GTX1080 but I ran out of VRAM all the time, hence the new GPU purchase.

Anyways, I have tried everything. I was doing great and then out of nowhere I got device hung 3 out of 4 flights. It was driving me crazy. Anyways, I looked into the factory settings of my new 6800XT. I noticed that the factory clock was 2400mhz in the Radeon software.

I went to AMD's website and it says: Game Frequency, Up to 2015 MHz (this is for 6800XT). So I reduced my mhz to 2015. Applied the changes and first flight was a success and have four total without an issue and like I said before it was 3 out of 4 flights resulting in a device hung. I will also add that my settings are high, fps on unlimited getting 45fps at FlyTampa KTPA with ORBX TrueEarth Florida.

Changing from 2400mhz to 2015mhz did not drop my fps.

So if you own a 6800, 6800XT or 6900XT maybe you should set your clock within Radeon software for the actual AMD spec number from their website.

I will do an actual posting about this when I hit the 30 day mark. I have never had 30 flights without an issue since installing my 6800XT.

Ray

[mpni]

@sportpilot67
Very interesting feedback.
It seems it is the same with nVidia video card.
Sometimes, P3D does not like OC.
Regards
Michel

[pommy80]

@ Ray

Thanks for the tip Ray. I've adjusted mine and completed a flight for the first time in a while as well. Will keep testing further this weekend.

Daniel

[Mb944]

@Ray

Wow Ray u might be my new hero. u know what now that I think of it I had my speed set at 2245. That’s what AMD had it set at so I didn’t bother changing it because I thought it would be ok. I dropped it to 2015mhz and I will let u know if it worked.

[sportpilot67]

@mb944

What card do you have?

Ray