The bug tracker was made in such a way that Fdev didn't really have to fix anything and it would automatically expire most . It gives the impression that Fdev are doing stuff and keeps the natives happy?
Report issues using the Issue Tracker
- Thread starter Paul_Crowther
- Start date
Sure, but they didn't have to fix anything anyway unless they wanted to - and plenty of fixes do show up in the patch notes. If anything the bug tracker gives the impression they do less to fix bugs than actually happens.
If you go to the "Reported Bugs: Elite Dangerous" page it says "page 1 of 3683" because - unlike conventional bug trackers - it includes all the closed bugs on the default view...
Conversely, of the "top 10 voted" bugs, two are actually feature requests, and two (possibly three?) are fixed, and shouldn't be there at all any more.
They'd get better customer satisfaction by going back to the old "bug reporting forum" and never reading it (or if they want to keep the "Confirmed" mechanic, only reading threads which get above three pages) - at least that way, people reporting misunderstandings of features or things which would be handled better as support tickets might get other players telling them what's happening.
If you go to the "Reported Bugs: Elite Dangerous" page it says "page 1 of 3683" because - unlike conventional bug trackers - it includes all the closed bugs on the default view...
Conversely, of the "top 10 voted" bugs, two are actually feature requests, and two (possibly three?) are fixed, and shouldn't be there at all any more.
They'd get better customer satisfaction by going back to the old "bug reporting forum" and never reading it (or if they want to keep the "Confirmed" mechanic, only reading threads which get above three pages) - at least that way, people reporting misunderstandings of features or things which would be handled better as support tickets might get other players telling them what's happening.
That got tried a lot but very few of us listened to what we were told.
Back then with the bug reporting forums I got a lot of replies and help by the developers. Yes, they sometimes missed the bug by actually looking wrong into the issue but at least they did. Since the bug reporting forum was replaced by the bugtracker I never ever got a response again, also the vast majority of my bug reports just expired.
I got an email from Support yesterday asking if I could get netlogs for an issue, so they are still doing stuff.
The issue was raised in April, and I'd assumed it was fixed as I haven't seen it since. And it only happens in a small number of offline settlements - so the chances I'll actually be able to help isn't high. But they are still out there it seems.
(Though this was the first time I've been contacted for years)
The issue was raised in April, and I'd assumed it was fixed as I haven't seen it since. And it only happens in a small number of offline settlements - so the chances I'll actually be able to help isn't high. But they are still out there it seems.
(Though this was the first time I've been contacted for years)
Issue Tracker
issues.frontierstore.net
.Attachments
Last edited:
This process is something of a problem for me. I submitted an issue surrounding the inability to apply suit cosmetics that I paid for to a load out, and it's been in "confirming" status for 2 months, even though somebody else has already confirmed the issue.
Granted, it isn't an earth-shattering, game-ending problem, but it sure does feel as though there is an abundance of "we don't really care" at work.
Granted, it isn't an earth-shattering, game-ending problem, but it sure does feel as though there is an abundance of "we don't really care" at work.
Is that the issue talked about in The Discovery Scanner for this week, quoted below?
- We have been aware of a Livery Error for Commanders currently, when attempting to equip any pre-Odyssey suit cosmetics. Thank you for your continued patience on this one as investigations move forward.
If you take into account the price of those cosmetic items, well... There's an easy lesson to learn.
Thanks. I guess I have another problem with the tracker. I spent several minutes looking for a similar issue before submitting mine and never came across this one.
In any event, does that mean that there isn't anybody looking at new submissions - at all - until they're "confirmed"? I suspect more than enough duplicate-but-named-differently submissions are out there that would otherwise confirm each other.
That said, I'm glad they've confirmed the issue and are looking into it, but I have another question:
How the heck do "pre-Odyssey" suit cosmetics exist?
For the standard flight suit.
Cosmetics is what Holo-Me has been all about for years now.
Last edited:
Oh. You know, I completely forgot about that.For the standard flight suit.
Cosmetics is what Holo-Me has been about for years now.
I have collected scenes of irrational hostility by allies in battle for defending megaship, and I have tried to examine the causes of such hostility.
Source: https://youtu.be/k644_QMEQ0Q
Broadly, yes. Occasionally someone at Frontier does look at the new unconfirmed submissions but it shouldn't be relied on.
The fact that duplicate submissions and the poor search can make it much harder for any individual submission to reach the magic 10 (or 11, or 12) confirmations before it expires has to be presumed to be intentional by now.
Ozric
Volunteer Moderator
Unfortunately I forgot to update my screenshots of the various number of issues since the 22nd of November. I do know that on the 1st of February there were 3,700 confirming issues on the Issue Tracker. Seeing the thread about the BGS issue today made me realise that the cull had just taken place.
Over 3,000 confirming issues have just been wiped off the tracker
(kudos on the number of pages )
Just thought I'd do a comparison of November to now. Obviously it's an almost 3 month gap so it's not ideal, but I expect there to be little movement outside of confirming issues turning into confirmed. We do know that the last time a manual cull of issues was done was in June of 2022, so it's been 8 months since all of the sections were looked at. (I have screenshots, no need to clutter the post with them though)
By Design (plus 2)
Confirmed (minus 20)
Confirming (minus 3,000+)
Expired (plus 3,198)
Fixed (plus 59)
Invalid (plus 7)
I think the lack of additions to the 'Invalid' category show that the Issue Tracker is still not being used correctly by either parties. 3,198 issues at 5 minutes an issue to create gives a total of 266 1/2 player hours wasted creating issues, many of which are still problems with the game they just didn't get enough people also posting on that specific issue.
Is there any chance we can get an update of the situation with it?
Over 3,000 confirming issues have just been wiped off the tracker
(kudos on the number of pages
)Just thought I'd do a comparison of November to now. Obviously it's an almost 3 month gap so it's not ideal, but I expect there to be little movement outside of confirming issues turning into confirmed. We do know that the last time a manual cull of issues was done was in June of 2022, so it's been 8 months since all of the sections were looked at. (I have screenshots, no need to clutter the post with them though)
By Design (plus 2)
Confirmed (minus 20)
Confirming (minus 3,000+)
Expired (plus 3,198)
Fixed (plus 59)
Invalid (plus 7)
I think the lack of additions to the 'Invalid' category show that the Issue Tracker is still not being used correctly by either parties. 3,198 issues at 5 minutes an issue to create gives a total of 266 1/2 player hours wasted creating issues, many of which are still problems with the game they just didn't get enough people also posting on that specific issue.
Is there any chance we can get an update of the situation with it?
I spent a week or so looking at it twice a day to try and develop a bit of empathy with Sally/Bruce and the fix teams and work out whether to shut up moaning or not (I think it's genuinely terrible that FDev as a whole have asked the staff who have to fix these things to work with such a terrible system for getting feedback from players. There are about 10,000 better open source tools and several million paid offerings so there's really no need for it...)
It's interesting what you say about both parties; because I can tell you absolutely nobody in the player community bothers to check for duplicates before posting; the Ferrari defect was reported three times on some days, as was a defect with Cyrillic character set failing to render. So I have plenty of sympathy there! But then again, all the decent platforms run a simple fuzzy match and let the reporter know they might be reporting a duplicate - this one doesn't.
Staying with the Ferrari example, during that week or two I took the time to mark all the duplicates I found and also cross reference them a bit. One of them was eventually Accepted and voted on. There's now a thread on the forum signposting that one specifically and asking for feedback, but none of the duplicates have been marked, despite being flagged, and there are at least 20+ good, solid, non-expired examples in those duplicates. There's really no need for any more feedback so I think this is again evidence that even though the tools are terrible, FDev are not taking even the the limited benefits they do get from using this approach. I think one of the perceived benefits may have been that forcing people to report details of their rig upfront saves a lot of time on gfx troubleshooting, but since 90% of the defects are in the back-end, connectivity, or in the business logic, it doesn't really matter - most of these defects could be demonstrated repeatably on an Intel USB stick.
All that said it IS good that since Christmas there is definite visible progress on going through the pile o' crap and working out where to start with the shovel. If you want some volunteers to help or at least bring you a flask of tea whilst you carry on shovelling, then... make it easier for everyone by at least using information you already have.
It's interesting what you say about both parties; because I can tell you absolutely nobody in the player community bothers to check for duplicates before posting; the Ferrari defect was reported three times on some days, as was a defect with Cyrillic character set failing to render. So I have plenty of sympathy there! But then again, all the decent platforms run a simple fuzzy match and let the reporter know they might be reporting a duplicate - this one doesn't.
Staying with the Ferrari example, during that week or two I took the time to mark all the duplicates I found and also cross reference them a bit. One of them was eventually Accepted and voted on. There's now a thread on the forum signposting that one specifically and asking for feedback, but none of the duplicates have been marked, despite being flagged, and there are at least 20+ good, solid, non-expired examples in those duplicates. There's really no need for any more feedback so I think this is again evidence that even though the tools are terrible, FDev are not taking even the the limited benefits they do get from using this approach. I think one of the perceived benefits may have been that forcing people to report details of their rig upfront saves a lot of time on gfx troubleshooting, but since 90% of the defects are in the back-end, connectivity, or in the business logic, it doesn't really matter - most of these defects could be demonstrated repeatably on an Intel USB stick.
All that said it IS good that since Christmas there is definite visible progress on going through the pile o' crap and working out where to start with the shovel. If you want some volunteers to help or at least bring you a flask of tea whilst you carry on shovelling, then... make it easier for everyone by at least using information you already have.
OK, so it's pretty clear someone at FDev is tidying up the Issues Tracker pretty much every day now - thanks!