YokoZar wrote:Hmm why does 1.02 label itself as "1.03" when I host a game
Oops
YokoZar wrote:If you have two separate coops on a team, you can't see the allied coops start pyramids
Can fix this.
One player connected very late (I think after his coop buddy clicked a point and hit ready), resulting in a desync
I can possibly see this happening if they connected after GameStart, i'll look into fixing this.
We tried two largish games with different hosts and it got rather laggy. This might not be a coincidence - if every player were sending duplicate commands for their entire coop (like we observed with the start points), then the number of commands would increase exponentially (for 2v2 would have 4 times the number of commands as 1v1, and a 4v4 would have 4 times the number of commands as a 2v2 (so about as much as a 16 player normal game). A 7v7 like we tried would thus have a number of commands equal to what would otherwise be a 98 player game (!!!)
If this is the case, then the lag is due to an engine bug.
There's no duplicate commands that was due to something unrelated in the early gadget for coop mode which is now fixed.
The lua behind coop pretty much lays dormant once the game is started aside from watching for self D orders, if there was noticeable lag in this mode but not in a normal game it would be due to something in the engine.
