Counter-Strike 2 Forum

Per the game's AppDB page, I entered "echo 0|sudo tee /proc/sys/kernel/yama/ptrace_scope" in a terminal prior to running the game (Kubuntu 12.04 x64). I also verified the game cache which resulted in one file being reacquired. From there clicking "play" resulted in the game going through the "Completing Installation" stage and then attempting to install DirectX. I let it continue and the game proceeded to load. I was able to make appropriate changes to audio and video settings, and I managed to load a map for offline play with bots. However mouse movement/looking was not functioning; while I could move my character around using "WASD" and firing and cycling through my weapons with the mouse, I was unable to look around which effectively renders the game unplayable. I think with a little more work CS:GO will be fully playable.

My hardware:
AMD Athlon 64 3200+
2 GB DDR400
NVIDIA GeForce 7600 GS
NVIDIA Driver Version 304.37
Kubuntu 12.04 x64

Please Codeweavers, lets get this game supported. At least until Valve officially ports this to Linux.

And thanks for the heads up Charles.

Hmm...tried again tonight, no luck. It appears as if the changes I made to my audio and video settings didn't save, and the game crashes when I attempt to change the resolution. Further when I attempt to join a game via quick match or create my own game, the progress bar reaches about 75%-80% before the game and the Steam client both crashes. I re-verified the game's cache, one file was downloaded again, but this did not solve the crashes. I generated a log file using "Run a Windows Command" and launching csgo.exe directly.

The last few lines in the log included:```
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
err:ntdll:RtlpWaitForCriticalSection section 0x2b2fa0f0 "mmdevdrv.c: ACImpl.lock" wait timed out in thread 0037, blocked by 0030, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x2b2fa0f0 "mmdevdrv.c: ACImpl.lock" wait timed out in thread 0037, blocked by 0030, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x2b2fa0f0 "mmdevdrv.c: ACImpl.lock" wait timed out in thread 0037, blocked by 0030, retrying (60 sec)

After looking over the log in its entirety (log is 63kb total), I noticed numerous d3d errors. I can post or email the log if necessary. Hopefully others can test the game and we can work towards getting it to a playable state.

**UPDATE**  
After logging out and logging back in to my desktop session, I managed to launch the game and change it from fullscreen to windowed. In windowed mode, apparently changes to my audio and video settings are saved properly, and I can start a game. I would also like to point out that desktop effects are disabled.

Apparently I also overlooked a remedy for the mouse problem on the Wine AppDB. I disabled "raw mouse input" under keyboard and mouse settings, and I can now use the mouse properly: aiming and mouselook works as intended. Slowly but surely I am beginning to get this straightened out.

For starters, I have a ginormous bottle for all things steam so getting technical on what settings I have at this point is impossible. That said, After buying the game and starting the D/L I had to bail for work. After getting home and having a moment to fart with this the only thing I had to do was turn down the settings royally and disable the raw mouse input. I got a few rounds in sofar, with mostly performance issues that are minor.

I would like to see some recommended settings for this or a newer CX build that uses a newer wine. Raw wine 1.5.10 doesn't behave poorly at all, and in fact all it requires to run perfect is raw input disabled.

After fully reading your reply, I realized (late, but I got there!) that you may have run into what I have been putting up with on a Ubuntu install I recently got up and going. (just in case the Linux Steam client only will work on Ubuntu at first).

Read and follow these. I got to nearly where I am on my RHEL/CentOS/SL installs.

http://www.codeweavers.com/support/wiki/linux/faq/ubuntu1204
http://www.codeweavers.com/support/wiki/linux/faq/ubuntu1206jpeg <-- Not as obvious, but this resolved some issues for me. No error dialogues, just quirks until I did that.
http://stackoverflow.com/questions/9151491/extending-default-lib-search-path-in-ubuntu <--- I also recall adding some stuff to /etc/ld.so.conf or something from that first link... here is a tab that I had open at one time that detailed more on that.

Needless to say, I am still not all that impressed with Ubuntu, and although much more stable that Fedora ever will be (on purpose), I find that OpenSUSE fits that bill without all the breakage.

Now most of the issues arise from x64 installs of *buntu, and all the fixes I had to implement were due to that. But going over them may not be a bad idea anyhow.

HTH,
Andrew.

Andrew,

I followed the information from your first link and now CS:GO is running a lot better than before. I put in about fifteen minutes and no crashes, yet. If my hardware was up to par I imagine the game would run a lot better than it does now, but I'm happy that I can at least play it.

It works for me, for the most part, I set mouse to raw input disabled and the game works great but randomly my whole system freezes and I have to do a hard restart just like with cs:source. I gave it a silver rating because when it runs it runs great and would get gold if the two issues could be fixed.

As far as installing it, I was playing the beta and it converted it to the release version which did not want to start, it kept telling me it had to update but would not. I had to remove (uninstall) it then reinstall it, which was not that big of a hassle. The part that bugs me is that fact that it just randomly crashes just like cs:source; and yes i have tried all the fixes posted for that.

System Specs:
intel q9550 2.83gz
nvidia gts 250
6gigs ram ddr3-1600mhz
nvidia driver 304.37
fedora 16 x64

One other thing that I suggest is turning off multicore rendering and putting the shaders to medium or low. I know the source engine had some issues when using multicore rendering and furthermore, applications that try to use more than 2 cores on wine tend to slow down quite a bit (Diablo 3 and WoW come to mind) Unfortunately I'm not big on CS like games so I have not tested extensively. I've played a few maps and that's that. Ran very smooth for me.