Will not play a broken game

[RenamedUser_92906789]

 

 

Limiting to farming snowflakes in coop.

 

Game is unplayable.

 

 

[Pukovnik7]

Yeah, I uninstalled it today. Installed World of Tanks instead, though I will see how frequently I will be playing that game either. I think I will mostly be writing instead.

[Itwastuesday]

The heck? I can't even tell what's supposed to be different about the camera but certainly it was worth breaking gunnery for :D

[JohnMac79]

6 minutes ago, Pukovnik7 said:

Installed World of Tanks instead...

 

[HARBINGER_OF_SKULLS]

18 minutes ago, RenamedUser_92906789 said:

Limiting to farming snowflakes in coop.

But how? Ramming? Because with gunnery being a lottery and unguided torpedoes conventiently spreading around targets (if those targets do not smoothly dodge by using divine precognition)... you need to earn some BXP. 

[OldSchoolFrankie]

I look forward to when someone accuses Wargaming of not playing/testing their own game and then they vehemently deny it again.  Yoyo, all right!

Maybe offer Flamu to become a CC because he's really doing something useful for the community.. oh wait.. Players who are also critical of the game are not wanted.

 

However, mistakes can always happen, but the frequency is impressive Wargaming.

 

[Karkong_the_Impaler]

@Seraphice

@YabbaCoe

 

Care to comment?

[Guest]

Great, even more shells falling short, just like the game in general.

[SV_Kompresor]

I mean....if you're dumb enough to try and aim by jerking your mouse like that, that's on you.

[JohnMac79]

2 minutes ago, SV_Kompresor said:

I mean....if you're dumb enough to try and aim by jerking your mouse like that, that's on you.

 

You are not really defending WG potato coding are you?

[SV_Kompresor]

1 minute ago, JohnMac79 said:

 

You are not really defending WG potato coding are you?

No, however being stupid is no excuse. Nobody plays by jerking their camera like that which means that this problem does not exist unless you're the one that decides that it does.

[JohnMac79]

Just now, SV_Kompresor said:

No, however being stupid is no excuse. Nobody plays by jerking their camera like that which means that this problem does not exist unless you're the one that decides that it does.

 

I wouldnt call it stupid to expose a bug and show how it is easily recreated. Sounds more like playing the player rather than the ball...

[steve665]

Try playing dd, you are "jerking" your camera much faster than this in the heat of battle.

This fix is really unbelievable.

[Guest]

1 minute ago, SV_Kompresor said:

No, however being stupid is no excuse. Nobody plays by jerking their camera like that which means that this problem does not exist unless you're the one that decides that it does.

In the heat of the battle you frequently change targets, mouse positions, whatever. Naturally you do not first aim for the water of course and then on to the ship. But imagine fastly switching from one (maybe a dead) ship to another live one, or from no taget being visible to a suddenly spotted target, or you fastly want to aim at a certain part of the ship because of saturation. All these attempts can be corrupted by WG's potato code. The video simply reveals the basic problem.

[Mad_Dog_Dante]

7 minutes ago, SV_Kompresor said:

No, however being stupid is no excuse. Nobody plays by jerking their camera like that which means that this problem does not exist unless you're the one that decides that it does.

Not exactly like that sure, because he is showing what actually happens. But I know for sure there were plenty of situations for me when fighting multiple targets or threats that a pot shot and quickly moving the mouse to look at other stuff was all too common. I appreciate the Flam is a jerk knee reaction but this is a very poor fix, hopefully temporary.

[Karasu_Browarszky]

Why don't the ships firing at me ever have any issues....

[SV_Kompresor]

4 minutes ago, Von_Pruss said:

In the heat of the battle you frequently change targets, mouse positions, whatever. Naturally you do not first aim for the water of course and then on to the ship. But imagine fastly switching from one (maybe a dead) ship to another live one, or from no taget being visible to a suddenly spotted target, or you fastly want to aim at a certain part of the ship because of saturation. All these attempts can be corrupted by WG's potato code. The video simply reveals the basic problem.

You don't do it by jerking the camera like that. Or maybe some do (for no reason) which is why they miss so much. A bug is a bug yes, but this is one of those that might only ever noticable in those quickshot CSGO moments that rarely happens where you have to snap shot a ship that appeared for just a second. I'm more poking fun at everybody going "yet another game breaking bug" like the railgun bug was.

 

[Karasu_Browarszky]

Just now, SV_Kompresor said:

You don't do it by jerking the camera like that. Or maybe some of you do which is why you miss so much. A bug is a bug yes, but this is one of those that might only ever noticable in those quickshot CSGO moments that rarely happens where you have to snap shot a ship that appeared for just a second. I'm more poking fun at everybody going "yet another game breaking bug" like the railgun bug was.

 

 

Yes, but.. if there is a delay, even a minute change may throw your aim off. Or a readjustment.

[SV_Kompresor]

Just now, Karasu_Hidesuke said:

 

Yes, but.. if there is a delay, even a minute change may throw your aim off. Or a readjustment.

True. I'm just saying that a bug that isn't noticable (or is barely noticable) unless you specifically try to do it, it's not a game breaking one. Though it should obviously still get fixed.

[tocqueville8]

This explains how I could miss a broadside Kleber at 5 km

 

38 minutes ago, SV_Kompresor said:

I mean....if you're dumb enough to try and aim by jerking your mouse like that, that's on you.

 

Flamu exaggerates the "jerking" for clarity, but this bug has huge implications even for small aiming corrections, the kind that should make you hit the waterline (citadels) instead of splashing short.

 

See: https://www.reddit.com/r/WorldOfWarships/comments/xf2x33/i_hate_this_bug_so_much_it_has_caused_me_so_much/

 

That's not dispersion. Well, not entirely.

Notice the minimap circle: the St Vincent player raised his aim before shooting, but it clearly didn't register, it wasn't updated in time. That's not a "quickshot": the adjustment is small, but decisive.

 

This is the worst bug since the "Coriolis torpedoes"  a year ago.

[tocqueville8]

I wonder which classes aren't affected by this...

[Karkong_the_Impaler]

28 minutes ago, SV_Kompresor said:

You don't do it by jerking the camera like that.

When I take a pot shot of opportunity at someone, I sure do. I don't aim for half a second before I click.

[tocqueville8]

35 minutes ago, SV_Kompresor said:

True. I'm just saying that a bug that isn't noticable (or is barely noticable) unless you specifically try to do it, it's not a game breaking one. Though it should obviously still get fixed.

 

Doesn't it mean that any aiming correction in the last second (or so) is void?

 

You go for the citadel.

The guy starts turning just before you finish reloading.

You aim higher to at least hit the superstructure...but you don't track his movements for the whole delay (even just one second is a lot, when all you need is a small adjustment and your target turns at several degrees per second), so you shoot on the hull and only get some bounces.

The salvo is ruined, now wait another 30 seconds.

 

The previous "railgun" bug was weird and, I'm assuming (I never tried to replicate it), difficult to abuse in the middle of the game.

But this can affect every single salvo you shoot, especially at some range

[UnderDuress]

49 minutes ago, SV_Kompresor said:

I mean....if you're dumb enough to try and aim by jerking your mouse like that, that's on you.

Every shot you take is aimed at a point a bit before you pressed the fire button.

[Karasu_Browarszky]

7 minutes ago, tocqueville8 said:

 

Doesn't it mean that any aiming correction in the last second (or so) is void?

 

You go for the citadel.

The guy starts turning just before you finish reloading.

You aim higher to at least hit the superstructure...but you don't track his movements for the whole delay (even just one second is a lot, when all you need is a small adjustment and your target turns at several degrees per second), so you shoot on the hull and only get some bounces.

The salvo is ruined, now wait another 30 seconds.

 

The previous "railgun" bug was weird and, I'm assuming (I never tried to replicate it), difficult to abuse in the middle of the game.

But this can affect every single salvo you shoot, especially at some range

 

I'm trying to think how I aim, and I aim differently at targets that are more or less broadside on from those targets that are at an angle, and then again differently at targets that are changing their course. Typically, I keep moving and adjusting the aim incrementally when trying to decide on how much to lead, and how much to adjust for the correct angle.