Update 16 Deployment + Release Notes

Status
Thread Closed: Not open for further replies.
Guys, if the sync files freezes when downloading the update, clean your cache.
In the Windows 10 search bar, look for "Internet Options". Click "Delete ..." And check the boxes for the second, third and fourth items.
 
servers still offline?
1690916547352.png
 
Can't jump my carrier to Pwyll. Just says "no free slots" although there's only one carrier showing in the system map already. I assume the carrier jump queuing system is still overloaded from people trying to move around after the patch, but really if that's the case the error message being thrown up is misleading.

OK, it's saying "no time slots" which makes slightly more sense. Sorry, my eyesight's not the greatest.
 
Last edited:
I've 10Gbps internet. I'm already playing Update 17...

And what about people with 10Mbps internet? Will they still be playing U15??? ;)

OK, seriously now, some patience is needed for the updater to start, but it eventually starts. Just give it a few minutes...
 
I can't log in !
 

Attachments

  • Elite Dangerous Screenshot 2023.08.01 - 21.39.19.48.png
    Elite Dangerous Screenshot 2023.08.01 - 21.39.19.48.png
    1.1 MB · Views: 78
  • Elite Dangerous Screenshot 2023.08.01 - 21.39.57.65.png
    Elite Dangerous Screenshot 2023.08.01 - 21.39.57.65.png
    1.3 MB · Views: 80
I am unable to get into the game. I get a "login failure" message. I've tried verifying the files, completely reinstalling the game and tried on both horizon and odyssey. I just get this message:

failed.png
 
I am unable to get into the game. I get a "login failure" message. I've tried verifying the files, completely reinstalling the game and tried on both horizon and odyssey. I just get this message:

View attachment 362877

An issue I had once after an update, unlikely to apply to you, but you never know....

I have TWO Network Cards, one has internet access, the other does not. After a game update, it decided to use the other NIC and I didn't realise initially, just thought it was the usual post update quirkiness, where it's fine for some, while others have issues. Game thankfully has a setting to pick the NIC you want to use. Changed it back to what it had always been previously, and all was well. Basically, the launcher worked, but the game didn't think it had internet access, as it was using the wrong NIC.

Long-shot this applies to you, but you never know.
 
Can't jump my carrier to Pwyll. Just says "no free slots" although there's only one carrier showing in the system map already. I assume the carrier jump queuing system is still overloaded from people trying to move around after the patch, but really if that's the case the error message being thrown up is misleading.

OK, it's saying "no time slots" which makes slightly more sense. Sorry, my eyesight's not the greatest.
I have the same problem. It must be a major day for Cmdrs to come back to the game and finding their carriers out of position or something. Keep trying - it took me like 10-15 goes in each of my jumps out in the black, and each jump has a ridiculous warm up time of over an hour. I have to assume it'll settle down in a few days.
 
I have the same problem. It must be a major day for Cmdrs to come back to the game and finding their carriers out of position or something. Keep trying - it took me like 10-15 goes in each of my jumps out in the black, and each jump has a ridiculous warm up time of over an hour. I have to assume it'll settle down in a few days.
Yes...Me too, I'm getting the same error message of No Time Slots, and sometimes a Carrier warm up time of over an hour :-(
 
No mission board on Thargoid Alert Over (or thargoid alert - conflicting info really) system HIP 20485 Shinn Enterprise. I think it has been a long time now for it to be down...
 
My carrier jump timer started at 75 minutes. Is that a new standard not mentioned in the release notes or some side effect of heavy server loads?
Well, I get a "no time slots" error so definitely something temporary, I hope. I think the same thing happened during the last big update where a lot of players returned.
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom