Elite Dangerous Issue Report - 10/08/2021

Ignoring the issues with Odyssey that you are currently addressing obviously, some PP groups have noticed that the PP issue that was in the top 10 most upvoted issues since last year, September, WAS MARKED AS FIXED and is thus not listed in this ranking, at all. Without any actual fix to this issue being rolled out in the game or its backend DBs.

This is the issue:

We have verified it multiple times over this week and last PP Cycle and we are slightly disheartened by the fact that this issue, that has over 60 contributions and even more upvotes was swept under the rug. We don't even know when it was removed from the "existing issue"-board, and we hope that you awesome CMs can poke the QA folks that handle this sort of thing to please reopen it :) (and maybe look into it further, the Inflation Bug since then has been even more exploited and Odyssey has caused some hiccups as well. A full recalculation of Income Values based on the systems in a sphere is probably necessary in our opinion!). There have been other reports that greatly overlap with the big one, although those are not marked as "fixed", so this was most likely just a mistake by someone.

unknown.png


Anyway, love your work, and if you can explain what happened here, that would be awesome!
~Oraki

The bug with miscalculation of CC was reported in October 2020 - would really appreciate some sort of response from FDev on this ^

Power Play is an important aspect of the game for a large number of people, a game mode that depends on accurate calculation of CC, right now we are playing Monopoly where the banker randomly takes money from one side and gives it to another; this is game-breaking and needs to be addressed as a matter of urgency.
 
I’d just like to give a 👍👍 to a small change to Issue Tracker that I’ve just noticed - if you’re adding a confirmation to an existing report, you are now required to select one of the reproduction options before you can click submit.

This should hopefully help get a few more issues across the 10 Confirmations line because previously some people would forget to click “can reproduce” and their submission wouldn’t be counted.
 
This is a really positive move.

But @Zac Cocken @sallymorganmoore what about reports that are duplicated many times and have been closed many times over the years. For example, the most recent incarnation of this particular bugbear of mine: https://issues.frontierstore.net/issue-detail/37939

Which has been reported many, many times in the past:

https://issues.frontierstore.net/issue-detail/696
https://issues.frontierstore.net/issue-detail/1014
https://issues.frontierstore.net/issue-detail/2881
https://issues.frontierstore.net/issue-detail/15648
https://issues.frontierstore.net/issue-detail/18081
https://issues.frontierstore.net/issue-detail/19503
https://issues.frontierstore.net/issue-detail/20350

Any chance of getting this one onto your radar - I'm pretty sure combining the votes for all the above (which are very likely not all the variants) would bump this one up close to or into the top 20!
 

sallymorganmoore

Senior Community Manager : Elite Dangerous
This is a really positive move.

But @Zac Cocken @sallymorganmoore what about reports that are duplicated many times and have been closed many times over the years. For example, the most recent incarnation of this particular bugbear of mine: https://issues.frontierstore.net/issue-detail/37939

Which has been reported many, many times in the past:

https://issues.frontierstore.net/issue-detail/696
https://issues.frontierstore.net/issue-detail/1014
https://issues.frontierstore.net/issue-detail/2881
https://issues.frontierstore.net/issue-detail/15648
https://issues.frontierstore.net/issue-detail/18081
https://issues.frontierstore.net/issue-detail/19503
https://issues.frontierstore.net/issue-detail/20350

Any chance of getting this one onto your radar - I'm pretty sure combining the votes for all the above (which are very likely not all the variants) would bump this one up close to or into the top 20!

Very much part of the discussion already, with how to handle duplicates and such.
I've collected many duplicate tickets from forum Commanders to find in TOTAL across all tickets there are 10+ individual contributions, but none of the tickets go to voting stage because none of them as individual tickets total up to the 10 contribution thingy...
LOOK AT ME HAVING A RANT HAHAHA!!
 
Very much part of the discussion already, with how to handle duplicates and such.
I've collected many duplicate tickets from forum Commanders to find in TOTAL across all tickets there are 10+ individual contributions, but none of the tickets go to voting stage because none of them as individual tickets total up to the 10 contribution thingy...
LOOK AT ME HAVING A RANT HAHAHA!!
I am sure these have been discussed internally yet just throwing ideas based on my experience anyway. I wonder if using an existing solution would be simpler in this case. Maybe using a GitHub repo or a public facing JIRA (I guess everyone uses JIRA internally anyway) for issue tracking. At least where we work, we pretty much always decide to buy instead of make when existing solutions are available. I am sure other 3rd party devs for ED would echo my thoughts.
 
I am sure these have been discussed internally yet just throwing ideas based on my experience anyway. I wonder if using an existing solution would be simpler in this case. Maybe using a GitHub repo or a public facing JIRA (I guess everyone uses JIRA internally anyway) for issue tracking. At least where we work, we pretty much always decide to buy instead of make when existing solutions are available. I am sure other 3rd party devs for ED would echo my thoughts.

that would be hilarious.. use git for tracking issues... but keep using some garbage old svn/cvs type system for the actual code.
 
that would be hilarious.. use git for tracking issues... but keep using some garbage old svn/cvs type system for the actual code.
What??? I never implied using "git" to track issues. GitHub has an issue tracker that is totally separate from its git repository and you can use one without the other. Moreover, SVN has its uses. Git is bad when handling large files like game assets (git-lfs handles that issue somewhat but there are core assumptions in git that were not meant for large file use) and hence many game devs still use SVN.
 
Last edited:
Very much part of the discussion already, with how to handle duplicates and such.
I've collected many duplicate tickets from forum Commanders to find in TOTAL across all tickets there are 10+ individual contributions, but none of the tickets go to voting stage because none of them as individual tickets total up to the 10 contribution thingy...
LOOK AT ME HAVING A RANT HAHAHA!!

That's really good to hear you're tackling this, and that a GOOD RANT is all part of the process ;)

A good ticketing system will have a tool that automatically tries to identify duplicate tickets, not just for ticket submissions but for staff dealing with them. If Frontier's doesn't already have something like that, it should be pretty easy to add. Also, a tool to allow merging of duplicates (not just marking duplicates) would be really handy, as in your case the tool could also automatically merge votes and comments / contributions, which would help truly assess which issues are the most popular.
 
What??? I never implied using "git" to track issues. GitHub has an issue tracker that is totally separate from its git repository and you can use without the other. Moreover, SVN has its uses. Git is bad when handling large files like game assets (git-lfs handles that issue somewhat but there are core assumptions in git that were not meant for large file use) and hence many game devs still use SVN.
you did say using a repo on github. But no. SVN doesn't have it's uses except as something you tell someone to stop using for managing code post 2010. Manage the large game assets separate from the code using something other than git if you wish...but there is no reason to handicap yourself across the board because you find large asset management easier in a different system. We dont have bugs because texture files are getting mis-managed. We often have regressions and bugs because whatever they're using is garbage for merging branches. ..and garbage for bisecting commits to find where bugs were introduced to track them down. ...giving them the benefit of the doubt there in that it's not a skill/competency issue that gives us these issues every release - and just (largely) the wrong tools in place.
 
I have been through rcs, cvs, subversion and perforce... when it comes to code, nothing beats git.
Indeed. I am mostly talking about game assets. Some devs use git for code and something else for assets, some use svn for both. Issues and regressions never depends solely on a VCS and beating a strawman here makes no sense. We were discussing issue tracking and reporting and I never intended to discus VCS. If you want to do so, we can do that elsewhere.

I personally am a Git user but I can understand why people might use other VCS.
 
This is a reflection of the current scenario, and due to the ever-evolving nature of game development, the planned release for these fixes is subject to change. Let us know what you think of this report below!
What I think is that it's great and should've been part of the alpha/beta release. It does give a sense of direction and the impression that Frontier not only know about issues but are working on them and where they are at the moment. Jolly good. :)
 
Very much part of the discussion already, with how to handle duplicates and such.
I've collected many duplicate tickets from forum Commanders to find in TOTAL across all tickets there are 10+ individual contributions, but none of the tickets go to voting stage because none of them as individual tickets total up to the 10 contribution thingy...
LOOK AT ME HAVING A RANT HAHAHA!!
Welcome to the dark side!

The way that duplicate bugs can actually make it harder for an issue to be confirmed, and therefore advising people to "report bugs" can be a really bad idea is my #1 issue with the bug tracker process.

I'm not at all clear why Elite Dangerous needs 10 confirmations to start with when all other Frontier games need 3 - if one person has reported it, and three more have specifically searched for it and said "yes, that happens to me as well" ... do you really need another seven?

There'd still be duplication issues even with 3 but it'd be a lot more manageable and the chances of one of them passing the threshold would be much better.
 
And still nothing about the terrible Galaxy and System map user experience and UI? Extremely dissapointed not to see attention in this area and I'm certain others are well based on forum threads and bug trackers.
 
Joystick Buttons 32+ Not Working: Not started as other issues are prioritised.
I just wanted to say thank you / the team for acknowledging this as being something that has been highly voted. I understand that it is not currently prioritized, however, I am still looking forward to this eventually being fixed.

That aside, this is a great improvement in the transparency and it's fantastic seeing lists like this.
 

Deleted member 110222

D
Honest opinion FD?

The issue tracker working by votes is flawed.


This right here is an issue that is causing players to get engineers unlocked for free.

This is not something you should trust common gamers to vote for as needing a fix.

If a bug benefits players, they will do everything in their power to make sure it remains unfixed.

Not only this, but you are asking players to take advantage of what is likely an exploit to "confirm it."

You need to get external testers. If you cannot reproduce this internally for whatever reason, you need external testers to confirm it instead. This is not something you should trust us to help you with. Most of us won't, sadly.

The desire to make this game run well and right is not as pure as you might think.
 
Honest opinion FD?

The issue tracker working by votes is flawed.


This right here is an issue that is causing players to get engineers unlocked for free.

This is not something you should trust common gamers to vote for as needing a fix.

If a bug benefits players, they will do everything in their power to make sure it remains unfixed.

Not only this, but you are asking players to take advantage of what is likely an exploit to "confirm it."

You need to get external testers. If you cannot reproduce this internally for whatever reason, you need external testers to confirm it instead. This is not something you should trust us to help you with. Most of us won't, sadly.

The desire to make this game run well and right is not as pure as you might think.

Reading this it's just the unlock access to the Engineer. I think they should just get rid of most of the Engineer unlock requirements.
Thinking I'll add my thoughts to suggest things forum.
 
Back
Top Bottom