mpStatistics.log: Difference between revisions
Lou Montana (talk | contribs) m (Text replacement - "\[\[[Cc]ategory:ArmA:[ _]?([^|]+)\]\]" to "{{GameCategory|arma1|$1}}") |
Lou Montana (talk | contribs) m (Text replacement - "y[ _]*\|[ _]*(arma[0-9]+)[ _]*\|[ _]+" to "y|$1|") |
||
| Line 42: | Line 42: | ||
{{GameCategory|arma2|Multiplayer}} | {{GameCategory|arma2|Multiplayer}} | ||
{{GameCategory|arma1| | {{GameCategory|arma1|Multiplayer}} | ||
Revision as of 13:09, 22 June 2021
mpStatistics.log
The mpStatistics.log file contains some statistics relevant to Join In Progress performance.
Minimum version
Introduced in OA 1.55.
Location
The text file called mpStatistics.log is created in the game folder.
Remote statistics
Since beta 1.59.84886 you can also use #debug jipPerf to check those statistics remotely from a client, without having to terminate the mission. The client needs to login as admin on the server, OutputDebugString Win API is used to output the results, you need to use a debugger or debug output utility to watch it.
Debug output utility:
Content
MP diagnostics are logged into the mpStatistics.log file at the end of mission. This means a mission must end one way or another to have the stats to be written to the file. So are no stats written on the fly/while the mission is running.
Sample entry generated per mission session:
AddInitAndRemoveOverridden statistics ... total messages = 14 1 ... Type_10 1 ... Type_42 1 ... Type_45 1 ... Type_46 1 ... Type_142 1 ... Type_204 1 ... Type_213 1 ... Type_214 1 ... Type_215 1 ... Type_231 1 ... Type_233 1 ... Type_234 1 ... Type_248 1 ... Type_249
The meaning of Type_XXX is unknown.