Jump to content
Forum Shutdown - July 28, 2023 Read more... ×
Forum Shutdown - July 28, 2023 Read more... ×
You need to play a total of 20 battles to post in this section.
Cats_Paw

I think Aoba is bugged/broken after the last patch?

11 comments in this topic

Recommended Posts

3
[-NYA-]
Members
28 posts
10,176 battles

Let me preface, I'm aware of how threads like this are usually perceived.  Something along the lines of "you're not aiming right" or " you just had bad RNG rolls" right?  But let me plead my case and hope a Dev takes a look.

 

I just played multiple matches in my Aoba where my ship was completely, totally ineffective.  I could not damage any ship, at any range, under any condition.  Case in point, I just played a match on Fault Line where I had a perfect sweetheart shot on an Omaha who had beached himself to dodge torps.  He was 3.8km away from me.  I hit him dead in his citadel with all 6 rounds (yes, I'm quite certain I hit the citadel, I've defeated Omahas plenty of times before).  I got 1,000 damage off the whole volley.  A Konisburg is sailing dead broadside to me 7km away, I hit him in his citadel area twice with full salvos.  I get 940 damage each time.  I fired 24 rounds into a Bogue, 6 volleyes off the bow guns, into the citadel area and got exactly 940 damage each and every time.  940 damage, over and over again while hitting citadel hit boxes on the waterline.

 

And before somebody says anything, yes I was firing AP the whole time.  Yes I was aiming near the waterline.  Yes the shots were striking the ships in the right place. 

 

This is just a few examples.  The entire evening my ship was incapable of doing more than 1,000 damage to anything under circumstances where normally I would rack up big damage.  I am completely confident it was not my shooting, something felt extremely wrong with the ship.  Both hands completely tied behind my back is what it felt like.  The only time I did any damage at all was hitting destroyers with HE.

 

It feels like the AP krupp value of Aoba got set to zero by accident or something.  Is anybody else experiencing this in this ship?  For further evidence I was engaged with several Aobas who shot me and did absolutely no damage to my ship either.  My division mate got hit soundly by an Aoba in his Nurnberg and only suffered 1,000 damage, that same suspicious number.

 

Thoughts?  Hopefully a dev or tester can look into this?

Edited by Cats_Paw
  • Cool 1

Share this post


Link to post
Share on other sites
Members
245 posts
1,619 battles

Hey, a forum complaint that isn't made by a [edited], what do you know?! It's entirely POSSIBLE, friend, but you'd still have to send in a replay for them to take you seriously.

Share this post


Link to post
Share on other sites
Beta Testers
1,821 posts
10,838 battles

A reply would help verify things.

 

But due to the consistency of the issue, perhaps you were having issues with desync? You might have seen your shells hitting citadel, but they might have been all been overpenning the stern according to the server.

  • Cool 1

Share this post


Link to post
Share on other sites
522
[IN3PT]
Beta Testers
1,703 posts
6,531 battles

2 AP overpens happening simultaneously would result in hits for 940 damage, a single Aoba round hitting for 470 in the case of an over pen. 

 

I'm inclined to go with Kenjister's opinion. Most likely you're having some sort of de-sync issue and not hitting the Omahas/N-bergs where you think/visually see yourself hitting them. 

 

As you're getting overpens, I'd doubt your Krupp value accidentally got zeroed, as that would cause bounces.

 

Without a replay, we can't be certain (it's unreal that WG hasn't made replays able to be activated with a tick-box yet), but I'm willing to bet your issue is de-sync causing you to hit non-citadel areas as far as the server is concerned.

 

Share this post


Link to post
Share on other sites
492
[STW]
Beta Testers
1,984 posts
10,616 battles

Let me preface, I'm aware of how threads like this are usually perceived.  Something along the lines of "you're not aiming right" or " you just had bad RNG rolls" right?  But let me plead my case and hope a Dev takes a look.

 

I just played multiple matches in my Aoba where my ship was completely, totally ineffective.  I could not damage any ship, at any range, under any condition.  Case in point, I just played a match on Fault Line where I had a perfect sweetheart shot on an Omaha who had beached himself to dodge torps.  He was 3.8km away from me.  I hit him dead in his citadel with all 6 rounds (yes, I'm quite certain I hit the citadel, I've defeated Omahas plenty of times before).  I got 1,000 damage off the whole volley.  A Konisburg is sailing dead broadside to me 7km away, I hit him in his citadel area twice with full salvos.  I get 940 damage each time.  I fired 24 rounds into a Bogue, 6 volleyes off the bow guns, into the citadel area and got exactly 940 damage each and every time.  940 damage, over and over again while hitting citadel hit boxes on the waterline.

 

And before somebody says anything, yes I was firing AP the whole time.  Yes I was aiming near the waterline.  Yes the shots were striking the ships in the right place. 

 

This is just a few examples.  The entire evening my ship was incapable of doing more than 1,000 damage to anything under circumstances where normally I would rack up big damage.  I am completely confident it was not my shooting, something felt extremely wrong with the ship.  Both hands completely tied behind my back is what it felt like.  The only time I did any damage at all was hitting destroyers with HE.

 

It feels like the AP krupp value of Aoba got set to zero by accident or something.  Is anybody else experiencing this in this ship?  For further evidence I was engaged with several Aobas who shot me and did absolutely no damage to my ship either.  My division mate got hit soundly by an Aoba in his Nurnberg and only suffered 1,000 damage, that same suspicious number.

 

Thoughts?  Hopefully a dev or tester can look into this?

 

this.... Thread feels familiar...

Share this post


Link to post
Share on other sites
332
Beta Testers
2,580 posts
4,750 battles

Can confirm Myoko AP still citadels the crap out of Aoba anyway :playing:

 

Share this post


Link to post
Share on other sites
Beta Testers, In AlfaTesters
305 posts
135 battles

Thoughts?  Hopefully a dev or tester can look into this?

 

shot-16.03.25_19.05.47-0307.jpg

Seems to be working fine here. As mentioned by others in this thread, the most likely cause was a case of de-sync

shot-16.03.25_19.05.47-0307.jpg

Share this post


Link to post
Share on other sites
3
[-NYA-]
Members
28 posts
10,176 battles

Appreciate the input so far from everybody.  Sadly I don't have a replay, I've never really had a reason to capture replays until now.  It was really the shooting at the Bogue that convinced me something was weird.  I've been in that exact same situation before, firing the same shots and getting 4-8k damage rolls on average.  Given the angle and range I don't think I should have been overpenning the Bogue.  Plus even on an over-pen a shell going through the citadel still does full damage is my understanding.

 

If we assume de-sync is the issue, how does one fix that?  Is it limited to just that client session and things will be correct the next time I launch the game?  Or would it be advisable to re-install the game?  I know lots of people tend to get weird bugs after multiple patches.  Hasn't happened to me yet but maybe here's my first time.

 

It was so frustrating because they would have been great matches, but I felt like the ship was shooting blanks the whole time.

Edited by Cats_Paw

Share this post


Link to post
Share on other sites
3
[-NYA-]
Members
28 posts
10,176 battles

Well, I solved the problem by finally unlocking Myoko.  Very first match I did all kinds of damage with AP/Cits.  Guns felt normal like I remember them being (since Myoko and Aoba have the exact same guns).  I'm still convinced something weird is going on with Aoba, maybe it's just MY Aoba due to de-sync or something else, but moving on seems to be the solution regardless.

Edited by Cats_Paw

Share this post


Link to post
Share on other sites

  • Recently Browsing   0 members

    No registered users viewing this page.

×