Lol @ the guy in the front right, he looks SO pale and chooses to wear a white t-shirt
Okay.
1) The white shirt was to pimp out the QLtv name, as I was staff. 2) Pale is due to the lighting! 3) The strange pose is because I thought I was out of frame when I wasn't. 4) I was running on empty and caffeine 5) FU!!! :p
If you look into the QCon photos from QLtv, you'll find some better shots of me, this one being my favorite.
Sir, I wasn't running the bot at the time and I was not the one who did any of that. You would know this if you hadn't gotten yourself banned from #tastycast.
So... your entire post is moot.
What's that phrase? When you assume, you make an ass out of you and me?
1 192.168.1.1 (192.168.1.1) 1.979 ms 1.152 ms 1.023 ms 2 10.54.224.1 (10.54.224.1) 9.990 ms 12.479 ms 9.494 ms 3 gig2-2.lyncoh1-ybr1.cinci.rr.com (24.29.0.61) 19.221 ms 12.439 ms 8.498 ms 4 srp13-1.mtgmoh1-rtr4.cinci.rr.com (24.29.0.210) 9.008 ms 10.953 ms 10.999 ms 5 tge1-1-0.clboh1-rtr0.mwrtn.rr.com (65.25.137.241) 13.035 ms 12.452 ms 15.039 ms 6 ae-4-0.cr0.chi30.tbone.rr.com (66.109.6.68) 31.529 ms 22.988 ms 25.446 ms 7 ae-1-0.pr0.chi10.tbone.rr.com (66.109.6.155) 35.130 ms 22.214 ms 21.506 ms 8 gblx-twc.pr0.chi10.tbone.rr.com (66.109.9.202) 22.982 ms 22.903 ms 25.688 ms 9 The-Planet.TenGigabitEthernet2-3.ar2.HOU1.gblx.net (64.214.196.58) 143.055 ms 151.131 ms 141.180 ms 10 et5-4.ibr03.dllstx3.theplanet.com (70.87.253.49) 143.204 ms 142.210 ms 148.607 ms 11 te3-5.dsr01.dllstx3.theplanet.com (70.87.253.86) 151.214 ms te7-1.dsr02.dllstx3.theplanet.com (70.87.253.18) 150.200 ms te7-1.dsr01.dllstx3.theplanet.com (70.87.253.2) 148.657 ms 12 * * te1-3.dsr02.dllstx2.theplanet.com (70.87.253.122) 136.865 ms 13 te1-1.car06.dllstx6.theplanet.com (70.87.254.178) 145.993 ms 137.066 ms te1-2.car06.dllstx6.theplanet.com (70.87.254.182) 134.710 ms 14 tastyspleen.net (74.54.186.226) 133.194 ms 137.093 ms 140.196 ms
Well, since Cleancode is going to take over the world... don't limit your imagination on what you'd like to see. We can make client and game dll interactions that are specific to cleanq2 and cleancode working together, but will maintain compatibility so that cleanq2 can play on regular old quake2 servers (This is the goal, anyways). Paril has even found a way to have IRC in quake2 and it be entirely server-side, so don't limit your imagination when it comes to suggesting ideas!
Improved UI seems to be a recurring theme, so I'll go ahead and throw that on the list. I'm also going to take a look at q2pro for ideas, so thanks for the mention :p
As for the question as to why aprq2 instead of X client... well, a few reasons. 1) AprQ2 already works on Windows and Linux, and it does this well. 2) AprQ2 is my personal client of choice 3) AprQ2 is used in the kicker package 4) I like AprQ2 5) See 4
Paril just fixed another bug effecting Windows users, so hooray for that. Bugfixes come first, as always.
Alright, so at the moment there isn't really a whole lot new about it. Paril and I have taken jdolan's aprq2 and are using it as a base to make a sister engine to the Cleancode game DLL. We are looking at adding improvements, moving it over to C++, etc... Right now it's just AprQ2 with some bug fixes (HTTP downloading fix on linux and support for libpng14/libjpeg8). Anticheat... we'll have to consider that if the engine takes off like we hope.
Ideas thus far include hud scripting, VoIP, and a strong cross-platform support...but who cares what we want?What do you guys want? What are your favorite features from other clients that AprQ2 doesn't have? What do you dream about having in a Q2 engine? We want to know! This client is for all of you to make your Quake 2 experience the bomb.
It's Hz, not MHz :p This is an important distinction!
Most likely your mouse doesn't support a higher polling rate if you're having problems getting it there. To be honest, if you're under or at 125FPS, anything above 125Hz is pretty unnecessary (as 125Hz means, literally, 125 polls per second which matches exactly with 125 frames per second, creating one poll per frame). Not to mention that the mouse is polling with an 8ms response time, while your body's response time is about 200ms or more. One could put up a good argument that you're simply wasting cpu cycles by increasing the polling rate above 125Hz. Also, 500Hz and 1000Hz are a single millisecond delay apart, meaning that by using 1000Hz over 500Hz, you really are just plain wasting CPU cycles.
As for DPI, I'd say... high DPI for high sensitivity and low DPI for low sensitivity. You need more precision with a high sensitivity, not so much for a low sensitivity. Most of it is preference, though.
The m_pitch being lower than m_yaw suggestion sounds interesting...
Come idle in #tastycast on irc.globalgamers.net. The channel is always active and there are people there, like myself, who play anything and everything and will play those games with you :p
Hell, we organized an online 'table-top' RPG group, ffs.
Show Posts
