Greetings CMDRs,
Here’s a further update on where we are with Odyssey, and to keep you updated on our progress and our investigations, and talk a little about our next steps. This will be a long post, but please bear with me.
Firstly, once again I apologise for the experience many players have had running Odyssey, particularly the server issues and disconnects. Despite careful server spooling up anticipating significant demand, they were still overloaded. After a good deal of investigation, the main cause of this proved to be to do with Fleet Carriers and the systems they use. I’ll try and explain the gist of what the problem was, how we found it, and why it didn’t show during the public Alpha. The whole team are working incredibly hard to resolve the issues as quickly as possible and improve player’s experiences and this is part of that process.
As you probably know, we split Horizons and Odyssey into two sets of servers – with the plan to keep it that way until we ship Odyssey on console. Fleet Carriers exist in both ‘worlds’ and when a Fleet Carrier jumps, this (and all the players on board) are kept in sync between the two galaxies. Due to a bug with them, significant amounts of data were going back and forth between the two worlds unnecessarily, and this loop between the sets of servers simply mounted up and started bringing servers down or blocking them (resulting in many players getting disconnect errors). This is why we stopped Fleet Carriers jumping, and immediately we saw a significant improvement overall. There were other issues too with this subsystem, keeping the BGS and other things in sync between the ‘worlds’. Once we had a solid fix for the Fleet Carrier and sync issues we deployed it to the servers, and re-enabled Fleet Carriers jumping. This was compounded by the fact we had a record number of concurrent players, so the servers were already working hard. Initially we thought this was the effect we were seeing – that the high number of players was the main issue - but eventually some very smart people determined what was happening with Fleet Carriers.
Turning to the subject of performance, first of all I’d like to provide some background. When we first set the min specs for Elite Dangerous (back at the time of the Kickstarter in 2012) we made the assumption that for low-spec machines the game was playable as long as the frame rate was above 30 fps, with 60 fps for higher spec machines. Over the subsequent weeks and months after release in 2014 we optimised the game significantly. We had a similar thought process for Odyssey, especially considering that the lower spec machines will tend to be five years old or more, or be laptops, that 30 fps would be acceptable as a minimum spec performance. Separately, we have heard reports of very high spec machines failing to perform as expected. We believe this is a different issue, possibly CPU-related, and are looking into that too, as we speak.
We will get to the bottom of the performance issues, particularly with the support of the community who are already providing useful information.
Elite has always been about scale and ambition. With this latest, and biggest, expansion the team have taken on an amazing challenge. The whole galaxy in 1:1 scale, now down to the millimetre. Millions of players interacting with each other and many millions of AI game characters on billions of worlds, all orbiting around each other in an incredibly rich galaxy-wide ballet. I truly believe the team have created a milestone in modern video game history. This is not a static arena shooter where all the players join at the start, but where players are continually joining, leaving, travelling between servers alone and in groups, and so many other things. It is a real shame this incredible achievement is somewhat overshadowed by the issues we have been seeing. We remain committed to improving everyone’s experience. In the words of JFK: “We choose to go to the moon this decade and do the other things… not because they are easy, but because they are hard.”
So what are we doing to fix the issues?
As mentioned above, the team have been working incredibly hard to support and fix critical issues. They have already made good progress with three hot fixes and many server tweaks too, but we can see there is still more to come. Disconnects are now greatly reduced, despite record concurrent player numbers.
As already explained, the performance issues may take a little longer to resolve, and we greatly appreciate your patience.
Our plan is to publish a road-map by 4th June as we continue to push forward addressing issues, including giving some details on specific improvements, building upon the fixes the team have already made.
Thank you and my apologies again for the bumpy start to Odyssey.
Here’s a further update on where we are with Odyssey, and to keep you updated on our progress and our investigations, and talk a little about our next steps. This will be a long post, but please bear with me.
Firstly, once again I apologise for the experience many players have had running Odyssey, particularly the server issues and disconnects. Despite careful server spooling up anticipating significant demand, they were still overloaded. After a good deal of investigation, the main cause of this proved to be to do with Fleet Carriers and the systems they use. I’ll try and explain the gist of what the problem was, how we found it, and why it didn’t show during the public Alpha. The whole team are working incredibly hard to resolve the issues as quickly as possible and improve player’s experiences and this is part of that process.
As you probably know, we split Horizons and Odyssey into two sets of servers – with the plan to keep it that way until we ship Odyssey on console. Fleet Carriers exist in both ‘worlds’ and when a Fleet Carrier jumps, this (and all the players on board) are kept in sync between the two galaxies. Due to a bug with them, significant amounts of data were going back and forth between the two worlds unnecessarily, and this loop between the sets of servers simply mounted up and started bringing servers down or blocking them (resulting in many players getting disconnect errors). This is why we stopped Fleet Carriers jumping, and immediately we saw a significant improvement overall. There were other issues too with this subsystem, keeping the BGS and other things in sync between the ‘worlds’. Once we had a solid fix for the Fleet Carrier and sync issues we deployed it to the servers, and re-enabled Fleet Carriers jumping. This was compounded by the fact we had a record number of concurrent players, so the servers were already working hard. Initially we thought this was the effect we were seeing – that the high number of players was the main issue - but eventually some very smart people determined what was happening with Fleet Carriers.
Turning to the subject of performance, first of all I’d like to provide some background. When we first set the min specs for Elite Dangerous (back at the time of the Kickstarter in 2012) we made the assumption that for low-spec machines the game was playable as long as the frame rate was above 30 fps, with 60 fps for higher spec machines. Over the subsequent weeks and months after release in 2014 we optimised the game significantly. We had a similar thought process for Odyssey, especially considering that the lower spec machines will tend to be five years old or more, or be laptops, that 30 fps would be acceptable as a minimum spec performance. Separately, we have heard reports of very high spec machines failing to perform as expected. We believe this is a different issue, possibly CPU-related, and are looking into that too, as we speak.
We will get to the bottom of the performance issues, particularly with the support of the community who are already providing useful information.
Elite has always been about scale and ambition. With this latest, and biggest, expansion the team have taken on an amazing challenge. The whole galaxy in 1:1 scale, now down to the millimetre. Millions of players interacting with each other and many millions of AI game characters on billions of worlds, all orbiting around each other in an incredibly rich galaxy-wide ballet. I truly believe the team have created a milestone in modern video game history. This is not a static arena shooter where all the players join at the start, but where players are continually joining, leaving, travelling between servers alone and in groups, and so many other things. It is a real shame this incredible achievement is somewhat overshadowed by the issues we have been seeing. We remain committed to improving everyone’s experience. In the words of JFK: “We choose to go to the moon this decade and do the other things… not because they are easy, but because they are hard.”
So what are we doing to fix the issues?
As mentioned above, the team have been working incredibly hard to support and fix critical issues. They have already made good progress with three hot fixes and many server tweaks too, but we can see there is still more to come. Disconnects are now greatly reduced, despite record concurrent player numbers.
As already explained, the performance issues may take a little longer to resolve, and we greatly appreciate your patience.
Our plan is to publish a road-map by 4th June as we continue to push forward addressing issues, including giving some details on specific improvements, building upon the fixes the team have already made.
Thank you and my apologies again for the bumpy start to Odyssey.
![Ed [FCOC]](https://forums-cdn.zaonce.net/data/avatars/m/144/144754.jpg?1583440657){kind=avatar}
