Another Monday update - and apologies we know many of you are waiting for news on new content. We are too. But there are limits to what we can realistically add to the current game without introducing more risk or instability. Issues that stop people playing the game as it stands have to come first.
As a result the latter part of last week was largely spent tracking down and fixing a tricky bug that was causing online crashes.
As we shared on Discord, we’ve now identified the root cause of crashes when the host launches an online event. In short, challenges were sometimes being launched before all players had fully received the data. The larger the challenge, or the higher the latency or lower the bandwidth, the more likely this was to happen.
We have a potential fix in place, which includes:
Waiting longer before a challenge starts to ensure all players have received the data (you will notice longer load times on larger challenges or with lower bandwidth connections)
Fixing an issue where a default engine cap meant larger challenges were not always being broadcast correctly
Displaying challenge size as a percentage in the map popup so you can see when you are near or over the limit
Preventing hosts from launching challenges over 100% of the allowed size in multiplayer (these can still be played offline)
Unfortunately good and bad news - good news is that this fix has now made it much easier to recreate the disconnects issue - bad news they are now much more prevalent. So we can't share it as yet until we have also fixed the problem with disconnects.
We are indeed playing a game of whack-a mole.
Once we find and fix that issue we will be testing a beta build on Steam. If that testing confirms things are stable, we will move to submit the update.
We’ll update again once we’ve got more news.
In the meantime look for Part 2 of our Origins of Burnout series tomorrow and another poll coming later in the week.
Thanks for your continued support, it is so appreciated.