Elite Dangerous Issue Report - 10/08/2021

Deleted member 182079

D
This is one of the most surreal things I have ever seen.
So much wrong with our game we made a top 20.
I don't think it's wrong, in fact I think it's great that FDev finally join other developers who take the same approach.

What I do find a bit troubling is that the number 1 issue is considered fixed, when there's still so many issues with it, many which are also very easy to spot. So I can either assume that something that looks "different" now in EDO (vs Horizons) is by design, or simply not on their radar. Oof.

The fact that all the changed and downright broken paintjobs didn't even make it into the list at all makes me a little sad - though I'm not blaming the top 20 but the god awful issue tracker (that should really be the number 1 issue at this point!) as I reckon there are a lot of dupe tickets out there (given the number of PJs involved for one).
 
ok so .. to get an issue solved you need plenty of votes on your issue (this for each of the +2800 issues present, and before they expire) or you don't even look at them ?! .. meaning small gameplay issues like un-scannable Stratum on plenty of planets (although it's signaled as solved, it's not.) is not a priority because too few players interesed in exo-scanning ? .. maybe you'll fix some VR issues too when 80% of your player-base buys a headset and then vote on the VR tickets (aka never) .. funny Fdevs .. I know you should prioritise when in crisis, but this again proves the game was just not ready to be released. I'm mildly positive on the evolution, but realise now I'll have to stop reporting tickets, as you just don't care if not voted upon .. useless system for 'small' but real issues.
 
7B7Ers8.png


Problems with lighting and illumination fixed? Now this will be the first time I say this and I regret it already, but do you actually play your own game?
 
You need an angry mob of upvotes to get anything fixed. its pathetic really

There's nothing necessarily wrong with this. I think it's a fair system to highlight an issue and bring it front and center. Many times when a player faces a bug or rare issue in the game, they'll sometimes be met with statements along the lines of:

  • "Well this hasn't happened to me, so it must be a you problem"
  • "Seems too rare to be a priority"
  • "Not that big a deal"

This system at least allows those who are facing a particular bug to increase it's visibility via other players who are dealing with similar problems that can then be addressed. It's not necessarily "angry mobs", it's just a tiered way of bring issues to the forefront.

This is one of the most surreal things I have ever seen.
So much wrong with our game we made a top 20.

Most if not all games have "so much wrong". Even the most well designed games have underlying issues. Some are just more transparent with those issues. I don't see why this is surreal. Microsoft Flight Simulator has a similar system to showcase more glaring issues via community votes and whether they're being worked on with an ETA, investigated or in progress. This is a good thing. It makes it aware that things are being worked on, especially something that may be of interest to a particular player and gives them a little hope to come. This is much better than the silence we're accustomed to.
 
Thanks for the update. please continue with these sort of updates.

things I think I have gleaned (reading between the lines)
  • at least two more major updates planned - assuming one a month / at least two months of fixes. (Sep & Oct)
  • low FPS performance - ‘work will continue up to the end of the year’ - sounds like a third update, (Nov) if not a fourth.
  • bit of a stretch, but if PC FPS is being worked on until the end of the year, then the Odyssey release for console won’t be until 2022. Assuming that the majority of the Frontier programmers will only be thrown at console optimisation once PC is in a subjectively ‘fit’ state, console release won’t be until Feb 2020 at the earliest.
 
Greetings Commanders!

I'd like to introduce you to something new. Below is our first Top 20 Issues table, summarising the highest voted issues on the Issue Tracker. As part of being open and honest about the game's development, we'll be regularly posting updated versions of this table and discussing it on our Supercruise News streams.

Note: the status and planned release of each issue is subject to change as various factors affect the ongoing development schedule.

jOe0Fjl.png


Top 20 Issues:

  1. Problems With Lighting and Illumination: We're happy to say this is now fixed since Update 6, having spent some time to monitor it afterwards. Any new issues to do with lighting should now be reported on the Issue Tracker as normal.

  2. Degraded Terrain Textures Compared To Horizons: A lot of the work for this went into Update 6, with some finishing touches coming in Update 7.

  3. Tiling Planetary Features: Changing the way planets are generated signifies a huge undertaking, so we're still investigating this.

  4. Low FPS Performance In Odyssey: This work will continue up to the end of the year, with improvements added already in Update 6, we know there is more to do.

  5. Limited Gameplay During Apex Shuttle Rides: Nothing to share at this time.

  6. Game Hangs On Exit Sometimes: Currently under investigation, we'll aim for the next update but it's one of the fixes more likely to end up in a later update.

  7. Invincible Thargoid Heart: We know this is a longstanding issue which has a complex cause. It's still being investigated and hasn't been forgotten. If you would like to contribute some information to this issue and others, please read this post.

  8. Anti-Aliasing Not Working Correctly: Some changes will go in Update 7 or 8, with significant improvements, but a full anti-aliasing system is slated for later this year.

  9. Joystick Buttons 32+ Not Working: Not started as other issues are prioritised.

  10. Expose Telemetry Data For Motion Simulators: We're currently discussing this internally, and may decide against it. If it does go ahead, it won't be before Update 8.

  11. NHSS Signals In Odyssey That Should Contain Interceptor Are Empty: Appears to be fixed, should arrive in Update 7 pending some further QA testing.

  12. Increased Performance Problems Since Update 5: Some further improvements are coming in Update 7, while general optimisation will be ongoing. The coming change won't be a fix for everyone, but will resolve some of the drops players are seeing.

  13. Supercruise Stuck At '0' Time Remaining With Tunnel Forming: Currently under investigation.

  14. Fleet Carrier Modules And Finances Not Calculated Towards Assets: In progress, slated for Update 7.

  15. NPC Fighter Kills In Conflict Zones Count As Progression: Currently under investigation.

  16. Support Missions Have Been Culled: Fix should be incoming in Update 7.

  17. A Previously Present Codex Entry Is Now Missing: Under investigation. Currently considered lower priority.

  18. System & Galaxy Map Misalignment In Widescreen Aspect Ratios: In progress, unlikely for Update 7.

  19. Stolen Tritium Cannot Be Donated Into A Fleet Carrier's Fuel Depot: Fixed, should arrive in Update 7.

  20. Missions and Rewards Not Sharing With The Team: Fixed, should arrive in Update 7.


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!

See you in the black Commanders,

o7
Appreciated. Sometimes the most frustrating thing can be trying to figure out whether Frontier even recognizes the existence of a given problem.

This part:
“As part of being open and honest about the game's development, we'll be regularly posting updated versions of this table and discussing it on our Supercruise News streams.”
Implies an established consistent time frame (you said “regularly” as opposed to “sporadically”); can you share anything about how frequently we can expect updates to this table?
 
All well and good. Just wait until you will fall through the net and can't get an issue fixed that is only annoying to you, but no one else. I'm pretty sure this will change your mind in no time.

Btw, in the OP table I see "TBC". What does it mean?

They mentioned in the stream that this table isn't like, a list of things they'll only work on as everything else falls to the wayside. For example, although numbers 08 and 09 - the joystick numbers 32+ and the expose telemetry data - are high on the list, they aren't a priority or necessarily being worked on as it's not a major concern over more mechanical issues. I'd imagine it's a complexity vs time and effort situation. If a mild bug that is annoying to some is a quick fix even if not in the top 20, it'll get a fix along with another patch that is released. This isn't supposed to be an end all be all list.

I took "TBC" to be something along the lines of TBD but I can't for the life of me think of what the "C" could stand for lol.
 
No. Nothing to report means nothing to report. It's stuff like this that gets studios to turtle up and stay silent. If they want to confirm its in progress they'll say it.
Sure, and I keep myself from getting hyped, let alone fantasize on what this point could mean, but "in progress" sure is closer to us than "investigating" or "not started" in their table.
 
I mean, it's not like this term is ambiguous in the slightest: so which one is it? 🤪


I suspect nobody dared to ask because no one wants to look as stupid as I do in the moment, right?
If it only would be TBCC, I would guess something like "Too Big Can't Compute"...
I wanted to say it was a typo since the C and D keys are so close but it's up there more than once lol
 
Hi @Zac Cocken - thanks so much for the update. Really reassuring to see. And I’m very excited to hear of improvements to antialiasing!

regarding your comment to keep using the Issue Tracker - I have unsuccessfully tried to raise several issues in the Issue Tracker recently, but the issue tracker throws an error when I try to create it.

I raised a support ticket (#92433) and was told it was a known issue and to basically “sit tight until it’s fixed”.

Are you aware of this issue? If so, how can we raise issues in the meantime to ensure they are tracked properly?

thanks!
 
Back
Top Bottom