Benoit Beausejour · Chief Technology Officer

So interestingly, that's still being investigated, but the current hypothesis on this is that the way the Pyro system was built... So first of all, the requirement when you connect, what the hell is the game doing in that loading screen? And then you open the console and it's stuff flying around. What is it doing? It's going through this context establisher set of tasks, which are all the phases for the connection. Currently, when players load into Pyro and have a long load time, it seems to be related to the way the system was built, where there's an entity in the Pyro system that holds the spacescape for the system. Now, we're peeking behind the curtains of how the levels are made, but there's a requirement for the CET connection that requires that all the entities that the client needs to load need to have an authority assigned. So this is directly a server meshing change. And so if an entity that you're loading doesn't have an authority yet, which could be any server in the mesh, if one of them doesn't have an authority yet, then the load time will have to wait for this entity to gain an authority. Now, how can this entity not have an authority? So our current hypothesis is that if the server that is hosting that Pyro spacescape entity, which has a giant radius, so every client loading into Pyro needs that entity, if the server that hosts that entity is currently rebooting because it has a crash on it, then all players will have to wait for that server to do the full provisioning loop, boot up, load the data, acquire the entity, and then players will load in. For some players, that busts the time it needs for the timeout for the login. So that's our current lead, and we think we have a fix, but obviously that's another one that we would roll out. I think it's a code fix on the hybrids that we can actually roll out for that.