Jump to content


Examples of WG ignoring feedback


  • Please log in to reply
48 replies to this topic

F2PEXP #1 Posted 04 April 2018 - 06:33 PM

    Private

  • Player
  • 2910 battles
  • 41
  • Member since:
    03-26-2018

so in test server there was an issue of tank hits not giving a sound register so you did not realise you were being shot, WG say they aware but hey presto upon release of 1.0 still got same issue, and hey presto today still same issue

 

when WG going to listen to the constructive comments and sort this issue out?



Slyspy #2 Posted 04 April 2018 - 06:35 PM

    Field Marshal

  • Player
  • 14186 battles
  • 16,480
  • [T-D-U] T-D-U
  • Member since:
    12-07-2011
I expect that bug reports are in fact listened to and that deadlines are deadlines. 

F2PEXP #3 Posted 04 April 2018 - 06:41 PM

    Private

  • Player
  • 2910 battles
  • 41
  • Member since:
    03-26-2018

View PostSlyspy, on 04 April 2018 - 06:35 PM, said:

I expect that bug reports are in fact listened to and that deadlines are deadlines. 

 

​listened to , and ignored

 



Erwin_Von_Braun #4 Posted 04 April 2018 - 06:45 PM

    Brigadier

  • Player
  • 36880 battles
  • 4,475
  • [T-D-U] T-D-U
  • Member since:
    01-25-2014

View PostF2PEXP, on 04 April 2018 - 05:41 PM, said:

 

​listened to , and ignored

 

 

Have a good read through these forums - everything is broken &/or OP and all feedback is 'ignored'.

I doubt you are being ignored as such, just that the problem isn't that high on their list of problems.



Steve8066 #5 Posted 04 April 2018 - 06:46 PM

    Warrant Officer

  • Player
  • 10691 battles
  • 687
  • Member since:
    10-06-2015

View PostSlyspy, on 04 April 2018 - 06:35 PM, said:

I expect that bug reports are in fact listened to and that deadlines are deadlines. 

 

deadlines that are adhered to even tho the product is faulty does more harm to a company than a deadline delayed in order to release a working product. 1.0 is shoddy, broken and a disgrace to be passed off as `working`.



Azazel_and_chill #6 Posted 04 April 2018 - 06:48 PM

    Private

  • Player
  • 9249 battles
  • 40
  • Member since:
    12-16-2015

View PostErwin_Von_Braun, on 04 April 2018 - 06:45 PM, said:

I doubt you are being ignored as such, just that the problem isn't that high on their list of problems.

This. For example the massive game lag at the beginning was a big issue when I crashed my tank because of it. And guess what. Its fixed now. The fact that you cant hear 1 hit in 100 isnt that important and can wait.



Erwin_Von_Braun #7 Posted 04 April 2018 - 06:49 PM

    Brigadier

  • Player
  • 36880 battles
  • 4,475
  • [T-D-U] T-D-U
  • Member since:
    01-25-2014

View PostSteve8066, on 04 April 2018 - 05:46 PM, said:

 

deadlines that are adhered to even tho the product is faulty does more harm to a company than a deadline delayed in order to release a working product. 1.0 is shoddy, broken and a disgrace to be passed off as `working`.

 

Works perfectly for me and many others.:confused:
 

View PostAzazel_and_chill, on 04 April 2018 - 05:48 PM, said:

This. For example the massive game lag at the beginning was a big issue when I crashed my tank because of it. And guess what. Its fixed now. The fact that you cant hear 1 hit in 100 isnt that important and can wait.

 

Indeed, bugs are to be expected with such a massive update but, to their credit, they have been minimal and they do seem to be on the case :)
 

Steve8066 #8 Posted 04 April 2018 - 06:51 PM

    Warrant Officer

  • Player
  • 10691 battles
  • 687
  • Member since:
    10-06-2015

View PostErwin_Von_Braun, on 04 April 2018 - 06:49 PM, said:

 

Works perfectly for me and many others.:confused:

 

it `works` for me, but it doesnt mean it was fit for release. Hit boxes too big, hit boxes not existing, no hit detection just HP bar decreasing with no visible signs/sounds of why, etc. etc. etc. Its far from working perfectly.

Slyspy #9 Posted 04 April 2018 - 07:01 PM

    Field Marshal

  • Player
  • 14186 battles
  • 16,480
  • [T-D-U] T-D-U
  • Member since:
    12-07-2011

View PostSteve8066, on 04 April 2018 - 06:51 PM, said:

 

it `works` for me, but it doesnt mean it was fit for release. Hit boxes too big, hit boxes not existing, no hit detection just HP bar decreasing with no visible signs/sounds of why, etc. etc. etc. Its far from working perfectly.

 

The only issue I've had is this missing hit sound every now and then. The hit box thing has been a common fault through out the life of this game and is nothing new. Nothing here is a big enough problem to warrant holding up or cancelling a major update.

Erwin_Von_Braun #10 Posted 04 April 2018 - 07:01 PM

    Brigadier

  • Player
  • 36880 battles
  • 4,475
  • [T-D-U] T-D-U
  • Member since:
    01-25-2014

View PostSteve8066, on 04 April 2018 - 05:51 PM, said:

 

it `works` for me, but it doesnt mean it was fit for release. Hit boxes too big, hit boxes not existing, no hit detection just HP bar decreasing with no visible signs/sounds of why, etc. etc. etc. Its far from working perfectly.

 

I can't recall many games at all that work perfectly?

Seriously, I've been gaming for 30+ years and I'm sat here struggling to think of any game I have played that was, in some way, flawed.

Whether it is through bad design or otherwise - and especially in recent times, a few big games from so called Triple A Developers were released littered with bugs &/or flaws.

Anyone who played Batman Arkham Knight when it was released will know what I'm talking about :trollface:



jabster #11 Posted 04 April 2018 - 07:37 PM

    Field Marshal

  • Beta Tester
  • 12526 battles
  • 22,494
  • [WSAT] WSAT
  • Member since:
    12-30-2010

View PostSteve8066, on 04 April 2018 - 05:46 PM, said:

 

deadlines that are adhered to even tho the product is faulty does more harm to a company than a deadline delayed in order to release a working product. 1.0 is shoddy, broken and a disgrace to be passed off as `working`.

 

So you’ve not been able to play the game then. I’d raise a ticket if I was you.

Strappster #12 Posted 04 April 2018 - 07:44 PM

    General

  • Player
  • 23695 battles
  • 8,888
  • [WJDE] WJDE
  • Member since:
    10-20-2015
Warboats released a video today detailing the steps they took in dealing with a bug that emerged in the 0.7.2 patch, where after about a dozen battles your FPS would drop to 10-20. In addition to apologising for the error, they're giving everyone who played between 0.7.2 and 0.7.3 three days premium time as compensation, which you can choose when to activate. I know Warboats is produced by a different team but it's a welcome sign of feedback and acknowledgement.

F2PEXP #13 Posted 04 April 2018 - 07:47 PM

    Private

  • Player
  • 2910 battles
  • 41
  • Member since:
    03-26-2018

it is not about the bug

 

it is about being informed about the bug in first test, then second test and still not sorting it before they release

 

an unknown bug happens, a bug reported and acknowledged is an example of WG ignoring feedback, that's my point



Shaade_Silentpaw #14 Posted 04 April 2018 - 07:51 PM

    Staff Sergeant

  • Player
  • 21570 battles
  • 354
  • Member since:
    10-12-2015
According to WG, EU players are "Drama Queens" - so yeah, they don't listen much to what we say.

jabster #15 Posted 04 April 2018 - 07:53 PM

    Field Marshal

  • Beta Tester
  • 12526 battles
  • 22,494
  • [WSAT] WSAT
  • Member since:
    12-30-2010

View PostF2PEXP, on 04 April 2018 - 06:47 PM, said:

it is not about the bug

 

it is about being informed about the bug in first test, then second test and still not sorting it before they release

 

an unknown bug happens, a bug reported and acknowledged is an example of WG ignoring feedback, that's my point

 

Yep because software has never been released with know bugs in it has it.

Agent_327 #16 Posted 04 April 2018 - 07:58 PM

    Staff Sergeant

  • Beta Tester
  • 16479 battles
  • 340
  • [CAF] CAF
  • Member since:
    09-20-2010

View PostF2PEXP, on 04 April 2018 - 06:33 PM, said:

so in test server there was an issue of tank hits not giving a sound register so you did not realise you were being shot, WG say they aware but hey presto upon release of 1.0 still got same issue, and hey presto today still same issue

 

when WG going to listen to the constructive comments and sort this issue out?

It's annoying but not something that they should have delayed 1.0 for. That's just completely out of proportions. :facepalm:


Edited by Agent_327, 04 April 2018 - 07:58 PM.


Strappster #17 Posted 04 April 2018 - 07:59 PM

    General

  • Player
  • 23695 battles
  • 8,888
  • [WJDE] WJDE
  • Member since:
    10-20-2015

View PostF2PEXP, on 04 April 2018 - 06:47 PM, said:

it is not about the bug

 

it is about being informed about the bug in first test, then second test and still not sorting it before they release

 

an unknown bug happens, a bug reported and acknowledged is an example of WG ignoring feedback, that's my point

 

Bugs get reported, they're assessed and assigned a priority. The occasional missed sound on a received hit is unlikely to be game-breaking so it's probably got a low priority and wouldn't be considered grounds for delaying the delivery of the 1.0 version of the game that's been advertised extensively.

 

IMO a much bigger issue was the long loading times - when the suggested workaround is to buy new hardware, you know it's going to have a higher priority and what do you know, we've already had a micro-patch to address that fault.

 

The fact that WG have acknowledged the sound bug is evidence that they're not ignoring feedback. This thread merely confirms that the EU community has plenty of drama queens looking for something to complain about.



ThinGun #18 Posted 04 April 2018 - 07:59 PM

    Second Lieutenant

  • Player
  • 33566 battles
  • 1,001
  • Member since:
    12-08-2014

All software contains errors, unless proven otherwise.  Which is impossible.

This was the first thing I learned when I went to coding classes.

 

Deadlines are the worst enemy of the software tester.  And let's be honest here ... we're the beta testers.



Balc0ra #19 Posted 05 April 2018 - 12:57 AM

    Field Marshal

  • Player
  • 63764 battles
  • 15,018
  • [WALL] WALL
  • Member since:
    07-10-2012

View PostErwin_Von_Braun, on 04 April 2018 - 06:45 PM, said:

 

Have a good read through these forums - everything is broken &/or OP and all feedback is 'ignored'.

I doubt you are being ignored as such, just that the problem isn't that high on their list of problems.

 

This. I suspect there are bigger issues that needs fixing. Like the long loading times and invisible tanks most are still experiencing. I suspect most want that fixed then a sound that's lacking. As there are still other visual hints that you have been hit. Unless you never register those either, you might need the sound. That or the reason for it was not as simple as a 5 min fix. But hey... there is yet another micropatch coming tomorrow morning. So who knows. It might fix it.

Edited by Balc0ra, 05 April 2018 - 12:58 AM.


Geno1isme #20 Posted 05 April 2018 - 01:04 PM

    Lieutenant General

  • Player
  • 41137 battles
  • 6,984
  • [TRYIT] TRYIT
  • Member since:
    09-03-2013

View PostSteve8066, on 04 April 2018 - 07:51 PM, said:

it `works` for me, but it doesnt mean it was fit for release. Hit boxes too big, hit boxes not existing, no hit detection just HP bar decreasing with no visible signs/sounds of why, etc. etc. etc. Its far from working perfectly.

I guess you're no familiar with the saying that "perfect is the enemy of good".

 

View PostF2PEXP, on 04 April 2018 - 08:47 PM, said:

it is about being informed about the bug in first test, then second test and still not sorting it before they release

 

There is a massive difference between being aware of a bug and actually knowing what the underlying problem is. And the latter is generally a requirement for fixing it.

This is especially true for issues that have no clearly observable trigger (aka "happens sometimes" ).


Edited by Geno1isme, 05 April 2018 - 01:09 PM.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users