Nvidia Shader cache size?

[Zixpk]

A few people recommend setting this to 'unlimited', but I was wondering if 10gb would be good enough.

[Tommy Wiseau✔]

I had 10gb right off the bat and it didn't helped.

[Arokhantos]

Originally posted by Not Pareidolia:

I had 10gb right off the bat and it didn't helped.

It has to generate up to 10 gb shader cache first and it will delete and rebuild every driver update so the setting is pointless it just puts a size limit on shader cache nothing more.

[Krythic]

Originally posted by Zixpk:

A few people recommend setting this to 'unlimited', but I was wondering if 10gb would be good enough.

Setting this does nothing, because DX12 defines and builds it's own shader cache. Setting the size only affects <= DX11

[Qoojo]

10 gb should be more than enough. You can verify by looking in "C:\Users\<windows username>\AppData\Local\NVIDIA\DXCache" and checking the usage.

Edit: I did not know that dx12 uses its own cache.

[Yew Nough]

Changing shader cache setting does nothing if you're looking for a fix for stuttering. Just leave it at default until further notice.

[Zinx]

try nvidia systemcontrolling with rightclick and choose 3d setting programmsetting and there you have to choose the Elden Ring game itself.

[Zixpk]

Originally posted by Krythic:

Originally posted by Zixpk:

A few people recommend setting this to 'unlimited', but I was wondering if 10gb would be good enough.

Setting this does nothing, because DX12 defines and builds it's own shader cache. Setting the size only affects <= DX11

Damn, that sucks big time

[Zixpk]

Originally posted by Zinx:

try nvidia systemcontrolling with rightclick and choose 3d setting programmsetting and there you have to choose the Elden Ring game itself.

Did this already, set the game to max performance and vsync off (to use freesync)

[Zixpk]

On an unrelated note, setting this to 10gb should then solve stutter in something like dishonored 2 right (dx11)

[CrusadeEclipse]

Originally posted by Zixpk:

A few people recommend setting this to 'unlimited', but I was wondering if 10gb would be good enough.

Shader cache only affects DX11 games. Elden Ring is DX12, so the developers are in charge of handling their own shader cache.

[KingKangIV]

Changing your gpu setting wont work, the game is building them for you and that is the root cause of many issues. This is thanks to DX12 ans so unless From improves performance changing your gpu around wont help. Or at least that is how I understand it from watching a video explaining some of these issues.

[Zinx]

Originally posted by Zixpk:

Originally posted by Zinx:

try nvidia systemcontrolling with rightclick and choose 3d setting programmsetting and there you have to choose the Elden Ring game itself.

Did this already, set the game to max performance and vsync off (to use freesync)

No try pls to change the DX12 to DX11, that maybe is going to help more and if you can change it FS developed this game especially to DX12 and that causes the problems

[Krythic]

Originally posted by Zixpk:

Originally posted by Krythic:

Setting this does nothing, because DX12 defines and builds it's own shader cache. Setting the size only affects <= DX11

Damn, that sucks big time

No. It's actually a really good thing. The old way of doing it is deprecated, because allowing developers to define and manage their own caches allows for better dynamic shaders.

[Whamarama]

I tried playing for multiple hours with default and unlimited shader cache in nvidia control panel and it made no difference.
The stuttering in game seems to mostly be from the game streaming in textures and world data.
Unfortunately at the moment it seems there is nothing you or I can do to remedy the issue.

[Zixpk]

Originally posted by Krythic:

Originally posted by Zixpk:

Damn, that sucks big time

No. It's actually a really good thing. The old way of doing it is deprecated, because allowing developers to define and manage their own caches allows for better dynamic shaders.

I meant short-term--no doubt it's a good thing, but clearly FromSoft has mishandled it here