# Components Overview

Below is a list of all the components that are part of HOOPS Envision for Desktop. Please note that some of these components require a specific license feature. See License System for more information.

Core [cee]

The Core Component defines the base classes in HOOPS Envision for Desktop. It includes classes for strings, vectors, matrices and other basic types. There are no dependencies to OpenGL in this component.

Dependencies: None

Visualization [cee::vis]

The Visualization Component contains the Envision Rendering Engine and is required in all applications that will use the visualization capabilities of HOOPS Envision for Desktop. It contains the `View`, `Camera` and `Overlay system` as well as a `MarkupModel`.

Dependencies: Core Component

Geometry [cee::geo]

The Geometry Component is the component to use for rendering pure geometry (as opposed to element models with results) in HOOPS Envision for Desktop. Effects like front and back color, opacity, texture mapping, etc. are supported in the Geometry Component. It provides a `model` that is highly optimized and can handle a large number of parts efficiently. This model is especially well suited if the parts provided have equal/shared attributes like color, line width and so on.

Dependencies: Core Component, Visualization Component

UnstructGrid [cee::ug]

The UnstructGrid Component is by far the largest and most feature rich component in HOOPS Envision for Desktop. It is tailored towards support FEA and CFD type models and results, and leverages Tech Soft 3D’s 25 years knowledge in scientific visualization.

Dependencies: Core Component, Visualization Component, Plot2d Component

Particle [cee::pt]

The Particle Component provides support for time-stepped particle simulation data. It can read PTFX and VTP file formats, and supports custom format integration via reader plugins or user-supplied dataset readers. The component handles frame caching, scalar field selection, bounding box queries and depth sorting for transparent rendering.

Dependencies: Core Component, Visualization Component

Export [cee::exp]

The Export Component add Envision’s Share Everywhere technology to your application. By adding VTFx export to your application, you can share your results on the cloud (Ceetron Cloud) and in the free Viewers.

Dependencies: Core Component, Visualization Component, UnstructGrid Component

Import CAE [cee::imp::cae]

The Import CAE Component provides a DataSource for the UnstructGrid Component that can read files from commercial FEA and CFD simulation software systems.

Dependencies: Core Component, Visualization Component, UnstructGrid Component

Report [cee::rep]

The Report Component provides repository management and report generation in PowerPoint, Word and HTML.

Dependencies: Core Component, UnstructGrid Component

Win [cee::win]

The Win Component provides GUI bindings for Windows (.NET/MFC/Win32) applications.

Dependencies: Core Component, Visualization Component

Plot2d [cee::plt]

The Plot2d Component provides basic 2D plotting as an overlay item. Plot data and settings can be stored within the VTFx file.

Dependencies: Core Component, Visualization Component

App [cee::app]

The App Component provides an interface to HOOPS Envision for typical application logic: models, views, selection

Dependencies: Core Component, Visualization Component, UnstructGrid Component, Plot2d Component, Export Component, Import CAE Component

OpenGL [cee::ogl]

The OpenGL Component adds support for rendering using OpenGL

Dependencies: Core Component, Visualization Component

Conversation saved
HOOPSY BETA

### Hello! I'm HOOPSY

Your multilingual generative AI assistant for documentation. Ask me anything about HOOPS Envision for Desktop in your own language, or choose a sample question below to start a conversation:

What is HOOPS Envision for Desktop?
What are the latest release notes for HOOPS Envision for Desktop?
How do I start evaluating HOOPS Envision for Desktop?
How do I write my first sample application?
How can I get assistance?

HOOPSY may store conversations according to OpenAI's policy. Responses may not always be accurate.

HOOPSY is thinking...