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
Don't spread more idiotic rumors if you don't know. For one it just gets more people ♥♥♥♥♥♥♥♥ about things they're not fully informed on, and for two it diverts attention away from the actual culprit and responsible party.
I've seen this type of freezing MULTIPLE times in other games. In all cases, the only common thing between those games is Denuvo. Denuvo hogs CPU, and if you have an older CPU without much GHz to spare then it causes these freezes.
I'm not a fan of Denuvo, but most the time it's everything except Denuvo being broken which causes the weird as hell issues. Like FFXV, it's SteamAPI being hammered constantly. Some games also do weird things with input devices polling for gamepads constantly. Don't remember which game but there was one where like having a gamepad vs. no gamepad could massively alter the performance.
Yeah don't mess with that, it won't help most the time and can just break things more.
That sounds EXACTLY like the type of freeze I experienced which I fixed with this method.
The only performance issue I've ever personally seen with Denuvo is the occasional long loading when first opening a game. Not an issue with Y0 though. Like you say, it's doing plenty of weird non-Denuvo stuff all by itself.
Let's start listing the common things in all games, shall we? They all send data from CPU->GPU with a driver in the middle -- a driver, whose overhead is less predictable than Denuvo. They've all got a dedicated thread (sometimes two or three) to buffering audio, this thread has to run at very high priority because it only feeds the sound card a couple of milliseconds worth of data and if the thread is interrupted, BAM, audio stutter.
Most Steam games also have a dedicated connection between the game and the Steam client, sort of like a network link between two running programs on the same computer. If the Steam client goes tits up for some reason, your game also slows down because at least once per-frame the two things are synchronized. Really stupid games on Steam will synchronize themselves with the Steam client 36,000 times a second -- these games have @#$%ing horrible performance characteristics.
I covered all the bases, audio is just a really good example of why a thread can be up at 99% load and be operating as intended. Any thread that must bias responsiveness over number crunching actually tends to be the thread that gets all available CPU time in a properly operating program. Windows will lower the priority of any CPU-intensive thread relative to I/O threads if they are causing priority inversion.
And you're totally using this software the wrong way. You are supposed to throttle background services whose priority level is high enough to pre-empt the game. You're done the exact opposite of what you need to do to fix any priority issues -- you're basically just creating bottlenecks where none existed.
Don't mind me though, I'm just shilling for Denuvo ... somehow.
Frankly I couldn't care less what the specific mechanics of how it froze was, I am only concerned in the fact that it appears to be Denuvo causing it, and that this is how I was able to fix it.
In fact, ALL of you have misread the entire point of this thread. It is not to argue about Denuvo. It's to share a way to fix the intermittant freezing that occurs in the game for many people.