** Bug Posting Guidelines **

Is there something that doesn't work right in the latest ZDoom? Post about it here.

Moderator: Developers

Forum rules
Please, if you can include a wad demonstrating the problem, do so. Bug reports that include fully-constructed demos have a much better chance of being investigated in a timely manner than those that don't.

** Bug Posting Guidelines **

Postby Mr. Tee » Wed May 19, 2004 3:18 pm

===============================================

1. The title shouldn't just say "Bug" or "Crash", it should take the form of:
[ZDoom_Version] Effect : Possible_Cause


Here are some examples:
[2.1.3] Bug : Backpack messes up items
[2.1.1] Crash : Decorate actors using A_Custom Missle
[2.1.0] Total Lockup : Dividing by zero in ACS scripts

===============================================

2. Do not copy&paste the crash log's contents in your post. Please attach the unaltered 'CrashReport.zip' that is saved.

===============================================

3. If your bug requires some kind of further explanation, please put this before the crash log.

===============================================

4. Only post bugs for ZDoom, i.e. not Skulltag, ZDoomGL, GZDoom or anything else.
(submitted by Randy and Graf)

===============================================

5. If you need to report something not working properly, use the Bugs forum. Do not send private messages to the developers! There is a high probability that such reports just get ignored without being investigated.

===============================================

6. Don't post bug reports for any version older than 2.4.0 (such as 2.3.1, 2.0.99x, 1.22) These versions are old and won't be updated anymore. If you encounter a problem with these versions please verify first with a more recent version that the problem still exists. If the bug happens with the latest official version, check with a recent unofficial SVN build if it happens as well. No need to report a bug that's already been reported and fixed.


==============================================

7. If you experience a crash with a custom WAD please post a link to a download location for that WAD if possible.

===============================================

8. If you post a bug for a self-compiled SVN version, please try to gather some information in the debugger yourself. Since you are able to compile it you should have access to one. Crash logs for such builds are of no use.

===============================================

9: If you need to attach something to check the bug (such as a test mod, demo, save, etc.), then DO NOT use a non-permanent host like Rapidshare, MediaFire, or similar. If the file is small enough, zip it and attach it. Otherwise, host it on your own webspace or on the DRD Team files service. Often bugs can't be examined right away. However, if by the time the bug is being examined the attachment is gone there is no way to address the issue and the report will be closed without any action taken as a result.
Last edited by Mr. Tee on Mon Jan 11, 2010 5:00 pm, edited 40 times in total.
User avatar
Mr. Tee
Finished ZDoom Editing Demo, yep, it was that hard.
 
Joined: 08 Feb 2004
Location: On the other end of the water pistol.

Postby Graf Zahl » Wed May 19, 2004 3:24 pm

These are some really useful guidelines which should be stuck in a sticky thread at the top of the bugs forum. I think this is a response to the latest useless bug report from today, right?
User avatar
Graf Zahl
 
Joined: 19 Jul 2003
Location: Germany

Postby Vaecrius » Wed May 19, 2004 3:51 pm

Sounds good to me, although I'd put the version number first to make it easier to sort out old vs new bugs in a search...
User avatar
Vaecrius
Team Bad Allocation, blast off at the speed of light!
 
Joined: 04 Jan 2004
Location: Gotham City Special Administrative Region, Wyld-Lands of the Lotus People, Soviet Canuckistan

Postby Csonicgo » Wed May 19, 2004 5:59 pm

Graf Zahl wrote:These are some really useful guidelines which should be stuck in a sticky thread at the top of the bugs forum. I think this is a response to the latest useless bug report from today, right?


I was in a hurry, and it was on my mum's computer, so I couldn't stay on long after the crash.
User avatar
Csonicgo
AAAAAAA
 
Joined: 15 Apr 2004
Location: Leeds

Postby QBasicer » Thu May 20, 2004 5:30 am

Why limit it just to ZDoom information? What about system? Windows Version? Processor? Ram? Sound card? Video?

It all effects the way ZDoom runs.
User avatar
QBasicer
#include <QBasicer.h>
 
Joined: 16 Sep 2003

Postby Graf Zahl » Thu May 20, 2004 5:46 am

It depends on the bug whether this is necessary. For obvious gameplay bugs this really isn't necessary. For crashes it should be included, though.
User avatar
Graf Zahl
 
Joined: 19 Jul 2003
Location: Germany

Postby Lexus Alyus » Thu May 20, 2004 6:20 am

If you just use the basic title suggestion that Mr Tee suggested and then, if it's relevent, stick the OS, computer specs, etc... in the actual post. This would keep the title reletively short, yet still important, and any additional information is contained within the post.

Good work Mr Tee :).

:twisted:
User avatar
Lexus Alyus
I may be back...
 
Joined: 15 Jul 2003
Location: Nottingham, UK

Postby Xaser » Thu May 20, 2004 5:23 pm

Go Mr. Tee! I hope this helps out alot!

Heh. I never knew a Cajun Bot could be so helpful (no offense). :P
User avatar
Xaser
.ɔıɥɔʎsd.
 
Joined: 20 Jul 2003
Location: .plɹoʍɹǝʌǝu.

Postby Bouncy » Sun May 23, 2004 8:44 pm

This is EXACTLY what the Bugs forum needed. I waited for something like this...
User avatar
Bouncy
HERESY
 
Joined: 24 Aug 2003
Location: Forbidden Forest

Postby Giest118 » Thu Jul 15, 2004 1:06 pm

Perhaps another guideline should be posted saying that you should probably attempt to reproduce that crash/bug before posting it... 'cause if you can't reproduce it, then it's probably just a one-time thing that you'll never see again.
User avatar
Giest118
I don't trust people who trust me. Because they're stoned.
 
Joined: 05 Dec 2003

Postby Graf Zahl » Thu Jul 15, 2004 1:09 pm

No. Even one time crashes may point Randy to a potential problem.

I once had a strange crash in one of my programs which I was unable to reproduce but investigation got me to a very serious error that only rarely resulted in a crash but could also silently destroy data.
User avatar
Graf Zahl
 
Joined: 19 Jul 2003
Location: Germany

Postby Csonicgo » Tue Nov 30, 2004 10:47 pm

I get crashes every day like that.... maybe I SHOULD POST THEM.
User avatar
Csonicgo
AAAAAAA
 
Joined: 15 Apr 2004
Location: Leeds

Postby Mr. Tee » Wed Dec 29, 2004 1:48 pm

Teh new guidelines... Simpler, and closer to the style most people like to bugs in.

Happy Holidays,
Merry ZDooming!
User avatar
Mr. Tee
Finished ZDoom Editing Demo, yep, it was that hard.
 
Joined: 08 Feb 2004
Location: On the other end of the water pistol.

Postby Janizdreg » Mon Jan 24, 2005 5:56 pm

I second that the title form recommended in the first guideline should be [ZDoom_Version] Effect : Possible_Cause. Most people seem to use it already anyway.
User avatar
Janizdreg
 
Joined: 01 Jan 2004
Location: Finland

Postby doom2day » Thu Jan 19, 2006 4:02 pm

giest118 wrote:Perhaps another guideline should be posted saying that you should probably attempt to reproduce that crash/bug before posting it... 'cause if you can't reproduce it, then it's probably just a one-time thing that you'll never see again.

If someone knows how to reproduce a bug then that would be useful
User avatar
doom2day
So much to learn, so little attention span!
 
Joined: 27 Jun 2005

Next

Return to Bugs

Who is online

Users browsing this forum: Gez and 1 guest