# VizStateStrategy

The available memory usage strategies (both Javascript and GPU) for an UnstructGridModel

Enumeration Members

- VIZ_STATES_ALL
- VIZ_STATES_ALL_SINGLE_GPU
- VIZ_STATES_SINGLE

## Enumeration Members

### VIZ_STATES_ALL

Keep everything needed for all states to be rendered as quickly as possible.

This is the fastest way to play an animation, but requires sufficient resources (both main browser memory and GPU) to run.

### VIZ_STATES_ALL_SINGLE_GPU

Keep the visualization data for all states, but delete GPU buffer resources when changing state.

This option will use more main memory, but still keeps GPU memory usage at the same level as what is needed for a single state.

### VIZ_STATES_SINGLE

Only keep the visualization data and GPU buffers for the current state. Changing states will require a regeneration of the display model.

This is the option with the smallest memory footprint (both GPU and main memory).

Conversation saved
HOOPSY BETA

### Hello! I'm HOOPSY

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

What is HOOPS Envision for Web?
What are the latest release notes for HOOPS Envision for Web?
How do I start evaluating HOOPS Envision for Web?
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...