Skip to content

Operations and resources

Arke Forge is designed around serial execution. Only one managed tool may remain active because the image, reconstruction and motion models compete for RAM, VRAM and WSL memory.

Normal cycle

  1. Check the RAM and VRAM panel before starting a tool.
  2. Start one card and wait for its ready state.
  3. Complete and save the stage.
  4. Stop the card.
  5. Confirm that memory returns toward its idle range before starting the next heavy tool.

Buttons on other cards are disabled while a managed tool is active. The application also enforces the lock in its process supervisor.

Closing the application

Closing Arke Forge stops tools that it started. Processes opened independently may be detected but are not forcibly terminated because ownership cannot be proven.

Use Stop all to close all managed tools. Use Release WSL only after saving work; it shuts down all WSL distributions and terminals, not only an Arke Forge model.

Resource expectations

The safe TRELLIS profile uses 512 resolution. Peaks vary by stage and model initialization. A first run can take longer while weights load into memory. Browser tabs, Blender scenes and stale WSL allocations can raise the idle baseline, so compare against the workstation's normal idle state rather than a fixed number.