Qa Riverbank, crashes clients
Posted: Thu Aug 07, 2014 2:59 pm
Be warned, avoid Qa Riverbank Something is wrong there, which prevents the client from entering the world. Attached is my (extended) VGClient.log, hoping other brilliant analysts can take a look to see if it spells out exactly what is crashing.
This is my first error:
This is my client dying:
Volt and I discovered I can fix it by dropping all the spawns in Qa Riverbank, but I'd like to leave this error in place in case it's not just spawns, but something wrong with our Unreal bitwriter. Not sure if hooking a collector to New Telon will tell us anything else.
Are there any other extended loggings I can turn on in this client?
PS: I did zone over INTO Qa Riverbank, stood there for a few seconds with a red ping bar and the client just closed.
Edit: Oh, I just remember what was probably causing this... Xinux's report of bad draw_scale size.
So this becomes a server bug, that if the draw_size is ridiculous, let's not send the spawn.
Fixed with:
This is my first error:
Code: Select all
2014-08-07 14:49:24 1407448126 944 2 5254462750 Error: (Karma): KInitActorDynamics: No Model.2014-08-07 14:49:25 1407448126 961 2 5254463779 Error: Unable to serialize Class Core.Class static object because Ar.IsError, Index is 4986, from 2014-08-07 14:49:25 1407448126 962 2 5254463779 Error: NetSerializeItem failed for PawnClass (PlayerController2)! Element = 0This is my client dying:
Code: Select all
2014-08-07 14:49:29 1407448126 1277 2 5254467179 Critical: HandleStream2014-08-07 14:49:29 1407448126 1278 2 5254467179 Critical: HandleStream2014-08-07 14:49:29 1407448126 1279 2 5254467179 Critical: UActorChannel::ReceivedBunch2014-08-07 14:49:29 1407448126 1280 2 5254467179 Critical: UActorChannel::ReceivedBunch2014-08-07 14:49:29 1407448126 1281 2 5254467179 Critical: (Actor SGONPCPawn0)2014-08-07 14:49:29 1407448126 1282 2 5254467179 Critical: (Actor SGONPCPawn0)2014-08-07 14:49:29 1407448126 1283 2 5254467179 Critical: UChannel::ReceivedSequencedBunch2014-08-07 14:49:29 1407448126 1284 2 5254467179 Critical: UChannel::ReceivedSequencedBunch2014-08-07 14:49:29 1407448126 1285 2 5254467179 Critical: Direct2014-08-07 14:49:29 1407448126 1286 2 5254467179 Critical: Direct2014-08-07 14:49:29 1407448126 1287 2 5254467179 Critical: UChannel::ReceivedRawBunch2014-08-07 14:49:29 1407448126 1288 2 5254467179 Critical: UChannel::ReceivedRawBunch2014-08-07 14:49:29 1407448126 1289 2 5254467179 Critical: UNetConnection::ReceivedRawPacket2014-08-07 14:49:29 1407448126 1290 2 5254467179 Critical: UNetConnection::ReceivedRawPacket2014-08-07 14:49:29 1407448126 1291 2 5254467179 Critical: (From IP , Count=22)2014-08-07 14:49:29 1407448126 1292 2 5254467179 Critical: (From IP , Count=22)Are there any other extended loggings I can turn on in this client?
PS: I did zone over INTO Qa Riverbank, stood there for a few seconds with a red ping bar and the client just closed.
Edit: Oh, I just remember what was probably causing this... Xinux's report of bad draw_scale size.
So this becomes a server bug, that if the draw_size is ridiculous, let's not send the spawn.
Fixed with:
Code: Select all
UPDATE `spawn` SET `draw_scale`='1' WHERE `id`='930058';
UPDATE `spawn` SET `draw_scale`='1' WHERE `id`='930059';