You are not logged in.
Pages: 1
Plantronics DSP 500. $30ish. Very nice headset which isn't made anymore. It is USB and has a volume and mute on the cord. Mine are probably 8 years old and they sound very nice. Google it or check out something like Ebay. Win 8.1 and later it works straight away. I am not sure about Vista and Win 7. I think you may need drivers if the OS doesn't detect it.
*edit* I noticed some do not have the fuzzy on the end of the mic. It's probably best you find one with it included.
Did you try turning it off then turning it back on again? Once your IP changes comeback with an alias and keep having fun
In the meantime go here it is free: *URL sent to you via PM for privacy* There may be a 3 day wait on some posts but a tech support person will stick with you until everything is resolved.
No more packet loss. Instead it is just high latency at the server. My ms is 12 until it hits the server, then it goes over 80ms.
Name: 168.235.75.198
Address 1: 168.235.75.198
PING 168.235.75.198 (168.235.75.198): 56 data bytes
64 bytes from 168.235.75.198: seq=0 ttl=51 time=474.201 ms
64 bytes from 168.235.75.198: seq=1 ttl=51 time=87.312 ms
64 bytes from 168.235.75.198: seq=2 ttl=51 time=99.493 ms
64 bytes from 168.235.75.198: seq=3 ttl=51 time=86.435 ms
64 bytes from 168.235.75.198: seq=4 ttl=51 time=363.617 ms
64 bytes from 168.235.75.198: seq=5 ttl=51 time=95.020 ms
64 bytes from 168.235.75.198: seq=6 ttl=51 time=299.606 ms
64 bytes from 168.235.75.198: seq=7 ttl=51 time=87.314 ms
64 bytes from 168.235.75.198: seq=8 ttl=51 time=86.452 ms
64 bytes from 168.235.75.198: seq=9 ttl=51 time=86.681 ms
--- 168.235.75.198 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max = 86.435/176.613/474.201 ms
I do not know OS differences. I use Win 10. Press Windows key then type cmd. Right click the cmd icon and run as administrator. (right click "command prompt") Note this IP: The [USA] Server IP is 168.235.75.198.
At command prompt you can type: tracert 168.235.75.198 then press enter. This gives ya a look at how many hops you take to get to the destination and your latency at each hop. If you want a copy or text file then add c:\trace001.txt The text file will be in C:\ named trace001.txt.
tracert 168.235.75.168
or
tracert 168.235.75.198 c:\trace001.txt
Below this is a copy paste I saw from a Reddit user:
"Providing a traceroute would be good, but there are a couple things to know before you say "Ah ha! There's the problem!"
Let say you're having issues reaching a certain server. Take the following example:
You -- 1ms
Hop 2 -- 5 ms
Hop 3 -- 12ms
Hop 4 -- *
Hop 5 -- 20 ms
Server -- 22 ms
Looking at this traceroute, you may think hop 4 is the cause of the problem. It's possible, but more than likely that particular router either sends ICMP messages at a low priority, or doesn't bother to send one back at all.
Let's say you have a lot of latency reaching this server.
You -- 1ms
Hop 2 -- 5 ms
Hop 3 -- 12ms
Hop 4 -- 177 ms
Hop 5 -- 20 ms
Server -- 22 ms
Note hop 4 is responding with a latency of 177 ms. Again, this doesn't really prove an actual issue with that router as it may send ICMP responses at a low priority. More notably however is the high latency does not continue after hop 4. If there were a true issue with latency, it would look more like this:
You -- 1ms
Hop 2 -- 5 ms
Hop 3 -- 12ms
Hop 4 -- 177 ms
Hop 5 -- 182 ms
Server -- 187 ms"
With all this info there are a few things you can do. Within the first few hops you can contact your ISP for help. Another thing you can do is contact the hosting company of the server. (This [USA] server for example) and beyond that, the "in between" hops well your only option is to single out a specific hop with packet loss and try to contact them directly.
If all you laggers read this then please check where the lag is happening. If it is server side lag there may not be any hope. I have no contact information for the hosting company nor the person paying them to host our [USA] server. In any case someone must be responsible so post in forums. Make your voice heard.
There are sections of the internet that ping this server just fine and do not understand what or why we are complaining. Please do not be silent about it. No in game spam, however, keep it civil and in the forums. Thank You
This rubber banding type of lag is cause by a gateway at 54.239.109.12. If you do a trace route and do not pass through this gateway you will not be getting this same lag. Anyone can ping this gateway for a few seconds to see the packet loss.
My ISP cannot do anything about it. They can't even route my connection through different IP addresses. The tech support agent said it may be possible to do some kind of port forwarding on the USA server itself but had no other technical advice.
Damage_Inc wrote:I did a latency test and a packet loss test to the IP address displayed in game. It shows obvious spikes or drops in connection.
For Example:
This IP addy or hop is having problems.
54.239.109.12 (located in virginia, usa)Amazon Technologies Inc. AMAZON-2011L (NET-54-224-0-0-1) 54.224.0.0 - 54.239.255.255
Amazon.com, Inc. AMAZON-3Z (NET-54-239-0-0-1) 54.239.0.0 - 54.239.127.255...
I am trying to solve this problem but I need help. I am not a networking guru and I do not have access to the server hosting company's tech support.
...
You can call them. Normally in the same country it's possible that they fix it. One way is also call your provider and tell them the story. But ask there for a chat with a Tecnician and send him the screenshot from the Traceroute.
There's a chance they help to fix it.
...
I have sometimes the same problem with a Hop to the simple server. But because it's another country, they can't help in my case.
...
Who do I contact and on whom's behalf? Amazon? I do not know the people who host our server.
I think the silly things in the topic are a result of people thinking we are complaining about the same lag everyone gets online. This is different and it is not being caused by our home networks or wireless setups. It isn't malware on our PC's. This is 1) A Server Problem or 2) A Gateway between us and the server.
I traced the SiMPLE USA IP to Macon, Ga. I thought it was in LA. Does the server go through a proxy? It seems people on the West Coast USA are unaffected. People in Virginia and North Carolina are affected. This isn't consistent high ping. It is normal ping for about one second then 800ms and back to normal again. It looks like it is "high ping" but I think it is a lost connection or interrupted connection resulting in packet loss.
I did a latency test and a packet loss test to the IP address displayed in game. It shows obvious spikes or drops in connection.
For Example:
This IP addy or hop is having problems.
54.239.109.12 (located in virginia, usa)
Amazon Technologies Inc. AMAZON-2011L (NET-54-224-0-0-1) 54.224.0.0 - 54.239.255.255
Amazon.com, Inc. AMAZON-3Z (NET-54-239-0-0-1) 54.239.0.0 - 54.239.127.255
I am trying to solve this problem but I need help. I am not a networking guru and I do not have access to the server hosting company's tech support.
This jittery lag has been going on over a week. Is the server free or in someones closet? There must be someone that can send a simple reboot command or contact techs at the hosting company. Can we donate money towards the server to get a better one?
jaystar wrote:I wonder who was the great tanker who gave axis m10 that's the real story
None, someone snuck into the base and drove away with it. IMHO, it would be a real bummer to have both your tanks sitting in the enemy base the whole round and not be able to do anything about it without risking a ban.
You may also steal Axis Tigers. It would be a bummer for Axis then
The M10 wasn't firing back and was going to a repair pad. But if it is engaged the entire time it can continuously be attacked even though it is just sitting there inside the base doing nothing? Axis stole the M10 then drove it to the Axis uncappable base. Seems it should be safe there if not engaging enemies outside the base.
I was on TS3 with a non admin regular. He said you can attack people in an uncappable base if they had left the base and came back. So if a player leaves the main base and runs back to safety he can be killed while in the uncappable base? I thought no. But I have not memorized all possible situations and their rules. This sounds odd but is it accurate?
Pages: 1