TXR_TA
24-11-2006, 16:14
I've been exeriencing two new problems for a couple of days now. I've been using TS2 for about one and a half year and about this week me and my 2 friends have been having two problems while Counter-Strike: Source or DOD: Source is running.
1. After stopped pressing the push to talk button the mic randomly stays open, and requires a couple of pushes to get it closed again. (ONLY IN SOURCE GAMES)
2. While CS:S or DOD:S is running and someone is talking, his voice is breaking up and you can only hear parts of what he is saying. OR Someone has a Source game running and someone else (that haven't got any Source game running) is talking, the guy that is playing can't hear his voice properly (same problem both ways!!!!) (ONLY IN SOURCE GAMES)
!!! - This appears to be happening only when the game is open (not minimized!) and you are connected to a server. If you are not connected to a server, for example in the menu, there are no problems, or the server is changing the map, no problems there either. - !!!
We've been experiencing these problems for a few days now, and it's really hard to play matches because you can't hear complete sentences.
We've tried 2 servers and total of 3 people are having this problem. The two servers were different versions, the newest and one version older. Two clients were the newest and the one had probably one version older. So we are pretty convinced that it is something related to CS:S/DOD:S/Source engine. Maybe a new CS:S/DOD:S/Source engine update has messed up something between TS2 and Source?? Well mainly we think so because this hasn't been happening very long. Maybe there is some stuff that CS:S is using at the same time with TS2 (CS:S in-game talk system)??
Saget @ QuakeNet though: that it might be something related to the anti-cheating system.
I checked my friends connection info at the time his voice was breaking up and his packet loss was 0% and his ping was normal.
We tested DOD:S bandwidth usage when playing with a bandwidth meter and it doesn't seem to take any more bandwidht than normal. Though we use the SPEEX 25.9 codec, there should be enough bandwidth left.
We also tried to turn the in-game sound off (didnt find a box to uncheck it) so we turned it as low as possible, no effect.
If there's anyone else having same kind of problems, if so and have solved it, I would be pleased to know.
If you need more info, msg TXR @ QuakeNet.
PS. It appears to make these in the TS2 clients log all the time when someone is talking:
<date> <time>,2596,DEBUG,All,TClientEventThread.HandleVoicePack et,attemting to storing packet <changing_number> from client 3
<date> <time>,2596,WARNING,All,,packet nr <changing_number> (speak 140) was not stored
<date> <time>,2596,WARNING,All,,packet nr <changing_number> (speak 113) was not stored
<date> <time>,3908,WARNING,All,procedure TDICallBack.execute,"The operation had no effect." or "The device buffer overflowed and some input was lost." or "The device exists but is not currently attached." or "The change in device properties had no effect."
1. After stopped pressing the push to talk button the mic randomly stays open, and requires a couple of pushes to get it closed again. (ONLY IN SOURCE GAMES)
2. While CS:S or DOD:S is running and someone is talking, his voice is breaking up and you can only hear parts of what he is saying. OR Someone has a Source game running and someone else (that haven't got any Source game running) is talking, the guy that is playing can't hear his voice properly (same problem both ways!!!!) (ONLY IN SOURCE GAMES)
!!! - This appears to be happening only when the game is open (not minimized!) and you are connected to a server. If you are not connected to a server, for example in the menu, there are no problems, or the server is changing the map, no problems there either. - !!!
We've been experiencing these problems for a few days now, and it's really hard to play matches because you can't hear complete sentences.
We've tried 2 servers and total of 3 people are having this problem. The two servers were different versions, the newest and one version older. Two clients were the newest and the one had probably one version older. So we are pretty convinced that it is something related to CS:S/DOD:S/Source engine. Maybe a new CS:S/DOD:S/Source engine update has messed up something between TS2 and Source?? Well mainly we think so because this hasn't been happening very long. Maybe there is some stuff that CS:S is using at the same time with TS2 (CS:S in-game talk system)??
Saget @ QuakeNet though: that it might be something related to the anti-cheating system.
I checked my friends connection info at the time his voice was breaking up and his packet loss was 0% and his ping was normal.
We tested DOD:S bandwidth usage when playing with a bandwidth meter and it doesn't seem to take any more bandwidht than normal. Though we use the SPEEX 25.9 codec, there should be enough bandwidth left.
We also tried to turn the in-game sound off (didnt find a box to uncheck it) so we turned it as low as possible, no effect.
If there's anyone else having same kind of problems, if so and have solved it, I would be pleased to know.
If you need more info, msg TXR @ QuakeNet.
PS. It appears to make these in the TS2 clients log all the time when someone is talking:
<date> <time>,2596,DEBUG,All,TClientEventThread.HandleVoicePack et,attemting to storing packet <changing_number> from client 3
<date> <time>,2596,WARNING,All,,packet nr <changing_number> (speak 140) was not stored
<date> <time>,2596,WARNING,All,,packet nr <changing_number> (speak 113) was not stored
<date> <time>,3908,WARNING,All,procedure TDICallBack.execute,"The operation had no effect." or "The device buffer overflowed and some input was lost." or "The device exists but is not currently attached." or "The change in device properties had no effect."