Articles in this section

Early access: bug report Template

Avatar
Gary Campbell
  • Updated
Follow

First, we would like to thanks Comrademoco for the thread that he made on our forums:

https://board.dualthegame.com/index.php?/topic/11790-guide-to-posting-proper-bug-reports/

 

He has set a complete guideline for bug reporting. You do not have to follow it entirely each time you want to submit a request, of course. However, if you're not sure about how to form your report, you might want to take a look at it.

 

We are reposting his template here, with some adjustments of our own. It's up to you if you want to follow them or not :)

See you soon in Dual Universe!

 

 

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -


BUG TYPE CATEGORIES

 
Please note that you can choose the Category of your issue while reporting a bug in the drop-down list.
 
  • Gameplay - Any bug related to a core feature of the game (Tools, Piloting)
  • Character - Any bug pertaining to the Character Avatar itself
  • Character Creator - Any bug related to the character creator
  • Animation - Animation is any type of Bug related to animations done by character or contrstruct
  • Audio - Audio is any type of Bug related to audio such as music, sound, or voiceover work
  • UI - UI is any type of Bug related to the User Interface, missing icons or nonfunctional buttons
  • Environment - Any bug related to a biome or terrain you come across
  • Elements & Items - Bugs Related to Elements themselves (cockpits, TCUs, Thrusters etc) or to items found on your inventory (Materials, Ores etc)
  • Constructs - Any bug related to a construct or its behaviour
  • Performance - Bugs related to Performance issues with Dual Universe in game (thrust power, gravity etc)
  • Technical - Bugs related to the Technical side of Dual Universe (Crashes, Frame Drops, Memory Leaks etc)
  • Voxel - Bugs related to the voxel aspect of Dual Universe (Tools, Construct Building, Sculpting) 
  • LUA - Bugs related to the LUA aspect of Dual Universe (scripting)
  • RDMS - Bugs related to the RDMS of Dual Universe (Permissions, Legate status etc)
  • Forum - Bugs related to the Forum (rss feeds, cant post replies etc)
  • Community Page - Bugs related to the Community Page (org creation, info updating etc)
  • Support Page - Bugs related to the Support Page (summit reports, missing reports etc)

 

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 

BUG REPORT OUTLINE

 

Topic/Thread Title: [Category] - Issue Title (This is the title on you put on the Thread)

Issue (Title of the Issue)

Client Version: (client version the bug was found on)

Summary (Quick summary of what the bug/issue is
 
Reproduction Steps (self explanitory - ALL steps taken that leads to the bug)
  • Step
  • Step
  • Step
  • Step
  • Step
     
Actual Result
(result from taking the steps above that leads to the bug)
 
Expected Result
(result which you think should be expected when there is no bug)
 
Forum Posts
(if there's any other forum posts on this subject, link them here)
 
Notes
(any notes you'd like to include here that may help NQ)
 
Crash Dumps
(Default Path: "c:/Users/you/AppData/Local/NQ/DualUniverse/CrashDumps"
Note: because crash dump files can vary in size, it is recommended you use the Costumer Support Page if there is a crash dump file
 
Screenshots/Videos
(any screenshots or videos that showcase the bug/issue)
 
System Specs (always include your system specs when reporting bugs).
You can also send your DxDiag directly; instructions below:

If you are running Windows 7 or higher:

  1. Go to your Taskbar.
  2. Click on, "Start Button".
  3. Click on, "Run".
  4. In the pop-up window enter DxDiag and hit ok.
  5. The DirectX Diagnostic Tool pop-up window should appear.
  6. Click on, "Save all information".
  7. "Save As" window should be present.
  8. Click on, "Save" (The file should be saved to your desktop as DxDiag.txt)
  9. Exit the DirectX Diagnostic Tool.

If you are running Windows 10:

  1. Click Start.
  2. Type DxDiag and press enter.
  3. The DirectX Diagnostic Tool pop-up window should appear.
  4. Click on, "Save all information".
  5. "Save As" window should be present.
  6. Click on, "Save" (The file should be saved to your desktop as DxDiag.txt)
  7. Exit the DirectX Diagnostic Tool.

Then, add DxDiag.txt as an attachment to this ticket.

 

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 

EXAMPLE BUG REPORT

 

Topic/Thread Title: [Technical] - Application Error (0xc0000142)

 

Category: Technical (if not inquired in the bug-type drop-down list)
Issue: Application Error (0xc0000142)
Client Version: September 2017 0.6.28 (ATV pre-alpha)
Summary: Application Error when trying to start the client
 
Reproduction Steps
  • Download and Install game
  • Click on Start Game
  • Error Pops Up
  • Click Ok
  • Client redownloads the game again (infinite loop)

 

Actual Result
  • Application Error
  • Window pops up when hitting the "Start Game" button.
  • Error #: 0xc0000142

 

Expected Result
No error should show up when Starting the game if installation is successful
 
Notes
  • Ran Client as Administrator
  • Windows 7 Compatibility Mode
  • Uninstalled and Reinstalled Microsoft Visual Studio C++
  • Uninstalled and Reinstalled Client 3 times

 

Screenshots/Videos

<pending>

 

Crash Dumps
N/A

System Specs
  • Phenom II x4 B45 3.00GHz
  • 12GB DDR3 Ram
  • Samsung 850 EVO 120GB SSD
  • Radeon HD 7850 2GB
  • Windows 10 Pro 64bit