CIT

Version 96 (rok, 12/21/2011 17:50)

1 22 alef
 
2 22 alef
3 21 alef
{{>toc}}
4 21 alef
5 72 kju
!CIT_Banner.png!
6 2 alef
7 41 kju
h1. Welcome to the Community Issue Tracker!
8 1 alef
9 38 kju
* This is a _free service_ - *please use it in respect to other volunteers free time work*.
10 82 alef
* Discuss about CIT on Bohemia Interactive Forums dedicated "thread":http://forums.bistudio.com/showthread.php?t=102991.
11 31 alef
* [[Versions]] older than the latest patch will be [[Workflow#Diagram|rejected]].
12 1 alef
13 86 alef
Since March 31th 2011, version *[[1_59|1.59]]* for *Operation Arrowhead*.
14 85 alef
Since June 23th 2011, version *[[1_10|1.10]]* for *ArmA2*.
15 1 alef
Since November 30th 2010, version *[[1_02_BAF|1.02]]* for *BAF DLC*.
16 70 kju
Since December 22th 2010, version *[[1_01_PMC|1.01]]* for *PMC DLC*.
17 40 kju
18 1 alef
h2. Why participate?
19 1 alef
20 40 kju
This is what *Bohemia Interactive* has to say:
21 35 kju
22 59 alef
> *Question*:
23 59 alef
> Have you compiled a list of fixed issues or implemented feature requests that have occurred since the community created CIT came into use?
24 59 alef
> This data would be useful to show new community members how well the CIT works or how receptive, as a studio, are to your community of users. 
25 59 alef
>
26 59 alef
> *Answer*:
27 59 alef
> We have not. However, it is fairly easy for anyone to filter issue in CIT and see how much has been addressed.
28 59 alef
> +CIT has become very important resource for us to gather feedback from our community.+
29 35 kju
30 35 kju
31 59 alef
> *Question*:
32 59 alef
> How does BIS prioritize bugfixes/features? (What are the design procedures for picking what to fix or what to include) 
33 35 kju
34 59 alef
> *Answer*:
35 59 alef
> Internally, we usually have a lot of obvious or critical issues to fix or implement.
36 59 alef
> Between those, selecting order or priorities mostly depends on available resources and also individual preference or interest.
37 59 alef
> +The CIT is often looked at, and we use Votes as good indication of how important a particular fix is for our users.+
38 35 kju
39 35 kju
40 35 kju
Reference: "Ask Bohemia about A2OA":http://community.bistudio.com/wiki/Ask_Bohemia_about_A2OA_-_Answers interview.
41 35 kju
42 35 kju
h2. How to report a crash?
43 1 alef
44 1 alef
> !WER-100.png!
45 1 alef
_a message that the game has crashed (WER)_
46 42 kju
47 42 kju
Send crash error information to BI through Microsoft with "WER":http://www.microsoft.com/whdc/winlogo/maintain/StartWER.mspx. Or follow [[WER|these instructions]].
48 43 kju
49 1 alef
* WER does *not* work with *betas patches*. For these attach the [[attachments|.mdmp and .bidmp]] files zipped to your ticket.
50 87 Fireball
* Set the *Category* field to _Game Crash_ and fill the fields:
51 40 kju
** *Maxmem parameter* (if used)
52 40 kju
** *Operating system*
53 40 kju
** *Graphics card*
54 40 kju
** *Graphics card driver version*
55 40 kju
** *CPU*
56 40 kju
** *Mainboard chipset*
57 40 kju
** *System RAM size*
58 40 kju
** *GPU VRAM size*
59 40 kju
** *Audio card*
60 40 kju
** *Size of OS swap file*
61 1 alef
* Upload as much as files described in [[attachments]].
62 1 alef
63 88 Sickboy
h3. Full Memory Dump
64 88 Sickboy
65 88 Sickboy
Sometimes it can be useful to include a full memory dump, info: http://technet.microsoft.com/en-us/sysinternals/dd996900.aspx
66 88 Sickboy
You should attach the utility to the game before the game crashes using a command line like: @procdump -e -ma arma2oa.exe crash.dmp@
67 90 Fireball
68 90 Fireball
After it crashed you can upload the crash.dmp to a free uploader service like "Multiupload":http://www.multiupload.com, preferably packed in a zip/rar/"7zip":http://www.7-zip.org.
69 88 Sickboy
70 95 Fireball
h3. Dumps on a Hung Process
71 94 Fireball
72 95 Fireball
On stuck processes you'll get a full dump automatic when the process window not responding for 5 second: @procdump -h -ma arma2oa.exe crash.dmp@
73 94 Fireball
74 95 Fireball
A mini dump will be created by running it as: @procdump -h arma2oa.exe crash.dmp@
75 94 Fireball
76 95 Fireball
If the process only appears to be hung for you, but the window/task does still basically respond, you can omit parameter @-h@ and just run it at the time you wish to take a dump.
77 94 Fireball
78 88 Sickboy
79 1 alef
h2. How to vote an issue or feature?
80 40 kju
81 40 kju
* "Browse":/projects/cis/issues the issues, pick one and click !http://dev-heaven.net/plugin_assets/redmine_vote/images/arrow_090.png! if you agree with it, !http://dev-heaven.net/plugin_assets/redmine_vote/images/arrow_270.png! if you disagree.
82 1 alef
* Have a look at the "Most Community Wanted":/projects/cis/issues?query_id=30 issues.
83 1 alef
84 1 alef
h2. How to report a bug?
85 44 kju
86 44 kju
<pre>
87 44 kju
First please use the search feature in the top right to see if you issue or suggestion was already posted.
88 40 kju
</pre>
89 40 kju
90 49 kju
* Think of a *clear* and *descriptive* ticket name first.
91 40 kju
* Be *short* and *descriptive*, use a !/images/jstoolbar/bt_ol.png! bullet point step-by-step reproducibility report in this way (use the [[Ticket_template|template]]):
92 96 rok
# *Repro*_duction steps_
93 76 kju
** Bullet point/numbered list of what one has to do to let it happen
94 75 kju
# *Obs*_erved_
95 60 alef
** Describe briefly the behavior you see
96 60 alef
# *Exp*_ected result/behavior_
97 60 alef
** Describe briefly the behavior you expect to see instead
98 60 alef
99 42 kju
* Providing a *simple demo mission* (explained by the repro steps) *improves your chances considerably* to have the issue looked at.
100 40 kju
* *For stability or performance issues* upload as much as files described in [[attachments]] and fill out all the hardware and settings fields.
101 61 alef
* New tickets: as you press "Preview", the upload files list is emptied. Please check before submitting.
102 2 alef
* Express opinions or do discussions at the "forums (BIF)":http://forums.bistudio.com and link them in the ticket.
103 45 kju
104 81 alef
*Good examples of reported issues*: #3080 #8212 #5353 #5301 #6426 #13620 #20164.
105 61 alef
106 61 alef
107 50 alef
108 40 kju
Why this format? Read some explanations from BI: "1":/issues/1745#note-45, "2":/issues/6471#note-5, "3":/issues/2551#note-21, "4":/issues/1753#note-9, "5":/issues/2755#note-9, "6":/issues/3399#note-18, "7":/issues/1704#note-10, "8":/issues/1704#change-9386, "9":/issues/1701#note-14.
109 32 kju
110 40 kju
*IMPORTANT*:
111 2 alef
* *Priority* is set +only+ by BI (if at all). It has little meaning in general.
112 30 alef
113 92 Sickboy
h3. Videos
114 91 Sickboy
115 93 Sickboy
Videos are not debugable. They provide nice evidence that the bug exists, but they do not help fixing it.
116 91 Sickboy
Instead of posting a video, please post instructions how to make one (i.e. how to see the bug) instead.
117 91 Sickboy
118 91 Sickboy
119 1 alef
h2. Details
120 30 alef
121 2 alef
h3. Beta users
122 56 kju
123 78 kju
*Latest beta patch*: OA *[[1_60_BETA|1.60 BETA]]*.
124 52 alef
125 18 alef
* Instructions on how to install can be found [[Beta|here]]
126 51 alef
* Betas for ArmA2 have been "discontinued (by Suma)":http://forums.bistudio.com/showpost.php?p=1667411&postcount=41
127 84 alef
* Please read the "BI article ("The complexity of Arma 2 has reached a nearly critical level, especially with all of the user addons and modifications, that testing of the game also requires a more agile approach and this is our attempt to address it." - Marek Spanel, 19 August 2009)":http://www.bistudio.com/index.php/english/company/developers-blog/139-arma-ii-beta-builds-released. Downloads and changelog "here":http://www.arma2.com/beta-patch.php
128 78 kju
* Specify the exact build number in the title [79600] or somewhere in the report, and use _version BETA_ as _Affected ArmA II version_.
129 78 kju
** Beta version are one number ahead: if you read 1.59.79600 in-game, that means *1.60 BETA*
130 1 alef
> !version-150.png! 
131 1 alef
_the version displays in the main screen, lower right_
132 42 kju
133 1 alef
h3. DOs and Don't DOs
134 42 kju
135 42 kju
 !/images/true.png! Do set _Due Date_ three months later when you open an ticket please.
136 42 kju
!/images/true.png! Do use the [[ticket_template|template]] of *Header*, *Observed*, *Expected* and "*Repro*":http://dev-heaven.net/wiki/cis/What_does_it_mean key points in your new tickets
137 42 kju
!/images/false.png! Do NOT assign issues to any person. This is a moderator job.
138 42 kju
!/images/false.png! Do NOT set priority. Priority has meaning only at BI side.
139 42 kju
!/images/false.png! Do NOT set the target version. Use the _Affected ArmA II Version_ only.
140 79 Fireball
!/themes/dh_squish/images/fugue/document_text_image.png! Read the *"workflow":http://dev-heaven.net/projects/cis/wiki/workflow*, if you want to understand the process.
141 26 alef
142 1 alef
h3. Links & Acronyms
143 6 alef
144 6 alef
* [[Versions]] and changelogs, "ArmA II Object class library":http://forums.bistudio.com/showthread.php?t=75455, "Unlock armory items":http://community.bistudio.com/wiki/ArmA:_Cheats
145 83 alef
* "Killing Bugs - Bohemia Interactive":http://www.bistudio.com/index.php/english/company/developers-blog/81-killing-bugs, "How to Report Bugs Effectively":http://www.chiark.greenend.org.uk/~sgtatham/bugs.html, "Old instructions for the A1 BTS":http://community.bistudio.com/wiki/BTS_Instructions
146 20 alef
* *BI* "Bohemia Interactive":http://www.bistudio.com , *BIF* "Bohemia Interactive Forums":http://forums.bistudio.com "Beta patch testing":http://forums.bistudio.com/forumdisplay.php?f=82, *BIKI* "Bohemia Interactive Community Wiki":http://community.bistudio.com/wiki/Main_Page
147 6 alef
* *CTD* "Crash To Desktop":http://en.wikipedia.org/wiki/Crash_to_desktop, *WER* "Windows Error Reporting":http://msdn.microsoft.com/en-us/isv/bb190483.aspx, ArmAII: *OA* "Operation Arrowhead":http://www.arma2.com/arrowhead/arrowhead.html
148 8 alef
149 1 alef
h2. Sample
150 1 alef
151 1 alef
A crash in beta (click to zoom)
152 1 alef
153 1 alef
!sample_new_CTD_issue_400.png!:/attachments/4680/sample_new_CTD_issue_800.png