Hier werden die Unterschiede zwischen zwei Versionen gezeigt.
csgo_beta:known_bugs [2012/06/03 19:31] DeaD_EyE |
csgo_beta:known_bugs [2012/06/03 22:53] (aktuell) DeaD_EyE [Bekannte Bugs] |
||
---|---|---|---|
Zeile 3: | Zeile 3: | ||
^Segfault bei Debian Squeeze 64bit wenn Großbuchstaben im Pfad vorhanden sind ^ | ^Segfault bei Debian Squeeze 64bit wenn Großbuchstaben im Pfad vorhanden sind ^ | ||
- | |If the full path leading up to where srcds is located is all in lower case then I have no problems. If there is a folder in the way that has a capital in then it fails. For example srcds run from /home/users/upper1case27215/server/server/csgo works fine, but /home/users/Upper1Case27215/server/server/csgo does not - giving me the same error and segmentation fault as the others here. I am running srcds as follows: ./srcds_linux -console -game csgo -port 27215 -usercon +map de_dust2_se +game_type 0 +game_mode 1 +maxplayers 12 | | + | |Wenn sich im kompletten Pfad keine Leerzeichen, gibt es keine Probleme mit dem Start des Servers. Sollten im Pfad Großbuchstaben vorhanden sein, muss der Server woanders installiert werden. | |
^bash: ./srcds_run: ''/bin/sh^M'': bad interpreter: No such file or directory on Linux ^ | ^bash: ./srcds_run: ''/bin/sh^M'': bad interpreter: No such file or directory on Linux ^ | ||
|Verwende das Tool dos2unix\\ Alternativ kann auch die srcds_linux direkt verwendet werden. | | |Verwende das Tool dos2unix\\ Alternativ kann auch die srcds_linux direkt verwendet werden. | | ||
Zeile 9: | Zeile 9: | ||
|Einfach sv_consistency auf 0 setzen | | |Einfach sv_consistency auf 0 setzen | | ||
^round_end lag ^ | ^round_end lag ^ | ||
- | |Most noticeable when the round_end is triggered by all players dead Apparently setting srcds to run on just 1 core fixes this problem, however this is unconfirmed since I have the same problem on a single core. I quote: I just tested this over and over again , and came to the result that affinity affects csgo server ( I have also windows 2008 R2 , my virtual machine). With affinity enabled to one of the 4 cores , I didn't notice any round end lag , compared to when It was before , with all cores enabled. | | + | |Es ist berichtet worden, dass nach einem Rundenende ein Lag kommt. Es soll am Multithreading liegen. Sobald die Affinität des Servers auf eine CPU mit taskset gesetzt wird, soll es nicht zu diesen Lags kommen. | |
^mp_autoteambalance 0 ^ | ^mp_autoteambalance 0 ^ | ||
- | |If you start a server with mp_autoteambalance 0, bots will not join and you will get an error that says the game is full when you try to add them. Also only 1 person can join per team. If a 3rd player trys to join a team they get a team is full message for both teams when trying to join. Just started after the May 21st update. | | + | |Wenn mp_autoteambalance 0 gesetzt wird, joinen die Bots nicht. Man bekommt die Fehlermeldung, dass das Spiel voll ist, wenn man Bots hinzufügen will. Es kann auch nur eine Person pro Team joinen. Wenn ein dritter Spieler versucht zu joinen, bekommt er die Meldunge, dass das Team voll ist. | |
^Hidden cvars ^ | ^Hidden cvars ^ | ||
- | |Some cvars are hidden when they shouldnt be:\\ servercfgfile\\ mp_timelimit\\ retry | | + | |Verschiedenen Cvars sind versteckt. Z.B:\\ servercfgfile\\ mp_timelimit\\ retry | |
^Arms Race Kill Values ^ | ^Arms Race Kill Values ^ | ||
|I changed all of my weapon progression values from 1 to 2 and it caused players to not be able to join the game including bots. Only 1 bot could join, when I tried adding more it said that the server was full. Bot mode was on full. After changing it back to one, everything worked. | | |I changed all of my weapon progression values from 1 to 2 and it caused players to not be able to join the game including bots. Only 1 bot could join, when I tried adding more it said that the server was full. Bot mode was on full. After changing it back to one, everything worked. | |