cs:go ubuntu 14.04LTS bug fps down

[ace62160]

i playing cs:go on ubuntu, and any time on game my fps down ~10. :/

i use command "LC_ALL=C LANG=en_US.UTF-8 SDL_AUDIODRIVER=pulse %command%"

processor : AMD Phenom(tm) II X4 840 Processor × 4 graphic card : GeForce GTX 560 Ti/PCIe/SSE2 os: ubuntu 14.04LTS 64bits (Unity) NVIDIA binary driver - versiob 331.38 (nvidia-331)

http://cloud-4.steampowered.com/ugc/548634682857625884/B639DC83AA78041EDA33A3E589370AB86B354990/

http://cloud-4.steampowered.com/ugc/548634682857864476/8DE0012872546E32B8E2D58B3668990940D47AAB/

capture of my monitor system and nvidia setting with fps down http://postimg.org/image/epeqnx78v/ http://postimg.org/image/m5fh75r2b/

[Tele42]

Please include your system information as requested at https://github.com/ValveSoftware/Counter-Strike-Global-Offensive#system-information.

[Gasur]

I have the samme issue as @ace62160 Without the launch command, the game fails to even load up a map & just crashes, however with there's some interesting things happening. On Windows I get the 300fps capped with everything maxed out. Linux it's 30fps (steadily), this is regardless of graphical settings.

CPU: AMD FX 8320 (OC to 3.8GHz). GPU: Nvidia GTX 660 (Gigabyte version). OS: Ubuntu 14.04 LTS 64 bit. Nvidia driver(s): I tried the 331.38 (latest), however the game can't even start up with that, neither with some other versions. But with the open-source x-org one Nouveau, I can - with horrible FPS.

[nhowe1991]

I am also having this issue. I will be able to get more detailed information when I get home but here is what I have for now:

CPU: Phenom II 955 RAM: 4GB GPU: Nvidia GTX 560 Ti Distro: Ubuntu GNOME 14.04 64 bit

Everything runs great on windows and runs great when I first start playing (pretty consistent at ~150 FPS) I thought it was maybe my system running out of RAM but it appears I'm not the only one with the issue.......but I could use more RAM anyway....

When it does happen it quickly goes down to 10-15 very unplayable FPS. It also causes the menu to become very laggy and unresponsive as well even when not connected to a server.

[pyamsoft]

Performance issues may be related to the resource consumption of your Window Manager / Desktop Environment. For both Unity and Gnome Desktop, compositing is (I believe) enabled by default. This may lead to an increased usage of resources for the desktop, and as a result, less resources being available for the CSGO client. On another note, by default the environment variable vblank_mode is set to 1, which I believe means that v-sync is enabled desktop wide regardless of your in game setting. by adding vblank_mode=0 to your environment or game launch settings, it will turn off this forced v-sync and should in theory increase your FPS, although there are no guarantees.

Performance decreasing over time may be the result of heat building up in your system causing your CPU to throttle its speeds in order to maintain safe temperatures.

[nhowe1991]

I installed another DE (LXDE) to game in and the RAM is no longer an issue(or the compositing) but the FPS still dropped quite alot after playing for a while. I'll try the vblank_mode=0 later tonight as I forgot to when last time I played.

[pyamsoft]

If FPS is dropped after extended periods of time, it could be that your computer has created enough heat to cause its CPU to throttle frequencies for safety purposes. Try to monitor the temperatures of your CPU heat and be sure that they stay consistantly below the "maximum" temperatures.

[Gasur]

@pyamsoft Negative. Even at full load (100% for both CPU & GPU), it never goes above 50-60 degrees. However, I found the culprit. The drivers Ubuntu gives out, even the proprietary ones doesn't seem to work as they should. I removed all drivers & then installed the latest Nvidia driver without X (screen) & now I have 200+ FPS. @Junixx Please try to do what I did, it might work.

[Tele42]

Closing as general driver quality from 2014 is no longer relevant. If you are still having this issue, please update to a recent driver release and if that does not help, then open a new issue report.