Overly Chatty Penguins
The Ready Room => General => Topic started by: Niteowl on July 24, 2004, 11:20:56 AM
-
as many of you have noticed, i can't comm because my mic keeps on freaking breaking up! the weird thing is that it's fine in Teamspeak..
any ideas from the LMers? and it doesn't matter my ping, i go on servers with less than 50 ping, still get a mic that's breaking up...
-
Get a Platronics Model 90 headset.
-
What's your cl_cmdrate in NS?
-
voice_dsound 0 in your userconfg IIRC
-
pah who needs mics :p i win over like half my comm games and ive only used my mic once :)
-
squad all the idiots into squad1 and use those "defend" waypoints... works for me, i hardly ever use mic.
-
squad all the idiots into squad1 and use those "defend" waypoints... works for me, i hardly ever use mic.
But last game I played with you comming I was squad... heeeyyyyy...
-
FIX IT SOON! we need the commrage fully operational! :D
-
well i do that for meny reasons, the biggest is just a way for me to see everyones HP really fast...
only down side is everytime someone new joins up you gotta resquad everyone and they all hear, "your squad 1" again...
-
Get a Platronics Model 90 headset.
i do have one :p
-
What's your cl_cmdrate in NS?
99999 .. IIRC.
-
voice_dsound 0 in your userconfg IIRC
i'll try that.
and to Seth: naw, i need to talk to my rines :)
and for the squad 1 thing, i find it useful to bidn a key to SELECT all to quickly see everyone's health. it's pretty much just like your squad 1 thing, except i dont' have to regroup them :)
-
What's your cl_cmdrate in NS?
99999 .. IIRC.
That would be your rate or cl_rate, which would be 9999 not 99999.
Depending on your connection, you can probably put your cmdrate to at least above 60. There are a few servers which default your cmdrate and updaterate to 15 for some god forsaken reason, but if you really want them to stay you can just alias them.
If all your rates are in check, then it probably is your mic or you microphone half-life settings.
-
What's your cl_cmdrate in NS?
99999 .. IIRC.
That would be your rate or cl_rate, which would be 9999 not 99999.
Depending on your connection, you can probably put your cmdrate to at least above 60. There are a few servers which default your cmdrate and updaterate to 15 for some god forsaken reason, but if you really want them to stay you can just alias them.
If all your rates are in check, then it probably is your mic or you microphone half-life settings.
what other rates should i be checking? just those three?
cmdrate
rate
oh crap.. what's the third one?
and i think my mic is fine, since it works clear and fine in TeamSpeak. the settings for voice in HL is only that little dialog tab in Options right? are there other settings i can mess around with?
-
Well, I've heard that this problem is caused by a low cl_cmdrate, so check that.
-
as many of you have noticed, i can't comm because my mic keeps on freaking breaking up! the weird thing is that it's fine in Teamspeak..
any ideas from the LMers? and it doesn't matter my ping, i go on servers with less than 50 ping, still get a mic that's breaking up...
Whats your FPS? If its below about 45, it begins breaking up.
-
Well, I've heard that this problem is caused by a low cl_cmdrate, so check that.
what is a good cl_cmdrate?
qua: er, no, it's fine. and even if it dips, the dipping in FPS never messed with my voice before :/
-
OK, basic netcode related commands explained as I understand them:
rate and cl_rate are the number of bytes/sec worth of bandwidth you have available for download and upload, respectively. Just set cl_rate to 9999 (which is all it will let you set it to anyway) and rate to 20000.
Cl_cmdrate and cl_updaterate are updates per second from client -> server and from server -> client, respectively. Cmdrate can be set about as high as you want, it won't really hurt anything. Anything above 75 or so for cl_cmdrate probably wont' have any effect at all, but it won't really hurt anything either.
Cl_updaterate on the other hand has to be carefully tweaked, because it works hand in hand with ex_interp. Ex_interp interpolates frames of movement inbetween actual frames of movement that you get from the server. Ex_interp at the moment isn't supposed to be changeable, and it's locked at .1. Correct ex_interp should be 1/cl_updaterate. So this interp is good for a cl_updaterate of 10 and nothing else. Bear this in mind when you start upping your cl_updaterate. That said, a cl_updaterate anywhere from 15 up to 30 should work fine on most servers, depending on how you ping to them. The trick is to open up a net graph and adjust until you're no longer getting choke and don't have a lot of extra lag showing next to your updaterate (net_graph 3... I think... is the one that shows you this on the top line). Then once you've adjusted your cl_updaterate, you'll probably want to adjust your ex_interp as well. (1/cl_updaterate remember. So an updaterate of 20 would need an ex_interp of .05. You'll know if you're fooling yourself with an updaterate that you can't support if everyone appears to be jerking around madly... you're not getting as many updates from the server as you think you are, and your client isn't interpolating enough extra 'fake' movement frames... you've told it not to, thus, jerky players) It's possible to change ex_interp, but you have to alias it immediately afterwards. As in type "ex_interp .05" in console, immediately followed by "alias ex_interp". You won't be able to change it again, but it won't be immediately changed back either.
Now that all that's out of the way, does it make no sense at all? :D
I'm not sure if any of these commands will help with your screwy voice, but it's worth a try. Turn on your netgraph anyway. Getting a lot of choke? Loss? Lots of lag showing? We'll figure it out, if it kills... uh... Grimm.
-
ex_interp .05; alias ex_interp ""
ex_extrapmax 6; alias ex_extrapmax ""
cl_cmdrate 101; alias cl_cmdrate ""
cl_updaterate 30; alias cl_updaterate ""
cl_cmdbackup 81
rate 20000
cl_rate 9999
My settings.
-
Sorry to go offtopic, but how big is the Plantronics Model 90 earpiece? I am still using a separate headset for the mic which I wear around my neck and my big old Sony headphones. It's a pain when I have to get up to take a whiz or get a beer and have to take off/put on two separate things. I've tried multiple headsets but any headphones that don't completely cover my ear tend to annoy me. This Plantronics looks quite nice but it's hard to gauge if it would cover my ears or not.
-
doobie: they do cover yer ears, they rox. they dont' ENCASE your ears, just cover them.
Key and Bob: thanks, i'll try BOTH of those tips when i get home. i seem to recall haxing my interp values to some "correct" one, since other values were considered hacking.. hmm. didn't know it was interdependent with other stuff.
*hopes to get commrage going nicely soon*
THANKS!
<3 <3 <3
-
doobie: they do cover yer ears, they rox. they dont' ENCASE your ears, just cover them.
Meh, I need to have my ears encased... they're just too BIG.
-
i copied key's config, and my MIC WORKS NOW!! YAAA!!! downside.. LM is full of rsrvs :(
THANKS FOR HELPING ME GUYS!!!
-
i copied key's config, and my MIC WORKS NOW!! YAAA!!! downside.. LM is full of rsrvs :(
THANKS FOR HELPING ME GUYS!!!
http://www.lunixmonster.org/forums/index.p...topic=1425&st=0 (http://www.lunixmonster.org/forums/index.php?showtopic=1425&st=0)
-
How can the server being full be a problem for you? You've GOT a slot too, silly. ;)
-
owls arent supposed to command, there supposed to fly around, hoot, and eat mice!
-
eat MEECES!!
bob: it was full of RESERVE slots, as in, 17/17.
-
Nothing to see here. Move along. Move along.
:p
-
uh.. you do realize you just posted that in general right?
as to the hint, i couldn't do that, that's EBIL!
-
>.>
Hmm, this could be fun...
-
Haf haf, JHunz could help too :p
-
OMG CONSPIRACY!!!! GASP!!!