« Previous - Version 36/103 (diff) - Next » - Current version
kju, 07/09/2010 11:36


Community Issue Tracker - Welcome!

  • This is a free service, please use it in respect to other volunteers free time work
  • Versions older than the latest patch will be rejected.
    Since Jun 25th 2010, version 1.07 for ArmA2. Since June 29th 2010, version 1.52 for Operation Arrowhead

Why participate?

This is what Bohemia Interactive has to say:

Have you compiled a list of fixed issues or implemented feature requests that have occurred since the community created CIT came into use?
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.

We have not. However, it is fairly easy for anyone to filter issue in CIT and see how much has been addressed.
CIT has become very important resource for us to gather feedback from our community.

How does BIS prioritize bugfixes/features? (What are the design procedures for picking what to fix or what to include)

Internally, we usually have a lot of obvious or critical issues to fix or implement.
Between those, selecting order or priorities mostly depends on available resources and also individual preference or interest.
The Community Issue Tracker is often looked at, and we use Votes as good indication of how important a particular fix is for our users.

Reference: Ask Bohemia about A2OA interview.

How to report a crash?

a message that the game has crashed (WER)

  • Send crash error information to BI through Microsoft with WER. Or follow these instructions
  • WER does not work with betas. Attach .mdmp and .bidmp files zipped to your ticket
  • Set the Category field to CrashToDesktop and fill the fields:
    • Maxmem parameter (if used), Mainboard chipset, CPU, Operating system
    • Graphics card, Graphics card driver version
  • Upload as much as files described in attachments

How to vote an issue or feature?

How to report a bug?

  • Be short and descriptive, use a bullet point step-by-step reproducibility report in this way:
  1. Repro steps: what to do for the bug to happen
  2. Results seen: what is the bug
  3. Desired results: how should it behave once the bug is fixed
  • Due is set by CIT manager
  • Priority is set by BI only (if at all)
  • Reproduce must be a second person (NOT the issue reporter)


Beta users

Latest beta patch: OA 1.53 BETA.

  • Betas for ArmA2 have been discontinued
  • Please read the BI article. Downloads and changelog here
  • Specify the exact build number in the title [79100] or somewhere in the report, and use version BETA as Affected ArmA II version.
    • Beta version are one number ahead: if you read 1.52.79100 in-game, that means 1.53 BETA

the version displays in the main screen, lower right

What and what not

 Do set Due Date two weeks later as you open an issue
Do use the template of Description, Repro, Observed and Expected key points in your new tickets
Do NOT assign issues to any person. This is a moderators job
Do NOT set priority. Priority has meaning only at BI side
Do NOT set the target version. Use the Affected ArmA II Version only
Read the [[workflow]], if you are interested in the process

Links & Acronyms


A crash in beta (click to zoom)

sample_new_CTD_issue.svg (8.8 kB) alef, 02/02/2010 15:12

sample_new_CTD_issue_400.png (56.8 kB) alef, 02/02/2010 16:07

sample_new_CTD_issue_800.png (123.9 kB) alef, 02/02/2010 16:07

WER-100.png (4.7 kB) alef, 02/03/2010 22:27

version-150.png (4.7 kB) alef, 02/03/2010 22:52

CIT_Banner.png (8.3 kB) kju, 01/19/2011 16:37

CIT_Banner2.png (14.9 kB) admin, 02/15/2012 10:46