Current naïve implementation looks like shit when latency got introduced

[eugene-sy]

Use client prediction and other technics.
Good article on topic:
http://buildnewgames.com/real-time-multiplayer/

There is links to other great resources on topic, like Source Multiplayer Networking

[Oregu]

Most of the work is already done.
Still need to add:

• client correction if data from server differs.
• Smooth enemy animation.

[Oregu]

From TODO file:

• На сервере дельта времени берётся фиксированная, надо сделать, как у клиента.
• Синхронизировать время на клиенте и сервере.
• Аппроксимировать позицию противника
• Код проверки правильности позиции клиента, сейчас server is not the man. :(

[Oregu]

Smoothed ball animation. Now there is a little problem when ball bounces from paddle — it's not moving along with server ball. Green one is server updates and white ball is client predicted.
Just a note to fix it next day.
🍶

[Oregu]

And also just found out that client predicted paddle also desyncs with server one. There is still a lot of work to do.
🍶 🈂️

[Oregu]

And also just found out that client predicted paddle also desyncs with server one. There is still a lot of work to do.

Ну в этом, кстати, нет ничего удивительного, потому что до сих пор не сделана корректировка позиции, aka "Server is the Man".

[Oregu]

I did several commits and problem with ball desync gone…
Looks like this removal in d54b106 did the trick (also introducing diffTime helped)

• @ball.t = @updateTime

Weird. 🍶

[Oregu]

Now it's time to fix gamer's paddle synchronization 🍶