Shell Flying Wide

Posted on by

Working as intended…

 

 

Thanks to Wuestenfoxx for the video…

Edit: To explain – this issue happens, when you move your turrets and fire. It’s caused by the fact that server reticle at that moment is much larger than the regular one and shells fire to the edges of the server reticle, not the client one. The problem is not the fact that something like that happens if it is intended (bad a mechanism as it is), but the fact that most players probably don’t even know about the serverside reticle and will get confused.

44 thoughts on “Shell Flying Wide”

    • Same for me, although my internet isn’t so bad…
      Could it possibly be due to playing with client reticle while server reticle is sometimes lagging (especially while turning the turret, like in the above video)…?

      • Yep, that’s the problem.

        The only way to fix it, if you don’t want to use the server reticle, is to just wait 1-2 secs before shooting, no matter what you’re doing.

        • I use the server side reticule, and wait a couple seconds. It still happens to me about every 10th time I’m in a clinch.

    • i had that also one time and i use server reticle, i turned my turret, both reticle’s (normal and server) where aimed at the enemy tank, i shoot and my shot whent to the far right, i think it has something to do with packet loss or so, cuz yesterday was realy bad, allot of my clan members had 800+ ping on that day, i had 20/30 ping but the light whent green/red/green/red and the server reticle zoomed in very slow

  2. Will happen all the time, when you shoot with still rotating turret (At least for me it is so even with good ping times).
    This is easily explainable – enable server reticle and check out, where’s your aim circle in reality – most probably you will be surprised, but that is how internet works – server can’t get that turret turning info as fast as it draws that rotation, so in reality you’ll shoot way off the local aim circle.

    • Its easily explainable indeed – its WG server problem. If you have like 50 ping for example then there is no way for such a big difference between server and client reticle. Its a server lag or it is a bug, like with the arty shells and either way WG should fix it asap. This happened to me lot of times and it was only in 8.11 in last moth or so, its really annoying.

      • Same for me, but it is because of lagging.If you enable the server reticle you’ll see what I’m talking about.

  3. happens to me ALL the time. go around the corner, aim at someone, my gun shoots the corner…

    WG has to fix their server lag asap.

  4. ~40ms ping here and i have this very often. Very annoying especially when you peek around the corner to shoot and shell goes into building.

    • what exectly does that change?
      ill try though

      edit: okay it is explained somewhere below that post :)

    • Still happens with server reticle on. I have always used it, and it happens more and more since 8.10. Never had it before then.

      • Not if you use the old style server reticle where you have additional server side crosshair together with client side one.

  8. Yeah this is obviously clientside reticles. Basic story: Your turret/gun will always be pointing towards where your client thinks it is, but the server doesn’t necessarily need to agree with this. I have managed to have my gun and turret come in from one side while my aiming circle hops over from the OTHER side and they sort of collide into eachother to line up. This is especially easy to do with something like a KV-2, basically your aiming circle is always behind your turret rotation, so if you do it properly you can have your turret exceed 180 degrees while your reticle isn’t and they start rotating opposite of eachother.

    The video above is a normal consequence of not using server-side reticles and then being surprised over the results.

    • It is not just clientside reticle. I have used server reticle for years, and this just started happening to me since 8.10. Never before then.

  9. Well that is an easy case of server crosshair. There is a little german tutorial to show what happens when you are driving around a corner:(Some explaining in German at the beginning so i started it at 40 secs for all the others.
    http://youtu.be/ttOOZWjZXWo?t=40s

  10. He isn’t using SERVER RETICLE and with a little lag and some bad luck this can happen’. Nothing new..

  11. I agree with all the guys saying use server side crosshair but the problem is relatively new, at least for me. It was fine few weeks ago. Don’t know what they messed up again. Or is it my ISP?

  12. Play on low (2-4) fps and you won’t notice this. :D
    Or use autoaim at corners.

  13. This happens every time for me when there is LAG. This is no surprise. His turret may be in position, but the server reticule is not. It’s lagged behind.

  15. This has nothing to with the client. This is 100% a server-side issue (well, if you lag on top of that it won’t get better).

    Maybe Wargaming is thinking about an enhancement of the server tickrate ?

  16. ITS NOT UNUSUAL
    it happens 4-5 times /day so they did said its not bug its our internet connection =)))0 BULLSHIT !

    my country have the best internet over the europe ,and that bitch tells me that its my internet ,damn ruskies vokta drinky

    • but there is a big problem with that: server-side reticle was screwed up since full release (IIRC) of the game, the old reticle was NOT replacing the client one (and that is really important) and never was so twitchy like it is now (it’s unusable because of that).

  19. Hell, I can even get my reticle to be on the opposite site of the turret. As in the gun is facing forward, while the reticle is shown behind the tank :D

  20. SS, the explanation you put is not correct, i has nothing to do with server reticle “bloom” it has to do with bad netcode and bad design decisions on WG side (tradeoff that shouldn’t be allowed).
    with 200mS latency the “REAL” reticle LAGS by at least 5°+ on rotation, meaning that when you turn a corner or turn a fast turret(or double-traverse) you need to wait ~2S whilst aimed to really fire, or your shot WILL MISS by several tank lengths.
    It’s very noticeable on tournament when your teammates are spectating you and they go “WTF” when you turn a corner and shoot the wall 2 tanks to the left of your target(since spectators see the server side) whilst you where zeroed on the target.

    If you enable server reticle, you will see that your turret AIMS where your mouse wants to, but the REAL reticle takes 2+s to catch up and then start aiming(very noticeable on an IS-3, anything that traverses faster is unplayable essentially).

    this can also cause all kinds of “but i was zeroed and my shell flew outside reticle”, yeah, your client sight was zeroed for 2s, but the real one just arrived on target by the time you decide to fire=you fired on a full bloomed sight

  23. It happened to me a lot, my clan m8s calling me noob while I was saying that the reticle was right at the target with sever side enabled.

    Ridiculous WG as usual!

  25. It would be nice if they would work on this issue instead of nerfing all our tanks. And I just can’t wait for the new HD models so I can lower my win rate some more! Maybe some of you should buy more gold so WOT dev’s can afford to work on this!

  26. What seems odd in this video is that his ping is REALLY good (20-30) and yet his shot lagged way behind.

  28. The most fun part is when the server & client thinks you are turning the turret in different directions.