Objects

Objects in MV3D can represent just about anything. In fact, Gateways are objects too. Objects don't have to have a position or any other 3D data. Generally, they just need to exist within an area or within another object. Because of this flexibility, a wide range of things can be objects. Some objects are Viewable?. This means that clients have some sort of local representation of them. It doesn't necessarily mean the object is visible. An object with no visual aspects that only emits a sound is possible.

Viewable objects define a View for which they are responsible for updating. The view is sent to clients. The client side of the view should be able to create all visual or audible aspects of the object while following orders from the server side (and ultimately the Object itself)

odeObjects or other objects that simulate physical properties do have a position, rotation, velocities, and a physical form. Their views on the clients have the same so that the client can do local simulation.

Back to DesignDocument?.