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
The next thing (or maybe in parallel) would be to see if there are any demanding third-party programs or processes running (e.g. Nahimic sound, systray programs, third party antiviruses, etc). If so, try to deproritize them ( https://www.tenforums.com/tutorials/89548-set-cpu-process-priority-applications-windows-10-a.html ) or close them.
Thanks for the reply, but i managed to solve my issue.
I disabled the xbox overlay and also set the game's priority to "realtime" in the task manager, this solved BOTH the "optimising shaders" and the fps issues (which may have been the same issue)
I dont know if it was either the overlay or the priority that solved the issue (or a combination of both) but it is the first time i have ever had to do this with any game so I'm a little disappointed.
It's how it's designed by the developers since patch 1.07, and it's nothing to worry about (just continue to the game):
https://store.steampowered.com/news/app/1151640/view/2947004218177288149
All games need shader optimisation. Not all game developers decide to make this step visible to the players.
DX12 games achieve better performance by performing a one-off time-consuming pre-optimisation.
This should only happen ONCE until the user changes hardware/updates drivers.
The issue i was having was that it was not just performing the full process every time i started the game (something that theoretically should not have to happen) but it was ALSO doing the full process every time i backed out to the main menu (that should DEFINITELY not happen).
On top of this i suspected that it was optimising the shaders during the game as if i had not let it complete the process at all, causing massive frame drops, DESPITE letting it reach 100% each time it was telling me it was optimising.
By performing the fixes i listed in my follow-up comment (which i will add to my original post, for clarity) not only have i eliminated the performance issues, but the game no longer needs to optimise shaders every time i start it up
Then 1.07 came out and changed that because the devs got tired of people with low end systems whining because they were crashing during it.
Also: Never set a program to realtime priority.
Ever.
I noticed you are using a mobile CPU. Laptops are usually full of heavy unnecessary bloatware that may interfere with playing games and performance. It's recommended to uninstall all of it before using the laptop. Maybe it's time for some software cleaning? There are guides for this somewhere, I suppose. But that's just my guess, as it's very common.
There was also a post by a laptop user with similar random dips in performance. The cause was excessive heat and thermal throttling. Maybe it's worth looking into as well at some point.
Just writing this in case any of this happens again, in any game.
Im not saying for CERTAIN the two issues were linked, but given the fact that the only times my GPU maxed out was during the optimisation and during the frame drops (which was independent of performance) it just SEEMS like they are related, especially since both problems were solved at the same time.
Just booted up the game, and there was no optimising shaders message, so it looks like my fix stuck.
All bloatware was removed when i got the computer
As for the fixes i used specifically, performance guides for this game specifically mentioned that changing the priority to realtime and turning of the game bar were pretty crucial depending on your hardware.
https://devblogs.microsoft.com/oldnewthing/20100610-00/?p=13753
Something else was or is probably happening.
I do, my machine never reaches temperatures high enough to require throttling, even without it.