For some reason, I cannot have my sliders cranked up after updating to the latest HF. It seems like with very reasonable, medium settings, I am close to maxing out my VRAM. 6.2/6.5GB. Where as before the update, I had my sliders very high and still had VRAM leftover to spare. Something isn't right here.

1 minute ago, captain420 said:

For some reason, I cannot have my sliders cranked up after updating to the latest HF. It seems like with very reasonable, medium settings, I am close to maxing out my VRAM. 6.2/6.5GB. Where as before the update, I had my sliders very high and still had VRAM leftover to spare. Something isn't right here.

It is right. They are managing the budget of VRAM with a different algorithms in order to catch when you are about to run out and avoid a CTD.

So before you were allowed to crank your settings outside of your current hardware limits and then boom issues / CTD.

Be sure you enabled textures streaming as well since that will remove textures outside of your view and other things to utilize your VRAM more accurately.

I do recommend deleting the Prepar3D.cfg to start your settings from scratch and adjust settings slowly until you reach your limits.

Regarding Windows, you need latest Nvidia drivers and at least Windows 10 1909.

Regards,

Simbol 

Wait till MSFS goes from DX11 to DX12 later it will likely eat your GPU for breakfast.

I did do all those. But I haven't updated to the latest nvidia drivers yet.

5 minutes ago, simbol said:

It is right. They are managing the budget of VRAM with a different algorithms in order to catch when you are about to run out and avoid a CTD.

So before you were allowed to crank your settings outside of your current hardware limits and then boom issues / CTD.

Be sure you enabled textures streaming as well since that will remove textures outside of your view and other things to utilize your VRAM more accurately.

I do recommend deleting the Prepar3D.cfg to start your settings from scratch and adjust settings slowly until you reach your limits.

Regarding Windows, you need latest Nvidia drivers and at least Windows 10 1909.

Regards,

Simbol 

Sounds like they have dumbed it down so we get less performance than before the hot fix for the sake of stability

7 minutes ago, simbol said:

It is right. They are managing the budget of VRAM with a different algorithms in order to catch when you are about to run out and avoid a CTD.

So before you were allowed to crank your settings outside of your current hardware limits and then boom issues / CTD.

Be sure you enabled textures streaming as well since that will remove textures outside of your view and other things to utilize your VRAM more accurately.

I do recommend deleting the Prepar3D.cfg to start your settings from scratch and adjust settings slowly until you reach your limits.

Regarding Windows, you need latest Nvidia drivers and at least Windows 10 1909.

Regards,

Simbol 

Hi Raul,

Is there a reason why the latest drivers are needed?

Jose

Yes, I definitely cannot run at high settings like I used to anymore. Sigh...

5 minutes ago, DJJose said:

Hi Raul,

Is there a reason why the latest drivers are needed?

Jose

LM works closely with NVIDIA and MS. This is why Windows 2004 is also giving more VRAM available.. 😉

S.

4 minutes ago, captain420 said:

Yes, I definitely cannot run at high settings like I used to anymore. Sigh...

What a monumental stuff up, give great performance then take it away

8 minutes ago, suchw said:

Sounds like they have dumbed it down so we get less performance than before the hot fix for the sake of stability

They didn't dumbed it down.. they made it smarter.. people always want to crank everything to the "right" without having the required hardware to be able to sustain it and then they claim the simulator is faulty..

With new generation of simulators you cannot spec to keep moving sliders to the right and still use the same hardware you had... 

Any DX12 game out there will do the same thing..

S.

3 minutes ago, simbol said:

They didn't dumbed it down.. they made it smarter.. people always want to crank everything to the "right" without having the required hardware to be able to sustain it and then they claim the simulator is faulty..

With new generation of simulators you cannot spec to keep moving sliders to the right and still use the same hardware you had... 

Any DX12 game out there will do the same thing..

S.

It simply doesnt make sense for the people that were getting much better performance over v4.5 to have this performance taken away because this was released before it was ready, i may be jumping the gun but based on reports i will be 10+ frames down due to changes to stabilise vram usage, 

Edited May 1, 20206 yr by suchw

4 minutes ago, simbol said:

They didn't dumbed it down.. they made it smarter.. people always want to crank everything to the "right" without having the required hardware to be able to sustain it and then they claim the simulator is faulty..

With new generation of simulators you cannot spec to keep moving sliders to the right and still use the same hardware you had... 

Any DX12 game out there will do the same thing..

S.

What has me scratching my head is that some users say that they had excellent performance (about 10 fps more) without the CTDs. If the HF1 now reduces textures to prevent vRAM exhaustion why the lower fps? FPS should be higher, not lower.

Edited May 1, 20206 yr by DJJose

Before updating I was able to have high settings and it ran decently well on my system and I never had any crashes at all. Now I am very limited with my settings and can't run it like I used to due to higher VRAM usage now in HF1.

25 minutes ago, DJJose said:

What has me scratching my head is that some users say that they had excellent performance (about 10 fps more) without the CTDs. If the HF1 now reduces textures to prevent vRAM exhaustion why the lower fps? FPS should be higher, not lower.

It depends of your settings + the dynamic texture streaming.. if you are running at 4K, you set texture resolution at 4096x4090 (4K again) you set 4xSSAA (you run now everything at 4x4K) the GPU is under stress and will be unable to maintain those 10FPS and keep your VRAM under budget.

Reducing the texture resolution will alleviate, so you can disable the dynamic streaming, and then thing will come back a bit normal..

Before nothing was restricted and your system will over-run resources at some stage causing a CTD one way or another... DX12 is very powerful and will ramp up your GPU resources super fast.. think about it as a hungry bulldog leaving it starving for 2 weeks and then showing him a big Big-Mac while we are still under lockdown..

S.

It's the opposite here. Same flight, same settings but a less VRAM uses (4.8 instead 5.3). Unfortunately, it does not matter because it crashed anyway.