Re: ** Bug Posting Guidelines **

Sun Feb 21, 2010 7:34 am

Mr. Tee wrote:2. Put crash logs in CODE tags, but don't use spoiler tags.
(submitted by Randy the ZDoom God)


I suggest that this particular rule may be a bit out of date/ misleading.

In order to post a crash log between CODE tags, the person posting it will have opened up the crashreport.zip file, opened up report.txt from the zip and copied/pasted the contents in to the forum. In doing so, they have probably also not included local.txt and minidump.mdmp from the zip file and are therefore not including all the information that they can.

Surely, it is just better to post the crashreport.zip file unaltered unless there is a good reason not to (eg I think that perhaps guests can't post attachments)?

Re: ** Bug Posting Guidelines **

Sun Feb 21, 2010 7:39 am

Changed that line.

Re: ** Bug Posting Guidelines **

Sun Mar 28, 2010 6:31 am

Another guideline I'd suggest: include a startup log (explanations for creating one are here).

Re: ** Bug Posting Guidelines **

Sat May 28, 2011 3:12 pm

just wondering, do the features and bug fixes also get applied to gzdoom?

Re: ** Bug Posting Guidelines **

Sat May 28, 2011 3:41 pm

mancubus wrote:just wondering, do the features and bug fixes also get applied to gzdoom?
Yes. It's synchronized with ZDoom quite frequently.

Re: ** Bug Posting Guidelines **

Sat Jun 16, 2012 3:29 pm

Yes. It's synchronized with ZDoom quite frequently.


Is that mean, that I can post here a bug concerning GZDoom or older versions of ZDoom? There is an elevator glitch coming up in almost every version of ZDoom (except for the most recent development versions) or ZDoom based source ports. Can I post it somewhere here or not? Because the fourth rule says it is not allowed to post such bugs here.

Re: ** Bug Posting Guidelines **

Sat Jun 16, 2012 3:34 pm

If it's fixed in the most recent versions there's no need to post it. We can't fix it twice.

Re: ** Bug Posting Guidelines **

Thu Dec 12, 2013 2:50 pm

How much of the new version number is requested for bug posting?

Re: ** Bug Posting Guidelines **

Tue Jan 27, 2015 11:23 am

As a quick pseudo-bump, here's an item that IMO ought to deserve its own big-text header:

#. Bug reports for GZDoom should be posted on the GZDoom forums. GZDoom bug reports posted here are likely to be closed without investigation.

Item #4 doesn't cover this adequately; it's much less clear that ZDoom & GZDoom are separately maintained entities versus, say, ZDoom & Zandronum,

Re: ** Bug Posting Guidelines **

Tue Jan 27, 2015 4:32 pm

I'm surprised it wasn't already. No wonder the reports keep getting posted here. Honestly that should also be noted for feature requests as well. People seem to think that because GZDooms feature request forum is closed, that it's an excuse to post them here.

Re: ** Bug Posting Guidelines **

Thu Jan 29, 2015 3:37 pm

edward850 wrote:People seem to think that because GZDooms feature request forum is closed, that it's an excuse to post them here.
Considering there's a new renderer in, I don't know for sure why it hasn't been reopened.

Re: ** Bug Posting Guidelines **

Fri Jan 30, 2015 2:18 am

To see it end up like ZDoom's feature requests forum?

No, thank you!
I barely have time to work on the engine, if you can find me another dev to help out, things might change.

Re: ** Bug Posting Guidelines **

Fri Jan 30, 2015 11:52 am

NeuralStunner wrote:Considering there's a new renderer in, I don't know for sure why it hasn't been reopened.


New renderer in? What do you mean?

EDIT: Oh, wait I see now, the difference between OpenGL 2 and 3. Nevermind.

Re: ** Bug Posting Guidelines **

Mon Jul 25, 2016 9:05 pm

I think it's worth noting that users should specify whether their bugs happen with the 32 bit or the 64 bit executables. There have been more than one case where the reporter insists that the bug still persists yet a dev says the bug does not happen... after a lot of exchange, it turns out that the dev does not experience the bug because he was only testing on an x64 build.