Author Topic: Please READ before posting a BUG REPORT  (Read 5965 times)

Offline Superfly

  • Gold Member
  • *****
  • Posts: 2062
      • http://www.hitechcreations.com
Please READ before posting a BUG REPORT
« on: July 29, 2009, 09:36:16 AM »
Bug reports help make the game better for everyone, but the quality of the bug report will dictate whether or not we can do anything to correct any potential issue.

Information is key.  Remember this;  The key to fixing any software issue lies in being able to reproduce the issue on our development systems.  Without proper information it is a waste of time to try and duplicate the problem.

Example:

Hey, the game crashed, fix it!

Okay, this will simply be ignored as there is nothing there to help point us in the direction of the potential problem.

versus

I was on [terrain name], in [specific arena] performing [specific action] when the game crashed to the desktop.  I have attached the dmp file, and [optionally] the .psave file "cmepos.txt".

I'll break it down.  We almost always need the terrain name, as the problem could be terrain related. 
We need the arena name, as different arenas have different configurations. 
The dmp file is very important.  If there is one, it will be the best tool available to us for debugging a problem.  See the post for details about it in this thread.
The .psave information file "cmepos.txt" gives us your exact location on the terrain.  Also important.

Optionally, we may need the DXDIAG output from your computer.
It never hurts to provide it.  When used in conjunction with the dump file, it may point to a potential conflict with some piece of hardware we need to resolve.
« Last Edit: December 06, 2017, 09:08:38 AM by Skuzzy »
John "Superfly" Guytan
Art Director
HiTech Creations, Inc.

"My brain just totally farted" - Hitech, during a company meeting

Offline Skuzzy

  • Support Member
  • Administrator
  • *****
  • Posts: 31462
      • HiTech Creations Home Page
DXDIAG Info
« Reply #1 on: September 25, 2009, 06:51:05 AM »
Here's how to use DXDIAG to gather and post the information about your computer.

NOTEIf you do not see the "Run" option when you press the "Start" button, then right-click on the "Start" button, select "Properties", then select the "Start Menu" tab and press the "Customize..." button.  Scroll down the list to the "Run Command" and check the box next to it.

1) Go to "Start" from the Windows desktop
2) Select "Run" or place the cursor in the "Search" box.
3) In the Run or Search box, type DXDIAG and press <ENTER>
4) After a few seconds the DXDIAG utility will be ready

Now press the "Save All Information" button.  This will save all the DXDIAG information into a text file.  Post that as an attachment in your bug report post.  Do not try to embed the content as it is too large to fit into a post.
« Last Edit: December 06, 2017, 06:40:05 AM by Skuzzy »
Roy "Skuzzy" Neese
support@hitechcreations.com

Offline Skuzzy

  • Support Member
  • Administrator
  • *****
  • Posts: 31462
      • HiTech Creations Home Page
Dump (*.dmp) files
« Reply #2 on: October 31, 2016, 11:34:21 AM »
Look in the games "temp" folder, where the game is installed, and see if there are any "*.dmp" files.  Those files are created, when the game crashes and contain useful information about the cause of the crash.

Here is an example of the filename format:

ahfilm_03020F_2017_11_8_6_18_3.dmp

NOTE: You may not see the extension, depending on how you have Windows settings configured.

  • The first part is the name of the program which crashed, in this case "ahfilm". It could be "aceshigh9", "aceshigh11", "ahedit", or others.
  • Followed by the game version number in hexidecimal 03020F (Version 3.02 Patch 15) in this case.
  • Next is the date 2017_11_8_6_18_3 in YYYY_MM_D_H_M_S format.

Once you ZIP them up you can attach them to a post in the bug report forum. See "Attachments and other options" at the bottom of the forum posting edit box.
« Last Edit: December 06, 2017, 06:34:09 AM by Skuzzy »
Roy "Skuzzy" Neese
support@hitechcreations.com