search

fnuecke / Circuity

Other
10 stars 0 forks source link

Prioritize pending synchronizations by distance to player #19

Open fnuecke opened 8 years ago

fnuecke commented 8 years ago

The further away, the less it generally matters if values are synchronized with a bit of delay. For example, would make nearby screens update smoothly while far away ones don't have to, reducing bandwidth use a bit.

iamgreaser commented 8 years ago

For screens, physical size will also be an important factor closer to BTM17.

How many ticks of VRAM/SCbuf backlog should we track? I'm thinking 20 should be OK.

fnuecke commented 8 years ago

That's a good point. We'll need some way to dynamically determine the update frequency in addition to distance then... will keep that in mind.

Currently there's no backlogging at all; if something gets sent later, it'll just send the new state at that later time, nothing of the inbetween. I'm not sure backlogging would be a good idea actually, as it would pretty much defeat the won bandwidth reduction I think?

iamgreaser commented 8 years ago

I'm thinking of backlogging on the server, mostly so suitable diffs can be given to clients who are several frames behind.