40 replies to this topic

[eekeeboo]

Piq_Mastika, on 22 November 2018 - 01:33 PM, said:

 

 

Any gaming company works that way. You have to allocate resources, budget, staffing etc. Of course for critical issues you have delays for which we have had in the past, hence "filler events" until the patch is finished where it's more stable. But the thing with bugs is that there can be more than 1 thing that causes the same result. If people don't report the bugs then there's no reliable way for the development team to find all the causes. 

 

Testing takes place, but many bugs in the past were not reproducible on development machines. This was why there was a push for reports, screenshots, and logs to help with this. It's why, regardless of the reply you receive from support if it's a bug report, the info is passed on to the development team. Every time you crash the game compiles a crash report to send off etc. 

 

wlatopa, on 22 November 2018 - 02:13 PM, said:

 

 

And the black screen bug is more prevalent for some than others, that cause still needs people to send off info. For instance, do people minimize the game a lot? 

 

FPS drops was recently hotfixed with the info the devs had. Audio bug is being worked on thanks to reports allowing the team to reproduce it more effectively and reliably. Disconnection, you need to do ping plotter and send off the log reports to show the cause (if you haven't done this). Levitation of aircraft is the same as I haven't seen this. Bots indestructible how? Lag is again only present for some people and needs ping plotter so the team can find out what the cause is. 

 

And out of ALL the bugs you've just mentioned, how many have you reported in a bug report with as much info as possible and sent the requested info to give the development team the information required to be able to fix the cause?

 

Yes, there "shouldn't" be any bugs, but the whole thing with a bug is that they appear unplanned and they get through the cracks. It is still important that players help themselves, others and the developers by sharing the information to help find the cause. 

[wlatopa]

eekeeboo, on 22 November 2018 - 02:32 PM, said:

 

Any gaming company works that way. You have to allocate resources, budget, staffing etc. Of course for critical issues you have delays for which we have had in the past, hence "filler events" until the patch is finished where it's more stable. But the thing with bugs is that there can be more than 1 thing that causes the same result. If people don't report the bugs then there's no reliable way for the development team to find all the causes. 

 

Testing takes place, but many bugs in the past were not reproducible on development machines. This was why there was a push for reports, screenshots, and logs to help with this. It's why, regardless of the reply you receive from support if it's a bug report, the info is passed on to the development team. Every time you crash the game compiles a crash report to send off etc. 

 

 

And the black screen bug is more prevalent for some than others, that cause still needs people to send off info. For instance, do people minimize the game a lot? 

 

FPS drops was recently hotfixed with the info the devs had. Audio bug is being worked on thanks to reports allowing the team to reproduce it more effectively and reliably. Disconnection, you need to do ping plotter and send off the log reports to show the cause (if you haven't done this). Levitation of aircraft is the same as I haven't seen this. Bots indestructible how? Lag is again only present for some people and needs ping plotter so the team can find out what the cause is. 

 

And out of ALL the bugs you've just mentioned, how many have you reported in a bug report with as much info as possible and sent the requested info to give the development team the information required to be able to fix the cause?

 

Yes, there "shouldn't" be any bugs, but the whole thing with a bug is that they appear unplanned and they get through the cracks. It is still important that players help themselves, others and the developers by sharing the information to help find the cause. 

 

Is not my work.......i give the informations to developing team as other players over the bugs (all same bugs),but if the game is not satisfying or unplayable,i shut up the game and i go to see tv.

[eekeeboo]

wlatopa, on 22 November 2018 - 03:13 PM, said:

 

 

If something is broken and someone is offering to repair it, as long as you tell them what's wrong. Your choice to play or not, that has nothing to do with whether you choose to submit bug reports or not though. 

[wlatopa]

Eekee,i pay to play,who take my money must be able to fix the issues that are in the game. My job is another and if  someone tell me that he have an issue about my job,i thank and move my bottom to fix it.

Edited by wlatopa, 22 November 2018 - 03:38 PM.

[R0I]

eekeeboo, on 22 November 2018 - 03:20 PM, said:

 

If something is broken and someone is offering to repair it, as long as you tell them what's wrong. Your choice to play or not, that has nothing to do with whether you choose to submit bug reports or not though. 

 

ekeee i am owner of software dev company since 2004 .. 

i take your sentance about: you play or not and declare it or not ... seriously there is 4 issues of logic:

1- you play and you declare

2- you play and you do not declare

3- you do not play and you declare

4-you do not play ant you do not declare

play for free does not mean free of provider... free of the user

for beta testing i see  lot of user labelled 'beta testers and alpha testers'  if there is problem of servers for beta testing i can help you with that but 

please be constructive WG ... 1.x 2.x bugs are the same.

if no one is already ready to hear from customers (as you pretend waiting for tickets) ... you will not got far sadly.

i see how new are devs or devs staff to decision when they decided to replace (not to add) conquest logic to the game and they do not master the source code / logic / practice ... you blamed old that was not their fault / you may blame 2.x when illuminated devs will suggest a dumbed 3.x

ps: we can be constructive if working staff know that customer is important.... not just a touch and go guy.... years are passing and just tell us what did you do in face of concurrent softwares already up and running on internet... 

some old that loved this game had and have patience... the option you made for net passengers they will not have the patience we had....

save your game or you will just CRASH

alpha testers for alpha testing

beta testers for beta testing

end users for enjoying game

never test you medecine on final patients it is a crime

good night all

 

 

 

[eekeeboo]

wlatopa, on 22 November 2018 - 03:37 PM, said:

 

 

And if you don't report the issues, you are not helping the person fix the issue for you. Right now you're not even telling the development team the issue you have. That's the whole point of the bug report. 

 

R0I, on 22 November 2018 - 11:36 PM, said:

 

 

First: the beta tester and the alpha tester emblems are for people who were in the alpha and beta of the game before its release. Currently, testing is done through the Dev team QA dept, super-tasters have very specific testing of features not looking for bugs. The bugs pre 2.0 are actually somewhat different to the ones now because of the huge amount of changes made the UI and the gameplay, for instance, the missions. 

 

And it's not about not ready to hear about bugs. The fact is when you report a bug, any bug you will be asked to give details on how it came about, instructions best how to replicate it and software and hardware info so the development team can find the cause. As a person who owns a company you will know this process that you need more than just "It doesn't start". Especially considering a lot of the reports from people usually are fixed with a clear cache. But the same result can come from more than 1 cause and more than one issue, again something I'm sure you're more than aware of as an active owner of a development company. 

 

Next you have priority of bugs when you have resources to allocate, though you may have a "serious" bug if it's reported by one person that's not as serious for the team as say a less severe bug reported by a thousand people. Priority is not just about the severity but the frequency, the only real way to get that across is from the bug reports to help highlight the severity of the issue. Crashes have auto-generated reports because the client knows what happened and will send it. But a bug where your screen goes black for 1 spawn is not something the client will register, you are the one who knows this and can report it. 

 

Once again ALPHA testers were for the alpha of the game. BETA testers were for the beta of the game. These are tags for people who were around at that time, not current processes, again you should know this as a person who owns a development team or someone who knows the processes of game development, the alpha tester was someone who played the game in the alpha part of the game. These titles and tasks have changed a lot in the game with more emphasis being on early access vs actual testing. 

 

Once again I highlight to you as someone who will know this in a development industry. Bugs that get through are bugs you don't know about until they're reported. That's why they're called bugs. You don't plan for them and they're the ones that got through, they weren't reproduced or found and the only way you get to know the cause is someone telling you a) what happened, b) what they did (to reproduce the effect) c) What they're using that may be unique in causing the effect. If you don't provide this information the development team has to work even longer to find all that information and the bug will be present for an even longer period of time while the fix is found. You then also have priority of bugs and if there's 1 report without that information vs a lot of reports for another bug, the more reported and serious bugs will get more priority based on resource allocation. I'm sure you know all of this full well with your indepth industry knowledge, but just in-case. 

 

You will also benefit from reading what I was replying to about playing or not. A person who says they will not provide bug reports because it's not their job and if the game breaks they just won't play and watch TV instead, that is at the end of the day their choice, they have made the choice they have the full right to make.  

wlatopa, on 22 November 2018 - 03:13 PM, said:

Is not my work.......i give the informations to developing team as other players over the bugs (all same bugs),but if the game is not satisfying or unplayable,i shut up the game and i go to see tv.

Edited by eekeeboo, 23 November 2018 - 10:02 AM.

[wlatopa]

EEkee,for beta testing i want money,is not my job. You forget that who pretends money, MUST give a functional product.not an experimental bugged software.

PS the bugs are so many,that is useless to describe some. To reproduce it is enough to play some games with pc like the users,intel cpu core I3-I5-I7,radeon or nvidia gpu,win 10. Very easy...........

Edited by wlatopa, 23 November 2018 - 02:48 PM.

[klbergmen]

Do the dev's know about about these bugs or should I open tickets:

- soundbug (cannonsound doesn't stop)

- spawn point jumping back to default

- turrets sporadicly refuse to fire

- respawn bug (respawn doesnt show own plane but still some others - 2xENTER helps)

- chat sproadicly not working

- battle start crashes to Desktop

- MM broken (uneven teams)

- all kinds of errors on the minimap (ghostplanes, bomber in wrong location,...)

Only the soundbug is new.

We are waiting long enough now for them to be solved. I'm sure I forgot several others.

If it helps I open tickets to increase the priority.

[eekeeboo]

wlatopa, on 23 November 2018 - 02:45 PM, said:

 

 

You're NOT beta testing. As mentioned you can submit bug reports or not, that's your choice. For hardware, everyone uses different things, software and hardware, I'm sure you took this into account and took the time to think about this before typing your sentence but merely neglected to mention it. 

 

klbergmen, on 23 November 2018 - 04:35 PM, said:

 

 

1) Known, reported and being worked on. 

2) Not that many reports - Need more with details on how to reproduce effectively. 

3) Turrets not firing, this needs more details and definitely reproduction detail and control scheme. 

4) Respawn until hitting chat enter twice - known but needs more reports because the big can be caused by a variety of actions, with a fix working for some people and not for others. 

5) Chat stopping working I've not heard anything of so will need bug reports to be passed on so we can know whether it's the chat dev team or the wowp dev team to work on. 

6) CTD's have auto-generated reports that are sent off, but submitting a ticket to ensure the info is passed on, does not hurt. 

7) The new MM can be imbalanced for many reasons so you need to be specific. 

8) Ghost mini map problems need bug reports to find out if it's server, client or game/map/UI error. 

 

For new bugs you mention, actually the MM is a new MM system, please refer to the patch notes. The respawn problem I've only seen problems of most recently and have only experienced it in the bomber escort game mode. Turret not firing I've experienced 2 types, 1 is known and the other is controller issue (joystick). Respawn bug was fixed but has seemingly seen an increase in people stating this. Chat issues I've not had anyone come to me mention any issues with it not working. CTD is something I experience only when i am alt-tabbing often in long gaming sessions but can be caused by a variety of reasons. Minimap problems I've not had. 

 

And that should help illustrate why bug reports are so important in helping find and fix and prioritse bugs. 

[dreambill]

- spawn point jumping back to default

- turrets sporadicly refuse to fire

You don't need specific tickets, just put one of your testers to play for 1 hour the game. It happens on Every game all the time.

[R0I]

took time reading ekee wlatopa and dreambill posts..

if releases are done on the fly (without intensive testing) the bugs of course it ever existed in all codes (as we say in coding world 'only god is a good programmer')

but did persha perform testing before releasing ? did persha ever took users suggestion/reactions during open CT tests overs years ?

i think marketing timelines are stressing coders progressions so (and i know what i am typing) the 2.x branch was not really decided by coders ...

so all work done since open beta did not assume conquest testers conclusions... go into conquest forum and look ...

some hardened users will confirm that 2.x is not a new core code it is main core code of 1.x with lot of commented code (desactivated)..

work done on GUI and on Game logic to  anwer to the marketing expectations not to the gamers ...

in conclusion: most of bugs are due to the fact that new code (2.x) are made over an old one (1.x) made by coders that i am sure he do not work for persha anymore..

that BIG CHANGE ANTICIPATED could NOT be FOR SURE zero bugs ...

half off topic just about frustration :

but what may bore the customers i think it is not the bugs .. old players were patients during years and adapted to the flawing fps etc...

what is boring today is the absence of real challenge in game. so a 3 month new player when begin to masters all concepts will start to ask questions about the real meaning to run from circle to circle and shooting at white and red planes and will looke on similar games that offers more options (those game that we disliked since the start...).. even the respawn it could be logic in a standalone signle player version... but in a multiplayer game emmmm

 

Edited by R0I, 24 November 2018 - 09:47 PM.

[Piq_Mastika]

klbergmen, on 23 November 2018 - 06:35 PM, said:

Do the dev's know about about these bugs or should I open tickets:

- soundbug (cannonsound doesn't stop)

- spawn point jumping back to default

- turrets sporadicly refuse to fire

- respawn bug (respawn doesnt show own plane but still some others - 2xENTER helps)

- chat sproadicly not working

- battle start crashes to Desktop

- MM broken (uneven teams)

- all kinds of errors on the minimap (ghostplanes, bomber in wrong location,...)

Only the soundbug is new.

We are waiting long enough now for them to be solved. I'm sure I forgot several others.

If it helps I open tickets to increase the priority.

 

Plus what I've seen:

Black screen with visible UI (and I cannot move up/down, can't crash)

Disconnect after game finishes (not a big deal)

No loading/black screen at the start of the game (I have to Alt+F4 and reload the game in the middle)

Locked in sniper mode, seeing my plane going ahead. ( I could move freely, but went oos) This happened only once to me and I forgot to report it.

[wlatopa]

dreambill, on 23 November 2018 - 06:02 PM, said:

- spawn point jumping back to default

- turrets sporadicly refuse to fire

You don't need specific tickets, just put one of your testers to play for 1 hour the game. It happens on Every game all the time.

 

Testers want money to play, they aren't stupid like players that pay to play.....;) For WG is better to have 1000 beta tester gratis et amori dei (better if they pay...;) )

[eekeeboo]

dreambill, on 23 November 2018 - 06:02 PM, said:

 

 

Please read the previous posts. 

 

R0I, on 24 November 2018 - 09:46 PM, said:

 

 

Everyone is entitled to their opinion on the game vs their old one. But sweeping judgments by players who have played less than 100 battles on the effective strategies, play styles, and battle performance is somewhat superficial. 

[wlatopa]

Sorry Eekee,but seem that WG don't change the politics.They don't ear the customers, they are unable to fix the bugs.In previous version of the game,the developers was more fast to fix it,now seems that they are very slow.Probably R0I have seen far,the code is not write from those devs and every patch,show more bugs without fix older.

[eekeeboo]

wlatopa, on 26 November 2018 - 11:50 AM, said:

 

 

The bugs in the "old game" were just as fast to fix. I myself towards the end of 1.9 could not play from the Dunkirk bundles because of a crew bug which meant if I used anything to do with my barracks my game crashed. 2.0 allowed me to play again when it was fixed. This is definitely a case of rose-tinted goggles. 

 

Bugs are always fixed as and when they development team can with the resources they have. The more people don't report bugs and give information the developers need then the longer this process takes as well as the priority of these bugs. 

[Piq_Mastika]

eekeeboo, on 26 November 2018 - 01:55 PM, said:

 

Bugs are always fixed as and when they development team can with the resources they have. The more people don't report bugs and give information the developers need then the longer this process takes as well as the priority of these bugs.

 

I agree, but is it possible to release a patch with none (or just minor) bugs? Why the goal is not releasing pure content, instead of fixing a broken one. Maybe the last 20-30 forum treads topics from players are all for the bugs. I mean, no offense, but rethink the politics even with a cost of 1-2 weeks without new content and events.

[R0I]

things could be better.. if evolution stop and more concentration on polishing (as a forum mate said in a different post).

if developers or real decision ppl are just lookin here because only polishing here is cleaning comments even if they are fun critics ofc... using forums for years (professional use the most).

here during years and years ... i am sure that community managers old and new  forwarded the requests i am sure beta tests forum topic on CT where readable to deciders ...

i know that the role of officials is to keep honourable/ positive face on public forums even if ...

we can not say 'you did it wrong' or 'you are doing wrong'

not my actual account number of battles will tell about my knowledge about the game if not the unified client model will not authorize the multi-server use .... (contradictions..)

if we all have to agree what is the goal of a forum ???

things get better when we accept to recognize failure. past failures was not community fault past failure was because of refusing to hear the community feed backs did  you think it changed ?

if we still post here (most old players) it is because we loved the game concept.. a total change let's say OK but politic is still the same ... and politic discussion is only prohibited in one voice system a.k.a. dicatorship.

in software world even if you are rich you can not go on (look at mircrosoft vs android (embedded linux)).. 

one day i will move away from here like lot did ... think what i will keep from my experience here...

i learned from my experience here 1 year passed same stuff but presented on a more nice looking gui with new people

what i earned here is not exp or planes.. it was good time spent with people that become friends after.. and i thank this game for this but ONLY for this.

to be CONSTRUCTIVE in t his post as WG suggests... let's talk directly with developers like in RU forums..a dedicated section.

you can not do this game great again if you are doing the same mistakes... HEAR THE COMMUNITY and make your long timeline strategy based on it.

good night.

[johncarps]

eekeeboo, on 23 November 2018 - 11:00 AM, said:

 

Once again ALPHA testers were for the alpha of the game. BETA testers were for the beta of the game. 

 

and the birds fly, and the fish swim,  

 

"a less severe bug reported by a thousand people"

thousand ppl playing wowp 2.0 ?? 

[TommyLobster]

A couple of other bugs I don't know if anyone else experiences.

 

occasionaly I get an invisible opponent, I can see the aircrafts damage bar but the aircraft graphic is missing ?

 

and since the last update

 

When my plane respawns it sometimes refuses to manoeuvre either with the joystick or mouse ?