Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Yea...install your drivers without GeForce Experience (Driver only)...I bet your issue disappears.
So I checked, Geforce Overlay was already disabled.
Tried this as well, installed the drivers without GeForce Experience. Still the same problem persists.
Thanks for the suggestion anyway.
Thanks for the suggestion anyway. I am reinstalled the drivers without Geforce Experience to remove it completely from my system as I never really use it,
Two other things you could try....
1) Open Nvidia Control Panel --->Manage 3D settings ---> Global settings ----> disable Shader Cache Size ---> Save then Restart PC ----> Go here: %localappdata%\NVIDIA ---> delete DX (if you have it) and the GLCache folder ---> back to Nvidia Contol Panel and turn Shader Cache Size back to default --->Open Disk Cleanup (C: Drive) and make sure the DirectX Shader Cache is checked (uncheck everything else if you don't know what your doing) click OK ---> Restart PC
2) Run the DirectX runtime installer.
Maybe one of these will help you.
Thanks mate, will give it a bash and let you know.
I have a funny feeling it maybe related to DirectX as I noticed in my testing DX11, the degradation in slowed considerably.
This is with a 7800X3D, so I reckon if you're affected by this issue, your hardware doesn't matter. CPU busy starts out around 10 ms i.e. 100 fps. Also happens with Dx11, Dx12 and Vulkan.
Interesting and we are using different hardware.
I have also tried other troubleshooting methods such as:
This leaves me to believe that there maybe some sort of memory leak, or Satisfactory seems to be caching or not de-referencing menus after they have been accessed which is caused huge frame-rate drops when accessed again.
I have updated my post on the QA website, the only thing I can suggest for now is up vote the post that I have shared in the original post.
At least I know now it can't be my hardware. But I have been pretty confident of this from the beginning as I have zero issues with any other title.
Thanks for the suggestion, I have tried this but the problem still persists.