PDA

View Full Version : [Brainport] Crash/Bug submission



Carinth
04-12-03, 22:22
Somehow kk is not receiving any info from the players about the rampant crashes. I believe this is because of how Neocron works currently. When you fatal, it creates the callstack.log which is what you're supposed to mail to the apropraite email address. Yet when most players fatal, they were in the middle of doing something and they are going to immediatly log back in. The log sits there until we crash again and it's overwritten. Couldn't we find a way to streamline this? Maybe a small app that extracts the log and mails it to kk. When you crash, you run the app and return to neocron. This may seem like we're being lazy, but I'm pretty sure most of us would be more inclined to just double click a program rather then open up our email and submit a crash report. At the very least you would have proof to backup your claims that Neocron is relatively crash free. Even better you'd find that there really is a problem and fix it before you introduce the new players to Neocron.

My other beef is with Bug submission. There are 3 ways to report a bug, that I know of. There is an ingame interface, the web forum here, and happening to find a GM/KK employee and telling them. The third method is the most likely to actualy get something done about it and also the rares to happen. The forum bugtracker is a black hole, you report bugs and others might agree with you. Then nothing comes of it. Your post gathers dust until It's replaced by somene new posting the same bug. The ingame bugtacker I've only tried a few times, there is even less feedback there. If your bug is major enough you can also mail kk directly, you might get some response or might not. I know of people who have submitted hacks and exploits multiple times and nothing has changed.

We need one absolute method of reporting bugs, not several with varrying results. There also need to be feedback, even if it's a simple (we already know about this bug or thank you for submitting a new bug, we will look into it). Bugs are of course prioritized based on how game breaking they are, so your bugs may not appear in patch notes anytime soon... but you know kk is aware of it. It's really suprising how often bugs we think of as well known or common, actualy aren't known by kk.

I feel there is a real miscommunication going on here between kk and the players. If we are given an easy way to report problems, then we can give kk proof that we're having problems. Currently problem reporting is rather ambiguous, what exactly are you supposed to do, where do you do it at, etc. It also involves some work on the player's part, which most aren't willing to spend. So why not improve the system and make it easy to submit problems.

OpTi
04-12-03, 22:40
i'd much rather do that cuz i woud have already made about 6 email already today

Spy<VS>Spy
04-12-03, 23:03
Uh...look, i might hate KK...but not enough to punish their ISP tech staff by stuffing their mail server untill it pukes every hour on the hour to cause mass choas and over time for maintness crew.

maybe i'll start saving mine, and wrap them in a zip file for KK, and when they open it, jingle bells starts playing. We wish you a merry Crash-mas, we wish you a merry Crash-mas, and a happy Re-boot.

redjacket
04-12-03, 23:08
There was supposed to be some program that was supposed to allow you to easily submit the callstack thingy if you crash, it like runs in the background and starts NC, if it dies a pop-up comes up selling you porn or telling you that pop-ups are bad... then it asks if you wanna send the callstackedhooters.loginthepants file... then it auto-downloads an advanced form of Blaster worm that forces you to download goatse pictures and sets them as your desktop...

i dunno where it is or if it was ever finished... i blame dead people tho... not sure why... maybe it has something to do with the...

OMG! Peek-A-Boo! Silly peen!

Wilco
04-12-03, 23:44
I have "Callstack1.log" to "Callstack4.log" here. All where from yesterday, but they're all empty (and i got some FREs yesterday).
Ich move my "Error.log" into a different directory (as well as console.log) at NC-startup, and i get lots of errors there (mainly the same all over and over again) like the following:

Encountered since the last patch (192):
@WRefCnt < 0, Resource Name gfx\stdparticle.bmp [many errors]
@WACTOROBJECT : Index not Found, Index: 46, Section: 1
@WACTOROBJECT : Index not Found, Index: 45, Section: 1
@WACTOROBJECT : Index not Found, Index: 44, Section: 1
@WSOUNDRSCMGR: Get Ref Failed : Index not found I:0 S:4 [massively many errors)]
@WSOUNDMGR : Sound File Open failed:sound\weapon_sfx\psi\master_fire\typ1.wav [many errors]
@WSOUNDMGR : Sound File Open failed:sound\enemies\mutantfly\idle1.wav
@WACTOROBJECT : Index for Anims not Found, Index: 100020, Section: 1
Exception created World Load failed
@WWORLDMGR : Editorobject spawn failed: World Load failed
VEHICLE : Sit for Update not found: 1 [many errors]
@WTEXTRSCMGR: Get Ref Failed : Index not found I:1107 S:5
@WSOUNDMGR : Sound File Open failed:sound\enemies\cavecreaper sm\idle2.wav
@WSOUNDMGR : Sound File Open failed:sound\enemies\cavecreaper sm\idle1.wav
@WSOUNDMGR : Sound File Open failed:sound\enemies\cavecreaper\idle1.wav
@WSOUNDMGR : Sound File Open failed:sound\enemies\cavecreaper\idle2.wav
@WRefCnt < 0, Resource Name gfx\decals\pistoldecal.bmp

On one occasion lots of those (different types, different sizes)
@WWORLDMGR : Corrupted Message Type:246, Size:19
@WWORLDMGR : Corrupted Message Type:54, Size:20
@WWORLDMGR : Corrupted Message Type:8, Size:20
@WWORLDMGR : Corrupted Message Type:76, Size:22
@WWORLDMGR : Unable to Spawn WA: 3
@WWORLDMGR : Corrupted Message Type:246, Size:47
LSTPLAYER : Update Message corrupted Size:30 3

On another occasion i got HALF A MEG of a log with almost only this line:
@WTEXTRSCMGR: Get Ref Failed : Index not found I:76 S:3

That's also a nice one:
<statement> expected;
last token read: `*' at line 9 in string "?"
attempt to call global `DIALOG' (a nil value) [occured twice since patch]

Also those at program end (on different occasions):
@WResource still referenced on program exit, 12 refs, Resource Name gfx\grascol02.bmp
@WResource still referenced on program exit, 1 refs, Resource Name gfx\grascol02.bmp
@WResource still referenced on program exit, 2 refs, Resource Name gfx\grascol02.bmp
@WResource still referenced on program exit, 2 refs, Resource Name gfx\rpos\rpos1.bmp
@WResource still referenced on program exit, 2 refs, Resource Name gfx\misc\crosshair_a2.bmp
@WResource still referenced on program exit, 1 refs, Resource Name .\models\objects\bush2.act
@WResource still referenced on program exit, 1 refs, Resource Name .\models\objects\wuestenkraut.act
@WResource still referenced on program exit, 21 refs, Resource Name .\models\objects\wuestenkraut_big.act
@WResource still referenced on program exit, 1 refs, Resource Name .\models\objects\gebuesch_trn.act
@WResource still referenced on program exit, 1 refs, Resource Name .\models\objects\schilf.act
@WResource still referenced on program exit, 1 refs, Resource Name .\models\objects\algeA.act
@WResource still referenced on program exit, 50 refs, Resource Name .\models\objects\bushleafs.act
@WResource still referenced on program exit, 6 refs, Resource Name .\models\objects\blattgewaechs1-B.act
@WResource still referenced on program exit, 21 refs, Resource Name .\models\small_stone_1.act
@WResource still referenced on program exit, 1 refs, Resource Name .\models\objects\strauchB.act
@WResource still referenced on program exit, 5 refs, Resource Name sound\amb\singles\hum\cityhum3.wav
@WResource still referenced on program exit, 4 refs, Resource Name sound\amb\singles\hum\lighthum.wav
@WResource still referenced on program exit, 28 refs, Resource Name .\models\objects\EasyChair_B.act

Regards, Wilco

Carinth
05-12-03, 01:56
We have been told that if we crash, we should submit crash logs. When their email server dives due to all the mail, maybe they will realize the game is not "fine."

I recall something like that too, now that you mention it redjacket. I'll do some digging and see if it's still around.

Bummer, looks like this idea has been brought up several times before. Someone did make an app, they called NeoCrash. I don't see any links though, looks like it flopped.

http://neocron.jafc.de/showthread.php?s=&threadid=53624&perpage=15