Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
First, I want to congratulate you for being the poster of an actual forum topic that is relevant.
Now, I want to only suggest you some variances for you to try.
Only this comes to my mind, for a start :
You didn't write there if you have tried with a "community server", as it is not your friend's game(P2P-like connection) nor will be like an official official server game (please explore which protocols are active for a connection such as this, TCP/IP, UDP or both, I don't know)
well, trying TF2 and CS:GO with community servers having NO VAC enabled, might be a good identification test to detect the problem, as you well know, TF2 official servers also use VAC.
I will check more this TCP/IP or UDP connection while doing so. But out of all the community servers I tried, the only time I couldn't play was because I got automatically kicked for whatever internal reason by the host.
that kick... can you reproduce that ?
as you well can identify I'm kinda out of knowledge on this, however I'm trying my best at least to identify the problem, so you can fix it easily.
because it comes to my mind, the host (server on the other side) has ACTUALLY communicated with your side succesfully but KICKED you out for a particular reason. my advice would be the analyze the ports during reproduction, and check out any .log (logfiles) that may be produced.
but still, knowledge about the usage of TCP/IP and/or UDP during connection also can come in handy still...
also, finally, may I suggest that, can you think :
"what could be the difference between a community server with VAC (which you say it's fine), and an official server with VAC OR P2P (friend's game) connection ?"
a reason coming to my mind, that Valve updated it's VAC sometime that started your troubles - that somehow creates noncompatibility with your OS - this will only be relevant, if you try to join those same official servers now, with a different OS - being the best candidate, a wide used one like Windows.
I wish you well...
Trying to connect to an official server mentions "Failed to communicate with routing cluster "[three letters]" " several times, before showing me ping location. I do not know if this is relevant or not.
"Try this, while in main menu open console and type "net_client_steamdatagram_enable_override -1"
http://steamcommunity.com/app/730/discussions/0/224446614465451925/ "
as between the "kick report" on the console you have from the community server, there are shader fail messages.
now, I know I sound completely like a monkey wrench in this thread, but isn't shaders about graphics library that CS:GO uses, to utilize the graphics card in your system ?
so, the reason may well as be the new "-d3d9ex" executable main argument add-up, if you have added it. if you haven't added it, try with this added. I know this is about CPU utilization part of the library, but may as well effect graphics interfaces.
I'm truly done now. Nothing else comes to my mind. :)
I don't own 1.6 but my bf, with whom we share our library mutually, has the old Counter-Strike, I installed it and it didn't worked unfortunately :[
I'm a bit doubtful with that DX3D9 argument, I'm on Linux, isn't Counter-Strike on Linux supposed to be only working with OpenGL?