Sign in to follow this  

Appwarp latency

This topic is 1109 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hello, 

Im making my first multiplayer game in libgdx with appwarp and i have problem with that other player reaction is deleyed 80-120 milliseconds.

This is dont look right, but i will ask, its normal?

What do you recommend that would work better? 

Share this post


Link to post
Share on other sites
There is always delay between the time user A presses a key, and the time that user B on another computer will see that action.
This is because of both processing time on systems, as well as transmission time over the internet.
Newcomers to networking will try to reduce the latency by, for example, sending commands as soon as they are detected rather than as part of the regular game update loop cycle, or by trying to establish peer-to-peer connections to cut out the server in multi-player games.
In the end, such attempts end up making the code more fragile, and doesn't actually solve the problem, because there is an unavoidable delay between users -- the travel time of electric signals in copper between New York and California is significant, even before you add the additional processing overhead of the network infrastructure!

Thus, the art of creating a networked game is to design the game to work well within the limitations.
There are several different ways of doing this. Real-time strategy games will, for example, play a "yes, sir!" acknowledgement animation on the sending client, giving the command packet time to travel to the server and to other players.
Many MMO RPGs and some FPS-es will just accept the latency, and tune the game for a given latency target (200 ms is reasonable here.)
Other games will attempt to forward-predict the location/actions of remote player son the local target, and then somehow "fix up" when they receive information that is counter to the prediction. Some players like this; personally I don't particularly do so, because remote players will be snapping/warping/jumping around in an uneven manner.

The FAQ for the networking and multiplayer forum contains some links to good references on different models. The Source Networking Model document, the Zen of Networked Character Physics document, and the 1,500 Archers on a 28,800 Modem document are good starting points.

Share this post


Link to post
Share on other sites

To augment hplus0603, I've read that many real-time war strategy games (i.e.: Starcraft) handle multiplayer games by synchronizing the player's inputs data stream. This also has the side benefit of simple, efficient game replay.

 

I **think** I came to find this interesting piece of information somewhere from http://forrestthewoods.com/the-tech-of-planetary-annihilation-chronocam/

Edited by JeffCarp

Share this post


Link to post
Share on other sites

Yes i know there always is a delay, but

- peer to peer is slower than client/server?

- how much it increases the delay using cloud backend (appwarp) instead of normal connection?

 

Also i know there is many techniques how to reduce feelings of delay but im making easy mobile game and im looking for a easy way to make game response faster.

Share this post


Link to post
Share on other sites

- peer to peer is slower than client/server?


No. If you can make a peer-to-peer connection, it will likely be slightly (but not a lot) faster than client/server for a message that would go user->server->other user. Some people assume it will be 50% faster, but that's seldom the actual case.
However, peer-to-peer come with a number of really hard problems, including NAT punch-through, cheating, and privacy concerns. It is common that beginners underestimate these problems, and overestimate the potential gains.

- how much it increases the delay using cloud backend (appwarp) instead of normal connection?


What is a "normal" connection? The IP, UDP, TCP, and HTTP protocols don't know whether they are going to a "cloud" location or a "normal" location.
If you are not seeing the performance you expect, you should draw out the different parts of the equation that can affect the performance, and attempt to measure each of them separately. That will give you a good understanding of the problem.

I don't know about appwarp at all -- their technical support should be able to answer performance SLA questions.
All we've seen is that you suggest there is a 80-120 millisecond "latency" when using their platform. However, that doesn't help us answer the question at all.
Latency between what and what? Where is their server? Where are you? Where is the other party? What protocol are you/they using? What are the alternatives you could consider?

Share this post


Link to post
Share on other sites

Hi Pawelo,

 
I am part of AppWarp team at Shephertz. As answered by hplus0603 when you are communicating through network there will always be some latency as message has to travel through the network. Thanks hplus0603 for the great explanation.
 
We have servers at 4 different locations namely USA, Europe, Japan and Sao Paulo. You can choose the server that is near to you. This will improve your results. AppWarp also supports UDP so that you can send not so critical data at faster rates.
 
If you have any query you can contact as anytime by sending us email at support@shephertz.com or by positing your query to our forums(http://forum.shephertz.com/).

Thanks

Share this post


Link to post
Share on other sites

This topic is 1109 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this