- Mastering CryENGINE
- Sascha Gundlach Michelle K. Martin
- 151字
- 2021-07-16 12:07:26
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.
推薦閱讀
- Python GUI Programming:A Complete Reference Guide
- 計算機組裝與系統配置
- SDL Game Development
- 數字道路技術架構與建設指南
- Getting Started with Qt 5
- 3ds Max Speed Modeling for 3D Artists
- Unity 5.x Game Development Blueprints
- 超大流量分布式系統架構解決方案:人人都是架構師2.0
- 單片機開發與典型工程項目實例詳解
- LPC1100系列處理器原理及應用
- FL Studio Cookbook
- Intel FPGA權威設計指南:基于Quartus Prime Pro 19集成開發環境
- Angular 6 by Example
- Arduino項目案例:游戲開發
- ActionScript Graphing Cookbook