News for hackers. Stuff that matters.
Re:Erlang MMORPG Engine by bilbo0s on Monday December 07, 2009 @03:25PM (#982053)
Does anyone know what doing physics in Erlang is like on the zone or area servers? Or do most people just not do physics?

I would think that the physics is what makes things difficult. Of course, if you can think of a game where physics simulations are not as important, an Erlang engine really starts to make sense. At least that is my impression. I'd really be interested in hearing from anyone who has had experience with physics in Erlang.

Re:Erlang MMORPG Engine by forensic on Monday December 07, 2009 @04:02PM (#982139)
physics rarely matters for MMOs. The biggest MMOs like wow have almost no physics at all - just gravity and occasionally a single force vector being applied to a perfectly rigid, non-rotating object in a frictionless environment.
Re:Erlang MMORPG Engine by Periodic on Monday December 07, 2009 @04:17PM (#982178)
It seems that most MMOs, at least of the fantasy variety, tend to ignore physics. Mobiles have maybe three speeds, stopped, walking, and running and transition instantly between them. Jumping is just a pre-programmed arc that may have checks for colliding with other objects. Fall speed tends to be constant and non-accelerating.

However, space-based games would likely require a little more physics to be interesting.

Re:Erlang MMORPG Engine by Shamiq on Monday December 07, 2009 @07:11PM (#982606)
Re:Erlang MMORPG Engine by revoltingx on Monday December 07, 2009 @04:33PM (#982219)
Although I haven't gotten to that part of my game server, I've tried to design it to avoid any sort of physics, because of the potential latency between a client and the server. (I'm targeting mobile users.)

The only 'physics' that need to be calculated is when a player changes speed/direction, and you must calculate the path and detect collisions.

However, to minimize negative effects on gameplay, both the client and the server 'dead reckon' the position of players in their immediate view bubble.

In the client, this is done on a separate thread, on the server, a separate set of processes. Again, I don't expect my algorithms to be cpu heavy, but if they were I'd probably implement them in C and communicate with the erlang processes via message passing. However, this may not be feasible if the latency is too much, in that case, C/C++ is probably more apt. However, you'd have to implement your own scaling, so I'd rather modify my game design than write the functionality that erlang already provides.