Closed Crendgrim closed 8 years ago
Map [maps/surf_faint_fix.bsp] has incorrect BSP version (643383601 should be 21).
Couldn't CRC map maps/surf_faint_fix.bsp, disconnecting
Delete & download the map again.
It also happens when you're joining a full server. You see the countdown but go back to the mainmenu.
Can you provide a specific example of a server this happens to you on?
Similar issue, same OS: openSUSE 13.2 x64 / KDE (same versions), game always time out, console dump:
Failed to load gamerulescvars.txt, game rules cvars might not be reported to management tools.
Parent cvar in client.dll not allowed (cl_remove_old_ugc_downloads)
Parent cvar in client.dll not allowed (mp_endmatch_votenextleveltime)
Parent cvar in client.dll not allowed (mp_verbose_changelevel_spew)
maxplayers set to 64
Error: Material "debug/debugluxels" uses unknown shader "DebugLuxels"
KV Conditional: Unknown symbol INPUTSWAPAB
KV Conditional: Unknown symbol INPUTSWAPAB
Error: Material "___fillrate_0" uses unknown shader "FillRate"
Error: Material "___debugnormalmap_1" uses unknown shader "DebugNormalMap"
Error: Material "___debugdrawenvmapmask_2" uses unknown shader "DebugDrawEnvmapMask"
Error: Material "___debugdepth_3" uses unknown shader "DebugDepth"
Error: Material "___debugdepth_4" uses unknown shader "DebugDepth"
Requesting texture value from var "$basetexture" which is not a texture value (material: dev/constant_color)
Steam config directory: /home/enigma/.local/share/Steam/steamapps/common/Counter-Strike Global Offensive/platform/config
--- Missing Vgui material vgui/store/store_item_bg
--- Missing Vgui material vgui/store/store_item_bg_highlight
--- Missing Vgui material vgui/store/store_item_sel_bg
--- Missing Vgui material vgui/store/store_item_pickup_bg
--- Missing Vgui material vgui/store/store_preview_bg
--- Missing Vgui material vgui/store/store_bottom_bar_button_bg
--- Missing Vgui material vgui/store/store_bottom_bar_button_highlight_bg
--- Missing Vgui material vgui/store/store_default_dialog
--- Missing Vgui material vgui/store/store_backpack_bg
--- Missing Vgui material vgui/store/store_backpack_bg_highlight
--- Missing Vgui material vgui/store/store_backpack_bg_highlight
--- Missing Vgui material vgui/store/store_discount_corner
--- Missing Vgui material vgui/store/store_preview_bg
--- Missing Vgui material vgui/store/store_tooltip_bg
--- Missing Vgui material vgui/store/store_tab_selected
--- Missing Vgui material vgui/store/store_tab_unselected
--- Missing Vgui material vgui/btn_econ_blue
--- Missing Vgui material vgui/store/button_econ_blue_over
--- Missing Vgui material vgui/store/store_backpack_bg
--- Missing Vgui material vgui/store/store_backpack_bg_highlight
--- Missing Vgui material vgui/store/store_backpack_bg_highlight
Error: Material "___fillrate_0" uses unknown shader "FillRate"
Error: Material "___debugnormalmap_1" uses unknown shader "DebugNormalMap"
Error: Material "___debugdrawenvmapmask_2" uses unknown shader "DebugDrawEnvmapMask"
Error: Material "___debugdepth_3" uses unknown shader "DebugDepth"
Error: Material "___debugdepth_4" uses unknown shader "DebugDepth"
Error: Material "debug/debugluxels" uses unknown shader "DebugLuxels"
Requesting texture value from var "$basetexture" which is not a texture value (material: dev/constant_color)
Unknown command "cl_thirdperson"
Did not detect any valid joysticks.
Unknown command "tr_best_course_time"
Unknown command "tr_completed_training"
Unknown command "weapon_accuracy_logging"
Unknown command "cl_teamid_min"
Unknown command "cl_teamid_max"
Can't use cheat cvar cl_teamid_overhead in multiplayer, unless the server has sv_cheats set to 1.
Can't use cheat cvar cl_teamid_overhead_maxdist in multiplayer, unless the server has sv_cheats set to 1.
Unknown command "cl_thirdperson"
Did not detect any valid joysticks.
Unknown command "tr_best_course_time"
Unknown command "tr_completed_training"
Unknown command "weapon_accuracy_logging"
Host_WriteConfiguration: Wrote cfg/config.cfg
Host_WriteConfiguration: Wrote cfg/config.cfg
SignalXWriteOpportunity(4)
Connecting to public(146.66.159.206:27022) ...
Server using 'public' lobbies, requiring pw no, lobby id ffffffffffffffff
Retrying public(146.66.159.206:27022) ...
Server using 'public' lobbies, requiring pw no, lobby id ffffffffffffffff
Retrying public(146.66.159.206:27022) ...
Server using 'public' lobbies, requiring pw no, lobby id ffffffffffffffff
Retrying public(146.66.159.206:27022) ...
Server using 'public' lobbies, requiring pw no, lobby id ffffffffffffffff
Retrying public(146.66.159.206:27022) ...
Server using 'public' lobbies, requiring pw no, lobby id ffffffffffffffff
Retrying public(146.66.159.206:27022) ...
Server using 'public' lobbies, requiring pw no, lobby id ffffffffffffffff
Retrying public(146.66.159.206:27022) ...
Server using 'public' lobbies, requiring pw no, lobby id ffffffffffffffff
Retrying public(146.66.159.206:27022) ...
Server using 'public' lobbies, requiring pw no, lobby id ffffffffffffffff
Retrying public(146.66.159.206:27022) ...
Server using 'public' lobbies, requiring pw no, lobby id ffffffffffffffff
Retrying public(146.66.159.206:27022) ...
Server using 'public' lobbies, requiring pw no, lobby id ffffffffffffffff
Connection failed after 10 retries.
I tried replicating this issue, and was not very successful. Most of the time, issue #277 stops me from joining the servers at all, so this issue does not have a chance to pop up. I wish I knew what I changed, but from my observations it feels almost random. Two examples for servers it did happen on are in this thread. I could connect to the server in the report just fine later, though.
I will keep a detailed log with time and server whenever this happens from now on.
@Crendgrim, have you encountered this issue since the 64 bit client update?
Closing pending feedback.
I reported two bugs with the community servers on Linux separately, since I feel like they are unrelated. The other bug is here: #277
When I do manage to connect to community servers, it fails in the following way:
This is the console output of the latest occurence:
Whenever it happens, this behaviour is absolutely reproducable each subsequent time I try to connect.
OS: openSUSE 13.2 x64 (Linux 3.16.7) / KDE Plasma 5.2.0