Jump to content
You need to play a total of 50 battles to post in this section.
BoozyFloosy

Someone please explain

21 comments in this topic

Recommended Posts

[BOOBS]
Players
21 posts

Ok so without any "L2P" loz  can someone please explain how 5 Type 93 Mod3 torp hits from a Shimakazi can only do 16k dmg? 

 

It was an enemy shim I hit.   We exchanged torps at 3km...I sunk he didnt.

 

Torps-dmg-wtf.jpg

Share this post


Link to post
Share on other sites
[W-C]
Beta Tester, Players, In AlfaTesters
2,480 posts
6,696 battles

Damage saturation, torpedo belt, RNG

  • Cool 1

Share this post


Link to post
Share on other sites
[W-C]
Beta Tester, Players, In AlfaTesters
2,480 posts
6,696 battles
Just now, BoozyFloosy said:

Seriously? 5 torps into a shim at 3km? Nah

 

1 minute ago, domen3 said:

Damage saturation

 

Yes

Share this post


Link to post
Share on other sites
[W-C]
Beta Tester, Players, In AlfaTesters
2,480 posts
6,696 battles
1 minute ago, BoozyFloosy said:

I understand but that was 5 torps into his broadside at 3km.  They hit stem to stern

Provide us with a replay so we may analyse it

Share this post


Link to post
Share on other sites
Players
2,169 posts
1 minute ago, domen3 said:

Damage saturation, torpedo belt, RNG

 

DD's have no torpedo belt to speak of.

Was 1 hit, so how could that be saturation?

 

I've seen odd stuff like this myself and I believe they were even looking into weird damage results for torp hits on DD's, but I can't find where I read it a few weeks ago.

Share this post


Link to post
Share on other sites
[RONIN]
Beta Tester
3,058 posts
6,109 battles

Although a ship has a certain amount of HP, it is actually split into 4 sections (bow, aft, structure, centre). Of those, the bow/aft/structure have limits of how much damage they can take. Any damage beyond this limit is ignored. 

 

Its therefore possible to have the first torp hit the bow and do 16k damage which fully satuarates it, and the other 4 torps also hit the bow and do nothing

Share this post


Link to post
Share on other sites
[SCRUB]
Players
7,998 posts
10,396 battles

Let me guess, it went something like this:

 

1mALf7F.gif

 

Damage saturation.

Share this post


Link to post
Share on other sites
[BOOBS]
Players
21 posts

I dont have a replay, unless they are enabled by default...normally I couldnt care less but I am simply curious how on earth this could happen.

 

My best guess was a bug..he hits repair as the first torp hits and there is some kind of race hazard meaning the dmg form the other 4 torps doesnt register in a tiny window of time.

 

 

Share this post


Link to post
Share on other sites
[W-C]
Beta Tester, Players, In AlfaTesters
2,480 posts
6,696 battles
2 minutes ago, BeauNidl3 said:

DD's have no torpedo belt to speak of.

I missread "shim" as "ship"

2 minutes ago, BeauNidl3 said:

Was 1 hit, so how could that be saturation?

It was 5 hits

Share this post


Link to post
Share on other sites
[BOOBS]
Players
21 posts
1 minute ago, Aotearas said:

Let me guess, it went something like this:

 

1mALf7F.gif

 

Damage saturation.

Pretty certain they hit along him.  Just seemed like a bug.. I have actually managed to stop incoming dmg from a salvo by repairing the instant the fist shot hits which seems to prevent the other shots causing dmg within a short time window

Share this post


Link to post
Share on other sites
[BLITZ]
Modder
4,063 posts
7,474 battles
1 hour ago, BoozyFloosy said:

My best guess was a bug

and my guess is, that you were just wrong

 

now proof prove me wrong

Edited by principat121

Share this post


Link to post
Share on other sites
Players
2,169 posts
12 minutes ago, domen3 said:

I missread "shim" as "ship"

It was 5 hits

 

Ah I failed to see the 5 hits implied.

That said 1 hit from a Shima torpedo should do enough to outright kill another Shima.

Share this post


Link to post
Share on other sites
[KAKE]
Players
1,335 posts
3,588 battles
56 minutes ago, BoozyFloosy said:

I understand but that was 5 torps into his broadside at 3km.  They hit stem to stern

Well, a couple of possible explanations:

a) your memory is playing tricks on you

b) what your client drew on your screen isn't the same as what happened on the server

 

Now, I'm not very familiar with the WoWS game engine in particular. But for multiplayer games in general, the game clients tend to do a fair bit of prediction in order to compensate for the latency between client and server. E.g. the client will make a prediction of where any given object is going to be based on its last reported position and direction of movement from the server, and then draw it where it thinks it is instead of displaying a time-delayed snapshot of the server state. And that's usually fine, but it does some times lead to seemingly wonky results where you get nailed by a headshot when your own screen clearly shows that you had ducked behind cover (because your own client predicted that's what was going to happen before the server state overruled it).

 

That's just the nature of any multiplayer game, and it might be the explanation here as well. I.e. your game client predicted that all five torpedoes would hit different parts of the hull, but the game state on the server had all torps hitting the same saturated section.

Share this post


Link to post
Share on other sites
[AAO]
Players
1,997 posts
10,201 battles

Also, can we get a little cheer for wargaming for explaining their own game so well to everyone, that we regularly this question about a very basic game mechanic!

 

:Smile_medal::Smile_medal::Smile_medal:

  • Cool 1

Share this post


Link to post
Share on other sites

  • Recently Browsing   0 members

    No registered users viewing this page.

×