Just now landing in EGLL, 4k monitor, running texture resolution at 2k. The sim has never looked so good, real, and smooth.

5 minutes ago, ttbq1 said:

Just now landing in EGLL, 4k monitor, running texture resolution at 2k. The sim has never looked so good, real, and smooth.

I am excited for when PMDG/FSLABS drop and can fly into london and its smooth.

53 minutes ago, jmig said:

I run a 1080P projector with a GTX 970TI with 4Gbs VRAM. According to the MSI frame and usage counters I never have gone over 2700 mb of VRAM. Yet, I still get the 'Device hug' message.

Aren't the various DEVICE_HUNG errors and vram memory starvation two different bugs?

1 minute ago, Mace said:

Aren't the various DEVICE_HUNG errors and vram memory starvation two different bugs?

Yes. I think they are from what I have read over on LM forums directly.

8 minutes ago, Mace said:

Aren't the various DEVICE_HUNG errors and vram memory starvation two different bugs?

There are many causes to the DEVICE_HUNG crashes (g2d.dll fault, vcruntimexxx.dll fault and plenty of others), one of which is running out of VRAM and not being able to recover as intended with the choice to reset graphics settings to default.

I don't believe the author is right

I both develop in vulkan and opengl

There are no background process that switches textures between RAM and VRAM in OpenGL

OpenGL and Vulkan both allow to send textures directly to the VRAM, its nothing new.

The only advantage of Vulkan is its multi thread abilities and gives more access to certain functionalities

 

3 hours ago, dave2013 said:

I used a 24" 1920x1080 display for 10 years and recently upgraded to a 27" 2560x1440p display.  I wanted higher resolution mainly because of the larger screen area, not so much because the image would be so much sharper, although that is a plus. I would not even consider a 4K display as the cost and benefit would not be worth it for me.

I just wonder how much more benefit one gets from a 4K display versus the same size 2K display.  Not much IMO.  If you have a 40" display then I can see the advantage, but 4K resolution for anything 32" or smaller is overkill.

Given 32" is the largest size available for a UHD monitor what you're saying is that only TVs are suitable for UHD. The problem there is the smallest size is 43". And if you look through sites selling UHD monitors the 32" is by far the most popular size. I would have jumped at a 36" UHD monitor but they don't exist. There must be a reason for that.

It's often said 32" is the perfect size for UHD. Yes, a 50"+ TV will give you more immersion but it's at the expense of less clarity (PPI) and in your case the need tor additional AA. I run with a minimum of AA and although there are some artifacts they don't bother me.

 

3 hours ago, cwburnett said:

There are many causes to the DEVICE_HUNG crashes (g2d.dll fault, vcruntimexxx.dll fault and plenty of others), one of which is running out of VRAM and not being able to recover as intended with the choice to reset graphics settings to default.

Are people getting the DEVICE_HUNG even though the vram counter shows 5.2 GB / 9 GB?

Or is the DEVICE_HUNG typically seen in 8.1 / 9 situations?

4 hours ago, regis9 said:

2080ti is 11gb.

I’ve been able to manage for the most part in staying within the vram limits of my 8gb gtx1070, mainly flying GA around orbx airports/regions.  However, i expect once I start flying heavy iron into detailed airports some balancing will likely be necessary.  This is at 2k resolution.
 

P3D does need to have some kind of vram outlet other than crashing though.  It’s not like a closed ecosystem game where the developer can predict what vram usage will be incurred by specific settings ahead of time.

Developers will also have to be responsible in what impact their addon has on vram.  If we get to a situation where the airport, aircraft, and whatever other addon developer are all pointing fingers at each other as the generator of excessive vram usage, we all lose. 

Do you think MSFS20 will suffer from this...or users as a result?  I guess we don't even know to date, that it WILL be running DX12?!?!?

4 hours ago, Mroberts95 said:

Just wait til the fall when NVIDIA 3080 will have 10gb and 20gb options available and I am sure the 3080ti will probably only be a 20gb option.

So, in other words, some people's younger children won't be going to college...;)

16 minutes ago, Sesquashtoo said:

So, in other words, some people's younger children won't be going to college...;)

No children here so no worries but yes 🙂

OOM..really!

Well played LM and v5 and a lot of people on here do nothing but put down MSFS and tell us we are in for disappointment.Really! 

Let's go back to FSX days of trying our best to not oom....lol

---------------------------

I hope LM do fix it and when FSL and PMDG make v5 installers and orbx sort out EGNX i will buy it unless I still read endless OOM reports. No wish to go back to that, no point in having better FPS when you fear any second your going to oom.

Also unlike some that think choosing a flight sim is picking a religion, I'am happy to fly as many of them as i wish to enjoy.

4.5 / 5 < if it get fixed / DCS. MSFS. 

Edited April 27, 20206 yr by Nyxx

44 minutes ago, Mace said:

Are people getting the DEVICE_HUNG even though the vram counter shows 5.2 GB / 9 GB?

Or is the DEVICE_HUNG typically seen in 8.1 / 9 situations?

For the non VRAM-related DEVICE_HUNG errors, VRAM appears irrelevant. I've gotten them at 4GB/7.1GB, but it really is system dependent. I know 90%+ of mine are because of an incompatability with the AMD display drivers that LM is troubleshooting with AMD (that causes a DEVICE_HUNG CTD on changing view into the cockpit).  The VRAM related ones (for me) started with a message telling me I'm out of graphics memory and asking me if I want to adjust my settings - then any option I clicked caused a DEVICE_HUNG CTD.  I don't get those anymore because I've adjusted my settings accordingly.

But people are getting these by selecting menus, or over certain scenery, etc - there seem to be many cases and they're not always repeatable. For example, I got a DEVICE_HUNG CTD loading the FSW Falcon 50 at KSNA, but I can load it up at KSAN and fly to KSNA no problem - I just can't start there. I can start there with the FSW Lear 35, though, and change aircraft.

I got one taxiing at KBFI. Restarted at the same place, did the same taxi and didn't get one that time. So, you know, it's just occational general instability.  On the other hand, yesterday I flew KMIA-KEYW-MHRO-SKBG-SKPS (all v5 add on sceneries) in the v5 version of the FSW Falcon 50+RXP GTN750 and didn't have any crashes. It ran for hours with no problems other than crazy winds aloft and the weird texture border artifacting associated with Truesky.

 

8 hours ago, Sesquashtoo said:

Apparently, per the Internet, there is a 16.25% reduction in the amount of VRAM that the sim can use.
Re: my Nvidia 1060 with 6 GB ram
16.25% reduction = .975GB
So, v5 can only use 5 GB, and per Shift_Z keys twice: “GPU Memory: 3.6/5 GB”
And, v5 is currently using 3.6 GB

Per the Internet: "I have found that the two biggest VRAM hogs are Advanced Atmospherics (TrueSky Beta) and Texture Resolution."
Re: my tests:
Advanced Atmospherics setting for San Jose, CA airport departure:
On: 4.5 GB
Off: 3.4 GB

I wanted to mention a few observations about this...

With Win10 2004, I get 7.1GB/8GB for P3Dv5 to use, so the ratio is a little better - a little over 10% saved for the OS. I know others have mentioned this also.

In addition, it turns out that we don't have that much less VRAM in v5 than in v4.5 - I did some testing in v4.5 before I wiped my system for a fresh 2004 install + P3Dv5 - and found that my OS used about 0.5GB, so even in v4.5, the effective max that could be used by P3D was 7.5GB before I bled over into my shared GPU memory and P3D4.5 became a slideshow, so there's only a 0.4GB difference for me between what was available to me in 4.5 vs 5.  I realize every 0.1GB counts, but it actually is a reasonable tradeoff for the performance improvement DX12 offers, IMO.  If LM can fix the CTD that occurs for many when they hit the limit, it will be much less of a problem.  There is supposed to be an option to change graphics settings without a CTD, it just doesn't reliably work.

Further, with respect to Truesky, it is true that it takes about 1GB of VRAM. BUT...what I noticed is that in cloudy/bad weather in 4.5 with ASCA+ENVTEX+ENVSHADE+ASP4, my VRAM would jump about 1GB.  So, sure if you compare Truesky to a clear day in 4.5, there's a big difference because Truesky always uses about 1GB of VRAM - but, when you compare apples to apples with a fully tweaked 4.5 with high resolution (2k for me) could textures when weather is actually present, the VRAM usage is about the same ~1GB on both sides.  Truesky seems to, regardless of the weather, use the same amount of VRAM.  It remains to be seen what happens if/when Truesky gets more cloud layers...

Lastly, on my system at least, there are four important factors for VRAM conservation.

Overall Resolution - 1080p < 1440p < 2160p

Texture Size

Anti-Aliasing 0 < 2x < 4x < 8x

Level of Detail Radius (this one caught me off guard, but reducing this helped tremendously and was a worthwhile choice at a place like LVFR KMIA where I cared more about texture resolution than radius of coverage. The downside of this one is that to change it requires the loading screen, which isn't true of Anti-Aliasing or Texture Size.

With 8GB of VRAM I can fly anywhere I have scenery for (so far) with 2160p, 2048 textures, 2xSSAA and High LOD (which is the same as I had set on v4.5) EXCEPT for LVFR KMIA, where I EITHER have to lower my LOD to medium OR lower my textures to 1024.  But, I ran into VRAM problems there in 4.5 also on bad weather days, and I'd have to lower something to keep from going into shared GPU memory, otherwise it became a slideshow.

So, not defending the instability at all, and there's plenty to be frustrated with, but...the VRAM situation actually isn't that changed - it is just more obvious because stutters have been replaced with a firm end to the flight via CTD.

7 minutes ago, cwburnett said:

With Win10 2004, I get 7.1GB/8GB for P3Dv5 to use, so the ratio is a little better - a little over 10% saved for the OS.

That's because the amount of VRAM reserved for the OS is now a fixed amount.