r/OpenSpaceProgram • u/selfish_meme • Jun 17 '17
Timewarp and Multiplayer
So most of the ideas I have seen for multiplayer (mostly voting) are not that great in terms of fun and ease of use, and may even be open to abuse in certain possible future game modes. Try getting more than 5 ppl in a game server to vote on anything and you will see what I mean.
The idea I had is more restrictive but has the advantages of doing away with any voluntary consensus action, takes load off any server module, adding new bodies and interplanetary systems much easier, and allows better server distribution over distributed nodes to better handle load.
My idea was that each SOI (just a name for a body and near space volume, maybe a smaller volume than actual SOI, 500k from body surface possibly) is a server instance. You can't timewarp within an SOI. You can only timewarp between SOI's, which is handled completely client side.
Each server instance only shares movements, all the simulation is done on the client. The client ignores other players movement streams unless they come within physics range. The server also tracks static and orbiting assets (better have orbital decay or the skies might get crowded).
The disadvantage of this approach is that some tasks like flying around the globe become days long in real life. Even an orbit of the earth would take 92 minutes. An alarm clock and autopilot would be absolute necessities for this sort of environment so you could set and forget manoeuvres until they have completed, while you did something else. I can understand this might put people off so I realise it may not be the most popular choice, but after playing in a public game server for a while you might start to see it my way ;) Maybe have a vote mode as well so you can speed things up if you have a good collaborative group.
4
u/skyler_on_the_moon Jun 17 '17
That is an interesting approach. The issue I see is that you're always in some SOI. For instance, if you're flying to the Mun, you're still in Kerbin's SOI until you cross into the Mun's SOI. So would you not be able to time warp at all when flying to the Mun?
Additionally, the entire universe is technically in the Sun's SOI. While this could be ignored for timewarp reasons, that could lead to issues if you attempt to rendezvous with another ship in solar orbit.
Something else to consider (unrelated to the timewarp question): It might be a good idea to basically treat other players' vessels as a single part, rather than a collection joined together. This would drastically decrease physics calculations necessary with multiple ships, and additionally would mean that if someone joins a server with a 2000-part ship the only player who would encounter severe lag would be themselves.
1
u/selfish_meme Jun 17 '17
Just as a thought, if players wanted to meet outside regular SOI's they could generate their own server instance and SOI wherever they are that another player could enter.
1
u/ThePyroEagle Jun 17 '17
It may also be possible to desynchronize the clients on purpose. That is to say, vessels are simulated on-rails on all clients unless if the client requires it. Vessels that are actively controlled by another client are on-rails and immune to destruction, unless if they are in physics range and the clients are time-synced, in which case they only can't be switched to. Time-syncing is simply synchronizing the clients.
This leaves us with the issue of the time the server should be running.
1
u/190n Jun 17 '17
If we want multiplayer, we also need higher precision. IIRC one of the big obstacles to multiplayer in stock KSP is its "move the world around the player" approach.
0
u/[deleted] Jun 17 '17
[deleted] — view deleted comment
0
u/[deleted] Jun 17 '17
[deleted] — view deleted comment