mpStatistics.log: Difference between revisions
m (Add to ArmA 2 multiplayer category) |
Lou Montana (talk | contribs) m (Text replacement - "\[ *(https?:\/\/[^ = ]+) +([^= ]+) *\]" to "{{Link|$1|$2}}") |
||
| (5 intermediate revisions by the same user not shown) | |||
| Line 13: | Line 13: | ||
== Remote statistics == | == Remote statistics == | ||
Since beta 1.59.84886 you can also use <code>#debug jipPerf</code> 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. | Since beta 1.59.84886 you can also use <code style="display: block">#debug jipPerf</code> 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: | Debug output utility: | ||
* | * {{Link|http://technet.microsoft.com/en-us/sysinternals/bb896647|Windows Sysinternals - DebugView}} | ||
== Content == | == Content == | ||
| Line 41: | Line 41: | ||
The meaning of Type_XXX is unknown. | The meaning of Type_XXX is unknown. | ||
{{GameCategory|arma2|Multiplayer}} | |||
{{GameCategory|arma1|Multiplayer}} | |||
Latest revision as of 15:11, 28 April 2023
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.