Alef/MP testenv – User
Jump to navigation
Jump to search
mNo edit summary |
|||
| Line 1: | Line 1: | ||
==How to run 2 | ==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 | 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 | *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 | 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 | 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 | 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. | ||
Revision as of 15:20, 29 January 2009
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 __cur_mp.pbo 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
\ArmA\arma.exe -host
For Client
\ArmA\arma.exe -connect=localhost
I would suggest adding
-window -nosplash -nopause
to speed up things and run safe from alt-tabbing.
You can start the games at the same time, for instance using a .cmd like this:
start \ArmA\arma.exe -window -nopause -host start \ArmA\arma.exe -window -nopause -connect=localhost
Problems
All of this above should works if ArmA does not check for duplicated CD keys.
There is an option in server.cfg called 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 -server or the dedicated arma_server.exe or server on 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.