![crash bandicoot n sane trilogy pc dual monitors crash bandicoot n sane trilogy pc dual monitors](https://i.ytimg.com/vi/Q9a9JFI3rCs/maxresdefault.jpg)
- #Crash bandicoot n sane trilogy pc dual monitors drivers#
- #Crash bandicoot n sane trilogy pc dual monitors update#
- #Crash bandicoot n sane trilogy pc dual monitors verification#
- #Crash bandicoot n sane trilogy pc dual monitors windows#
If you can isolate why MuQSS makes the game behave badly, it may be worth a bug report.
![crash bandicoot n sane trilogy pc dual monitors crash bandicoot n sane trilogy pc dual monitors](https://interfaceingame.com/wp-content/uploads/crash-bandicoot-n-sane-trilogy/crash-bandicoot-n-sane-trilogy-level-selection-3.png)
Generally, in-kernel schedulers should not behave that poorly. Will go back to 4.20.12 and report back for anybody else who might be affected by this. I'll try fiddling with those, thanks once more! Just booted into 4.18.8 and that didn't change a thing. Before that I tried downgrading mesa and openrc (because I remembered they updated a while ago), but those didn't help.Īha, CPU scheduler. I booted to an older kernel which didn't have muqss enabled, so my culprit seems to be CPU Scheduler that I switched some month ago. Yes I run steam natively from steam-overlay.
![crash bandicoot n sane trilogy pc dual monitors crash bandicoot n sane trilogy pc dual monitors](https://cdn.staticneo.com/n/6/coco_display.jpg)
I'm sorry to tell you, but I got it working :P Would you mind posting your specs/setup? Currently, my guess would be on the kernel because I don't see any positive reports on Kernel 4.20.x and I'd be willing to try a few rounds of git bisect to see whether that would change things. I assume you're running steam natively? That would likely exclude the container being the culprit.
#Crash bandicoot n sane trilogy pc dual monitors update#
So I'm guessing some game update or system update has caused this, but no idea what it could specifically be.ĮDIT: advised to downgrade mesa, so I did downgrade to latest stable, but it didn't solve this for me either. I tried with different proton versions, but it didn't help. Well, inspired by this post I decided to launch my Crash Bandicoot straight from steam using proton. Last edited by ShinyDoofy on Wed 5:56 am edited 2 times in total Going back to Proton 3.16 shows all the same symptoms still, but 4.2 reproducibly fixes it for me with an untouched Proton installation (no config changes necessary whatsoever). edit: Updated to Proton 4.2 and everything is running as it should now, with 120fps and without hiccups. Via strace, the game exe does virtually nothing and wineserver is doing tons of readv/writev (for the shaders to be compiled, I guess). Looking into the running processes, the game exe consumes ~150% CPU and wineserver.exe does ~60%.