sallymorganmoore
Senior Community Manager : Elite Dangerous
Greetings Commanders,
A very warm and happy 3308 to you all - it's really great to be back in The Black with you all in another epic journey across our evolving Galaxy with another year set ahead of us.
We're taking time this week to gather our plans, catch up and prepare - so bear with us for a few days more on schedules and such as we get out stars aligned.
What I am happy to share is that the team have been working on a small hotfix this week for Elite Dangerous console players, to address the following:
I'm also refreshing lists with known issues we were tracking last year which are not yet planned for immediate fix (in the form of hotfixes like the above) BUT are in sight as candidates for Update 10 (again, as usual, if anything changes with scheduling fixes we'll let you know for sure).
One to call out specifically is that we've picked up on the following issue reported from the Community, which has been noted and logged:
The common heavy hitters/some fallout from Update 9 which are always worthy of noting are listed but not limited to the below:
I'm absolutely sure that I haven't included every issue you'd like to have seen mentioned in this real quick update for you super stars today, but rest assured that the same statement still stands in that these lists are just the surface "callouts and nods" to issues that have been more openly discussed previously.
UPDATED INFORMATION 07/01/2022
I'll keep it short and snappy because ah...few things going on today round the back here which needs some coordinated/focused attention
We're still actively reading, noting and trawling the Issue Tracker/Forums/Social Channels for reports which we remain ever grateful for. Thank you always! o7
Hope you've had a lovely week so far! Here's to 3308!
o7
A very warm and happy 3308 to you all - it's really great to be back in The Black with you all in another epic journey across our evolving Galaxy with another year set ahead of us.
We're taking time this week to gather our plans, catch up and prepare - so bear with us for a few days more on schedules and such as we get out stars aligned.
What I am happy to share is that the team have been working on a small hotfix this week for Elite Dangerous console players, to address the following:
- Cannot edit fire groups - menu navigation does not work.
- If your ship has modules that fall under the Utility category, you're unable to set your fire groups because navigation within the fire groups tab does not work.
- Further Reading: Commanders can become unable to set fire groups for such modules as the Detailed Surface Scanner (DSS), Data Link/Comp Scanner due to not being able to navigate down the menu at all. After subsequent investigation, it seems the Fire Groups menu works without issue when Hardpoints or large Optional Modules (such as a Multi-Limpet Controller) are equipped, but after removing those so only Utility Mounts or smaller Optional Modules (such as the DSS) remain, the Fire Groups menu becomes unresponsive.
The hotfix is looking good for release early next week with the usual caveat of "subject to change", but just wanted to give you a rough idea of timescale.
You'll be kept in the loop as we move with the release schedule specifics.
You'll be kept in the loop as we move with the release schedule specifics.
I'm also refreshing lists with known issues we were tracking last year which are not yet planned for immediate fix (in the form of hotfixes like the above) BUT are in sight as candidates for Update 10 (again, as usual, if anything changes with scheduling fixes we'll let you know for sure).
One to call out specifically is that we've picked up on the following issue reported from the Community, which has been noted and logged:
- Credit Balance Not Updating On Ship System Panel When Performing Any Balance-Changing Action (Buying/Selling Commodities, Missions etc.) Until After Relog.
- Checked internally for both Commodity Market changes and rewards from missions. Credit balances update only with a relog.
The common heavy hitters/some fallout from Update 9 which are always worthy of noting are listed but not limited to the below:
- Investigations on reports of performance issues continue (thank you for the latest threads/conversations!).
- Starting Frameshift makes the game freeze/lock.
- Unable to access Session Logs.
- Disconnect/suspended in Supercruise.
- Empty Faclities lists for Stations in the system map.
- Continued experiences of stability issues on console, particularly PS5 but also on Xbox.
- Inconsistency with Codex entries.
- Commanders are unable to use the Profile Analyser to clone the profile of NPC corpses (Can't believe Paul didn't use the term 'Corpse' in his last post on Known issues. Even Bruce didn't. I just wanted an excuse to use it again, but their use of 'deceased' was way more elegant to be fair).
- Hostile ships can appear incorrectly (as non-hostile) on the radar.
- “Floating” Guardian Materials at Guardian Sites were sighted and logged.
- The Scorpion turret remains to be inheriting textures/decals from the ground that dance/parallax across it. Texture movement is at its worst when the SRV itself is in motion.
- Instances of the Odyssey On-foot tutorial being unable to be completed due to it not finishing.
- Occasionally, when the player disembarks, the game will display ' Board the Dropship' even though Dylan leaves the port. The player can then go into the concourse of the social space, but nothing will work as it should as they're not supposed to be here.
I'm absolutely sure that I haven't included every issue you'd like to have seen mentioned in this real quick update for you super stars today, but rest assured that the same statement still stands in that these lists are just the surface "callouts and nods" to issues that have been more openly discussed previously.
UPDATED INFORMATION 07/01/2022
I'll keep it short and snappy because ah...few things going on today round the back here which needs some coordinated/focused attention
- I can now confidently confirm that (don't make me regret using those words) we are now aiming for the remaining issues with firegroups on PC to be fixed for Horizons players in line with the console fix outlined above.
- IMPORTANT NOTE:
- Commanders, this won't be taken lightly for sure and believe me when I say that I know the pain of reassigning firegroups for many of you, but giving you as much quick warning in advance:
This fix is highly likely (please prepare for it) to require you to once again reassign your firegroups for all ships once the hotfitx is applied. I was going to mention this in the deployment schedule on the day BUT I'm just thinking ahead and popping it here early. I don't want it to be as much of a pain for you as it would be to hear this on the very morning of the hotfix going live (I know it's a pain either way but I hope having the note here softens it even a little).
We're still actively reading, noting and trawling the Issue Tracker/Forums/Social Channels for reports which we remain ever grateful for. Thank you always! o7
Hope you've had a lovely week so far! Here's to 3308!
o7
Last edited:
)