Why Do You "Archive" Unfixed Bugs???

Just to clear something up here; the bugs don't get closed (although replies are disabled). Archiving them on the forum is very different to closing them in terms of how they're looked at and reacted to. While I can't give a specific answer to your questions I imagine this feedback has already been seen but I'll also pass it on to be certain.

If such it'd be nice to even know if the bug in question is still pending since you guys can still edit posts in such threads.
 
Update from QA:

Any reports that have been replied to: No further action is required - the problem has been logged and will be investigated internally. If we require further information, your thread will be moved to the 'Requires More Information' section.

If you have further details to provide that may help with the investigation (for example, more than letting us know it's still a problem), please create a new report (you can include a link to your old one) with the new information and we will add it to the existing investigation.

A new known issues list will be compiled for 3.1
 
I have found a bug while mining.
When the cargo rack is open, the max speed of my cutter is about 120ms.
When you launch a propector limpet, just after and during a short time, my speed increase, I was able to reach 200ms.

Shall I open a bug? No i don't think so, other bugs are a lot more annoying!
This archive strategy is an other reason not to open a bug.

I thought that was a bug to, but one day, I was in the camera view, and popped a limpet. The cargo hatch actually closes before the limpet comes out. I chalked that up to the game realizing it were closed, speeds up the ship, and after the limpet comes out, the cargo hatch opens again, slowing the ship.
 
Any reports that have been replied to: No further action is required - the problem has been logged and will be investigated internally.

Logged, categorized, and stored away in Warehouse 13.
 
"the bugs don't get closed (although replies are disabled)"
and
"
While I can't give a specific answer to your questions I imagine this feedback has already been seen "

Jesus Christ. Thats meme material right over there.


 
Thats all fine and dandy however, many issues are not added to the known issues....

I just looked at that "Known Issues" list.... [redacted]

It's like they are not even trying anymore.

You want a real list of "known issues" - do set subtraction of the patch notes from the archived bugs. You'll get a list that goes on and on and on.

Oh, and then do set addition using the new and shiny bug reports for 3.1 [blah]
 
Last edited:
Forgive me Frontier, but for the love of your customer's precious time, would you leave bug reports ACTIVE until you actually FIX the bug? When I go to the bug report forum right now, one would think that 3.1 is bug-free, when in fact this update is full of the very same bugs we reported back when 3.0 and even 2.4 dropped. Am I supposed to resubmit a bug report with every single update for the same bug that goes unfixed? Screw that, I'm not wasting my time documenting the same bug over and over and over again.

This really screams "We don't care!" from your QA department.... [snip rest of rant]

+1, +Rep to you!!
 
I just looked at that "Known Issues" list.... WHAT A JOKE!

It's like they are not even trying anymore.

You want a real list of "known issues" - do set subtraction of the patch notes from the archived bugs. You'll get a list that goes on and on and on.

Oh, and then do set addition using the new and shiny bug reports for 3.1 [blah]

Also worth remembering that the three "Known Issues" lists (PC, XBOX and PS4) are actually the exact same list, mentioning issues that happen regardless of platform.

So officially, there are no platform-specific bugs.

Problem solved!
 

stormyuk

Volunteer Moderator
Also worth remembering that the three "Known Issues" lists (PC, XBOX and PS4) are actually the exact same list, mentioning issues that happen regardless of platform.

So officially, there are no platform-specific bugs.

Problem solved!

I think the SRV bug is known to happen on Xbox as well as PS4, no idea about PC?
 
Just to clear something up here; the bugs don't get closed (although replies are disabled). Archiving them on the forum is very different to closing them in terms of how they're looked at and reacted to.

And yet here's what QA-Mitch says about one of the most game-breaking bugs in ED since 3.0 dropped:

I've reopened this investigation but any additional information would be much appreciated.

This implies this bug investigation was indeed closed, because one doesn't reopen something that's already open.

I'll stop now before I type something I regret....
 
It does wind me up seeing some of the bugs this game has either remaining or old bugs cropping up again. Crackling sound for one! And not being able to navigate after re-entering my ship in the SRV because the highlighter vanishes from the panel and tab switching won't work as it is unresponsive. Wingman target select or nav lock not working even when beacon's on. Forced restarts etc.

I can appreciate bugs being an issue that takes time to investigate and fix, but some of the updates have screamed "We don't care", as you put it, at least not where testing and observing the product properly prior to releasing the updates are concerned - here's looking at the AI bug with instant killing full auto rapid fire plasma etc and missions that are broken etc.

For the most part, the game works, although I do worry that we won't ever be seeing complex updates to the game without bugs galore when old ones keep rearing their old ugly heads.
 
Last edited:
It's saddening to read that someone from QA can't give definitive answers to legitimate questions. That makes you wonder how poorly their internal communication is. Btw Frontier... Didn't you also claim you followed up on combat logging reports from players? How did that work out? You think players forget? Your credibility is gone as far as I'm concerned. Fool me once, shame on me. Fool me twice, shame on you!
 
I think the SRV bug is known to happen on Xbox as well as PS4, no idea about PC?

And the PS4 headlook bug was PS4 specific for PS4 reasons.(PS4 Headlook is controlled by the Six Axis motion controls in the DS4, You just tilt your controller to look around, the bug was that the game wasnt resgestering the imputs properly)
 

stormyuk

Volunteer Moderator
And the PS4 headlook bug was PS4 specific for PS4 reasons.(PS4 Headlook is controlled by the Six Axis motion controls in the DS4, You just tilt your controller to look around, the bug was that the game wasnt resgestering the imputs properly)

Yeh, that was in the known issues.
 
Last edited:
Definitely a lot of bugs had to be reopened for 3.1 since the backlog from 3.0 wasn't moved at all, and the bugs don't appear in the known bugs list, and by a lot I mean by tenths.
 
I want to be able to comment or add to existing bug reports that are not yet fixed. It is impossible to do so at the moment without having to report and rewrite the bug report. +1
 
Back
Top Bottom