stefandoesinger at gmail.com
Mon Feb 3 08:46:33 CST 2014
> Hey list
> I'm trying to find out why CS:GO is slower under wine then windows.
> When running a benchmark in CS:GO Win8 gets ~134fps and wine ~51fps.
Overall 50% performance is about what you get on average on dual core machines, depending on the game and driver. The Nvidia binary Linux driver gives you roughly 60%, the open source radeon driver approaches 30%-40%. This depends a lot on the game as well.
Did you have a look at my command stream patches? They address a major shortcoming in wined3d - it adds the ability to move major parts of the CPU side work (The OpenGL calls) into a different thread. Windows had this since many years, and my (not yet upstream) work adds it to Wine. I recommend to search the Wine-devel archives, I’ve written a lengthy mail about it somewhen in January. The single-threaded nature of WineD3D is most likely where your 50% CPU usage (Dual Core?) comes from.
> I've been following Stefan Dösingers guide (http://wiki.winehq.org/Performance) and have
> compiled wined3d for windows and tryed running CS:GO using wined3d under win8 but it just crashes while loading the map. At a guess I'd say once it trys to do 3D rendering.
Did you define USE_WIN32_OPENGL? It is needed to adjust the calling convention to Win32’s WINAPI convention. I think it is explained in the Wiki article, but I cannot check at the moment because I am drafting this mail in an airplane.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
More information about the wine-devel