https://bugs.winehq.org/show_bug.cgi?id=42592
--- Comment #40 from Kai Krakow kai@kaishome.de --- Upon the pointer to downgrade the nvidia driver, I downgraded back from latest beta to latest stable (still above 375, tho). It may have changed a few bits of how the game feels, nothing dramatic.
But after playing around a little bit, I'm pretty sure that there is no overloading at any point. The game engine just becomes slow: Physics play slow motion, movement is slow motion. If the FPS go down, in-game speed also goes down, like there are some timer ticks missed which the game doesn't pick up within Wine. It almost always looks like the game does not or cannot skip frames to keep up with realtime but just slows down the whole game engine, trying to render every frame...
Something similar is also visible with some "native" ports like Mad Max, and I guess it uses some stuff that Wine also does (wrappers around syscalls etc). The guys from Feral pointed out that this may be a kernel issue, timing handled differently between kernel versions. They suggested to set the CPU governor from default ondemand to performance. Well, that didn't help at all. But at least they could reproduce it later and wanted to get a fix in when a newer kernel version goes stable on Ubuntu (which is their supported platform).
So, with this background: Are there known kernel options which could influence or explain such behavior within Wine? Since I'm on Gentoo and as such using a custom kernel build, I'd happily try a few options.