Installer f3d avec Homebrew, apt, dnf, Nix, pacman, zypper, scoop, winget

Liens du projet

• Page d'accueil
• Dépôt
• Docs amont
• Page du gestionnaire de paquets

Commandes et alias

• f3d

Historique du projet

F3D was initially created by Kitware SAS by Joachim Pouderoux, Michael Migliore, and Mathieu Westphal. The repository was created in 2020, and the project README describes it as maintained by the F3D-APP Foundation.

The early releases established the core viewer. The changelog shows v1.0.0, later v1.2.0 separating the executable into libf3d and the `f3d` application, and v1.3.0 introducing an alpha version of libf3d with Python bindings.

The 2.x and 3.x lines expanded F3D from a viewer into a small ecosystem: configuration files, file-manager integration, thumbnails, many plugin-backed formats, C/C++/Python/Java/JavaScript bindings, WebAssembly/browser viewing, and an Android version.

Historique d'adoption

F3D's adoption is driven by a gap between heavyweight CAD/scientific visualization tools and quick image viewers. Its package-manager value is that users can install one CLI-friendly viewer for glTF, STL, STEP, PLY, OBJ, FBX, Alembic, USD, VTK-related data, and other formats without launching a full modeling environment.

The input package facts list F3D across Homebrew, Debian, Ubuntu, Fedora, Arch, Nix, Scoop, winget, and openSUSE, reflecting broad interest from desktop, visualization, and developer workflows.

Modes d'utilisation

The simplest use is `f3d /path/to/file.ext`, optionally with `--output=/path/to/img.png` for noninteractive rendering. The README also emphasizes thumbnails, hotkeys, drag-and-drop, command-line control, configuration files, and file-manager integration.

F3D is used by people who need to inspect assets quickly: game and 3D artists checking mesh files, engineers previewing CAD-ish formats, scientists viewing VTK-style datasets, and developers scripting preview renders in CI or documentation pipelines.

libf3d turns the viewer into an embeddable renderer with C++17 APIs plus C, Python, Java, and JavaScript bindings, which explains why packaging often matters beyond the `f3d` executable.

Pourquoi les passionnés de paquets s'y intéressent

F3D is notable because it packages a hard dependency stack behind a small user experience: VTK, OpenCASCADE, Assimp, Alembic, Draco, OpenUSD, OpenVDB, PDAL, OSPRay, ImGui, and related libraries appear in the project's acknowledgments or plugin story, but the command remains a simple viewer.

For package maintainers, F3D is interesting because optional format support and plugins turn build choices into user-visible capabilities. For users, it is the rare 3D package that behaves like a Unix viewer: install it, point it at a file, get pixels.

Chronologie

• 2020: f3d-app/f3d repository created.
• 2021: v0.1.0 through v1.2.x releases published on GitHub.
• 2021: v1.2.0 separates the executable into libf3d and application layers.
• 2021: v1.3.0 introduces an alpha libf3d library and Python bindings.
• 2024: v3.0.0 modernizes libf3d APIs around C++17 and expands command/control APIs.
• 2025: v3.3.0 creates a WebAssembly-based F3D web application.
• 2026: v3.5.0 adds an Android version and more rendering, file-format, and plugin features.

Related projects

• VTK is a core rendering and visualization foundation for F3D.
• Assimp, OpenCASCADE, Alembic, Draco, OpenUSD, OpenVDB, PDAL, OSPRay, and ImGui are part of the broader dependency and format-support ecosystem documented by F3D.
• libf3d is the embeddable library shipped by the same project.

Sources

• https://github.com/f3d-app/f3d
• https://github.com/f3d-app/f3d/blob/master/README.md
• https://github.com/f3d-app/f3d/blob/master/doc/CHANGELOG.md
• https://github.com/f3d-app/f3d/blob/master/doc/dev/11-GOVERNANCE.md
• https://api.github.com/repos/f3d-app/f3d
• https://api.github.com/repos/f3d-app/f3d/releases/latest