User:Alef/MP testenv - Revision history

Alef: deleted

2011-08-29T17:36:24Z

deleted

← Older revision		Revision as of 19:36, 29 August 2011
Line 1:		Line 1:
	~~W.I.P.~~

	~~TODO: add the whole set of test scenarios and paths.~~
	* 3 ArmA (-server, -connect, -connect)
	* how to resize the -window in ArmA (alt, sysmenu, left+right keys)
	* link some xfire videos
	* don't use cygwin here. Find a tail -f / less +F solution to follo arma.rpt for native windows. http://www.ss64.com/nt/
	~~<pre>~~
	~~@echo off~~
	~~setlocal~~
	~~rem set BETA=beta\~~
	~~rem The line below has a TAB and TWO spaces~~
	~~for /F "tokens=3* delims= " %%A in ('reg query "HKLM\Software\Bohemia Interactive Studio\ArmA" /v MAIN') do @set _arma=%%A~~
	~~cd /D "%_arma%"~~
	~~start %BETA%arma.exe -window -nopause -nosplash -mod=%BETA%;@mod -host -nocdkey -world=intro~~
	~~start %BETA%arma.exe -window -nopause -nosplash -mod=%BETA%;@mod -connect=localhost -world=intro~~
	~~</pre>~~

	~~==How to run 2 ArmAs on the same PC==~~
	~~A fast way to setup MP missions is to run two ArmA games on the same computer. Let's call the first ''Editor'' and the second ''Client''~~
	*''Editor'' run the mission editor, selected by clicking on ''Multiplayer -> New -> Edit/New''
	*''Client'' can now join it selecting ''Multiplayer -> LAN'' or ''Remote'' wiht IP ''127.0.0.1'' or ''localhost''
	**It will see ''Editor'' in edit mode.
	*As ''Editor'' clicks on ''Preview'' to run the mission, a PBO named <tt>__cur_mp.pbo</tt> is created for ''Client'' to be downloaded.
	~~does*Both now enter the usual lobby and choose the slot they want~~
	*They play the mission, and when they leave back to the lobby, they can choose:
	**to run it again
	**to go back
	***''Editor'', in this case, returns in the the mission editor
	***''Client'', in this case, returns to the ''Wait for host'' screen.

	~~In order to avoid to click through the menus, you can choose to start the two ArmA by command line:~~
	~~For ''Editor''<pre>~~
	~~\ArmA\arma.exe -host~~
	~~</pre>~~
	~~For ''Client''<pre>~~
	~~\ArmA\arma.exe -connect=localhost~~
	~~</pre>~~
	~~I would suggest adding<pre>~~
	~~-window -nosplash -nopause~~
	~~</pre>to speed up things and run safe from alt-tabbing.<br>~~
	~~You can start the games at the same time, for instance using a .cmd like this:<pre>~~
	~~start \ArmA\arma.exe -window -nopause -host~~
	~~start \ArmA\arma.exe -window -nopause -connect=localhost~~
	~~</pre>~~
	~~===Problems===~~
	~~All of this above should works if ArmA does not check for duplicated CD keys.<br>~~
	There is an option in [[server.cfg]] called [[server.cfg#Server_Options\|kickduplicate]], which if set to 0 allows the same CD key to join a MP game. The problem is that server.cfg, or better, the file you provide with [[-config]], is only read if you run ArmA with [[ArmA:_Startup_Parameters#Network_Options\|-server]] or the dedicated <tt>[[ArmA:_Dedicated_Server\|arma_server.exe]]</tt> or <tt>server</tt> on [[ArmA:_Dedicated_Server#Linux_2\|Linux]].
	Because this check is done online at gamespy, if you drop your internet connection, the check isn't done. But this could be a problem, because while editing or testing, you usually want to search some forums or other online resources.
	~~===Solutions===~~
	~~# disconnect your PC from the Internet, ''or''~~
	~~# use my plugin [[User:Alef/nocdkey\|nocdkey]]~~

Alef at 00:16, 6 February 2009

2009-02-06T00:16:44Z

← Older revision		Revision as of 02:16, 6 February 2009
Line 12:		Line 12:
	rem The line below has a TAB and TWO spaces		rem The line below has a TAB and TWO spaces
	for /F "tokens=3* delims= " %%A in ('reg query "HKLM\Software\Bohemia Interactive Studio\ArmA" /v MAIN') do @set _arma=%%A		for /F "tokens=3* delims= " %%A in ('reg query "HKLM\Software\Bohemia Interactive Studio\ArmA" /v MAIN') do @set _arma=%%A
	~~CALL :main~~ "%_arma%"		cd /D "%_arma%"
	~~endlocal~~
	~~GOTO :eof~~

	~~:main~~
	~~%~d1~~
	~~cd %~f1~~
	start %BETA%arma.exe -window -nopause -nosplash -mod=%BETA%;@mod -host -nocdkey -world=intro		start %BETA%arma.exe -window -nopause -nosplash -mod=%BETA%;@mod -host -nocdkey -world=intro
	start %BETA%arma.exe -window -nopause -nosplash -mod=%BETA%;@mod -connect=localhost -world=intro		start %BETA%arma.exe -window -nopause -nosplash -mod=%BETA%;@mod -connect=localhost -world=intro

Alef at 23:25, 2 February 2009

2009-02-02T23:25:53Z

@@ Line 6: / Line 6: @@
 * link some xfire videos
 * don't use cygwin here. Find a tail -f / less +F solution to follo arma.rpt for native windows. http://www.ss64.com/nt/
 ==How to run 2 ArmAs on the same PC==

Alef at 10:31, 2 February 2009

2009-02-02T10:31:25Z

← Older revision		Revision as of 12:31, 2 February 2009
Line 5:		Line 5:
	* how to resize the -window in ArmA (alt, sysmenu, left+right keys)		* how to resize the -window in ArmA (alt, sysmenu, left+right keys)
	* link some xfire videos		* link some xfire videos
	* don't use cygwin here. Find a tail -f / less +F solution to follo arma.rpt for native windows.		* don't use cygwin here. Find a tail -f / less +F solution to follo arma.rpt for native windows. http://www.ss64.com/nt/

	==How to run 2 ArmAs on the same PC==		==How to run 2 ArmAs on the same PC==

Alef at 10:15, 2 February 2009

2009-02-02T10:15:12Z

← Older revision		Revision as of 12:15, 2 February 2009
Line 1:		Line 1:
			W.I.P.

			TODO: add the whole set of test scenarios and paths.
			* 3 ArmA (-server, -connect, -connect)
			* how to resize the -window in ArmA (alt, sysmenu, left+right keys)
			* link some xfire videos
			* don't use cygwin here. Find a tail -f / less +F solution to follo arma.rpt for native windows.

	==How to run 2 ArmAs on the same PC==		==How to run 2 ArmAs on the same PC==
	A fast way to setup MP missions is to run two ArmA games on the same computer. Let's call the first ''Editor'' and the second ''Client''		A fast way to setup MP missions is to run two ArmA games on the same computer. Let's call the first ''Editor'' and the second ''Client''

Alef at 13:34, 29 January 2009

2009-01-29T13:34:53Z

← Older revision		Revision as of 15:34, 29 January 2009
Line 30:		Line 30:
	There is an option in [[server.cfg]] called [[server.cfg#Server_Options\|kickduplicate]], which if set to 0 allows the same CD key to join a MP game. The problem is that server.cfg, or better, the file you provide with [[-config]], is only read if you run ArmA with [[ArmA:_Startup_Parameters#Network_Options\|-server]] or the dedicated <tt>[[ArmA:_Dedicated_Server\|arma_server.exe]]</tt> or <tt>server</tt> on [[ArmA:_Dedicated_Server#Linux_2\|Linux]].		There is an option in [[server.cfg]] called [[server.cfg#Server_Options\|kickduplicate]], which if set to 0 allows the same CD key to join a MP game. The problem is that server.cfg, or better, the file you provide with [[-config]], is only read if you run ArmA with [[ArmA:_Startup_Parameters#Network_Options\|-server]] or the dedicated <tt>[[ArmA:_Dedicated_Server\|arma_server.exe]]</tt> or <tt>server</tt> on [[ArmA:_Dedicated_Server#Linux_2\|Linux]].
	Because this check is done online at gamespy, if you drop your internet connection, the check isn't done. But this could be a problem, because while editing or testing, you usually want to search some forums or other online resources.		Because this check is done online at gamespy, if you drop your internet connection, the check isn't done. But this could be a problem, because while editing or testing, you usually want to search some forums or other online resources.
			===Solutions===
			# disconnect your PC from the Internet, ''or''
			# use my plugin [[User:Alef/nocdkey\|nocdkey]]

Alef: /* How to run 2 ArmA on the same PC */

2009-01-29T13:20:52Z

How to run 2 ArmA on the same PC

← Older revision		Revision as of 15:20, 29 January 2009
Line 1:		Line 1:
	==How to run 2 ~~ArmA~~ on the same PC==		==How to run 2 ArmAs on the same PC==
	A fast way to setup MP missions is to run two ArmA games on the same computer. Let's call the first *''Editor'' and the second ''Client''		A fast way to setup MP missions is to run two ArmA games on the same computer. Let's call the first ''Editor'' and the second ''Client''
	*''Editor'' run the mission editor, selected clicking on ''Multiplayer -> New -> Edit/New''		*''Editor'' run the mission editor, selected by clicking on ''Multiplayer -> New -> Edit/New''
	*''Client'' can now join it selecting ''Multiplayer -> LAN'' or ''Remote'' wiht IP ''127.0.0.1''		*''Client'' can now join it selecting ''Multiplayer -> LAN'' or ''Remote'' wiht IP ''127.0.0.1'' or ''localhost''
	**It will see ''Editor'' in edit mode.		**It will see ''Editor'' in edit mode.
	*As ''Editor'' clicks on ''Preview'' to run the mission, a PBO named <tt>__cur_mp.pbo</tt> is ~~create d on the fly~~ for ''Client'' to be downloaded.		*As ''Editor'' clicks on ''Preview'' to run the mission, a PBO named <tt>__cur_mp.pbo</tt> is created for ''Client'' to be downloaded.
	*Both now enter the usual lobby and choose the slot they want		does*Both now enter the usual lobby and choose the slot they want
	*They play the mission, and when they leave back to the lobby, they can choose:		*They play the mission, and when they leave back to the lobby, they can choose:
	**to run it again		**to run it again
Line 19:		Line 19:
	\ArmA\arma.exe -connect=localhost		\ArmA\arma.exe -connect=localhost
	</pre>		</pre>
	I ~~like to~~ suggest adding<pre>		I would suggest adding<pre>
	-window -nosplash -nopause		-window -nosplash -nopause
	</pre>to speed up things and run safe from alt-tabbing.		</pre>to speed up things and run safe from alt-tabbing.<br>
	You can start ~~them~~ at the same time, for instance using a .cmd like this:<pre>		You can start the games at the same time, for instance using a .cmd like this:<pre>
	start \ArmA\arma.exe -window -nopause -host		start \ArmA\arma.exe -window -nopause -host
	start \ArmA\arma.exe -window -nopause -connect=localhost		start \ArmA\arma.exe -window -nopause -connect=localhost
	</pre>		</pre>
	===Problems===		===Problems===
	All of this above should works if ArmA ~~doesn't~~ check for duplicated CD keys~~, and you have a single operative system user and a single installation of ArmA~~. ~~You maybe know that there~~ is an option in [[server.cfg]] called [[server.cfg#Server_Options\|kickduplicate]], which if set to 0 allows the same CD key to join a MP game. The problem is that server.cfg, or better, the file you provide with [[-config]], is only read if you run ArmA with [[ArmA:_Startup_Parameters#Network_Options\|-server]] or the dedicated <tt>[[ArmA:_Dedicated_Server\|arma_server.exe]]</tt> or <tt>server</tt> on [[ArmA:_Dedicated_Server#Linux_2\|Linux]].		All of this above should works if ArmA does not check for duplicated CD keys.<br>
			There is an option in [[server.cfg]] called [[server.cfg#Server_Options\|kickduplicate]], which if set to 0 allows the same CD key to join a MP game. The problem is that server.cfg, or better, the file you provide with [[-config]], is only read if you run ArmA with [[ArmA:_Startup_Parameters#Network_Options\|-server]] or the dedicated <tt>[[ArmA:_Dedicated_Server\|arma_server.exe]]</tt> or <tt>server</tt> on [[ArmA:_Dedicated_Server#Linux_2\|Linux]].
	Because this check is done online at gamespy, if you drop your internet connection, the check isn't done. But this could be a problem, because while editing or testing, you usually want to search some forums or other online resources.		Because this check is done online at gamespy, if you drop your internet connection, the check isn't done. But this could be a problem, because while editing or testing, you usually want to search some forums or other online resources.

Alef at 12:04, 29 January 2009

2009-01-29T12:04:41Z

← Older revision		Revision as of 14:04, 29 January 2009
Line 25:		Line 25:
	start \ArmA\arma.exe -window -nopause -host		start \ArmA\arma.exe -window -nopause -host
	start \ArmA\arma.exe -window -nopause -connect=localhost		start \ArmA\arma.exe -window -nopause -connect=localhost
			</pre>
	===Problems===		===Problems===
	All of this above should works if ArmA doesn't check for duplicated CD keys, and you have a single operative system user and a single installation of ArmA. You maybe know that there is an option in [[server.cfg]] called [[server.cfg#Server_Options\|kickduplicate]], which if set to 0 allows the same CD key to join a MP game. The problem is that server.cfg, or better, the file you provide with [[-config]], is only read if you run ArmA with [[ArmA:_Startup_Parameters#Network_Options\|-server]] or the dedicated <tt>[[ArmA:_Dedicated_Server\|arma_server.exe]]</tt> or <tt>server</tt> on [[ArmA:_Dedicated_Server#Linux_2\|Linux]].		All of this above should works if ArmA doesn't check for duplicated CD keys, and you have a single operative system user and a single installation of ArmA. You maybe know that there is an option in [[server.cfg]] called [[server.cfg#Server_Options\|kickduplicate]], which if set to 0 allows the same CD key to join a MP game. The problem is that server.cfg, or better, the file you provide with [[-config]], is only read if you run ArmA with [[ArmA:_Startup_Parameters#Network_Options\|-server]] or the dedicated <tt>[[ArmA:_Dedicated_Server\|arma_server.exe]]</tt> or <tt>server</tt> on [[ArmA:_Dedicated_Server#Linux_2\|Linux]].
	Because this check is done online at gamespy, if you drop your internet connection, the check isn't done. But this could be a problem, because while editing or testing, you usually want to search some forums or other online resources.		Because this check is done online at gamespy, if you drop your internet connection, the check isn't done. But this could be a problem, because while editing or testing, you usually want to search some forums or other online resources.

Alef: /* How to run 2 ArmA on the same PC */

2009-01-29T12:04:07Z

How to run 2 ArmA on the same PC

← Older revision		Revision as of 14:04, 29 January 2009
Line 1:		Line 1:
	==How to run 2 ArmA on the same PC==		==How to run 2 ArmA on the same PC==
	A fast way to setup MP missions is to run two ArmA games on the same computer. Let's call the first ''Editor'' and the second ''Client''.		A fast way to setup MP missions is to run two ArmA games on the same computer. Let's call the first *''Editor'' and the second ''Client''
	''Editor'' run the mission editor, selected clicking on ''Multiplayer -> New -> Edit/New''.		*''Editor'' run the mission editor, selected clicking on ''Multiplayer -> New -> Edit/New''
	''Client'' can now join it selecting ''Multiplayer -> LAN'' or ''Remote'' wiht IP ''127.0.0.1''. It will see ''Editor'' in edit mode.		*''Client'' can now join it selecting ''Multiplayer -> LAN'' or ''Remote'' wiht IP ''127.0.0.1''
	As ''Editor'' clicks on ''Preview'' to run the mission, a PBO named <tt>__cur_mp.pbo</tt> is create on the fly for ''Client'' to be downloaded.		**It will see ''Editor'' in edit mode.
	Both now enter the usual lobby and choose the slot they want. They play the mission, and when they leave back to the lobby, they can choose to run it again or go back. ''Editor'' in this case to the mission editor, ''Client'' to the ~~multiplayer or~~ ''Wait for host'' screen.		*As ''Editor'' clicks on ''Preview'' to run the mission, a PBO named <tt>__cur_mp.pbo</tt> is create d on the fly for ''Client'' to be downloaded.
			*Both now enter the usual lobby and choose the slot they want
			*They play the mission, and when they leave back to the lobby, they can choose:
			**to run it again
			**to go back
			***''Editor'', in this case, returns in the the mission editor
			***''Client'', in this case, returns to the ''Wait for host'' screen.

	In order to avoid to click the menus, command line ~~arguments are available.~~		In order to avoid to click through the menus, you can choose to start the two ArmA by command line:
	For ''Editor''<pre>		For ''Editor''<pre>
	\ArmA\arma.exe -host		\ArmA\arma.exe -host
Line 14:		Line 20:
	</pre>		</pre>
	I like to suggest adding<pre>		I like to suggest adding<pre>
	-window -nosplash ~~-world=empty~~ -nopause		-window -nosplash -nopause
	</pre>to speed up things and run safe from alt-tabbing.		</pre>to speed up things and run safe from alt-tabbing.
			You can start them at the same time, for instance using a .cmd like this:<pre>
			start \ArmA\arma.exe -window -nopause -host
			start \ArmA\arma.exe -window -nopause -connect=localhost
	===Problems===		===Problems===
	All of this above should works if ArmA doesn't check for duplicated CD keys, and you have a single operative system user and a single installation of ArmA. You maybe know that there is an option in [[server.cfg]] called [[server.cfg#Server_Options\|kickduplicate]], which if set to 0 allows the same CD key to join a MP game. The problem is that server.cfg, or better, the file you provide with [[-config]], is only read if you run ArmA with [[ArmA:_Startup_Parameters#Network_Options\|-server]] or the dedicated <tt>[[ArmA:_Dedicated_Server\|arma_server.exe]]</tt> or <tt>server</tt> on [[ArmA:_Dedicated_Server#Linux_2\|Linux]].		All of this above should works if ArmA doesn't check for duplicated CD keys, and you have a single operative system user and a single installation of ArmA. You maybe know that there is an option in [[server.cfg]] called [[server.cfg#Server_Options\|kickduplicate]], which if set to 0 allows the same CD key to join a MP game. The problem is that server.cfg, or better, the file you provide with [[-config]], is only read if you run ArmA with [[ArmA:_Startup_Parameters#Network_Options\|-server]] or the dedicated <tt>[[ArmA:_Dedicated_Server\|arma_server.exe]]</tt> or <tt>server</tt> on [[ArmA:_Dedicated_Server#Linux_2\|Linux]].
	Because this check is done online at gamespy, if you drop your internet connection, the check isn't done. But this could be a problem, because while editing or testing, you usually want to search some forums or other online resources.		Because this check is done online at gamespy, if you drop your internet connection, the check isn't done. But this could be a problem, because while editing or testing, you usually want to search some forums or other online resources.

Alef at 11:55, 29 January 2009

2009-01-29T11:55:07Z

New page

==How to run 2 ArmA on the same PC==
A fast way to setup MP missions is to run two ArmA games on the same computer. Let's call the first ''Editor'' and the second ''Client''.
''Editor'' run the mission editor, selected clicking on ''Multiplayer -> New -> Edit/New''.
''Client'' can now join it selecting ''Multiplayer -> LAN'' or ''Remote'' wiht IP ''127.0.0.1''. It will see ''Editor'' in edit mode.
As ''Editor'' clicks on ''Preview'' to run the mission, a PBO named <tt>__cur_mp.pbo</tt> is create on the fly for ''Client'' to be downloaded.
Both now enter the usual lobby and choose the slot they want. They play the mission, and when they leave back to the lobby, they can choose to run it again or go back. ''Editor'' in this case to the mission editor, ''Client'' to the multiplayer or ''Wait for host'' screen.

In order to avoid to click the menus, command line arguments are available.
For ''Editor''<pre>
\ArmA\arma.exe -host
</pre>
For ''Client''<pre>
\ArmA\arma.exe -connect=localhost
</pre>
I like to suggest adding<pre>
-window -nosplash -world=empty -nopause
</pre>to speed up things and run safe from alt-tabbing.

===Problems===
All of this above should works if ArmA doesn't check for duplicated CD keys, and you have a single operative system user and a single installation of ArmA. You maybe know that there is an option in [[server.cfg]] called [[server.cfg#Server_Options|kickduplicate]], which if set to 0 allows the same CD key to join a MP game. The problem is that server.cfg, or better, the file you provide with [[-config]], is only read if you run ArmA with [[ArmA:_Startup_Parameters#Network_Options|-server]] or the dedicated <tt>[[ArmA:_Dedicated_Server|arma_server.exe]]</tt> or <tt>server</tt> on [[ArmA:_Dedicated_Server#Linux_2|Linux]].
Because this check is done online at gamespy, if you drop your internet connection, the check isn't done. But this could be a problem, because while editing or testing, you usually want to search some forums or other online resources.