Announcement

Collapse
No announcement yet.

How to report an error message

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • How to report an error message

    Maybe I can make everyone's lives a little easier by making an easy to follow guide on how to report a problem. Just saying "This map crashes my quake" doesn't help us much to solve your problem. So be more specific. Follow these steps:
    1. Write down what the error does.
    2. Write down how you got the error. This is helpful for us attempting to recreate the error.
    3. Write down what quake client and version you were using
    4. Let us know if you were running a mod or custom sounds/textures/etc
    5. Show a screen shot
    6. If the error involves a crash, try to recreate the error after typing developer 1000* and writing out to a file**
    7. Any information about your hardware would be helpful as well***
    8. If it's a connectivity problem, write down your router, firewall, and anti virus information.


    The rest of the quake community will have an easier time helping you if you take the time to fill in all these steps.


    * Add this line into your autoexec.cfg file in the id1 folder (or mod folder if necessary). If you don't have an autoexec.cfg file, create one.
    Code:
    developer 1000;
    ** Add this option in the command to run quake
    Code:
    quakeengine -condebug
    Here's an example:



    When you use -condebug, it will write all the messages a developer needs in order to figure out the bug. You will find it in the id1 folder under the name 'qconsole.log'. It will be in the mod folder if you were using a mod.

    *** You can easily get this information by right clicking 'My Computer' and selecting 'Properties' on the drop down menu. You should see something like this:

    Last edited by Canadian*Sniper; 10-28-2007, 03:24 PM.

  • #2
    Thanks though i don't know how helpful the results are that it showed.

    It's like an overflow, at a guess....

    i'll post the log into the thing though. (forgot that command) as i did check for a .log file b4 but couldn't find one haha (forgot u needed that -condebug line in your cmd arguments before you started quake. (didn't know about the developer 100) line though.

    thanks.

    Comment


    • #3
      I changed developer 100 to 1000

      Comment


      • #4
        Is there a difference?

        I mean is developer 100 (100 being a vector range of 100?) thus array?

        Or is it nothing but a (special) something that nobody understands....

        Why pass it a 1000? (extra zero?)

        Curious... an not sure, and *nuzz* he -(void)-

        Comment


        • #5
          more info?

          Comment


          • #6
            I thought developer was just a true/false cvar.

            developer (0/1)

            The developer cvar is either on or off, 1000 vs 100 doesn't effect it.

            Comment


            • #7
              It affects darkplaces. Could be different for other engines as well.

              edit:

              in any case, any value that's not 0 will still count as 1 on proquake and any other engine that's 0 or 1 right?
              Last edited by Canadian*Sniper; 10-29-2007, 02:07 PM.

              Comment


              • #8
                correct

                Comment

                Working...
                X