Throttling that thread affected performance negatively, and a proper fix was invasive.Ī quick test run with Special K (and without CPU usage fixes from SilentPatch) shows that the CPU usage is indeed significantly lower: I was not able to easily patch the biggest offender, pxd::server_job.Loading times got significantly longer.My approach had some side effects, though: In the last blog post, I identified several hot pointsĬausing the needlessly high CPU usage and fixed some of them. While I’m at it, let’s also take a look at how This means that the fixes I bring need to be re-visited, as they might be obsolete. That changelog is… very similar to what SilentPatch brings! Random crash when ending fights with Heat Move – we managed to fix a crash occurring occasionally after finishing battles with a Heat Action.High CPU usage thread – CPU usage has been cut down by ~30%.
Setting ‘Auto’ as default framerate settings.Proper dedicated GPU detection so that the game won’t try to launch on integrated GPUs.Let’s have a look at this shared changelog! The majority of the changelog is shared across three games, with only Yakuza 3 receiving a single “exclusive” fix. I released a SilentPatch for Yakuza 3 and 4Īnd around a week ago those games (together with Yakuza 5) received official patches. This resulted in SilentPatch receiving support for Yakuza 5, which naturally delayed everything a few days.īecause of that, this post now consists of two parts, with Part 1 being the “original” patch analysis and Part 2 being a Yakuza 5 release post. However, just before releasing I was made aware of several issues with Yakuza 5 and looked into them. Scroll down to the Download section for a download link.ĭisclaimer: This post was almost ready a few days ago and was supposed to be an analysis of QLOC’s patch together TL DR - if you are not interested in an in-depth overview of what was wrong with the game and how it was fixed, Analyzing the official Yakuza 3, 4, 5 patches & SilentPatch update
0 kommentar(er)
