Open rootux opened 1 year ago
rootux
commented
1 year ago @AlonRDT @AlonArditi Is this complete?
I think the only thing left open is to make sure that if a client were not able to connect for 10 seconds - he should become a server? Because we want to be able for both computers to work as standalone (And try to keep on reconnecting in the background).
Can a client still spawn player?
AlonArditi
commented
1 year ago Its only the beginning, the loops they collect are also a network object
On Sun, Dec 11, 2022, 16:47 Gal Bracha @.***> wrote:
@AlonRDT https://github.com/AlonRDT @AlonArditi https://github.com/AlonArditi Is this complete?
I think the only thing left open is to make sure that if a client were not able to connect for 10 seconds - he should become a server? Because we want to be able for both computers to work as standalone (And try to keep on reconnecting in the background).
Can a client still spawn player?
— Reply to this email directly, view it on GitHub https://github.com/rootux/portal/issues/5#issuecomment-1345573593, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXYYRKRFHBE5FNWBZYUHTCDWMXSONANCNFSM6AAAAAASS3RQNI . You are receiving this because you were mentioned.Message ID: @.***>
Create the networking layer
Should support sending over the data of 20 vectors (x,y,z)
The idea is that each side would render it's own kinect data to a particle system + another particle system for the data received from the network layer
Bonus - make sure it supports more than 1 skelton for each side.
This data would be sent roughly ~60-100 times per second - as many times as the websocket allows us to sent. it's totally okay to send less then that amount - given that we'll create something kind of tweening between keyframes - where we will be smoothing the position of the body from 2 different keyframes (So also having 10-30 times per second would be great).