Why did they decide for DX11?

32 minutes ago, Tomaz Drnovsek said:

Why did they decide for DX11?

In P3Dv5, the DX12 implementation generates regular OOM when some graphic options are checked and saturate the video card. It is probable that they work implementing it better in FS20 to avoid this.

1 minute ago, Dominique_K said:

In P3Dv5, the DX12 implementation generates regular OOM when some graphic options are checked and saturate the video card. It is probable that they work implementing it better in FS20 to avoid this.

Is that a common issue/bug/feature with DX12?

1 minute ago, Tomaz Drnovsek said:

Is that a common issue/bug/feature with DX12?

Not a specialist but I read that the VRAM memory management has changed from DX11 to DX12 . It is not a bug but a new way of doing things that demands more attention from the developer. Before, excessive use of VRAM would lead to a general slowdown of the simulation, now it leads to a crash. 

6 hours ago, Jose Munoz said:

Not in the modem era of gaming or entertainment it is not. 60 fps is the benchmark. This is a generally accepted fact with any enthusiast.

It's a massive stretch to say it's standard, for things like fighting games like Street Fighter that would be true, but for open world games like Zelda or GTA it's very common for them to be at 30FPS.

10 hours ago, skully said:

lol

The only thing you're serving is a load of BS.

Millenials.......... 😉

10 hours ago, omarsmak30 said:

MSFS is CPU bottlenecked, huh? but on my system I have i9 and running it in 2k and I barley see the cpu usage goes over 60%, GPU is almost all time maxed out though. 

It's all in the numbers!! 😄

11 hours ago, SAS443 said:

in every alpha/beta release I tested with my 9900k I never, not even once managed to peg any CPU core to 99% load.

GPU? yes but that was with ultra settings and 4K, I would achieve the same result with any modern game. 

Compared to P3D which is a Core0 dramaqueen, MSFS is more easy on the CPU from my opinion.

Many things need to be corrected with MSFS, but claiming it to be CPU hog à la P3D is not accurate.

I can get it to peg my cpu at 100%, just turn off hyperthreading.

With Hyperthreading on, my cpu bumbles along at 50 -60%.

i7 7700K in my case.

Definately recommend having HT on in this sim.

Stu

54 minutes ago, Dominique_K said:

In P3Dv5, the DX12 implementation generates regular OOM when some graphic options are checked and saturate the video card. It is probable that they work implementing it better in FS20 to avoid this.

Never had any OOMs or CTDs in every P3D version on both my pc’s. Also none in V5 with all options on. But sliders set to have a stable franerate all the time.

It is the stability of your hardware icw the stability of your software that makes the stability of your system.

7 minutes ago, Bunchy said:

I can get it to peg my cpu at 100%, just turn off hyperthreading.

With Hyperthreading on, my cpu bumbles along at 50 -60%.

i7 7700K in my case.

Definately recommend having HT on in this sim.

Stu

Seems like it heavily profits from multicore. So much to FSX tech.

13 minutes ago, GSalden said:

Never had any OOMs or CTDs in every P3D version on both my pc’s. Also none in V5 with all options on. But sliders set to have a stable franerate all the time.

It is the stability of your hardware icw the stability of your software that makes the stability of your system.

Hi Gerard, glad for you knowing that you don’t have the setup of a regular simmer  at all.

But there are too many cases reported of VRAM OOM by people we can trust to discard the issue  and we know that DX12 doesn’t manage the memory as its older brother did. It was not an attack on v5. just an observation which may explain why Asobo still uses 11. Developers have to think differently and that takes time .  Also considering that FS20  uses the GPU and not the CPU as the main simulator engine, I suppose that calls for a greater prudence.

 

I'm pretty sure "Colonel X" works for a consortium made up of X-Plane and P3D fanboi's

Yours Sincerely

W cubed

In Beta, my dated hardware (see signature) was tolerable somewhere between medium and High settings, but in the release version, it is unflyable even on straight up medium settings all AI off.  The only relief I've gotten thus far is using the Manual Cache.  This is in the C172 only.  I don't care about heavy metal.  I'll keep tinkering until I can get things stable, but I didn't have one clean flight yesterday without extreme stutters and pauses - CPU pegged at 100%, GPU sitting at about 65% on straight medium.  Something has changed, but not sure what it is, but I'll keep trying to go as far as I can with what I have.  Things may get worse as complex add-ons start coming, but we'll cross that bridge when it gets here I suppose.

@SmokeDiddy turn turning off any live traffic or weather. And Azure ATC. Basically anything that uses the internet to see which is causing the issue.

 

21 minutes ago, Slides said:

@SmokeDiddy turn turning off any live traffic or weather. And Azure ATC. Basically anything that uses the internet to see which is causing the issue.

 

Thanks for that!  In another thread, I saw someone with similar hardware and he was advised to turn on V-Sync and and set frames to 30FPS.  I did the same and the stuttering is much improved.  I also did as you suggested and turned off live traffic and weather.  I cooking along at 50FPS and 85% CPU, 44% GPU atm

Edit:  So, I was cooking along on a short flight (21 miles) I turned on AP so I could watch things and as soon as I turned off the AP to start slowing for my descent, the stutters and pauses started again, so I paused the sim for about a minute and came back and the stutters are gone and I'm back up to 55 FPS.

Edited August 20, 20205 yr by SmokeDiddy