Playing against soviet snipers recently I noticed if I go to counter snipe it the instant it fires and reveals itself, it will recloak before the German sniper can actually fire. Totally lame.
(This goes for all snipers if they are like that!!!) Lengthen time out of camo! |
THe 64 bit has been live for a couple months now, and it's a buggy mess.
So this makes me think...
Relic can't seem to code much anything well, the game has been essentially dead to them for years, but they suddenly have some new magic anti-cheat implementation in place just when all this drama starts...bit skeptical of all this.... |
Give Command PIV HEAT shell ability so it has a anti-tank timed window, adjust to taste. |
What if his name is a cruel joke? Seeking
The Seekingguy...
See King
See
King
He is king at seeing.
|
I've been running some tests.
First of all, random note, vehicles apparently do not always appear in the FOW when they get hit. It seems completely random. But just as often they stay invisible. No idea why.
Second of all, a vet 1 Pak 40 does not have a high enough fire rate to manually target a vehicle that got lid up by a previous attack ground shot.
Yes, but it would give him all the information he needed to take a follow up attack ground. The fall of the hit by the little shed there could just be scatter from a shot in the same place, or maybe he assumed that the opponent would back up the T70 after the connecting hit and he adjusted for that, nothing in that clip seems remarkable. |
"Curved Shots" are caused by the accuracy check succeeding, and forcing the shell to home in on the target. They only occur on actual attacks, not attack grounds, and only when the shot succeeds an accuracy check, as previously mentioned.
The fact that the shot didn't actually hit the t-70 on the third attack indicates this didn't happen, I don't think there's anything to see with regards to a "Curved shot".
It's odd that he "knew" where the T-70 was after it trundled back into the fog, especially as it changed direction after it stopped being visible, but vehicle sounds in the fog can be used fairly well to locate an unit. I'm not sure I'd call this /all/ that suspicious.
When you hit something the FOW it is momentarily revealed. Note that the "FOW" box is clicked on but the T70 is visible. |
Curved shots can only occur when a gun rolls a hit, and then the shell will follow the enemy vehicle regardless of its movement, causing curved projectiles. It can obviously only do that when it can directly target the enemy vehicle. So with direct line of sight. A curved shot with attack ground is impossible.
The question however is whether the curve is a camera angle or replay illusion or real. I suspect it's the former because I highly doubt the maphack (I have no idea how it works) allows to directly target vehicles in the FOW.
So this implies the map hack interacts with the game play (basing rolls off vision provided by the map hack)? |
can you explain this shot?
T70 is in FOW but his AT shoot to T70 with curved projectiles that cause by normal attack not ground attack .
https://www.youtube.com/watch?v=jCfe8aslYDw
https://imgur.com/cD4oS2w
He takes an initial lucky shot through the FOW (nothing abnormal here, you can hear the T70 through FOW and taking attack ground shots is completely normal for the 1st...you see this all day on twitch streams of players attack grounding through that hedge). The lucky shot connects, now people seem to think the 2nd shot is very suspicious but it is not, when you hit something in the FOW through lucky attack grounds, the item you hit is momentarily revealed through the FOW (you can hear the *donk* of the round hitting). https://imgur.com/a/jFJKFlQ FOW enabled, but the T70 is revealed.
I don't know what the picture of the "curved" shot is supposed to imply...are you saying he has some sort of aim hack? |
Or Seeking is just a very intelligent player, who takes minimal risk of being caught as to why he is always on the edge with FOW.
Unless the map hack provides a FOW overlay to illustrate exactly where the edge lies, I find this extremely hard to believe someone would be that skilled to have such precise estimation at essentially 100%. Surely there would be instances people could find where he was pre-emptive sooner. |
What are you asking exactly? The clip has follow camera on, he stops building bags as soon as he looks into the fow and 'sees' pathfinders and stop building the bags immediately.
This seems to be the point at which the volks stop, unless I'm watching incorrectly (this is the earliest point where it looks like the volks begin the reaching for their rifles animation instead of having their hands on the ground). I agree that this would be too fast reaction time from Seeking, but on the other hand, why would he wait this long until the pathfinders are at this spot before canceling the sandbags? Why wouldn't he have moved his volks to an optimal position to the green cover right there before the Pathfinders reached their green cover? It would be nice to see this clip at normal speed from Seekings POV for the duration (it only has POV for a small portion). If there are desync issues in the game +/- 1 second (I believe there are) then wouldn't pretty much all of these cases of pre-emptive moves fall within the margin of error? |