PDA

View Full Version : Bug Report Tool Issue


warlcook
08-15-2007, 01:16 AM
When I crash (often) it asks me to send the report. When ever I DO send the report, once it sends, the 'play' button never becomes active, and I have to restart Regnum.

Suggestion: Allow me to "Send" "Send Later" and "Don't Send" Crash info.. and let me collect multiple crash logs then send them in at the end of the night.

Tyr
08-15-2007, 04:34 PM
Post this kind of threads in the forum that it should belong in.

What? If you read his post again he is reporting a problem. The problem being when he sends in a crash report the play button remains grayed out. Just because he added a suggestion does not atomically imply that he has post this info in the wrong spot.

ByteMe
08-15-2007, 07:23 PM
I'm having the same issue with sending bug logs on a WinXP system where the play button never becomes active. If I crash during a fight or hunting, I've found that I cancel and end up not sending the reports in an attempt to hurry and reconnect.

Angelwinged_Devil
08-15-2007, 10:09 PM
there's been so many crashes lately, I won't send every one of them, I get this one too with a grayed out button though.

Wyatt
08-16-2007, 05:22 AM
yeah crashes are as bad as ever and for some annoying reason my regnum program dont generate a crash log :S

ArcticWolf
08-16-2007, 05:30 AM
yeah crashes are as bad as ever and for some annoying reason my regnum program dont generate a crash log :S

It does, you just have to post the error_bactrace files you find in the c:\program files\regnumonline\liveserver folder. :)

Wyatt
08-16-2007, 09:29 AM
Yes i know that, but i dont seem to find them no more, is like it dont even produce 1.

warlcook
08-23-2007, 02:46 PM
Just to update:

After the patch, (I crash a LOT LOT LOT less now) my first crash, I sent the log and the play button came active. I was excited, and hoped the issue was fixed. Unfortunatly my second crash, the play button once again stayed inactive. :(

I'm using XP (Pro) as well.

warlcook
09-01-2007, 03:38 AM
FYI, still having this issue.