qsb-dev / quantum-space-buddies Goto Github PK

Ditching the wake up event should allow us to do everything mid-game. Like starting or joining a server. Would also make it easier to maintain the connection when travelling to the eye.

It would be absolutely incredible to play this multiplayer in VR. Any chance we could collaborate with the mods? They're both pretty extensive, I imagine.

Two ways we can go about this.

Easy way would be just showing a dummy ship model around the player if they're currently piloting a ship. Could be easily achieved by just having an isPilotingShip flag, that is broadcast with a bool message.

Harder way is to actually sync each ship's position separately from the players. Would need to replicate the behavior already implemented with the player models, including all the sector stuff. Be cool if we could refactor it so that the same behavior is used for syncing player positions, ship positions, and any other moving objects we might want to sync. But each synced object will mean an extra load on the server...

Couldn't figure out what was causing it. Has only happened when tying from the nova. If all else fails, better wrap the broadcast function in a try / catch, so that the usual death stuff can still happen.

Right now the speed is a constant 10x, which can still take a while to catch up. If it's constant and too fast, the player can easily overshoot the target time, and will have to pause afterwards. So making it dynamic is better: the bigger the difference, the faster it gets. As the gap becomes smaller, the fastforward speed becomes smaller.

• If server dies first, clients will pause because they're ahead
• If client dies first, it will sleep to catch up to server. Then, when server dies, it will pause because it's ahead.

Dozing off changes the time scale, so it would result in de-sync.

List of funny death messages: https://docs.google.com/document/d/17wH8Ck1mOv2q_MidEEDXrcE2GI7tPboKSm4DVW7qKc4/edit

Right now if the ship is destroyed, it will respawn at the start, but still be destroyed.

For instance, if player is 5 minutes ahead of server, pausing for 5 minutes would be annoying. In that case, might as well skip to the next loop. Important: don't increment the loop count for this kind of loop skip!

Please make it so if a character dies, it resets the loop for all! Teleporting back to Timber Hearth after flying into the sun is a tad underwhelming. Otherwise, give us the option to enable this functionality.

The NetworkManagerHUD hotkeys conflict with some game controls. Need to disable them.

happens after changing loops. I think?

Whenever I interact with one of the Nomai control orbs, it falls out of its track, either floating or bouncing wildly in place. This makes opening any door to a Nomai ruin impossible.

The console calls the following errors:

InvalidOperationException: Operation is not valid due to the current state of the object. Stack trace: System.Linq.Enumerable.First[NomaiOrbTransformSync] (IEnumerable1 source, System.Func2 predicate, Fallback fallback) System.Linq.Enumerable.First[NomaiOrbTransformSync] (IEnumerable1 source, System.Func2 predicate) QSB.OrbSync.Events.OrbUserEvent.HandleServer (QSB.WorldSync.Events.WorldObjectMessage message) QSB.OrbSync.Events.OrbUserEvent.OnReceiveLocal (Boolean server, QSB.WorldSync.Events.WorldObjectMessage message) QSB.Events.QSBEvent1[T].OnReceive (Boolean isServer, .T message) QSB.Events.QSBEvent1[T].<.ctor>b__5_0 (.T message) QSB.Messaging.MessageHandler`1[QSB.WorldSync.Events.WorldObjectMessage].OnClientReceiveMessageHandler (QuantumUNET.Messages.QSBNetworkMessage netMsg) QuantumUNET.QSBNetworkConnection.InvokeHandler (QuantumUNET.Messages.QSBNetworkMessage netMsg) QuantumUNET.QSBLocalClient.ProcessInternalMessages () QuantumUNET.QSBLocalClient.Update () QuantumUNET.QSBNetworkClient.UpdateClients () QuantumUNET.Components.QSBNetworkIdentity.UNetStaticUpdate () QSB.QSBCore.Update ()

InvalidOperationException: Operation is not valid due to the current state of the object. Stack trace: System.Linq.Enumerable.First<QSB.OrbSync.QSBOrbSlot> (System.Collections.Generic.IEnumerable1<QSB.OrbSync.QSBOrbSlot>,System.Func2<QSB.OrbSync.QSBOrbSlot, bool>,System.Linq.Enumerable/Fallback) <0x001a9> System.Linq.Enumerable.First<QSB.OrbSync.QSBOrbSlot> (System.Collections.Generic.IEnumerable1<QSB.OrbSync.QSBOrbSlot>,System.Func2<QSB.OrbSync.QSBOrbSlot, bool>) <0x00061> QSB.WorldSync.QSBWorldSync.HandleSlotStateChange (NomaiInterfaceSlot,NomaiInterfaceOrb,bool) <0x00133> QSB.OrbSync.OrbPatches.CheckOrbCollision (bool&,NomaiInterfaceSlot,NomaiInterfaceOrb,bool,single,single,NomaiInterfaceOrb&) <0x002ce> (wrapper dynamic-method) NomaiInterfaceSlot.CheckOrbCollision_Patch1 (object,NomaiInterfaceOrb) <0x0007a> NomaiInterfaceOrb.CheckSlotCollision (bool) <0x0023d> NomaiInterfaceOrb.FixedUpdate () <0x00645>

Examples:

• Alek died by Anglerfish
• Alek died by Energy

To avoid de-syncing, time scale needs to stay always at one. Will be useful even if we eventually sync everything manually instead of depending on the simultaneous start of all sessions.

When a character (e.g. Slate) is talking to another client, the local player walking around will affect the move spring of the character.

Related to #27

When arriving at the eye, suit is equipped by default. Since no "suit up" event happened, players don't see each other with suit equipped until suit state changes.

Right now the limit seems to be around 8. This should be as high as possible.

Needs further investigation for root cause

If player A dies from nova and goes to next loop, other players shouldn't be able to see player A until they are in that loop too.

Each client tracks what's the current loop. So when a client connects when the server is already in loop X, we need to make sure the client gets synced to that loop too.

Right now, if the player model is wearing the space suit, all other models will reflect that. We need to keep them independent and send messages declaring the model change.

...but ship one works fine

Meditation skips the current loop, so it would result in a de-sync.

If a player disconnects, we need to remove all the trash left behind, like any objects that the current client has local authority over (player body, ship body).

Players who have connected but not woken up keep a fixed universal rotation and slide around the camp, bouncing off walls.

And broadcast it on network:

• name joined

Other PRs:

• name died
  etc

Right now, "sectors" are used as references. Sectors exist around every planet, and a few other things. When a player enters a new sector, that sector becomes the "zero" position for that players, and all of that player's positions start being broadcast in relation to that sector.

One cool thing about this sector approach is that players will be synced to the planets they are on. This means that, if the game becomes slightly out of sync, the non-local player models will still appear to be standing correctly on the ground of whichever planet they're on.

Problems with this:

• If a player is far from any celestial object, their position will still be visibly affected by floating point imprecision.
• If a player is inside multiple sectors, the selected sector might not be the best one.

One solution to this is to create a bunch of references throughout the solar system. Just like sectors, they would be invisible triggers, which activate when a player is inside them. Each of these triggers would have a unique ID, so each player would communicate the reference ID, and their position relative to that reference. This way we can have precise position coverage for the entire solar system.

Potential problems:

• Slight de-sync will likely result in floaty players, since they're no longer reporting their position based on a planet. Maybe it would be possible to have both? Planet sectors and the extra reference objects?
• Possible performance impact of having thousands of new triggers. Outer Wilds has some code related to enabling / disabling collisions based on sectors I think, so maybe something like that could be used?

This includes the server.

To do:

• remove default death logic
• teleport to TH
• save
• supernova must reset loop for everyone (should probably be handled in separate issue)

Auto-doze to catch up to server time.