|
Author |
Thread Statistics | Show CCP posts - 1 post(s) |

Tokena
Federal Navy Academy
|
Posted - 2008.03.20 09:08:00 -
[1]
Has been happening a lot to me as well, not just at gates.
Been at a belt, enemy warps in. I try to target: "Target is invulnerable". Enemy starts flashing yellow (ie. has targeted me): "Target is invulnerable". Enemy starts flashing red (ie. weapons firing): "Target is invulnerable". I start taking damage and am finally able to lock him, maybe 10 seconds later than he could lock me.
Anybody tried bug reporting this yet? I'm too lazy to file a report that will just get filtered out...
|

Tokena
Federal Navy Academy
|
Posted - 2008.03.20 20:48:00 -
[2]
Edited by: Tokena on 20/03/2008 20:50:49 This has been happening to a lot of us on and off since Trinity 1.0. If we could reproduce it we'd have reported it a long time ago.
And I'm about to bang my head on the table because of this stubborn bug reporting system and attitude: There are bugs you cannot reproduce yet they are still there. Make bug reporting public and teach your bug hunters not to close a bug report just because they cannot reproduce the bug within two minutes. You'd be surprised how many bugs you'll find in a month that you didn't even knew (or acknowledged) that were there.
Duh. Now I'm all worked up and angry.
|

Tokena
Federal Navy Academy
|
Posted - 2008.03.21 09:22:00 -
[3]
I wonder what it will take to have CCP look into this? Being able to reproduce this consistently is very unlikely, so a bug report is out.
Any suggestions, CCP Gangleri, what to do with bugs we cannot reproduce at will?
|

Tokena
Federal Navy Academy
|
Posted - 2008.03.21 10:36:00 -
[4]
Originally by: Venkul Mul
Originally by: Tarminic
I'm sorry, but this response is ********. Did everyone who posted here include a DXDIAG file so the bug hunters know how their computer is configured? Or logserver files? Or anything more specific than "I have this problem and it sucks?" How could you possibly expect bug hunters to get better information from forum posts than from good bug reports? Bug hunters spend their time fixing bugs by analyzing bug reports, not inane forum posts.
Right reply Tarmic.
To the one asking why the Devs don't go and try to reproduce the bug playing with a T1 ship and the deas control tools to see what happens:
this bug hit me maybe 1 time every 6-7 hours of play. You really want the Dev to play the game for 6 hours to find 1 example of a specific bug, especially considering that they probably need 10-20 registered events of the bug to try a solution?
That is 60-120 work hours to spot a minor bug, when with some support from players using the logserver the time needed could be reduced to 1-2 hours.
Considering that we pay to play the game while they get paid to provide stable, reliable and bug free service, yes, I'd expect CCP to follow up on all bug reports.
Considering further that they get at least 3 million bucks a month from us hiring a few people (as opposed to relying on volunteers) to check out these bug reports doesn't sound that farfetched. For this bug, using your hours-estimate, that'd be just 3000 bucks to find it...
And considering that this bug is not as minor for most of us as it seems to be for you, yes, I'd expect a bit more than the copy&paste reply "bug report it and shut up".
Another thing worth considering is that we have no idea if this bug has been reported before or if CCP actually needs log server output so I don't see much sense in hundreds of us wasting our time trying to get this logged and reported.
And even if you did report it, chances are good you'd end up with a bug hunter on a bad day who'll just close your report without really heaving read it and you'd have to spend hours and hours arguing just to get it reopened and looked at by the people who can actually do something about it.
I've said it before, and I'll say it again till someone listens: CCP make your bug reporting system viewable by the public (hide exploits if you must) and you'll be surprised how helpful your player base can be.
|

Tokena
Federal Navy Academy
|
Posted - 2008.03.30 08:18:00 -
[5]
I went to the trouble of bug reporting this, just to see what happens. I've provided game logs and a log server file of it happening. And guess what?
Thank you for your bugreport - ID:55444 Title: Target Is Invulnerable The problem you have described was non-reproducible. If you are still having the problem you described, could you please updater your bug report with an improved set of reproduction steps.
I'll give them a link to this topic, maybe that'll make them take it seriously.
On a different note: I haven't played much the during last week and in the last two battles I was in this did not happen. Did they stealth-fix it? Or is it still happening?
|

Tokena
|
Posted - 2008.03.30 15:24:00 -
[6]
Originally by: Tokena I went to the trouble of bug reporting this, just to see what happens. I've provided game logs and a log server file of it happening. And guess what?
Thank you for your bugreport - ID:55444 Title: Target Is Invulnerable The problem you have described was non-reproducible. If you are still having the problem you described, could you please updater your bug report with an improved set of reproduction steps.
Originally by: Wild Rho The client comes with a program called Logserver that can you use. It'll generate a handy little file that you can attach to bug reports that gives bug hunters much more detailed info on what's happening at your clients end while the bug happens.
Uh. Yeah. Whatever. Thank you for reminding us.
/sarcasmn
|

Tokena
|
Posted - 2008.03.30 17:45:00 -
[7]
Originally by: Wild Rho I was responding to Viqer Fells post. 10/10 for observation.
Might wanna quote what you respond to. Otherwise people will view it as a generic answer to the whole thread.
But anyway, I gave them logserver files and they still tell me they can't reproduce it :(
So what's the next step? Bumping this post till it reaches 50 pages and a dev decides it is important enough?
|

Tokena
|
Posted - 2008.04.15 09:12:00 -
[8]
After some arguing and a long wait they finally decided that this is a real problem:
Thank you for your bugreport - ID55444 Title: Game Mechanics: Target Is Invulnerable We were not aware of this problem, and have used your bugreport to create a new issue in our defect tracking system.
The weird thing is: It hasn't happened to me lately and I was assuming they had fixed it already and just not answered the bug report. Anyway, just wanted to keep you up-to-date.
|
|
|
|