Backlogging - what is the deal ?
by Ivan Mandzhukov · in Torque 3D Professional · 04/12/2010 (1:48 pm) · 0 replies
Hi there,
These days I have been working on the networking stuff and I got confused about the backlogging.
I use my own camera system. It reads an input.
Instead of copying the ACK code,I decided to close the input into a single movemanager.
This results in a huge move queue.
And here is the problem - the client process list receives a full queue from the move list.This causes the client to find a deficit of time,recalculates a backlogging time and this one clogs the client-server connection.
In result the whole interpolation gets lagged with a few milliseconds.
I disabled the clogging from my process list and the problems are solved.Good so far!
The real question is how this will reflect further in time..
I am still new to the network stuff,so additional help from the gurues will be much appreciated.
Thanks in advance!
These days I have been working on the networking stuff and I got confused about the backlogging.
I use my own camera system. It reads an input.
Instead of copying the ACK code,I decided to close the input into a single movemanager.
This results in a huge move queue.
And here is the problem - the client process list receives a full queue from the move list.This causes the client to find a deficit of time,recalculates a backlogging time and this one clogs the client-server connection.
In result the whole interpolation gets lagged with a few milliseconds.
I disabled the clogging from my process list and the problems are solved.Good so far!
The real question is how this will reflect further in time..
I am still new to the network stuff,so additional help from the gurues will be much appreciated.
Thanks in advance!