The point is, you don't need to mesh lots of points for each solid, unless you want to make it flexible. The only boundary conditions would be at the joints between rigid bodies, and always less than six at each.

For example if that 2D human body in the game Tulac posted had say 13 joints, each with one DOF allowed (angle) and two restricted ones (position in 2D), that would mean 13x2=26 boundary conditions. These conditions are trivial equations, actually after applying them you have the same system but with 26 variables less, that is a simpler system (than if you had to account for each body part moving free).

OK back to topic, this is silly: :perv:
http://freeonlinegames.com/puzzle-ga...-go-happy.html

*gasp* O.o

This isn't exactly Flash, but it made me laugh - Guitar Hero, the text adventure.

Edit: And here's a Pac Man almost-MUD while I'm at it.

haha, amazing

i wanna see you code it in flash, you "big nerd" :bleh:

i bet you'd stumble even on collision detection algorithm=P

Nerds don't code in Flash. :bleh: Nerds do Fortran. :D (Nah I never learnt Fortran.)

You don't need to detect collisions in this case, the bodies can't move freely. The equations describe their movement and their solution will simply yield the positions of all solids--of course compliant with the boundary conditions that were inserted in those same equations.
__________________

This retro zombie fashion is getting old :P

in this case, the algorithm would be a real cpu killer, you can't code everything perfectly as it could be in real life

speaking about nerds, assembler ftw

No really, it isn't intensive at all, for that human body a 486 would be more than enough if coded in C for example. If you have for example 14 solids, in 2D that means 14x3=42 variables, after applying the boundary conditions you have only 42-26=16 variables. The kind of problems that can be solved with computers nowadays may have millions of variables.

http://upload.wikimedia.org/wikipedi...ualization.jpg

It's not like in real life, it's an approximation, you define the precission with the method (first, second... order, etc.) and the step size (in time). Every instant you estimate the 16 position variables from their values one step before.

http://upload.wikimedia.org/wikipedi..._rectangle.png

Assembly is for programmers, :p you can't ask an engineer to code in assembly. Most will even use Matlab, Maple or Mathematica most times instead of a generic compiled language.

well human body is usually placed in a complex world so it can be called "game" :p
(i mean, except the sick examples tulac gave us)