| 10 Jan 2026 |
 woobilicious | * Problem is protondb has a retarded policy of marking games with a Native Linux client as "great" even if the linux client is next to useless | 06:29:45 |
 Sandro 🐧 | ~protondb~ => proton github issues | 06:31:12 |
| woobilicious | The Linux client isn't multiplayer compatible with Windows clients | 06:31:17 |
| Sandro 🐧 | * ~~protondb~~ => proton github issues | 06:31:25 |
| Sandro 🐧 | * ~protondb~ => proton github issues | 06:31:28 |
| woobilicious | But yeah it's this game if you're curious: https://www.protondb.com/app/1142710 | 06:33:44 |
| woobilicious | I'll mess around with thread settings in the settings files, perhaps wine isn't describing the topology correctly to the game | 06:52:47 |
| woobilicious | IT's one of those games that always uses 100% gpu I vaguely remember this happening before with incorrect threading setup, didn't matter if it was running at 20 or 60fps, it was always 100% | 07:01:51 |
 Atemu | There's still reports using Proton there | 07:12:23 |
| Atemu | Like, locked to 20fps? | 07:12:51 |
| woobilicious | I mean I got a dual CCD system and the game seemed to be stuck at a max of 20fps but the GPU was still pinned to 100%, but if I adjusted the topology I got 60fps and it was still at 100% | 07:14:31 |
| Atemu | mhh | 07:15:34 |
| Atemu | I've seen different swapchain settings produce unexpectedly high reported GPU usage | 07:16:19 |
| Atemu | Or does it use dynamic resolution perhaps? | 07:17:21 |
| woobilicious | Na, I assume it's async compute stuff | 07:17:58 |
| Atemu | hm | 07:18:27 |
| Atemu | Anyhow; if CPU usage is anywhere near 100%, that'd imply a massive CPU bottleneck | 07:19:05 |
| Atemu | What's the hardware? | 07:19:13 |
| woobilicious | 5900X, the game was causing a full gpu crash followed by a CPU error, it now seems stable after disabling PCIe power managemnt. but after twaeking settings for a month I can't figure out how to get it working better again | 07:22:37 |
| woobilicious | and a Radeon 5700 XT | 07:22:53 |
| Atemu | Something doesn't add up here. I'm cofused, therefore an assumption I made is wrong. That usually points to some indirect cause like a thermal or power issue.
You could isolate the bottleneck first by lowering the resolution to something tiny
| 07:30:30 |
| woobilicious | Finally I'm getting 50fps, I changed WINE_CPU_TOPOLOGY from cores 12-17 to 0-5, no clue why that matters | 07:31:56 |
| woobilicious | But it still doesn't help that the game is using denuvo lol | 07:40:08 |
 K900 | Denuvo hurting performance is honestly mostly a meme | 07:50:23 |
| K900 | Denuvo is, fundamentally, just a big fat targeted obfuscatir | 07:50:41 |
| K900 | * | 07:50:45 |
| K900 | As long as the game doesn't use it on hot code, it should not actually matter | 07:51:17 |
| woobilicious | Well yeah but good luck stingy execs allocating resources to do that last bit | 07:52:49 |
| woobilicious | It also doesn't help that a rich mans cache hit is a poor mans cache miss, I bet this game ran better on release simply due to the lack of X3D and 1MB L2 cache that devs have access to, once you release a few DLCs games run so much worse | 08:05:23 |
 SigmaSquadron | didn't several media outlets test denuvo and non-denuvo copies of games and found that most of time, denuvo-enabled games had lower performance? | 08:12:18 |
