pureshores commented on issue Krock/dawn#444

I happen to have an AMD Polaris and I encounter this issue as well, though, only on high shadow settings with longer sessions. My guess is it could be VRAM spilling to system ram since performance does not change when changing (shadow?) setting. In my case, changing shadow quality to medium (then restart game) alleviates the issue.

1 year ago

pureshores commented on issue Krock/dawn#422

@Cha14ka If your Wine/Proton is set to fsync, try switching to esync. That should return to normal values (Only works with Zen/1000 Hz kernels).

1 year ago

pureshores commented on issue Krock/dawn#422

Currently playing, ~1hr 30m in. So far no issues encountered.

1 year ago

pureshores commented on issue Krock/dawn#422

Currently playing, ~1hr 30m in. So far no issues encountered.

1 year ago

pureshores commented on issue Krock/dawn#404

I tested it again this day (2023-04-26). In my case, it appears (for now?) to use hoyokprot now and starts with no error. Using the game from the website without channel modifications (directly launched the binary).

1 year ago

pureshores commented on issue Krock/dawn#407

Played for around ~1 hour. So far no issues encountered.

1 year ago

pureshores commented on issue Krock/dawn#404

Based on my observation: Before 3.6, the game has uncertain chance to switch kernel service (hoyoprot, mhyprot2). There are periods of time where it would use mhyprot2 causing the game to fail to launch, though when it uses hoyoprotect it does launch. (similar to 3Shain's comment)

1 year ago

pureshores commented on issue Krock/dawn#404

> it will (yet) come at a noticeable CPU usage uplift compared to applying the secondary patch which is definitely undesirable on low-end devices such as the Steam Deck.

1 year ago

pureshores commented on issue Krock/dawn#391

Played for around ~1 hour. One freeze encountered when accessing Paimon menu, but that's about it and it didn't happened anymore with subsequent gameplay.

1 year ago

pureshores commented on issue Krock/dawn#377

Played for ~1 hour, no issues so far.

1 year ago

pureshores commented on issue Krock/dawn#367

Played for an hour, no issues encountered.

1 year ago

pureshores commented on issue Krock/dawn#355

Played for an hour, one freeze encountered (might be due to renamed `mhypbase.dll`without `patch_anti_logincrash.sh`(?) ). Other than that, no issues so far. (There's mild stutter but that's given)

2 years ago

pureshores commented on issue Krock/dawn#195

I've been testing the patch daily with `patch_anti_logincrash.sh` ever since it was published. Of the entire testing, only one freeze/crash happened, after that no freezes/crashes ever happened again. Other than that, it's been a flawless experience for me.

2 years ago

pureshores commented on issue Krock/dawn#195

@jingai `mhypbase.dll` is what causes the high utilization. While `patch_anti_logincrash.sh` prevents the crash upon login due to `mhypbase.dll` not being present.

2 years ago

pureshores commented on issue Krock/dawn#195

@Krock Thank you for the patch. So far i haven't encountered any issues with it.

2 years ago

pureshores commented on issue Krock/dawn#195

> What shall be done?

2 years ago

pureshores commented on issue Krock/dawn#195

DXVK does not seem to have an affect in this, i have my state cache symlinked so i can easily restore it.

2 years ago

pureshores commented on issue Krock/dawn#195

Hello @Krock, sorry for the bother.

2 years ago

pureshores commented on issue Krock/dawn#345

Played for around 1 hour, no issues encountered (aside from the usual stutter caused by DXVK).

2 years ago

pureshores closed issue Krock/dawn#344

2 years ago