- 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.
推薦閱讀
- Arduino入門基礎(chǔ)教程
- 圖解西門子S7-200系列PLC入門
- Cortex-M3 + μC/OS-II嵌入式系統(tǒng)開發(fā)入門與應(yīng)用
- ATmega16單片機項目驅(qū)動教程
- 新型電腦主板關(guān)鍵電路維修圖冊
- 辦公通信設(shè)備維修
- 精選單片機設(shè)計與制作30例(第2版)
- 電腦常見故障現(xiàn)場處理
- 嵌入式系統(tǒng)設(shè)計教程
- VCD、DVD原理與維修
- 固態(tài)存儲:原理、架構(gòu)與數(shù)據(jù)安全
- 筆記本電腦維修實踐教程
- 無蘋果不生活:OS X Mountain Lion 隨身寶典
- STM32自學(xué)筆記
- 筆記本電腦維修技能實訓(xùn)