OSCAR 3D
Component-Based 3D Multimedia Development for Simulation Training

OSCAR 3D—the Open Source Component Architecture for Reusable 3D—is a complete component-based 3D multimedia development and presentation system that redefines and enriches the content development and delivery process for simulation training. OSCAR 3D is focused on ‘over-the-wire’ extensibility and content reusability.

OSCAR 3D is an open source solution. The architecture has been designed to be extensible externally, but the entire source code for the kernel and all key components of the system will be made available in its entirety. Documentation is being developed to allow third-party developers to understand and extend the architecture.

OSCAR 3D is designed to integrate with and enhance existing operating environments, including HTML-based content and other deployment focused applications.

OSCAR 3D is the ultimate consumer of any 3D content and associated behaviors. The component architecture has been designed to incorporate an extensible 2D and 3D file import/export capability. Additional importers can easily be added dynamically to the system, even across the Internet.

OSCAR 3D can be deployed in a number of ways depending upon specific needs of the application designer. First, the system can run stand-alone as a separate complete 3D deployment application. This is useful for pure 3D training and simulation applications. Second, the system can be embedded into standard HTML documents to allow for the extension of existing web based content. Third, the system can be used to extend any application via DLLs for Microsoft applications such as PowerPoint, and via XCMDs for Macromedia applications.

OVERVIEW
The OSCAR 3D architecture and framework is made up of two primary parts: components and a container that makes the components available. Any application that is built using OSCAR 3D will contain these two parts:

Containers. The container is the central administrator of the application’s components and the services provided to those components. The services provided by the container include 3D rendering, sound and media, model storage, collision detection and collision avoidance/attraction. Additionally, the application user interface is controlled by the container, and is part of the container development effort. Since the types of applications that can be built using OSCAR 3D vary significantly, containers are built to suit the possible application types.

Components. All significant application functionality is written into the components themselves. This results in an application based on small, portable, high-quality functional blocks that are dynamically linked to the application.

The benefits of an application based on self-contained components and abstracted technologies are numerous:

Focused development efforts. In OSCAR 3D, the container provides the underlying development technologies, so the developer can focus squarely on developing components. Eliminating the development or incorporation of underlying technologies leaves more time to address the application’s user requirements.

Shorter, more accurate development schedules. By virtue of containing their own behavior, components can be reused within and across applications. Once you have a reclining chair, you have a reclining chair that can be used in any number of applications.

Independent, upgradeable technologies. Since the underlying 3D technologies such as rendering and sound are independently provided through the OSCAR 3D container, they can go anywhere the container goes without modification.

FEATURES & BENEFITS
Component model
In OSCAR 3D, object behavior is just as reusable as object data models.

Component-based import/export
Additional formats can be easily and quickly added to OSCAR 3D, ensuring that new file formats and new versions of existing file formats can be quickly and readily supported.

Internet-based extensibility
Content and additional components are deliverable and can be dynamically installed within OSCAR 3D via standard Internet protocols.

Standard component object communication protocol
OSCAR 3D objects can communicate between themselves and the external system. This can be as simple as a behavior component controlling a 3D file import component, or as complex as a time/event component signaling other components to respond.

Open scripting support
OSCAR 3D supports appropriate interfaces to allow the use of a variety of scripting languages.

HTML compliance
OSCAR 3D enables 3D extensions of HTML content.

Stand-alone capability
Content developed in OSCAR 3D can be deployed in run-time environment.

Application extension
OSCAR 3D content is embeddable into applications such as Microsoft PowerPoint, OutStart Evolution, HTML-based Web pages, and even Microsoft Word documents.

Open source
Anyone can extend OSCAR 3D, and investments in the system are always secure.

SYSTEM REQUIREMENTS
Intel Pentium processor (Pentium 3 or later recommended)
Microsoft Windows 2000 Professional (with Service Pack 2) or Windows XP Home or Professional
128MB of RAM (256MB recommended)
20MB available hard disk space
1024x768 screen resolution
Hardware-based 3D acceleration