• 12
• 12
• 9
• 10
• 13

Help!How to transfer locomotion from client to server and how to validate the information in 3D browser MMORPG game?

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

Recommended Posts

I come from China, if my English make you feel uncomfortable, I make an apology! But please read my question and give me some advising.
I read Recast/Detour project to figure out how to navigation in 3D environment, I noticed the player position is floating point, it does't like 2D game that every point is integer. In 2D, I can deliver player position to server use two bytes(assume the grid map is 256*256), but in 3D, I need use three float numbers. The only thing I can think of to optimize the communication is zip the data, does it exist high-efficiency schema?
Another question: when server received the player position, it need be validated to makesure it's whether a nomal position or a fake position, How to do it? My idea is check the distance between this position and previous position, to guarantee player can't move too fast. But this can't guarantee player would not drilling soil or walking on the sky, I need more strict validation. By the way, we choose bullet as collition detection and physics engine. I browse some bullet demo, but could not find a Demo show character's jump action. I don't know how to implement jump action, if you know how to jump, or better free physics engine, please tell me. When player is jumping, the position on the sky is allowed, so the validation is more complex.
Our browser client language is AS, server language is JAVA.

Share on other sites
You can quantize floating point numbers to shorts, if you can accept the loss of precision:

short sent_value = floor(float_value / MAX_RANGE * 32767);

Unpack it on the other end:

float received_value = short_value * MAX_RANGE / 32767;

In general, you want to load a copy of the level geometry on the server, so you can validate movement and test for collisions against walls.
If you are doing physical simulation, you may even want to run the same simulation on the client and the server, so you can fully validate all player actions.

Share on other sites

You can quantize floating point numbers to shorts, if you can accept the loss of precision:

short sent_value = floor(float_value / MAX_RANGE * 32767);

Unpack it on the other end:

float received_value = short_value * MAX_RANGE / 32767;

Thank you very much! I test this method, set MAX_RANGE=1000, then sent_value approximate equals to received_value plus or minus 0.02. I can use the map which has 1800*1800 size
About the physical simulation,client just need calculate one character, but server has thousand of characters. If the server run the same simulation, I think may be it will crash.

Share on other sites
About the physical simulation,client just need calculate one character, but server has thousand of characters. If the server run the same simulation, I think may be it will crash.
[/quote]

This is one reason why massive game server design is hard.

One approach that is often used is to have fairly simple physics (sweep a sphere against a BSP tree, or similar) and then run "secondary simulation" on the client to make it look better (foot IK, moving guns/arms so they don't penetrate the wall, etc)

Share on other sites

One approach that is often used is to have fairly simple physics (sweep a sphere against a BSP tree, or similar) and then run "secondary simulation" on the client to make it look better (foot IK, moving guns/arms so they don't penetrate the wall, etc)

I am sorry I can't understand "secondary simulation", does means client received the position/state of character simulated by server, client simulate it again? has some articles explained this?

Share on other sites
If server just check the collision and broadcast the position of client, what will happen?

Share on other sites

[quote name='hplus0603' timestamp='1345825588' post='4973026']
One approach that is often used is to have fairly simple physics (sweep a sphere against a BSP tree, or similar) and then run "secondary simulation" on the client to make it look better (foot IK, moving guns/arms so they don't penetrate the wall, etc)

I am sorry I can't understand "secondary simulation", does means client received the position/state of character simulated by server, client simulate it again? has some articles explained this?
[/quote]

"Secondary Simulation" means that the client uses the same simple simulation data as the server, but as that's typically just a sphere swept against a collision volume, the client can run other kinds of simulation (IK for feet, suspension for vehicles, etc) that make it look better on the screen, without affecting the center of mass as defined by the server.

Share on other sites

If server just check the collision and broadcast the position of client, what will happen?

This is very risky. It is possible for clients to forge their own position reports and accomplish things like speed hacks very trivially if you are not careful. It also permits for teleportation hacks and possibly visibility hacks.

The safest thing to do is to simulate as much as you need to on the server in order to know for sure where clients should be. Extra animation etc. can be done purely client-side as hplus detailed.