General Category > AVWW Multiplayer Discussion
Server: Wandering Nomads (Closed for now)
keith.lamothe:
The black screen issue appears to be mostly resolved in 0.930, you just have to wait about a minute for it to finally "get through" with the "dump me on the world map" message. I've put a change in for 0.931 to make that more prompt.
Are there any more errors in the server logs since 0.930? If so it might shed some light on the original invalid-chunk issue. If not, that original issue may no longer happen and the black-screen thing is just inherited for those players it's affecting, but it should go away permanently once you finally do get to the world map.
Let me know if there are other problems :)
Wanderer:
--- Quote from: keith.lamothe on April 17, 2012, 09:28:29 pm ---The black screen issue appears to be mostly resolved in 0.930, you just have to wait about a minute for it to finally "get through" with the "dump me on the world map" message. I've put a change in for 0.931 to make that more prompt.
Are there any more errors in the server logs since 0.930? If so it might shed some light on the original invalid-chunk issue. If not, that original issue may no longer happen and the black-screen thing is just inherited for those players it's affecting, but it should go away permanently once you finally do get to the world map.
Let me know if there are other problems :)
--- End quote ---
Yeah, I've got firebats and icebats whining about getting shifted around. This is still 0.930, I just walked in the door and hit the forums. A queued abilityuse.execute rejection... A process assertion failure... daaaamn. Ya know, I'm just gonna attach it here.
Wanderer:
Server upgraded to .931.
keith.lamothe:
Thanks for the log :) I just started at the first 4/17/2012 entry.
--- Quote from: Wanderer on April 18, 2012, 12:11:35 am ---Yeah, I've got firebats and icebats whining about getting shifted around.
--- End quote ---
Not a big deal, though perhaps we could suppress those from being logged.
--- Quote ---A queued abilityuse.execute rejection...
--- End quote ---
Yea, those sometimes happen, though it shouldn't really be happening as much anymore since we made it hang on to entities (in an invisible, non-interactive state) for the rest of the ability messages applying to it to "clear through". So not sure what's going on there, unless they all apply to players that have transitioned to another chunk normally (those don't "stick around" as it'd be kinda bad for an entity to be in two chunks at once). Anyway, these particular rejections (projectiles exploding, adding just-entered-chunk-invincibility, etc) shouldn't hurt anything.
--- Quote ---A process assertion failure...
--- End quote ---
Those are more serious; particularly:
--- Quote ---ProcessAssertionFailure while IsInAbilityDeserializationOrProcessing, Message:Object reference not set to an instance of an object
at Chunk.PerformChunkLoadInitialization (Boolean IsFromTheNetwork, Int32 LoadedChunkVersion) [0x00000] in <filename unknown>:0
--- End quote ---
I'm guessing that this was from when Chomper was connecting, and it was trying to process whatever messed up hunk of chunk he'd gotten stuck in, and something that should never be null was null. I've put in an extra check towards the top of the method but that's a pretty big one. *shakes fist at Unity for making it impossible to have a release build with enough debug info in it to give line numbers in stack traces* That may be my biggest complaint; in the .NET/slimdx engine AIW was running on through version 3.189, I could always get line numbers from release-build stack traces.
Anyway, looks pretty clean, if that null one was indeed just a legacy of whatever grue ate Chomper and Hyrf a couple versions back.
Thanks :)
tigersfan:
--- Quote from: keith.lamothe on April 18, 2012, 10:26:48 am ---... if that null one was indeed just a legacy of whatever grue ate Chomper and Hyrf a couple versions back.
--- End quote ---
Great reference! :)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version