coupled with bind mouse2 quickload that equals instant five-dimensional death-evasion mastery right at your fingertips. who needs guns? 

but could totally have done without it. the noisiness and loudness... and the length they are on. Wasn't hard though - and I liked tricking monsters into frying themselves.

Liked it very much over all. 

Or a script with a "quicksave; wait 30; quicksave" loop. 

outstanding idea. That's 30 milliseconds, right? 

Quick, you have 0.015 seconds to dodge that bullet or you're dead! 

https://github.com/TTimo/doom3.gpl 

The Doom 3 GPL source code release does not include functionality enabling rendering
of stencil shadows via the "depth fail" method, a functionality commonly known as
"Carmack's Reverse".

Oh my. Carmack's Reverse not in Carmack's game. 

|| set func IP in your hosts file: 78.46.51.237 then run ipconfig /flushdns
|| where's hosts file in windows 7?
|| here you dumb shit: bit.ly/1tT6Zj
|| thanks sleepwalkr you smug patronising cock || you're welcome 

but how would they read this????? 

 

hosts file in win7:
C:\Windows\System32\drivers\etc\hosts
But... Each user has their own copy of the file. Using Windows Explorer, you can see this file, but you may need to remove the protection. 

http://celephais.fov120.com/board/ 

I've been recording video playthrough's of a fair few q1sp maps over the last few weeks and putting them on the yt at http://www.youtube.com/user/darrenweekes

I'll be adding more and more when I get the time, I want to get all the "classics" in there as well as videoing new releases.

Apologies for run quality of some of the earlier videos, I was doing them blind with fraps recording while I was playing which turns out pretty bad, ie lots of getting lost and derp moments. Now I've started running the maps through once or twice before recording and on the actual run I've been recording a demo and then frapsing that instead.

I've been considering adding minor commentary to videos also, so I wanted to know what kind of stuff would be interesting to listen to while watching the run. As a mapper I would probably talk most about the design of the maps and gameplay etc but I'm not sure it would be interesting enough. if you have any ideas let me know :) 

weird 

 

I just removed the www. from my bookmark and it seems to work fine now. Odd. 

that worked for me too :) 

so no more host file trickery necessary. Also, celephais.fov120.com was just temporary and does not allow you to log in. 

Please post them and let them know.

This place is a bit quiet but there's good discussions and banter when it gets going... 

I've kept this back for many years, but I thought you should all finally become aware of the new world order...
(lol sry, just jokes)
wait, who's that at the window...! 

i just wonder what happened with the tyranns base map

its been 90 something percent completed 

I would hurt somebody close to me to get to play that map in a finished state. 

To give people a way to verify.

www.quaddicted.com SSL fingerprints:
SHA1 Fingerprint =
55:51:B5:C5:89:84:DA:71
7C:6E:F1:84:90:AD:7B:F6
C3:DE:66:D2

SHA256 Fingerprint =
07:74:35:2A:11:54:D1:67
BE:FC:22:10:B1:D1:C9:7B
9B:39:0D:7A:0A:FC:DB:AA
73:EC:F1:25:D6:CE:1D:B9 

So I was running apsp1 to record demos for a future video and there is a strange bug in the map that only seems to happen in Fitzquake085.

The lifts in the map seem to bug out, for example one lift is not centered in the lift shaft and has buggy collision and other lifts act like you are getting crushed when you start moving on them, like there is some invisible wall above your head.

I checked in standard glquake and the map was fine, any ideas? 

regarding the "lift not centered in lift shaft", it's likely that this lift has "angle" "-1", which is rounded to 0 in regular quake. In fitzquake the rounding is more accurate and it will be rounded to -1.4 with protocol 15, or -0.9998 with protocol 666.

So it's a harmless mapper error that became harmful when engines started more accurate angles to the client.

More info here: http://forums.inside3d.com/viewtopic.php?t=3184

I have no idea about the collision/crushing issues, though, that's news to me.