
Nuschler22
-
Posts
64 -
Joined
-
Last visited
-
Days Won
1
Reputation Activity
-
Nuschler22 got a reaction from oRaGaMi in Terrible Hit Reg on Low Ping
There is a large component of Lag Compensation that affects those that have a great connection with low latency and buffer bloat. As I recall, CoD uses time rewind lag compensation which basically says if you both meet at "x" time, what would the outcome have been if you had an equal connection. That's why there are so many "behind cover" kills in this game where you think you should be safe. You are safe, but the lag compensation has awarded the kill to the person that has the higher latency because had it been equal, the game judges that they would have killed you.
It shouldn't happen, but being from the western United States, I can geolocate (when it works) to Australia and have a latency around 150-200 ms where I sponge bullets. There is normal lag, and it's not the greatest experience, but I can get kill streaks that I can't get with the best connection which shouldn't happen. I am about 22 ms on average away from two major servers. There is basically no difference between those that are closer, but since I'm so close, the whole part of the US that is farther out but the game connects them to the servers I'm on have a pretty noticeable difference in lag compensation.
The developer, or even the specific game, can greatly affect the benefit the higher latency gets. In older CoD's when they use to come out with patch notes about LC, and they would actually say how they adjusted the lag compensation, but they stopped doing that pretty quickly.
One huge issue is that the person with the higher latency always benefits. Being the lower latency, if I come around the corner at the same time someone else with a higher latency does, I can't do anything differently to affect that gunfight knowing that he will get about a 20ms "benefit," and sometimes more, of when the shots were fired making almost every heads up match virtually impossible to win verse someone with higher latency.
In older CoD's, I can run around the map and go heads up constantly. Now, I have to camp and pick people off to have any chance to do well.
There is a great paper from Valve corporation about lag compensation that describes what's going on, and why you're losing fights you shouldn't.
-
Nuschler22 got a reaction from Thechamp220 in Terrible Hit Reg on Low Ping
There is a large component of Lag Compensation that affects those that have a great connection with low latency and buffer bloat. As I recall, CoD uses time rewind lag compensation which basically says if you both meet at "x" time, what would the outcome have been if you had an equal connection. That's why there are so many "behind cover" kills in this game where you think you should be safe. You are safe, but the lag compensation has awarded the kill to the person that has the higher latency because had it been equal, the game judges that they would have killed you.
It shouldn't happen, but being from the western United States, I can geolocate (when it works) to Australia and have a latency around 150-200 ms where I sponge bullets. There is normal lag, and it's not the greatest experience, but I can get kill streaks that I can't get with the best connection which shouldn't happen. I am about 22 ms on average away from two major servers. There is basically no difference between those that are closer, but since I'm so close, the whole part of the US that is farther out but the game connects them to the servers I'm on have a pretty noticeable difference in lag compensation.
The developer, or even the specific game, can greatly affect the benefit the higher latency gets. In older CoD's when they use to come out with patch notes about LC, and they would actually say how they adjusted the lag compensation, but they stopped doing that pretty quickly.
One huge issue is that the person with the higher latency always benefits. Being the lower latency, if I come around the corner at the same time someone else with a higher latency does, I can't do anything differently to affect that gunfight knowing that he will get about a 20ms "benefit," and sometimes more, of when the shots were fired making almost every heads up match virtually impossible to win verse someone with higher latency.
In older CoD's, I can run around the map and go heads up constantly. Now, I have to camp and pick people off to have any chance to do well.
There is a great paper from Valve corporation about lag compensation that describes what's going on, and why you're losing fights you shouldn't.
-
Nuschler22 got a reaction from Netduma Fraser in Anyone get geolocate to work for MW3
I don't think anything is working, but thanks. As I said in a reply to you in another topic, the only success I'm having is bypassing the router entirely and going modem to console. It has way to many errors including not even showing Im on xbox live playing older games though the XBX home screen is fine, strict nat, booted from games, etc.
-
Nuschler22 got a reaction from Sentinel82 in Terrible Hit Reg on Low Ping
There is a large component of Lag Compensation that affects those that have a great connection with low latency and buffer bloat. As I recall, CoD uses time rewind lag compensation which basically says if you both meet at "x" time, what would the outcome have been if you had an equal connection. That's why there are so many "behind cover" kills in this game where you think you should be safe. You are safe, but the lag compensation has awarded the kill to the person that has the higher latency because had it been equal, the game judges that they would have killed you.
It shouldn't happen, but being from the western United States, I can geolocate (when it works) to Australia and have a latency around 150-200 ms where I sponge bullets. There is normal lag, and it's not the greatest experience, but I can get kill streaks that I can't get with the best connection which shouldn't happen. I am about 22 ms on average away from two major servers. There is basically no difference between those that are closer, but since I'm so close, the whole part of the US that is farther out but the game connects them to the servers I'm on have a pretty noticeable difference in lag compensation.
The developer, or even the specific game, can greatly affect the benefit the higher latency gets. In older CoD's when they use to come out with patch notes about LC, and they would actually say how they adjusted the lag compensation, but they stopped doing that pretty quickly.
One huge issue is that the person with the higher latency always benefits. Being the lower latency, if I come around the corner at the same time someone else with a higher latency does, I can't do anything differently to affect that gunfight knowing that he will get about a 20ms "benefit," and sometimes more, of when the shots were fired making almost every heads up match virtually impossible to win verse someone with higher latency.
In older CoD's, I can run around the map and go heads up constantly. Now, I have to camp and pick people off to have any chance to do well.
There is a great paper from Valve corporation about lag compensation that describes what's going on, and why you're losing fights you shouldn't.
-
Nuschler22 got a reaction from Nalsano_ in SmartQoS Version 4 like having AimBot!
Anyone that doesn't think EOMM or SBMM isn't a thing can't be very good.
Considering pros hate it as much as the "people that complain about anything," I would say you're living in a fairytale land believing it doesn't exist.
There is something to be said about lag compensation adding difficulty as well because when I geo locate (when it decides to work) to the other side of the world, I have my best games.
Its also been proven by a couple of well known you tubers working together that SBMM prefers that or over latency.
I've played a few "EOMM doesn't exist" people in local matches and they've been terrible every time. I've also let them play on my account and they can't compete in any way. It's sad how bad they've been.
-
Nuschler22 reacted to Netduma Fraser in Anyone get geolocate to work for MW3
If you're actually seeing it connect outside your radius then something isn't right, if you can provide a screenshot of the Geo-Filter page showing when that happens that will tell me more about what is happening. If it's not always connecting to live then it indicates a server needs to be whitelisted which may help overall. It's likely the game is using servers but they're misclassified as peers on the map.
Also, it's a 12 year old game, it pre-dates us even launching our first product so there won't have ever been a time in which we would have actively tested the game/explicitly supported it which is probably why you're encountering issues, we know most CoD games work the same from the time we launched to now but can't be certain it's the case before then. We generally keep active support for the current/last ~2 or so games as that's what people are most likely playing.
I get your frustration but we've never supported that specific game so it's unlikely to work right away, if you provide the screenshot from the first paragraph we can see what we can do. My instructions are a copy/paste for the specific issue you're having, that's why it says if on PC, otherwise you can ignore it.
-
Nuschler22 got a reaction from Hydros85 in Cod mw2 headset / footsteps
This is a game changer and it work's with any headset:
Download Steele Engine
Use Sonar
The following video shows you how Sonar can isolate the frequencies, which this guy tested, to enhance footsteps. I'm using the Steele Arctis 7p on PC and the footsteps are extremely loud. I would suggest using "Spatial Sound" to see if it isolates the direction better.
Watch this video and set it up how he uses it -
-
Nuschler22 got a reaction from Alex49H in Cod mw2 headset / footsteps
This is a game changer and it work's with any headset:
Download Steele Engine
Use Sonar
The following video shows you how Sonar can isolate the frequencies, which this guy tested, to enhance footsteps. I'm using the Steele Arctis 7p on PC and the footsteps are extremely loud. I would suggest using "Spatial Sound" to see if it isolates the direction better.
Watch this video and set it up how he uses it -
-
Nuschler22 got a reaction from Cajun72 in MW2 block geo locating, can't put myself in another location
To deal with the horrendous lag compensation, with previous games I have to put myself in other locations. Should I have to? No. Should it work? No. But, for some reason, it does.
I've had friends in the same city as me, but who don't know anything about what should be an ideal connection, play on my system and have a terrible experience. Most of them don't have gaming routers, play on wi fi with other connections going, dont try to open ports, and generally have no clue that they go against every suggestion that should make a good connection, but can compete at home but not here.
I play other games that require good latency and have no issues, nor do I have any other issues. My buffer bloat rating is A+ when I run it.
I have a gig up (sometimes more) and 35 MB down and from my location, my latency is typically less than 100 ms anywhere in the country. It's about 75ms within 2500 miles of my location. And it's around 20 ms to the CoD servers. I typically use congestion control at about 10 percent of down and 50 percent of up. I've found that putting them at 1 percent down and 5 percent up can help sometimes, but it gets laggy (regular game laggy) although, for some reason, it can help with the lag comp on close servers.
From the west coast of the US, I'll usually play in Australia and have a fighting chance. If I connect to the nearest servers, people see and hear me nearly a full second before I can see them. Playing thousands of miles away somehow eliminates that lag compensation. I can tell this easily because 1) I've been playing this game since the original on PC and know how the system works and 2) I can see reactions both live and in kill cams. If I play the original MW2, I don't need to do this but we all know how difficult it is to get a non-hacked game there. There have been a few CoD's like BLOPS III and I think one other one where this hasn't been an issue.
But with the current MW2, geolocating doesn't work. Neither the placement or the accepted range works. I put myself across the world with a small area and 0 assist ping, and it repeatedly only shows the nearest servers and connects me to them, albeit at a longer time in between games. And the game just is not close to playable when I'm connected to the nearest server.
I'm curious how many other people have this issue and if they have used geolocate to alleviate it. Also, have you had any success trying to geolocate yourself in the recent MW2 to a different area. I realize this was long winded, but I'm sure many of us are frustrated with trying to get a good connection with Call of Duty and always failing.
Thanks for any help provided.
-
Nuschler22 got a reaction from HoofHearted in Is it only the host that needs vpn
Just curious where you're from.
I'm in the US and can only get decent lobbies playing in Australia. But now, MW2 isn't allowing me to geolocate. It always finds the nearest servers regardless of where I put myself (nor how small the area is or ping assist at 0).
-
Nuschler22 got a reaction from Hydros85 in multiplayer settings mw 2
Geolocating isn't working for me. I usually fight lag compensation with previous games by putting myself on a different continent. Most of the time, I play in Australia from the US, and sometimes in Europe when I can't find games. I have no issues with other games, but CoD always has some extreme lag compensation that puts me about a second behind.
But now, geolocate does nothing. It still finds only the nearest servers even with ping assist set to zero and a small location area. I was able to geolocate fine during the beta and had good games.
For me, the game just isn't playable at the closest server. And with no way to find other servers, I don't think I'll be playing at all.
The lag compensation is not terrible in Cold War or Vanguard (which I didn't like nor play much), it just seems ramped up on MW2 for some reason. I had the same issue with MW 2019 as well.
-
Nuschler22 got a reaction from philo3391 in multiplayer settings mw 2
Geolocating isn't working for me. I usually fight lag compensation with previous games by putting myself on a different continent. Most of the time, I play in Australia from the US, and sometimes in Europe when I can't find games. I have no issues with other games, but CoD always has some extreme lag compensation that puts me about a second behind.
But now, geolocate does nothing. It still finds only the nearest servers even with ping assist set to zero and a small location area. I was able to geolocate fine during the beta and had good games.
For me, the game just isn't playable at the closest server. And with no way to find other servers, I don't think I'll be playing at all.
The lag compensation is not terrible in Cold War or Vanguard (which I didn't like nor play much), it just seems ramped up on MW2 for some reason. I had the same issue with MW 2019 as well.
-
Nuschler22 got a reaction from yeet05 in MW2 block geo locating, can't put myself in another location
To deal with the horrendous lag compensation, with previous games I have to put myself in other locations. Should I have to? No. Should it work? No. But, for some reason, it does.
I've had friends in the same city as me, but who don't know anything about what should be an ideal connection, play on my system and have a terrible experience. Most of them don't have gaming routers, play on wi fi with other connections going, dont try to open ports, and generally have no clue that they go against every suggestion that should make a good connection, but can compete at home but not here.
I play other games that require good latency and have no issues, nor do I have any other issues. My buffer bloat rating is A+ when I run it.
I have a gig up (sometimes more) and 35 MB down and from my location, my latency is typically less than 100 ms anywhere in the country. It's about 75ms within 2500 miles of my location. And it's around 20 ms to the CoD servers. I typically use congestion control at about 10 percent of down and 50 percent of up. I've found that putting them at 1 percent down and 5 percent up can help sometimes, but it gets laggy (regular game laggy) although, for some reason, it can help with the lag comp on close servers.
From the west coast of the US, I'll usually play in Australia and have a fighting chance. If I connect to the nearest servers, people see and hear me nearly a full second before I can see them. Playing thousands of miles away somehow eliminates that lag compensation. I can tell this easily because 1) I've been playing this game since the original on PC and know how the system works and 2) I can see reactions both live and in kill cams. If I play the original MW2, I don't need to do this but we all know how difficult it is to get a non-hacked game there. There have been a few CoD's like BLOPS III and I think one other one where this hasn't been an issue.
But with the current MW2, geolocating doesn't work. Neither the placement or the accepted range works. I put myself across the world with a small area and 0 assist ping, and it repeatedly only shows the nearest servers and connects me to them, albeit at a longer time in between games. And the game just is not close to playable when I'm connected to the nearest server.
I'm curious how many other people have this issue and if they have used geolocate to alleviate it. Also, have you had any success trying to geolocate yourself in the recent MW2 to a different area. I realize this was long winded, but I'm sure many of us are frustrated with trying to get a good connection with Call of Duty and always failing.
Thanks for any help provided.