(06-08-2016, 09:09 PM)Herr Straße Laufer Wrote: (06-08-2016, 04:44 AM)Battle Kat Wrote: Seriously Ed, people had bugs but did not report them? How can we know of them, then?
What?
Maybe you did not understand.
When one player had an issue but the team thought no one else had that issue, they dismissed the one, until another came forward and said "it's happening to me to". From the top down we were told "hey, we cannot repeat that on our installs. Maybe it is your machine or you have a faulty install. Why, it never came up in play testing so you cannot have had that happen."
C'mon. I did not say that "people had bugs but did not report them". Obviously you would be told if there were issues found so that you could to take care of them. I was more commenting on the way your team handled things. Though, I do know of some who were waiting to see if anyone else had the issues they did.
And, the thought that 'why report anything if you are going to be abused by the team' came to mind.
Just saying.
And, you are not trying to say that there were no bugs? Or, are still no bugs in ME?
And, Jason, I am both amused and un-amused by you and your condescending comments. One thing I'll give you is that you do not disappoint.
Just can't wait to see the witty retort.
HSL
(Once again, not a complaint post. Just a tear down the strawman argument post.)
As for my comment in quotes: OK, I misunderstood your post then.
As for the bolded part. That is what happened.
Every bug report is seriously. Every time, the first thing done is to fire up one of our several test beds to repeat the error.
A well behaving bug appears the same in all systems. Devious ones, as those which made the off board arty glitch, did not. Berto and I could not repeat it in any of our systems, despite you providing very clear steps as how it was.
Difficult to shoot what you don't see, at the end Berto sent exe version after exe version for Mike to try them out, until finally one of them worked and fixed the issue in Mike's system.
But not in all systems, as we next found out, having first thought it was squashed all right. Then, testing against that system (maybe it was Jim, don't recall anymore), more changes were made to code, and now it seems the bug's gone quiet. The bug I for one never had. Go figure. Welcome to the software development I guess.