Spring RTS Engine

gajop wrote:How does network's compression compare to https://springrts.com/wiki/Lua_VFS#Zlib ?

I didn't test it, but I highly doubt compressing each packet on its own with zlib will grant you better results then this.

Silentwings wrote:There's a widget(/gadget combo) that allows players to watch each others camera - to do so it has to send a large volume of data over the network; about doubles the size of the replay file, for raw data. For many games it's the ~only lua that causes a large volume of network traffic, so the two things have probably evolved together a bit.

Why is this better than to have it as just a widget? I mean widgets can be turned off and therefore puts more responsibility to the user instead of the game. Is it just because there is a desire to keep this option always available?

Is it just because there is a desire to keep this option always available?

Exactly that.

I think in general that a library is a good initiative. I think what really wanted to say is to be careful with the dependencies, because if libraries depend on too many things they defeat their purpose. For example, if you make a library of trees that depend on roots it's okay, but if you have a tree that depends on a car then it's not so good. I think everybody knows this but I still think it's good to point out.

hokomoko wrote:

PicassoCT wrote:what would happen if we would transfer only the keystrokes and calculate the resulting camera from that..
brb springs git repo

You'd find yourself wasting your time on a system that delivers worse results (not to mention mouse movement controls camera as well, so you're probably going to send much much more data than you have thought)

That was sarcasm?
Spring transfers commands of the players, so by having a initial camera send, and the input of the players, influencing the camera filtered out, you get the same thing you get with spring, a deterministic chain of steps from which you can derive the cameras position and direction.
And you dont have to communicate.
You can use whats there allready.

QED

PicassoCT wrote: That was sarcasm?

No.

PicassoCT wrote: Spring transfers commands of the players, so by having a initial camera send, and the input of the players, influencing the camera filtered out, you get the same thing you get with spring, a deterministic chain of steps from which you can derive the cameras position and direction.
And you dont have to communicate.
You can use whats there allready.
QED

Spring transfers commands, not raw mouse/keyboard input.
So it's a data you don't have.

Sorry, then - i missunderstood, and thought this to be tech-trollin.
Consider me schooled

:)