3.2.2.2
VEOS Design
home page

A primary design goal for VEOS was flexibility, the ability to reconfigure dynamically in real-time. Other systems required shutdown and relinking to make even small modifications in the virtual world. We needed a simple-to-use system that could be run through dozens of tests and hypotheses and designs inside the virtual environment, without turning off the virtual environment.

VR must be a social place, supporting many participants in interaction with each other. VEOS implemented concurrent divergent worlds in which participants share some of the constructed world, while diverging on specified components.

papers/essays
virtual reality
veos

what is veos?
∆ design
theses
kernel
entities/body

links
site structure

This design position is documented in the first two pieces. These memos are modules later put into the VEOS Overview Descriptions.

VEOS: PRELIMINARY FUNCTIONAL ARCHITECTURE
VEOS DESIGN GOALS

The next three pieces are design documents from a second group of students who used the VEOS specification to build a VR system. Everyone worked together to define the lower levels of the architecture, and two separate groups specified and implemented their design. MOSES and VEOS are quite similar.

A SECOND STEP TOWARDS VIRTUAL REALITY: THE ENTITY MODEL AND SYSTEM DESIGN (with Dan Pezely, Mark Evenson, and Michael Almquist)
THE ENTITY OPERATING SYSTEM: A DESIGN FOR THE IMPLEMENTATION OF VEOS (with Dan Pezely and Michael Almquist)
TEN COMMANDMENTS OF THE MOSES PROJECT (Dan Pezely)