Elite: Dangerous Dev Tracker

"Cori, post: 10208429, member: 89268"

You probably meant on Station exit attempt, but we understood you anyway.

Silly me, sorry Cori. Thanks o7

COMMANDERS, WE ARE LIVE!

Also just very quickly added this:

Community Issue of note:
[LIST]
[*]Alioth system permit will now be offered after obtaining friendly status with the Alliance - Issue ID 60974
[/LIST]

Phew! Come on in o7

COMMANDERS
Server stability should now be improving. I'll unlock the thread shortly.

COMMANDERS!
Investigating re-connect issues! Please stand by.

Maybe even less actually

COMMANDERS. BE READY.

We're to schedule.
Gates opening imminently...(well, in about 2 minutes).

COMMANDERS.

With not too long to go now until the deployment of 16.01 completes, an additional fix has been added to the notes above.

Community Issue of note:
[LIST]
[*]Sirius system permit will now be offered by Sirius Corp after obtaining full Ally status - Issue ID 60854
[LIST]
[*]The team are aware of additional issues with acquiring specific permits and are on the case o7.
[/LIST]
[/LIST]

[ATTACH type="full" width="650px" alt="MicrosoftTeams-image (190).jpg"]365634[/ATTACH]

Greetings Commanders.

Today sees the release of Update 16.01 for Elite Dangerous Live/4.0.

[HR][/HR]

The Elite Dangerous '4.0/Live' servers (only) are now offline until approximately 13:00 BST, when they shall return with the update available to you.

THIS THREAD SHALL REMAIN LOCKED AS A PLACE FOR ME TO KEEP YOU UPDATED ON DOWNTIME AND DEPLOYMENT PROGRESS.

Once the deployment is successful and the servers return, I shall unlock the thread.

If you wish to see the ... Read more

"View attachment 365416" < that was meant to be a nice little image...lovely.
Fixing.

[EDIT] Now complete with 'nice little image'. Sorry about that.

Commanders.
The following has been removed from the update notes due to instances still occurring.

[LIST]
[*]Ancient Relics can no longer rise into hovering or landed ships.
[/LIST]

Sincere apologies.

"DrinkyBird, post: 10208573, member: 272997"

[MEDIA=youtube]mlpYAaS2Efc[/MEDIA]
Source: https://www.youtube.com/watch?v=mlpYAaS2Efc

I literally just quoted this out loud.

COMMANDERS

Our apologies again for any turbulence around server connectivity. The team are working to correct it o7

"Flossy, post: 10208647, member: 27676"

I can't even see the CGs even if I did need to sign up again, they're just not there.

We're aware of this and on the case o7

"EARL TALTIN, post: 10208495, member: 302691"

The Imperial Cutter is still hitting the station wall when trying to leave a Coriolis station using the 'advanced' docking computer. The situation has not improved at all.

Checking o7

"Untilting, post: 10208490, member: 294702"

Various reports that the CGs have disappeared - is this a wait 5 mins thing or is action required?

https://forums.frontier.co.uk/threads/deliveries-requested-to-commemorate-duval-family-trade.619549/page-8

Noted!
On the case o7

Unlocking now I'm up to speed on both sides o7

"EARL TALTIN, post: 10208500, member: 302691"

Fleet Carrier jumps still require more than 15 minutes.

This can happen in busy periods. Times are only a concern if they extend beyond 60 minutes.

"Evazan, post: 10208531, member: 179481"

[USER=188830]@sallymorganmoore[/USER] Just to be clear, Its the auto launch, not autodock thats causing the Cutter to still crash into the station wall.

Unfortunately I'm just going to take that out of the notes entirely, one moment o7 Sorry about this.

COMMANDERS

Locking the thread just to prevent a little 'overwhelm' of the same issues reported.
Just want to confirm I've noted the following:
[LIST]
[*]Issue with autodock for the Cutter is reported as still present.
[*]CG information is missing.
[/LIST]