AB,
This is a good idea - I also found the approach below good which you could also test with your idea.
1] Decide direction to turn or move
2] Send the rotate or move instruction
3] Almost immediately after send the stop instruction - there is some inbuilt latency on the server and browser so even with no explicit delay some movement will occur, but your idea will test this further
4] Wait a while until there is no further movement - again your method can test this
5] Get the current position and direction while stationary and go to 1
This is what I meant by small steps and keep correcting movement.
The rotation angle dependence on time the message is sent will depend on lots of factors, PC hardware, internet, other processes on PC, browser window size, other users using the server etc and may vary from time to time as well from PC to PC.
This is a good idea - I also found the approach below good which you could also test with your idea.
1] Decide direction to turn or move
2] Send the rotate or move instruction
3] Almost immediately after send the stop instruction - there is some inbuilt latency on the server and browser so even with no explicit delay some movement will occur, but your idea will test this further
4] Wait a while until there is no further movement - again your method can test this
5] Get the current position and direction while stationary and go to 1
This is what I meant by small steps and keep correcting movement.
The rotation angle dependence on time the message is sent will depend on lots of factors, PC hardware, internet, other processes on PC, browser window size, other users using the server etc and may vary from time to time as well from PC to PC.