Crash Files: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
(→‎Sending Crash Files: Bug tracker is down)
m (→‎Sending Crash Files: WER is now preferred)
Line 19: Line 19:


== Sending Crash Files ==
== Sending Crash Files ==
[[Bohemia Interactive]] suggests that you email '''''support@bistudio.com''''' with those files, as it might help improve the stability of future patches.
When you experience a crash, you can help fixing the issue by sending the crash files using [http://www.microsoft.com/whdc/maintain/WERHelp.mspx Windows Error Reporting]. We are participating in this system and we are able to sort and analyze the crash dumps you send this way.


When you send the crash report to Microsoft using [http://www.microsoft.com/whdc/maintain/WERHelp.mspx Windows Error Reporting], we will get the data as well, however compared to reports send directly to us using the method above they sometimes miss some extended information useful for crash analysis.
By sending the crash files you help us to improve stability of the game, and you may also learn if there is perhaps a solution available to the problem you have.
 
If you are using operating system which has no Windows Error Reporting capabilities (like Windows 2000), you might
also send the crash files to email '''''support@bistudio.com'''''.


==See Also==
==See Also==

Revision as of 23:01, 3 March 2008

Bohemia Interactive has provided some helpful files when you experience a crash while playing or editing in Operation Flashpoint and Armed Assault.

Armed Assault

The arma.rpt, arma.bidmp and arma.mdmp files are located in your user\application\arma folder.

C:\Documents and Settings\username\Local Settings\Application Data\ArmA

Operation Flashpoint

Two files are created when OFP crashes, flashpoint.rpt and context.bin. These files are located in the root of the game directory and are only present if a crash is experienced.

The flashpoint.rpt contains information about which addons you have loaded, how much memory you have, which version you are running at the time of the crash. This can be a useful debugging tool if you are editing the mission files by hand, editing model configs. This file will often point to the cause of the crash.

The context.bin is a binary file and contains very little information to the end user.

DirectX

To better analyze the reason for malfunctions it might be useful to also create a DirectX diagnostic file.

To do this, hit the Windows "Start" button, and then select "Run...". In the dialog box that then comes up enter "dxdiag". After letting it finish (this will take a minute or so), click on "Save All Information", and specify a location of where the file should be created.

Sending Crash Files

When you experience a crash, you can help fixing the issue by sending the crash files using Windows Error Reporting. We are participating in this system and we are able to sort and analyze the crash dumps you send this way.

By sending the crash files you help us to improve stability of the game, and you may also learn if there is perhaps a solution available to the problem you have.

If you are using operating system which has no Windows Error Reporting capabilities (like Windows 2000), you might also send the crash files to email support@bistudio.com.

See Also

OFP: TroubleShooting

ArmA: Troubleshooting