SW had 5 segments on Nihilanth. So segment count will be tenfold and the time will be reduced by around 19 seconds.
So if applying SDA segment penalty it would actually turn out 6s slower ; >
Going to be honest here, I think you are insane.
You can take that as a compliment if you like.
I’m guessing that you’re segmenting lots there to cause things to reload faster or something?
EDIT: Wait, is that reduced by or to 19 seconds?
http://wiki.sourceruns.org/wiki/Fastfire - this trick needs a lot of segments
By* 22* seconds, sorry. Nihilanth’s 2000hp will be down in 2.0s starting from the first shot. Then it’s 13s til his head open up for finalization. Then another 28s til the map ends. So the actual fighting will go on for 2s compared to SW’s ~24s. You’ll hear briefly about it in the SourceCast.
looking forward to this run 8)
literally drowning in my hype
Wow. opgauss
quad you said in the new sourcecast that HL21 won’t be out for another month because no segments are encoded
say it aint so
In what fov are you gonna record the run?
Probably 110, because on 16:9 it equals to 90 (default value) on 4:3
106.27 on 16:9 equals 90 on 4:3. But it generally looks better with a bit higher fov.
What do you guys think?
https://dl.dropboxusercontent.com/u/9297051/HL/106.jpg
https://dl.dropboxusercontent.com/u/9297051/HL/110.jpg
https://dl.dropboxusercontent.com/u/9297051/HL/115.jpg
https://dl.dropboxusercontent.com/u/9297051/HL/120.jpg
Nihilanth have been slightly delayed but also a bit shorter. Found a new glitch to make him stop regenerating the last 500hp (out of 1000). So the fight will now take about 1.3s rather than 2.0s.
Well, since I play with 110 from the beginning of time, I’m gonna go with that because 106 looks too zoomed in and higher values look like they distort the view.
EDIT: well maybe 115 too
EDIT2: w/e just use what you’ve used for your previous runs
Nihilanth have been slightly delayed but also a bit shorter. Found a new glitch to make him stop regenerating the last 500hp (out of 1000). So the fight will now take about 1.3s rather than 2.0s.oh wow, I wonder how it works.
110 fov looks the best IMO
Agreed, 110 looked like the best option to me.
115 and above is just too distracting, so I vote for either 106 or 110.
180 Quake Pro
Everyone knows 65 is the only FOV
360 so that we can’t miss some awesomeness accidentally.
I vote 110, seems like a good balance between vision and distortion and it makes movement ‘feel’ faster than lower FOVs.