Lessons about virtual environment software systems from 20 years of ve building

  • Authors:
  • Russell M. Taylor;Jason Jerald;Chris VanderKnyff;Jeremy Wendt;David Borland;David Marshburn;William R. Sherman;Mary C. Whitton

  • Affiliations:
  • University of North Carolina at Chapel Hill Chapel Hill, North Carolina 27599-3175.;University of North Carolina at Chapel Hill Chapel Hill, North Carolina 27599-3175.;University of North Carolina at Chapel Hill Chapel Hill, North Carolina 27599-3175.;University of North Carolina at Chapel Hill Chapel Hill, North Carolina 27599-3175.;Renaissance Computing Institute.;University of North Carolina at Chapel Hill.;Desert Research Institute.;University of North Carolina at Chapel Hill.

  • Venue:
  • Presence: Teleoperators and Virtual Environments
  • Year:
  • 2010

Quantified Score

Hi-index 0.00

Visualization

Abstract

What are desirable and undesirable features of virtual environment (VE) software architectures? What should be present (and absent) from such systems if they are to be optimally useful? How should they be structured? In order to help answer these questions, we present experience from application designers, toolkit designers, and VE system architects along with examples of useful features from existing systems. Topics are organized under the major headings of 3D space management, supporting display hardware, interaction, event management, time management, computation, portability, and the observation that less can be better. Lessons learned are presented as discussion of the issues, field experiences, nuggets of knowledge, and case studies.