Understanding issue tracking in CryENGINE

When you create reports about new issues and bugs for your project, it is important to include as much relevant information as necessary. This will make life a lot easier for the person who has to fix the issue.

A badly written bug report can cause confusion and cost additional time. When you enter new bug reports into your bug tracking system, make sure you include all the information that is relevant in order to identify and fix the issue.

Relevant information for a CryENGINE issue includes the following:

  • CryENGINE build and version number
  • System specifications (hardware, DirectX version, and so on)
  • The crash log and call stack if available
  • The level name related to the problem (if applicable)

In addition to this, the issue should also be described as accurately as possible. The more information included, the easier it will be to fix the issue.