View Single Post
  #13  
Old 07-19-2012, 11:14 PM
ffcmike ffcmike is offline
Banned
Join Date: Jul 2004
Location: London
Posts: 2,029
ffcmike has a reputation beyond reputeffcmike has a reputation beyond reputeffcmike has a reputation beyond reputeffcmike has a reputation beyond reputeffcmike has a reputation beyond reputeffcmike has a reputation beyond reputeffcmike has a reputation beyond reputeffcmike has a reputation beyond repute
Send a message via AIM to ffcmike Send a message via MSN to ffcmike
Quote:
Originally Posted by ffcmike View Post
As a result of the default level 3 speed being 0.6 tiles per frame, a value which can not be divided into whole pixels, your characters display is rounded to the nearest whole pixel coordinate, which is also the value synchronised to the server and other players, while your actual clientside x/y values remain at decimal pixel values. Because of this, with default it is actually possible to see your character edge-on with another players sword, but you don't get hit because your absolute x/y value could be up to half a pixel away from that visible edge. The opposite can also be true, the synchronised value may be closer to your opponent than your absolute x/y value, which can result in your opponents client detecting a hit even though you were really up to half a pixel too far away.

That is the only difference I can account for, and if anything Classic's method is more accurate, as the visible coordinate matches the absolute coordinate on your client.
Incase this is hard to understand, perhaps this picture from Dev Polo (default) will explain it more easily:




Quote:
Originally Posted by Imperialistic View Post
The hit detection is very awkward and weird especially if you're used to the other 'default' servers, it almost makes it frustrating.
So what's weird about it compared to default exactly?
There's nothing more I can do unless someone can actually explain it, and it's not another case of "I hit people on my screen and they don't get hurt".
Reply With Quote