These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Ships & Modules

 
  • Topic is locked indefinitely.
 

Torps are so buggy
Author
Previous Topic Next Topic
Jahpahjay
Mechanical Basterds
#1 - 2011-09-07 15:35:00 UTC
I'm mainly curious if other people are having problems with torps not getting stat modifications to dmg from applicable skills and modules.

I sent a bug report before, and they sent a reply back that it's a "known issue." However, "known issue" does not necessarily mean everyone is affected by this problem.

I'd like to know who else has or had this problem, and if they were able to fix it. And before you ask, yes, I cleared my cache files many times over, to no avail.
Sphynix
Pandemic Horde High Sec Division
#2 - 2011-09-07 15:58:44 UTC
The issue that is "known" tends to happen at random from a "session change". This generally means that when you change system, dock, undock or etc the game kinda forgets to add your skills or the bonuses to the equipment/ammo.

The so called "fix" is to log out and back in each time you get to the system you want to fight in, because this apparently resets it all and should be fixed until you next dock or change system...

(it used to happen all the time if you were changing modules in space)
Dracoliche
Fried Plantains
#3 - 2011-09-07 22:37:29 UTC
I don't like to take special measures to make my $15/mo game work regularly for me.
I hope this isn't happening to any of my stuff.
FloppieTheBanjoClown
Arcana Imperii Ltd.
#4 - 2011-09-08 00:08:49 UTC
Dracoliche wrote:
I don't like to take special measures to make my $15/mo game work regularly for me.
I hope this isn't happening to any of my stuff.

This. A "workaround" shouldn't be treated as a long-term fix to a problem in a product that people pay for.

If they know what the problem is, they should know how to fix it. If they can't fix it, methinks they're in the wrong line of work.

Founding member of the Belligerent Undesirables movement.
Malcanis
Vanishing Point.
The Initiative.
#5 - 2011-09-08 09:14:02 UTC
FloppieTheBanjoClown wrote:
This. A "workaround" shouldn't be treated as a long-term fix to a problem in a product that people pay for.



Ah, I see that you're new to EVE.

"Just remember later that I warned against any change to jump ranges or fatigue. You earned whats coming."

Grath Telkin, 11.10.2016
Dorian Wylde
Imperial Academy
Amarr Empire
#6 - 2011-09-08 17:58:45 UTC
FloppieTheBanjoClown wrote:
Dracoliche wrote:
I don't like to take special measures to make my $15/mo game work regularly for me.
I hope this isn't happening to any of my stuff.

This. A "workaround" shouldn't be treated as a long-term fix to a problem in a product that people pay for.

If they know what the problem is, they should know how to fix it. If they can't fix it, methinks they're in the wrong line of work.



I love when people who know nothing about programming or computer science try to talk about bug issues.

Known issue can mean many things. It could mean there have been several reports, and they're looking into it. It could mean they've been able to reproduce it on their test server. It could mean they have a patch for it next week. It could also mean they know what's wrong, but its so deep into the code, and tied into a hundred other things, that it will takes years to fix.

Deal with it. All computer programs have bugs. Programs as large and complex as an MMO have lots of bugs, that may have no obvious cause or solution. That is a fact, and there is no way around it.
Dracoliche
Fried Plantains
#7 - 2011-09-09 01:47:17 UTC
Dorian Wylde wrote:
FloppieTheBanjoClown wrote:
Dracoliche wrote:
I don't like to take special measures to make my $15/mo game work regularly for me.
I hope this isn't happening to any of my stuff.

This. A "workaround" shouldn't be treated as a long-term fix to a problem in a product that people pay for.

If they know what the problem is, they should know how to fix it. If they can't fix it, methinks they're in the wrong line of work.


I love when people who know nothing about programming or computer science try to talk about bug issues.


I don't. Roll
Brotha Umad
Republic Military School
Minmatar Republic
#8 - 2011-09-09 09:52:06 UTC
Dorian Wylde wrote:
I love when people who know nothing about programming or computer science try to talk about bug issues.
Known issue can mean many things. It could mean there have been several reports, and they're looking into it. It could mean they've been able to reproduce it on their test server. It could mean they have a patch for it next week. It could also mean they know what's wrong, but its so deep into the code, and tied into a hundred other things, that it will takes years to fix.

Deal with it. All computer programs have bugs. Programs as large and complex as an MMO have lots of bugs, that may have no obvious cause or solution. That is a fact, and there is no way around it.


Hi.
My real life job is to find bugs in video game currently in production, and to see that they are corrected by devs. If I let a bug unattended for months, I am f---ing fired because I don't work at CCP.

Even for those odd bugs where the cause is unclear, there is always a workaround that does not require the end user to duct-tape its 60$ game.
And those are 90% of the time memory leaks that cause crashes, not bad session change programming.

Do you prefer it when people that know what they are talking about say the exact same thing ?
Dorotent
University of Caille
Gallente Federation
#9 - 2011-09-09 13:09:30 UTC
Dorian Wylde wrote:
FloppieTheBanjoClown wrote:
Dracoliche wrote:
I don't like to take special measures to make my $15/mo game work regularly for me.

This. A "workaround" shouldn't be treated as a long-term fix to a problem in a product that people pay for.


I love when people who know nothing about programming or computer science try to talk about bug issues.

Known issue can mean many things. It could mean there have been several reports, and they're looking into it. It could mean they've been able to reproduce it on their test server. It could mean they have a patch for it next week. It could also mean they know what's wrong, but its so deep into the code, and tied into a hundred other things, that it will takes years to fix.

Deal with it. All computer programs have bugs. Programs as large and complex as an MMO have lots of bugs, that may have no obvious cause or solution. That is a fact, and there is no way around it.


IRL I'm a Silicon Valley software development manager. Have been for going on 15 years now. The first posters are right. You are wrong.

(Oh sure, your explanation is technically correct but apologises for sloppy work. A bug like not applying skills in a skills based game can never be addressed with a workaround in a customer release. It's a showstopper. Having it in the wild for an extended period is terrible.)
Ecks Orion
Proposition Thirteen
#10 - 2011-09-09 18:14:20 UTC  |  Edited by: Ecks Orion
Dorian Wylde wrote:
FloppieTheBanjoClown wrote:
Dracoliche wrote:
I don't like to take special measures to make my $15/mo game work regularly for me.
I hope this isn't happening to any of my stuff.

This. A "workaround" shouldn't be treated as a long-term fix to a problem in a product that people pay for.

If they know what the problem is, they should know how to fix it. If they can't fix it, methinks they're in the wrong line of work.



I love when people who know nothing about programming or computer science try to talk about bug issues.

Known issue can mean many things. It could mean there have been several reports, and they're looking into it. It could mean they've been able to reproduce it on their test server. It could mean they have a patch for it next week. It could also mean they know what's wrong, but its so deep into the code, and tied into a hundred other things, that it will takes years to fix.

Deal with it. All computer programs have bugs. Programs as large and complex as an MMO have lots of bugs, that may have no obvious cause or solution. That is a fact, and there is no way around it.


Hi. I do this for a living, and have for 15 years.

You're WAY offbase here. What you say is true in a general sense (what "known issue" means), but the person you're replying to is absolutely, 100% correct. This behavior is a regression. Something that used to work, and now all of a sudden it doesn't. That is a serious problem, especially since numerous people have complained about it, AND it has a pretty serious impact on gameplay. The fact that it wasn't found in internal test is pretty disconcerting (I'd be having words with my guys if this happened in my org).

There's a known timeline here. We know when it worked, and we know that now it doesn't. We KNOW that something happened within that defined block of time that broke it. It should be a fairly simple exercise for them to narrow it down to a particular build, or even a specific changelist, and then examine the changes to figure out what did this. Successful software dev organizations do this ALL THE TIME.

This statement:
"A "workaround" shouldn't be treated as a long-term fix to a problem in a product that people pay for."
...is 100% correct and appropriate here, especially a workaround as intrusive as leaving the game and having to log back in.

Like the poster above me said, this bug is a showstopper. That means that if it's found before the code is actually released, you DO NOT release it until the bug is fixed. This issue would cause a release delay in any self-respecting software dev org.