I noticed that when ship hosting changes, the ship goes into its low poly state before becoming high resolution again. My assumption is that it takes time to download the ship state from the new host, even though the ship hasn't changed and the new clients all have the correct state of the ship locally.
It seems like some kind of version-control or hash would solve this problem. Every time the ship is modified, the hash is changed and everyone has to download the new state (ideally just the delta). Heck, if you make the ship specification plaintext, you could even use git to do it
With a system like this ideally one could "preload" all ships within a certain radius with intercept trajectories that would make co-visibility likely, so that ships aren't low-res like they currently are.
I'm sure you're already thinking of this, or otherwise there's some limitation of the peer to peer network that makes it challenging, but I thought to throw it out there just in case. Feel free to ignore if it's irrelevant!
It seems like some kind of version-control or hash would solve this problem. Every time the ship is modified, the hash is changed and everyone has to download the new state (ideally just the delta). Heck, if you make the ship specification plaintext, you could even use git to do it
With a system like this ideally one could "preload" all ships within a certain radius with intercept trajectories that would make co-visibility likely, so that ships aren't low-res like they currently are.
I'm sure you're already thinking of this, or otherwise there's some limitation of the peer to peer network that makes it challenging, but I thought to throw it out there just in case. Feel free to ignore if it's irrelevant!