(All these questions only pertain to Glitchless category)
- Can someone explain/link me to something that can explain Demo's? Not sure what purpose they serve or what they are.
- Also, I'm running on the most currently updated version of Portal. Is this not recommended? (Also, not using relaxation vault skip save)
- If I add footage captured through OBS is that sufficient proof for a run? I currently have a PB of 21:37 but can't post it because all I have in the way of proof is a screenshot of the end of the run and my saved PB in my Live-split. Obviously this won't be accepted so before I run again I'd like to know what I need before hand.
For run proof, I stream to Twitch via OBS and then create a highlight (in Twitch) and send the permalink as video proof
footage capture is usually a good form of proof, if you show what is needed. Also it is not recommended that you run on current patch (because that patched out most of the save glitches), so go to the bottom of https://www.speedrun.com/Portal/resources , click on source unpack and you'll download a folder with portal when it was first released. steam will have to be open in order for you to run it but other than that you ready to go. if you have any more questions just DM me on discord and i'll get back to you in a day or two. my discord is ThunderRa1der#8081
Demos are files that are basically just a recording of your inputs and a few other things that are required for replaying a demo, which recreates what you did in the game in-engine instead of being a mere video recording. In addition while watching demos you can turn on debug mode to see literally every input or command entered during the recording represented in the console.
It is recommended you always use the source_unpack version available here, because it's very common for demo files from different version to not be playable at all and all the moderators are definitely using the source_unpack from here, most probably also have the privately shared 3420 build, which is an even older version used exclusively for out of bounds runs.
In most cases video proof in plenty, althought I would recommend still recording demos, which in the source_unpack is very easy to do, just start your runs with the console command speedrun_start and you'll always be recording until you use speedrun_stop. Personally I have 8 bound to an alias to stop and restart the recording for resets and 0 simply bound to speedrun_stop. The alias I use is: alias r3s3t "speedrun_stop;disconnect;wait 100;speedrun_start" The wait is just there to so there's a clear break between runs in the recording, which makes editing easier for me personally. I'd recommend setting up these binds in the autoexec.cfg file (can be easily edited with notepad) found in "source_unpack\portal\cfg". As far as I know the alias set up in the actual console aren't save permanently, while the cfg file is automatically executed when first starting the game.
Hi I'm a bit late but I'd like to correct a couple of things. First of all, Source Unpack (build 5135) isn't the oldest version; it is in fact the latest version released before the SteamPipe update in 2013 or so which did weird things to save glitches and also made load times horrible.
Next, 3420 is indeed an older version but I've not seen anyone using it for OoB runs yet, not counting Icy's "no passing through portals" runs. In theory it makes it possible to save time in 02 but it has a couple of downsides like horrible FOV and no radios (although the latter only applies to inbounds). It also has free movement OoB which helps a little in 02 but makes other skips harder since missing a portal shot puts you in freefall. Also, I might as well mention I have an older build again, 3258, which I think is from only a few months after the retail release, however it has broken demo recording so it's not very useful. Oh yeah and the speedrun demo record plugin only "works" with 5135 (although it's a broken mess so it doesn't really work in the strictest sense anyway).
end of pedantry
how is the demo recording plugin a "broken mess"? I've never had a single issue with it ever and it always worked correctly and as intended.
Starting today, runs that require video proof (top 25) and runs beyond that where video is the only form of proof, now require audio, as recording audio for only the game is now a native OBS feature.
