Closed christerk closed 6 years ago
Are you talking about ModelChanges or Commands like ModelSync?
See enqueueCommand in controller.ts
Ah, ModelChanges. As far as I understood each ModelSync contains a number of ModelChanges which should be applied together. So it would only require a rerender for each ModelSync. Something like a CompoundCommand could be useful that simply wraps all ModelChanges in one ModelSync.
Until now I only looked at the replay use case, it might be different for spectating.
Quite possibly true. Right now, the system sends each ModelChange individually and triggers a ModelChanged event. Grouped messages may be a good idea. Note that this may impact the CommandHandler as well.
Feel free to open a new issue to allow grouped model changes.
Probably makes sense to solve #6 before taking on this one.
Atm, every ClientCommand message will trigger a re-rendering. Should be possible to disable the re-render for certain types of ClientCommands.