Post by tapping on Jan 15, 2015 22:41:37 GMT
This post will be updated and designed to be as clear and concise as possible while providing lots of info.
Also, this post assumes you are playing on PC.
Overview:
1. The basics
A. Developer console (How to enable it and use it)
B. Keybinding and Bunnyhopping (How to bunnyhop)
2. Single Segment
A. Rules
B. Timing (how to time your runs)
C. Tutorials (More in the forum, but the main ones will be linked here)
1. The Basics (For both CM and SS)
A. Developer Console
Before even starting, you'll want to enable developer console:
- Go to a menu, then go to:
- Options>>Keyboard/Mouse>>Allow Developer Console
- Make sure it is Enabled.
- Now, push the tilde key: "~" or "`" key (it's likely to the left of the "1" key on your keyboard).
- A window should pop up, this is the developer console.
This allows you to access the console commands. The important commands will be pointed out, but you can find a list of useful console commands here: forums.steampowered.com/forums/showthread.php?t=1999524
And a full list here: developer.valvesoftware.com/wiki/Console_Command_List
B. Bunnyhopping and Keybinds
Movement is very important for getting fast times in Portal 2. Most players use the w,a,s,d keys to move and the mousewheel to jump.
You can bind keys using the options menu, but it's important to know how to do it this way:
Bind keys:
- Open the developer console (push the "~" key)
- Type "bind <key> <command>" to bind a key to a command.
- Example: "bind r restart_level"
The advantage of setting up your keys this way is because you can bind different commands than default ones, as well as multiple commands to one key.
Bunnyhopping binds
- Type "bind mwheelup +jump" into the dev console and press enter.
- You can also type "bind mwheeldown +jump" so that both up and down allow you to jump.
- Some players also prefer to only use one of "mwheelup" or "mwheeldown" for jumping, and the other for grabbing; it's your choice.
To learn how to improve your movement in Portal 2, there are good tutorials posted:
Bunnyhopping by ABaby: www.youtube.com/watch?v=fNv1rj058DQ
Bunnyhopping by Invictus: www.youtube.com/watch?v=JX3_KxTXkr4
Wall strafing by Invictus: www.youtube.com/watch?v=CzELVBOZikk
2. Single Segment Runs
If you've already done the things in section 1. then you will be good to go!
Please take a look at Znernicus's tutorial here: www.youtube.com/watch?v=tcfJEeyERJc
This is fairly comprehensive, done by chapter, and includes a lot of technical detail that is better in video format than text.
There will also be important information summarized here.
A. Rules
-No quicksave/quickload.
Console command rules
-Anything protected by sv_cheats is not allowed
-Phys_timescale, developer 1, mat_ambient_light, or other unnatural modifications are not allowed
-sv_player_funnel_into_portals (Portal funneling) is allowed to be modified, as it was a basic user setting in portal 1.
Timing starts when cross-hair first appears and ends when the last portal to the moon is shot.
Portal 2 Live Timer:
A new timer by AlphaHelix235 allows runs to be timed by ticks (in-game time unit equal to 1/60 seconds in Portal 2) rather than actual time passed. This is useful in determining actual gameplay according to recorded demos, and does not take time between maps into consideration. A link to the directions on how to get the timer can be found here: bitbucket.org/nick_timkovich/portal-2-live-timer/wiki/Home
B. How to Time the Run
In Portal 2, loading times vary based on many variables including how good your computer is, what settings you play on, and how long you've been running the game.
Overall times can vary by minutes.
Because of this, it is very important to get the in-game time. We use demo recordings because they do not inhibit computer performance and because they are very reliable for measuring ticks (the frames).
The run is timed from the first frame the cross-hairs appear to the frame where you shoot the moon after the Wheatley fight.
Portal 2 Live Timer
Before even telling you how to time demos, follow the directions here. This timer was made by AlphaHelix235 and has made timing runs much easier, which is why you should use it too.
bitbucket.org/nick_timkovich/portal-2-live-timer/wiki/Home
How to use it:
- Open the timer
- Go to file>>set demo location
- Set your demo location appropriately (more info below)
- Usually the appropriate directory looks something like this: C:\Program Files (x86)\Steam\steamapps\common\Portal 2\portal2
- You may need to set the directory every time you close the timer, so make sure to do this each time!!
Once you've set the right demo location, you are ready to go.
You can also open/save previous splits, etc, if you have done a run before.
Keep the timer open during your run.
Starting a Single Player, Single Segment Run
- Go to the main menu
- Go to Play Single Player>>New Game>>The Courtesy Call
- At the end of the loading screen (last couple dots), push "~" to open the dev console.
- The first frame of the game should have the dev console open and the game paused. If not, exit the run, and start a new one.
- Type "record <demo-name>" into the dev console. For example, "record tehurn". Make sure to use a new name each time, otherwise the timer may not detect it.
- This will start the demo recording once you unpause.
- Resume the game/unpause.
- Make sure the timer is started, and is reading the correct demo: if not, exit the run, and start a new one.
- Everything should be good to go, now complete your run!
The demos will record from map to map, and the timer will take care of figuring out the total time.
If you are not using the timer, you will need to manually time the demos using the command "playdemo <demoname>".
The first frame is when the crosshairs appear, and the last frame is when you shoot the moon.
If you die during the run, you can still continue!
- Make sure to let your character die (do not save/load anything)
- During the loading screen, press "~" near the end; like you did for the first frame of the game.
- Start recording a new demo with a different name than any other demo you have made before
- ie, type "record <demoname>" again into the console.
- The timer will take care of the rest, you can continue your run now!
When you die, the demos stop. This is why it's important to start a new set of demos. Luckily, the timer handles this well and will pick up where you left off just fine.
C. Tutorials
The main tutorial made thus far is Znernicus's tutorial here: www.youtube.com/watch?v=tcfJEeyERJc
This is fairly comprehensive, done by chapter, and includes a lot of technical detail that is better in video format than text.
We hope to see more tutorials made in the forum itself, and posts from youtube, etc.
Also, this post assumes you are playing on PC.
Overview:
1. The basics
A. Developer console (How to enable it and use it)
B. Keybinding and Bunnyhopping (How to bunnyhop)
2. Single Segment
A. Rules
B. Timing (how to time your runs)
C. Tutorials (More in the forum, but the main ones will be linked here)
1. The Basics (For both CM and SS)
A. Developer Console
Before even starting, you'll want to enable developer console:
- Go to a menu, then go to:
- Options>>Keyboard/Mouse>>Allow Developer Console
- Make sure it is Enabled.
- Now, push the tilde key: "~" or "`" key (it's likely to the left of the "1" key on your keyboard).
- A window should pop up, this is the developer console.
This allows you to access the console commands. The important commands will be pointed out, but you can find a list of useful console commands here: forums.steampowered.com/forums/showthread.php?t=1999524
And a full list here: developer.valvesoftware.com/wiki/Console_Command_List
B. Bunnyhopping and Keybinds
Movement is very important for getting fast times in Portal 2. Most players use the w,a,s,d keys to move and the mousewheel to jump.
You can bind keys using the options menu, but it's important to know how to do it this way:
Bind keys:
- Open the developer console (push the "~" key)
- Type "bind <key> <command>" to bind a key to a command.
- Example: "bind r restart_level"
The advantage of setting up your keys this way is because you can bind different commands than default ones, as well as multiple commands to one key.
Bunnyhopping binds
- Type "bind mwheelup +jump" into the dev console and press enter.
- You can also type "bind mwheeldown +jump" so that both up and down allow you to jump.
- Some players also prefer to only use one of "mwheelup" or "mwheeldown" for jumping, and the other for grabbing; it's your choice.
To learn how to improve your movement in Portal 2, there are good tutorials posted:
Bunnyhopping by ABaby: www.youtube.com/watch?v=fNv1rj058DQ
Bunnyhopping by Invictus: www.youtube.com/watch?v=JX3_KxTXkr4
Wall strafing by Invictus: www.youtube.com/watch?v=CzELVBOZikk
2. Single Segment Runs
If you've already done the things in section 1. then you will be good to go!
Please take a look at Znernicus's tutorial here: www.youtube.com/watch?v=tcfJEeyERJc
This is fairly comprehensive, done by chapter, and includes a lot of technical detail that is better in video format than text.
There will also be important information summarized here.
A. Rules
-No quicksave/quickload.
Console command rules
-Anything protected by sv_cheats is not allowed
-Phys_timescale, developer 1, mat_ambient_light, or other unnatural modifications are not allowed
-sv_player_funnel_into_portals (Portal funneling) is allowed to be modified, as it was a basic user setting in portal 1.
Timing starts when cross-hair first appears and ends when the last portal to the moon is shot.
Portal 2 Live Timer:
A new timer by AlphaHelix235 allows runs to be timed by ticks (in-game time unit equal to 1/60 seconds in Portal 2) rather than actual time passed. This is useful in determining actual gameplay according to recorded demos, and does not take time between maps into consideration. A link to the directions on how to get the timer can be found here: bitbucket.org/nick_timkovich/portal-2-live-timer/wiki/Home
B. How to Time the Run
In Portal 2, loading times vary based on many variables including how good your computer is, what settings you play on, and how long you've been running the game.
Overall times can vary by minutes.
Because of this, it is very important to get the in-game time. We use demo recordings because they do not inhibit computer performance and because they are very reliable for measuring ticks (the frames).
The run is timed from the first frame the cross-hairs appear to the frame where you shoot the moon after the Wheatley fight.
Portal 2 Live Timer
Before even telling you how to time demos, follow the directions here. This timer was made by AlphaHelix235 and has made timing runs much easier, which is why you should use it too.
bitbucket.org/nick_timkovich/portal-2-live-timer/wiki/Home
How to use it:
- Open the timer
- Go to file>>set demo location
- Set your demo location appropriately (more info below)
- Usually the appropriate directory looks something like this: C:\Program Files (x86)\Steam\steamapps\common\Portal 2\portal2
- You may need to set the directory every time you close the timer, so make sure to do this each time!!
Once you've set the right demo location, you are ready to go.
You can also open/save previous splits, etc, if you have done a run before.
Keep the timer open during your run.
Starting a Single Player, Single Segment Run
- Go to the main menu
- Go to Play Single Player>>New Game>>The Courtesy Call
- At the end of the loading screen (last couple dots), push "~" to open the dev console.
- The first frame of the game should have the dev console open and the game paused. If not, exit the run, and start a new one.
- Type "record <demo-name>" into the dev console. For example, "record tehurn". Make sure to use a new name each time, otherwise the timer may not detect it.
- This will start the demo recording once you unpause.
- Resume the game/unpause.
- Make sure the timer is started, and is reading the correct demo: if not, exit the run, and start a new one.
- Everything should be good to go, now complete your run!
The demos will record from map to map, and the timer will take care of figuring out the total time.
If you are not using the timer, you will need to manually time the demos using the command "playdemo <demoname>".
The first frame is when the crosshairs appear, and the last frame is when you shoot the moon.
If you die during the run, you can still continue!
- Make sure to let your character die (do not save/load anything)
- During the loading screen, press "~" near the end; like you did for the first frame of the game.
- Start recording a new demo with a different name than any other demo you have made before
- ie, type "record <demoname>" again into the console.
- The timer will take care of the rest, you can continue your run now!
When you die, the demos stop. This is why it's important to start a new set of demos. Luckily, the timer handles this well and will pick up where you left off just fine.
C. Tutorials
The main tutorial made thus far is Znernicus's tutorial here: www.youtube.com/watch?v=tcfJEeyERJc
This is fairly comprehensive, done by chapter, and includes a lot of technical detail that is better in video format than text.
We hope to see more tutorials made in the forum itself, and posts from youtube, etc.