Crash Files: Difference between revisions

From Bohemia Interactive Community
m (Text replacement - "{{SideTOC}}" to "{{TOC|side}}")
m (Text replacement - "ArmA 2" to "Arma 2")
Line 192: Line 192:


[[Category:ArmA: Troubleshooting]]
[[Category:ArmA: Troubleshooting]]
[[Category:ArmA 2: Troubleshooting]]
[[Category:Arma 2: Troubleshooting]]

Revision as of 20:46, 29 December 2020

Location

ⓘ
The crash file folder of Arma 3 can be quickly accessed with:
  • Press WIN + R to open the run command.
  • Then enter %localappdata%/Arma 3 and confirm
  • Create a text file and copy start "" "%localappdata%/Arma 3" in it
  • Save it as arma3LogFiles.bat
  • Double click on the file and the folder will be opened
Replace the highlighted path with the paths listed in the right column of the table below to access other games' crash file folder.
⚠
If -profiles startup parameter is used, the crash files will be located in that directory. In addition, the Eden Editor option "Open Log Folder" will open this folder. This parameter can also be found in the Arma 3 Launcher.
Game Files Directory
Arma 3
  • arma3.rpt
  • arma3.bidmp
  • arma3.mdmp

Windows Vista → Windows 10
%localappdata%/Arma 3
%localappdata%/Arma 2 OA
%localappdata%/Arma 2

Arma 2:OA
  • arma2OA.rpt
  • arma2OA.bidmp
  • arma2OA.mdmp
Arma 2
  • arma2.rpt
  • arma2.bidmp
  • arma2.mdmp
Armed Assault
  • arma.rpt
  • arma.bidmp
  • arma.mdmp

<profileDirectory>\ArmA

Operation Flashpoint
  • flashpoint.rpt (same role as .rpt files)
  • context.bin

<GameDirectory>

Log File Content Explained

Arma 3
This section is only valid for Arma 3!
ⓘ
This is WIP, please provide feedback in the Arma 3 Discord #community_wiki channel.

Beginning of the Log File

Common Errors and Warnings

Message (Exact message can vary) Explanation Significance
Warning Message: Picture iconmanleader not found An image or icon was not found
Template:colorball
Updating base class RscShortcutButton->RscButton... Caused by inheriting from wrong config while modifiying an existing base class. Currently Arma 3 has a lot of these issues out of the box.
Template:colorball
Cannot delete class B_KickOff, it is referenced somewhere (used as a base class probably). Attempt to delete a class failed.
Template:colorball
SimulWeather - Cloud Renderer - noise texture file is not specified!
Template:colorball
Warning: looped for animation: a3\anims_f_epa\data\anim\sdr\cts\hubcleaned\briefing\hubbriefing_loop.rtm differs (looped now 0)! MoveName: hubbriefing_ext
Template:colorball
a3\characters_f\proxies\flag.p3d: No geometry and no visual shape
Template:colorball
B_LSV_01_unarmed_F: mainturret - unknown animation source mainturret
Template:colorball
No face for B Alpha 1-4:1
No speaker given for 'Sotiris Zenon'
Template:colorball
Strange convex component08 in a3\weapons_f_enoch\rifles\msbs\msbs65_ubs_f.p3d:geometryView
Template:colorball
hidebullet_001 - unknown animation source codrivermuzzle_revolving
Template:colorball
Trying to create an invalid center EMPTY
Template:colorball
ModParams - Undefined or empty mod directory modParams command was unable to find the specified mod directory
Template:colorball
Unit is not in cargo
Template:colorball
Deinitialized shape [Class: "C_Soldier_VR_F"; Shape: "a3\characters_f_bootcamp\common\vr_soldier_f.p3d";]
Template:colorball
Error: entity [ProxyFlag_Auto] still has its shape, ref_count=2
Template:colorball
"Some path": Missing ';' at the end of line
Template:colorball
"Unsupported language English in stringtable" Happens if an entry was not found in the desired language e.g., English. This error will even show if it falls back to another lanuage e.g., Original. When stringtable can't find the entry it wants, it first tries Original entry, then English after that, the first entry in the stringtable is taken.
Template:colorball
ⓘ
Template:colorball → No action needed


Template:colorball → Issue should be fixed
Template:colorball → Issue needs to be fixed


Template:colorball → A false error. No action required

Creating a diagnostic file for DirectX

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

  • Press WIN+R to open the run command.
  • Enter dxdiag and confirm
  • After data collection is done, click on "Save All Information" and specify a location of where the file should be created.

Sending Crash Files

Retrieved from "https://community.bistudio.com/wiki?title=Crash_Files&oldid=175902"