Hello,
Since the update of 28 april there is a bug into CSGO server.
Players are kicked of the server with the reason: "#GameUI_Disconnect_DeltaEntMessage" when there is more thens 1450 edicts in the game.
L 05/04/2015 - 19:31:43: "+_"brilliant sailor"_=<227><STEAM_1:0:83880768><>" entered the game
L 05/04/2015 - 19:31:44: "+_"brilliant sailor"_=<227><STEAM_1:0:83880768>" switched from team <TERRORIST> to <Unassigned>
L 05/04/2015 - 19:31:44: "+_"brilliant sailor"_=<227><STEAM_1:0:83880768><TERRORIST>" disconnected (reason "#GameUI_Disconnect_DeltaEntMessage")
L 05/27/2015 - 17:42:55: "Je suis une roux,<2><STEAM_1:0:22062638><>" entered the game
L 05/27/2015 - 17:42:55: "Je suis une roux,<2><STEAM_1:0:22062638><Unassigned>" disconnected (reason "#GameUI_Disconnect_DeltaEntMessage")
I've tried without addon, so you can easily reproduce the bug using prop_dynamic_create command. No player can join as long as there is 1450 edict or more.
Sadly, the lastest update did not solve this issue.
Can you please forward this to the dev team?
Thank you for your care,
Steve.
#GameUI_Disconnect_DeltaEntMessage
Since the update of 28 april there is a bug into CSGO server.
Players are kicked of the server with the reason: "#GameUI_Disconnect_DeltaEntMessage" when there is more thens 1450 edicts in the game.
L 05/04/2015 - 19:31:43: "+_"brilliant sailor"_=<227><STEAM_1:0:83880768><>" entered the game
L 05/04/2015 - 19:31:44: "+_"brilliant sailor"_=<227><STEAM_1:0:83880768>" switched from team <TERRORIST> to <Unassigned>
L 05/04/2015 - 19:31:44: "+_"brilliant sailor"_=<227><STEAM_1:0:83880768><TERRORIST>" disconnected (reason "#GameUI_Disconnect_DeltaEntMessage")
L 05/27/2015 - 17:42:55: "Je suis une roux,<2><STEAM_1:0:22062638><>" entered the game
L 05/27/2015 - 17:42:55: "Je suis une roux,<2><STEAM_1:0:22062638><Unassigned>" disconnected (reason "#GameUI_Disconnect_DeltaEntMessage")
I've tried without addon, so you can easily reproduce the bug using prop_dynamic_create command. No player can join as long as there is 1450 edict or more.
Sadly, the lastest update did not solve this issue.
Can you please forward this to the dev team?
Thank you for your care,
Steve.
0 commentaires:
Enregistrer un commentaire