CGD Global Cool Down

[H_A_R_L_O_C_K]

For those who don't know what is it, it is the 0.5 seconds delay imposed by the game, between one shot and another.

That is to say that if you keep the button constantly down or press quickly, you will never make a  second shot before 0.5 seconds from the previous, and if you press again before that the 0.5 seconds are expiring, voilà,  a new 0.5 seconds  period will start and no shot (and so on).

Someone perhaps would have already noticed in the anomalous wave event, when on board to a ship that had manual cannons and torpedoes, often in a close engagement changing from cannons to torpedoes quickly, the torpedoes are not been fired, and continuing to press fire in a situation excited, we get the result above, we added 0.5 + 0.5 etc etc and fired nothing.

More often it happens in the game normally to those who use above all English ships with single torp launch, same result.

See for yourself this replay in the final with a close engagement with the moskva, not even a torpedo has fired.

This CGD should be corrected, at least when switching from cannons to torpedoes or vice versa, if not completely removed.

Thanks for the attention (and sorry for english).

20190818_114919_PBSC110-Minotaur_28_naval_mission.wowsreplay

[CptMinia]

Hello,

          I've changed your text colour so I and others using the dark theme can actually read your post.

 

Interesting stuff, I have noticed this strange behaviour in the past but I thought it was just because I lock my guns a lot and because I'm forgetful I mess up when I switch to torpedoes... so I've always assumed that was the reason for torpedoes not firing.

 

Also not particularly sure why you've tagged us moderators for this thread, not exactly like we can do anything about it because, well we're moderators. We're not WarGaming employees. I'll be happy to pass the thread on to hopefully get some answers, but I can't promise anything. I'm curious though as to why do you think this particular problem arises from the delay with single-fire? Are you able to replicate this problem? Have you contacted customer support or published a bug report?

 

Kind regards,

                       CptMinia

[H_A_R_L_O_C_K]

13 ore fa, CptMinia ha scritto:

Hello,

          I've changed your text colour so I and others using the dark theme can actually read your post.

 

Interesting stuff, I have noticed this strange behaviour in the past but I thought it was just because I lock my guns a lot and because I'm forgetful I mess up when I switch to torpedoes... so I've always assumed that was the reason for torpedoes not firing.

 

Also not particularly sure why you've tagged us moderators for this thread, not exactly like we can do anything about it because, well we're moderators. We're not WarGaming employees. I'll be happy to pass the thread on to hopefully get some answers, but I can't promise anything. I'm curious though as to why do you think this particular problem arises from the delay with single-fire? Are you able to replicate this problem? Have you contacted customer support or published a bug report?

 

Kind regards,

                       CptMinia

Hi and thank you for your answer,

 

I've tagged moderators and developers, posting here, after support answer inviting me doing this post, because they said, have not direct contact with developers, asking me addressing you.

Single fire is usually used with ships with single torpedos fire, in the case of a short engagement (like ad example an enemy catching you behind an island), you would be firing with cannons frequently and fast, trying to switch to single torps as soon the enemy would be in the right angle launch (single torps give you more possibility to hit especially in short distance. 

Of course, the problem is replicable, I've posted only the last time occurred yesterday.

Kind regards.