Jump to content


What the HELL is this?!

bugs fix this

  • Please log in to reply
25 replies to this topic

Steve_Mc_Gregory #1 Posted Mar 13 2017 - 19:30

    Corporal

  • -Players-
  • 20947 battles
  • 42
  • [MILKY] MILKY
  • Member since:
    10-02-2015
HOW?! - https://goo.gl/H3UHMV

Hurk #2 Posted Mar 13 2017 - 19:31

    Major

  • Players
  • 43029 battles
  • 12,935
  • [KGR] KGR
  • Member since:
    09-30-2012

google "world of tank ghost shells". thats how. 

http://ritastatusrep...-explained.html

Short description

The problem is not the servers nor the clients, it's actually a BigWorld engine fault process that begins when the server fails to calculate a penetration value. In layman terms, here's the process (missing a few filler elements such as shell travel time, tank velocity, gun arc, type of shells, etc etc etc. for the sake of simplicity):

- client is driving
- server receives the "drive command" replies back "you are now driving" and sometime later it determines there is an enemy  tank in sight that the client can see, so it sends the data back saying "you have a tank in sight"
- client now sees enemy tank
- server acknowledges the tank is there and all the aiming mechanics occur 
- client shoots at tank
- server acknowledges the client has shot and triggers the reload timer for the client while also processing the penetration value of the shell, angle, RNG (+/-25%), area to damage and determines, if theres a penetration/ricochet or damage to any internal modules (shoot commander's hatch, driver dies! *trollface*) or (shoot driver's compartment, suddenly tank gets tracks damage *trollface v2*) (Insider: actually this is explained by ricochets inside the tank, but ill leave it at that).
- Bigworld engine which is running along the streamline of the server fails to process the client request and delivers a "null"
- Server: hey, but I just sent the data!
- Bigworld: yes and I say it's null, now obey!
- Server: ??? okay ._.

Server sends the ping back with null value: "lel, tank wasn't there". Client displays a ghost shell event in return.
 


Edited by Hurk, Mar 13 2017 - 19:33.


Korperal #3 Posted Mar 13 2017 - 19:32

    Corporal

  • Players
  • 7536 battles
  • 96
  • Member since:
    01-22-2013
You weren't aimed at him. . .lol. Just because your barrel was going through the tank doesn't mean that's where you were aimed.

Steve_Mc_Gregory #4 Posted Mar 13 2017 - 19:32

    Corporal

  • -Players-
  • 20947 battles
  • 42
  • [MILKY] MILKY
  • Member since:
    10-02-2015

View PostHurk, on Mar 13 2017 - 19:31, said:

google "world of tank ghost shells". thats how. 

 

WHY?! Ghost shells were existing in 8.x clients and still isnt fixed?

Hurk #5 Posted Mar 13 2017 - 19:35

    Major

  • Players
  • 43029 battles
  • 12,935
  • [KGR] KGR
  • Member since:
    09-30-2012

because the world server is still a separate process and it still fails to calculate a value in time occasionally.

every 1 in 1,000,000 times that happens, its just not a big deal... heck, there is a good chance it happens on a shell that didnt matter anyway. (like idiots shooting at the start of a battle)

 

also... its not a "client" problem. thus, no change.


Edited by Hurk, Mar 13 2017 - 19:36.


Patonb #6 Posted Mar 13 2017 - 19:36

    Major

  • Players
  • 26205 battles
  • 4,548
  • Member since:
    06-05-2012
With the BS packet loss and ping spikes this last week everything and anything is now possible.

Gurdy2383 #7 Posted Mar 13 2017 - 19:58

    First lieutenant

  • Players
  • 44374 battles
  • 960
  • [NA-CL] NA-CL
  • Member since:
    11-05-2012

While Hurk has done an excellent job of explaining ghost shells, I think in this instance this isn't a ghost shell (at least not in the typical sense).

 

This is a known issue especially on the backs of German TD's where your gun barrel goes entirely inside of the other tank. Since the game looks at penetrations occurring when a shell penetrates the armor, and in these cases no shell is going through the armor since it's actually originating inside of the tank, the game doesn't recognize the shot as having ever hit anything.

 

This happens more commonly on German TD's because people flank them regularly, and when they get to the rear they find a big flat rear end that when they push up against it it causes the entire gun to go inside of that tank.

 

One's entire gun must be inside the enemy tank for this to occur because the game considers shots as originating at the very beginning of the barrel not the end.

 



GeorgePreddy #8 Posted Mar 13 2017 - 20:04

    Major

  • Players
  • 14282 battles
  • 5,503
  • [L_LEG] L_LEG
  • Member since:
    04-11-2013
. never mind

geeknik #9 Posted Mar 13 2017 - 20:05

    Corporal

  • Players
  • 18853 battles
  • 82
  • Member since:
    04-13-2011
I don't see an issue here myself. The game shouldn't allow your gun to go inside objects like tanks and buildings in the first place.

GeorgePreddy #10 Posted Mar 13 2017 - 20:08

    Major

  • Players
  • 14282 battles
  • 5,503
  • [L_LEG] L_LEG
  • Member since:
    04-11-2013

View Postgeeknik, on Mar 13 2017 - 16:05, said:

I don't see an issue here myself. The game shouldn't allow your gun to go inside objects like tanks and buildings in the first place.

 

They tried doing it that way in earliest testing period.... it didn't work well at all, that's why the barrel is not a solid object.

D1rkjr #11 Posted Mar 13 2017 - 20:22

    Sergeant

  • Players
  • 20187 battles
  • 191
  • [GOONZ] GOONZ
  • Member since:
    11-26-2012
The barrel should be part of the collision model. There are limitations on real tanks in close quarters that these tanks don't have because their gun traverse can't be blocked. 

Jayrod413 #12 Posted Mar 13 2017 - 20:32

    First lieutenant

  • Players
  • 11454 battles
  • 530
  • [NET] NET
  • Member since:
    07-09-2013

View Postgeeknik, on Mar 13 2017 - 19:05, said:

I don't see an issue here myself. The game shouldn't allow your gun to go inside objects like tanks and buildings in the first place.

 

Have fun bringing any long barrel to himmelsdorf

Urdr #13 Posted Mar 13 2017 - 20:49

    Major

  • Players
  • 38388 battles
  • 3,555
  • Member since:
    12-07-2012

Ahahah

That's is a noob making me laugh

Thanks :teethhappy:

Rainbows



Kladston #14 Posted Mar 13 2017 - 21:13

    Corporal

  • -Players-
  • 30466 battles
  • 57
  • [RTL] RTL
  • Member since:
    05-28-2015

View PostSteve_Mc_Gregory, on Mar 13 2017 - 19:32, said:

 

WHY?! Ghost shells were existing in 8.x clients and still isnt fixed?

 

​it is working as program, just another way for WG to insure which team wins.  I have at least 50 to 60 ghost shots a day. JUst spend more money and kiss their butts a little harder, ]]

riff_ #15 Posted Mar 13 2017 - 21:15

    Major

  • Players
  • 24376 battles
  • 7,149
  • Member since:
    08-02-2013

View PostD1rkjr, on Mar 13 2017 - 14:22, said:

The barrel should be part of the collision model. There are limitations on real tanks in close quarters that these tanks don't have because their gun traverse can't be blocked. 

 

​No.  No it should not be. 

This game has little to do with "real" tanks.



Cheekyman #16 Posted Mar 13 2017 - 21:26

    Captain

  • Players
  • 45787 battles
  • 1,807
  • [VILIN] VILIN
  • Member since:
    04-14-2011
might be that the aiming reticle was actually aiming down into the ground and the shot went underneath the tank but the external view was not showing it properly, this happens a lot in close quarters (weird misses) if the user does not use sniper mode. the external reticle when manually aimed for reasons unknown to me does not always show exactly where the tank is aiming.

Scorpiany #17 Posted Mar 13 2017 - 21:43

    Major

  • Community Contributor
  • 28623 battles
  • 10,199
  • [N1NJA] N1NJA
  • Member since:
    06-27-2013

It's a problem with the German Tank Destroyers - You cannot actually do any damage to the rear of their vehicles while face-hugging their booties if your barrel is going through their tank.

 

This is not a problem with any other kind of tank in my experience; most often a problem with German Tank Destroyers. They broke it a while back during a patch that was not even related to the German TD's, yet they still managed to mess it up.

 

The Jg.Pz. E-100 is the most infamous example of this issue, but it can and will occur with other German TD's as well.

 

Because WarGaming.



scyorkie #18 Posted Mar 13 2017 - 21:57

    Major

  • Players
  • 60835 battles
  • 2,555
  • [RSSF] RSSF
  • Member since:
    10-26-2011
Interesting, that penetration-vs-armor indicator.

BackwoodsLegit #19 Posted Mar 13 2017 - 21:58

    Sergeant

  • Players
  • 23183 battles
  • 152
  • [L13TH] L13TH
  • Member since:
    12-14-2013

View PostPatonb, on Mar 13 2017 - 18:36, said:

With the BS packet loss and ping spikes this last week everything and anything is now possible.

 

It's been a joke.  I keep jamming my keyboard when my tank turns excessively or keeps driving after i've let off the button.  Let alone the firing delay and ghost shells...

 

#lotsofraging



jester350 #20 Posted Mar 13 2017 - 22:00

    Corporal

  • -Players-
  • 16179 battles
  • 57
  • [C_O_G] C_O_G
  • Member since:
    01-12-2015

Yes. We tested the Germany TD glitch in the training room. Your actually lucky it even fired. Some tanks won't even fire if the mantle is pressed into the back of the Germans. It's because of the flat and sometime back sloped rear armor. TD players know this, that's why he backed you up a slope. 

 







Also tagged with bugs, fix, this

1 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users