Multiplayer Server Commands - Revision history

Lou Montana: Fix exportJIPqueue

2025-06-11T15:21:39Z

Fix exportJIPqueue

← Older revision		Revision as of 17:21, 11 June 2025
Line 232:		Line 232:
	\| {{hl\|#debug limitOut 100000}}		\| {{hl\|#debug limitOut 100000}}
	\| Change bandwidth limit (in bits per second). Must be larger than 0. You get response message: "Outgoing bandwidth limited to %d B/s (%d bps) per client".		\| Change bandwidth limit (in bits per second). Must be larger than 0. You get response message: "Outgoing bandwidth limited to %d B/s (%d bps) per client".
			\|-
			\| {{hl\|#exportJIPqueue}}
			\|
			\| Creates a log file containing an overview on all JIP (network) messages currently in the JIP queue. See [[exportJIPMessages]] for more info.
	\|}		\|}

Line 257:		Line 261:
	\|		\|
	\| Creates a log file containing the list of all game entities in scene. See [[logEntities]] for more info.		\| Creates a log file containing the list of all game entities in scene. See [[logEntities]] for more info.
	\|-
	~~\| {{GVI\|arma3\|diag}} {{GVI\|arma3\|prof}} {{hl\|#exportJIPqueue}}~~
	\|
	~~\| Creates a log file containing an overview on all JIP (network) messages currently in the JIP queue. See [[exportJIPMessages]] for more info.~~
	\|-		\|-
	\| {{GVI\|arma3\|2.20}} {{GVI\|arma3\|diag}} {{GVI\|arma3\|prof}} {{hl\|#logremains}}		\| {{GVI\|arma3\|2.20}} {{GVI\|arma3\|diag}} {{GVI\|arma3\|prof}} {{hl\|#logremains}}

.kju: /* Performance Profiling */ added captureSlowFrame examples with new suffix option

2024-12-05T10:00:15Z

Performance Profiling: added captureSlowFrame examples with new suffix option

← Older revision		Revision as of 12:00, 5 December 2024
Line 247:		Line 247:
	\|-		\|-
	\| {{GVI\|arma3\|prof}} {{hl\|#captureslowframe}} ''scope, threshold, frameOffset, numberOfSlowFrames to capture''		\| {{GVI\|arma3\|prof}} {{hl\|#captureslowframe}} ''scope, threshold, frameOffset, numberOfSlowFrames to capture''
	\| {{hl\|#captureSlowFrame sLoop 0 0 0}} <br>		\| style="width:300px;" \| {{hl\|#captureSlowFrame sLoop 0 0 0}} <br>
	{{hl\|#captureSlowFrame sLoop 0.3 0 1}} ~~equals to~~ {{hl\|~~diag_captureSlowFrame ['~~sLoop~~', 0.3]~~}}		{{hl\|#captureSlowFrame sLoop 0.033 0 1}} <br>
	\| Captures the current frame '''on the server''' if it exceeds the set threshold in seconds and get written to a log file in the same directory as the [[Crash_Files\|.rpt file]]. See [[diag_captureSlowFrame]] for more info.		{{hl\|#captureSlowFrame sLoop 33ms}} <br>
			{{hl\|#captureSlowFrame sLoop 30fps}}
			\| Captures the current frame '''on the server''' if it exceeds the set threshold in seconds and get written to a log file in the same directory as the [[Crash_Files\|.rpt file]].<br>
			Note: {{hl\|#captureSlowFrame sLoop 0.033 0 1}} equals to {{hl\|diag_captureSlowFrame ['sLoop', 0.033]}}. See [[diag_captureSlowFrame]] for more info.
	\|-		\|-
	\| {{GVI\|arma3\|diag}} {{GVI\|arma3\|prof}} {{hl\|#logEntities}}		\| {{GVI\|arma3\|diag}} {{GVI\|arma3\|prof}} {{hl\|#logEntities}}

.kju: /* Performance Profiling */ fixed - DS to use sLoop

2024-12-04T10:06:51Z

Performance Profiling: fixed - DS to use sLoop

← Older revision		Revision as of 12:06, 4 December 2024
Line 247:		Line 247:
	\|-		\|-
	\| {{GVI\|arma3\|prof}} {{hl\|#captureslowframe}} ''scope, threshold, frameOffset, numberOfSlowFrames to capture''		\| {{GVI\|arma3\|prof}} {{hl\|#captureslowframe}} ''scope, threshold, frameOffset, numberOfSlowFrames to capture''
	\| {{hl\|#captureSlowFrame ~~total~~ 0 0 0}} <br>		\| {{hl\|#captureSlowFrame sLoop 0 0 0}} <br>
	{{hl\|#captureSlowFrame ~~total~~ 0.3 0 1}} equals to {{hl\|diag_captureSlowFrame ['~~total~~', 0.3]}}		{{hl\|#captureSlowFrame sLoop 0.3 0 1}} equals to {{hl\|diag_captureSlowFrame ['sLoop', 0.3]}}
	\| Captures the current frame '''on the server''' if it exceeds the set threshold in seconds and get written to a log file in the same directory as the [[Crash_Files\|.rpt file]]. See [[diag_captureSlowFrame]] for more info.		\| Captures the current frame '''on the server''' if it exceeds the set threshold in seconds and get written to a log file in the same directory as the [[Crash_Files\|.rpt file]]. See [[diag_captureSlowFrame]] for more info.
	\|-		\|-

Lou Montana: Add #logremains

2024-11-22T01:48:58Z

Add #logremains

← Older revision		Revision as of 03:48, 22 November 2024
Line 242:		Line 242:
	\| The current frame '''on the server''' is captured and written to a log file in the same directory as the [[Crash_Files\|.rpt file]]. See [[diag_captureFrameToFile]] for more info. <br>		\| The current frame '''on the server''' is captured and written to a log file in the same directory as the [[Crash_Files\|.rpt file]]. See [[diag_captureFrameToFile]] for more info. <br>
	{{Feature\|informative\|		{{Feature\|informative\|
	Until 2.20 {{GVI\|arma3\|prof}} on client was required to trigger #captureFrame ~~command~~ on server. Starting {{GVI\|arma3\|2.20}} they can mismatch. You can trigger #captureFrame on a {{GVI\|arma3\|prof}} server (always required), coming from a {{GVI\|arma3\|perf}} client for example.		Until 2.20 {{GVI\|arma3\|prof}} on client was required to trigger {{hl\|#captureFrame}} on server. Starting with {{GVI\|arma3\|2.20}} they can mismatch.
			You can trigger {{hl\|#captureFrame}} on a {{GVI\|arma3\|prof}} server (always required), coming from a {{GVI\|arma3\|perf}} client for example.
	}}		}}
	\|-		\|-
Line 257:		Line 258:
	\|		\|
	\| Creates a log file containing an overview on all JIP (network) messages currently in the JIP queue. See [[exportJIPMessages]] for more info.		\| Creates a log file containing an overview on all JIP (network) messages currently in the JIP queue. See [[exportJIPMessages]] for more info.
			\|-
			\| {{GVI\|arma3\|2.20}} {{GVI\|arma3\|diag}} {{GVI\|arma3\|prof}} {{hl\|#logremains}}
			\|
			\| Log remains collector entities into a file in the [[arma.RPT\|RPT]] directory. See also <sqf inline>diag_remainsCollector -1</sqf> and the {{hl\|{{Link\|Multiplayer Server Commands#Performance Profiling\|#logremains}}}} server command.
	\|-		\|-
	\| {{hl\|#debug jipPerf}}		\| {{hl\|#debug jipPerf}}

Dwarden: /* Performance Profiling */ #logEntities is supported on profiling branch

2024-11-21T18:29:36Z

Performance Profiling: #logEntities is supported on profiling branch

← Older revision		Revision as of 20:29, 21 November 2024
Line 250:		Line 250:
	\| Captures the current frame '''on the server''' if it exceeds the set threshold in seconds and get written to a log file in the same directory as the [[Crash_Files\|.rpt file]]. See [[diag_captureSlowFrame]] for more info.		\| Captures the current frame '''on the server''' if it exceeds the set threshold in seconds and get written to a log file in the same directory as the [[Crash_Files\|.rpt file]]. See [[diag_captureSlowFrame]] for more info.
	\|-		\|-
	\| {{GVI\|arma3\|diag}} {{hl\|#logEntities}}		\| {{GVI\|arma3\|diag}} {{GVI\|arma3\|prof}} {{hl\|#logEntities}}
	\|		\|
	\| Creates a log file containing the list of all game entities in scene. See [[logEntities]] for more info.		\| Creates a log file containing the list of all game entities in scene. See [[logEntities]] for more info.

.kju: Undo revision 370210 by .kju (talk)

2024-11-07T17:52:27Z

Undo revision 370210 by .kju (talk)

← Older revision		Revision as of 19:52, 7 November 2024
Line 254:		Line 254:
	\| Creates a log file containing the list of all game entities in scene. See [[logEntities]] for more info.		\| Creates a log file containing the list of all game entities in scene. See [[logEntities]] for more info.
	\|-		\|-
	\| ~~{{GVI\|arma3\|prof}}~~ {{GVI\|arma3\|diag}} {{GVI\|arma3\|prof}} {{hl\|#exportJIPqueue}}		\| {{GVI\|arma3\|diag}} {{GVI\|arma3\|prof}} {{hl\|#exportJIPqueue}}
	\|		\|
	\| Creates a log file containing an overview on all JIP (network) messages currently in the JIP queue. See [[exportJIPMessages]] for more info.		\| Creates a log file containing an overview on all JIP (network) messages currently in the JIP queue. See [[exportJIPMessages]] for more info.

.kju: Dedmen: #exportJIPqueue is also in prof

2024-11-07T17:51:30Z

Dedmen: #exportJIPqueue is also in prof

← Older revision		Revision as of 19:51, 7 November 2024
Line 254:		Line 254:
	\| Creates a log file containing the list of all game entities in scene. See [[logEntities]] for more info.		\| Creates a log file containing the list of all game entities in scene. See [[logEntities]] for more info.
	\|-		\|-
	\| {{GVI\|arma3\|diag}} {{GVI\|arma3\|prof}} {{hl\|#exportJIPqueue}}		\| {{GVI\|arma3\|prof}} {{GVI\|arma3\|diag}} {{GVI\|arma3\|prof}} {{hl\|#exportJIPqueue}}
	\|		\|
	\| Creates a log file containing an overview on all JIP (network) messages currently in the JIP queue. See [[exportJIPMessages]] for more info.		\| Creates a log file containing an overview on all JIP (network) messages currently in the JIP queue. See [[exportJIPMessages]] for more info.

Lou Montana: Fix

2024-11-06T14:49:48Z

Fix

← Older revision		Revision as of 16:49, 6 November 2024
Line 232:		Line 232:
	\| {{hl\|#debug limitOut 100000}}		\| {{hl\|#debug limitOut 100000}}
	\| Change bandwidth limit (in bits per second). Must be larger than 0. You get response message: "Outgoing bandwidth limited to %d B/s (%d bps) per client".		\| Change bandwidth limit (in bits per second). Must be larger than 0. You get response message: "Outgoing bandwidth limited to %d B/s (%d bps) per client".
	}}
	\|}		\|}

Lou Montana: Some wiki formatting

2024-11-06T14:49:18Z

Some wiki formatting

Show changes

.kju: fixed missing end tags for Feature|informative

2024-11-05T06:37:36Z

fixed missing end tags for Feature|informative

← Older revision		Revision as of 08:37, 5 November 2024
Line 246:		Line 246:
	{{Feature\|informative\|		{{Feature\|informative\|
	Until 2.20 {{GVI\|arma3\|prof}} on client was required to trigger #captureFrame command on server. Starting {{GVI\|arma3\|2.20}} they can mismatch. You can trigger #captureFrame on a {{GVI\|arma3\|prof}} server (always required), coming from a {{GVI\|arma3\|perf}} client for example.		Until 2.20 {{GVI\|arma3\|prof}} on client was required to trigger #captureFrame command on server. Starting {{GVI\|arma3\|2.20}} they can mismatch. You can trigger #captureFrame on a {{GVI\|arma3\|prof}} server (always required), coming from a {{GVI\|arma3\|perf}} client for example.
			}}
	\|-		\|-
	\| {{GVI\|arma3\|prof}} {{hl\|#captureslowframe}} ''scope, threshold, frameOffset, numberOfSlowFrames to capture''		\| {{GVI\|arma3\|prof}} {{hl\|#captureslowframe}} ''scope, threshold, frameOffset, numberOfSlowFrames to capture''

← Older revision		Revision as of 12:00, 5 December 2024
Line 247:		Line 247:
	\|-		\|-
	\| {{GVI\|arma3\|prof}} {{hl\|#captureslowframe}} ''scope, threshold, frameOffset, numberOfSlowFrames to capture''		\| {{GVI\|arma3\|prof}} {{hl\|#captureslowframe}} ''scope, threshold, frameOffset, numberOfSlowFrames to capture''
	\| {{hl\|#captureSlowFrame sLoop 0 0 0}} <br>		\| style="width:300px;" \| {{hl\|#captureSlowFrame sLoop 0 0 0}} <br>
	{{hl\|#captureSlowFrame sLoop 0.3 0 1}} ~~equals to~~ {{hl\|~~diag_captureSlowFrame ['~~sLoop~~', 0.3]~~}}		{{hl\|#captureSlowFrame sLoop 0.033 0 1}} <br>
	\| Captures the current frame '''on the server''' if it exceeds the set threshold in seconds and get written to a log file in the same directory as the [[Crash_Files\|.rpt file]]. See [[diag_captureSlowFrame]] for more info.		{{hl\|#captureSlowFrame sLoop 33ms}} <br>
			{{hl\|#captureSlowFrame sLoop 30fps}}
			\| Captures the current frame '''on the server''' if it exceeds the set threshold in seconds and get written to a log file in the same directory as the [[Crash_Files\|.rpt file]].<br>
			Note: {{hl\|#captureSlowFrame sLoop 0.033 0 1}} equals to {{hl\|diag_captureSlowFrame ['sLoop', 0.033]}}. See [[diag_captureSlowFrame]] for more info.
	\|-		\|-
	\| {{GVI\|arma3\|diag}} {{GVI\|arma3\|prof}} {{hl\|#logEntities}}		\| {{GVI\|arma3\|diag}} {{GVI\|arma3\|prof}} {{hl\|#logEntities}}