Testing Portal 2 Co-Op Maps Alone: Difference between revisions
m (→Loading the Map: Fix ss_splitmode settings) |
(Add more robust in_forceuser toggle, add other useful console commands.) |
||
| Line 29: | Line 29: | ||
; <code>[[BindToggle]] "z" in_forceuser</code> | ; <code>[[BindToggle]] "z" in_forceuser</code> | ||
: Swaps you between first and second player when you push "z". | : Swaps you between first and second player when you push "z". | ||
{{note|If you are moving, crouching, shooting portals or otherwise performing an action when you change players, you will stop during the change but immediately resume the action when you change back. For instance, if you're holding "w" to move forward, you will stop moving forward as soon as you hit "z" (assuming you use the BindToggle above), but immediately resume moving forward when you hit "z" again even if "w" is no longer being held down. To stop this, simply tap "w" again, or use a more robust keybinding: <code>[[Bind]] "z" "-moveleft; -moveright; -use; -forward; -back; -attack; -attack2; toggle in_forceuser"</code>. | |||
===Use a controller=== | ===Use a controller=== | ||
| Line 47: | Line 49: | ||
: {{todo|Verify that these values are correct.}} | : {{todo|Verify that these values are correct.}} | ||
Note that the color of portals fired will be unchanged -- Atlas will shoot blue and purple portals regardless of the setting of change_portalgun_linkage. | Note that the color of portals fired will be unchanged -- Atlas will shoot blue and purple portals regardless of the setting of change_portalgun_linkage. | ||
== Other useful console commands == | |||
; <code>[[cmd2]] ''command''</code> | |||
: Executes ''command'' as if typed by the second player. | |||
: <code>cmd2 name Player2</code>: Sets the name of the second player | |||
; <code>[[ss_force_primary_fullscreen]] ''enable''</code> | |||
: Makes the first player fullscreen if ''enable'' is 1, hiding the second player's view. | |||
: There doesn't appear to be a way to do this with the second player, nor does holding Tab to show partner view (+remote_view) work. | |||
== External Links/Sources == | == External Links/Sources == | ||
Revision as of 12:12, 29 April 2011
This is a guide on how you can test co-op maps alone utilizing the splitscreen capabilities of the Source engine. This also works for any existing coop maps. It does not require any modifications to the map file itself.
This does not cover the requirements for making a coop level in the first place.
Loading the Map
ss_map mapname- Load
mapnamein splitscreen 2-player mode. Analogous to map in singleplayer. Like map, it is not required to add the trailing .bsp. ss_splitmode mode- Changes the splitscreen mode.
ss_splitmode 0: Use recommended settings based on widthss_splitmode 1: Top-and-bottom splitss_splitmode 2: Side-by-side split
Dual Monitors
If you run dual monitors and want to split to each monitor, follow [this guide|http://forums.steampowered.com/forums/showthread.php?t=1857198]
Controlling the second player
If you could actually play the coop map entirely as one player, it wouldn't be a very cooperative map. These are some ways you can control the second player.
in_forceuser
in_forceuser playerindex- Take over the second player. All movement and other keybindings will be as if the second player used them. Requires cheats to be enabled.
sv_cheats 1: Turn on cheatsin_forceuser 0: Control player #1 (Atlas)in_forceuser 1: Control player #2 (P-Body)
To make this easy to use, set a keybinding for it:
BindToggle "z" in_forceuser- Swaps you between first and second player when you push "z".
{{note|If you are moving, crouching, shooting portals or otherwise performing an action when you change players, you will stop during the change but immediately resume the action when you change back. For instance, if you're holding "w" to move forward, you will stop moving forward as soon as you hit "z" (assuming you use the BindToggle above), but immediately resume moving forward when you hit "z" again even if "w" is no longer being held down. To stop this, simply tap "w" again, or use a more robust keybinding: Bind "z" "-moveleft; -moveright; -use; -forward; -back; -attack; -attack2; toggle in_forceuser".
Use a controller
This is actually more complicated than it sounds unless you have two controllers available. Source will map actions of the first detected controller to the first player and there doesn't seem to be away to override this. The workaround is to either have two actual controllers or use trickery to make your computer think it has two controllers.
More information for this can be found on the [forums]
change_portalgun_linkage
This doesn't truly let you play the second character, but it does allow you to create more than one set of linked portals.
change_portalgun_linkage team- Changes portals fired to belong to the specified team.
change_portalgun_linkage 0: Chellchange_portalgun_linkage 1: Unknownchange_portalgun_linkage 2: Atlaschange_portalgun_linkage 3: P-Body- Todo: Verify that these values are correct.
Note that the color of portals fired will be unchanged -- Atlas will shoot blue and purple portals regardless of the setting of change_portalgun_linkage.
Other useful console commands
cmd2 command- Executes command as if typed by the second player.
cmd2 name Player2: Sets the name of the second playerss_force_primary_fullscreen enable- Makes the first player fullscreen if enable is 1, hiding the second player's view.
- There doesn't appear to be a way to do this with the second player, nor does holding Tab to show partner view (+remote_view) work.