Swift-VVD

Cross-Platform Game Engine for swift programming language.

• GPGPU Library with Vulkan / Metal
• Game Physics & Audio
• Declarative UI framework similar to SwiftUI
• Tools and Utilities

Warning
It is not recommended for products as it is still in a very early stage in development and many features have not been implemented yet.

---

Things that require pre-installation

• Windows 10 (version 1903 or later) / Windows 11 x64

  • Swift 6.4 or later
  • GIT (with LFS)
  • Vulkan SDK
    • Requires a graphics driver installed that supports Vulkan 1.3 or later.

• Mac

  • Xcode 27 or later (Swift 6.4 or later)

  • Deployment targets: macOS 27.0, iOS 27.0, and Mac Catalyst 27.0 or later.

    Note
    When cloning this project, you must use a GIT client that supports LFS.

• Linux / WSL2

  • Vulkan SDK

    • Requires a graphics driver installed that supports Vulkan 1.3 or later.

  • Swift 6.4 or later

  • Wayland-1.20 or later (libwayland-dev)

  • ICU development headers and library (libicu-dev)

    Note
    Using devcontainer(Docker) is recommended.
    See devcontainer + Dockerfile

Included External Libraries

• FreeType
• HarfBuzz
• jpeg
• libFLAC
• libogg
• libpng
• libvorbis
• LZ4
• LZMA
• miniaudio
• minimp3
• SPIRV-Cross
• TinyGLTF
• Vulkan Headers
• Wayland protocols
• zlib
• Zstd

The VUI product also bundles portable fonts and Material Design-derived SVG symbols. SwiftSyntax is fetched as a build-time dependency, and Linux builds use the system ICU and Wayland libraries. See Third-party notices for the in-tree license and provenance locations.

---

Build and test

Clone with Git LFS enabled and materialize all LFS objects before building:

git lfs pull
swift build -c release --product VVD
swift build -c release --product VUI
swift build -c release --product VGame
swift build -c release --product VEditor
swift test
swift test -c release

VVD, VUI, and VGame are library products. VEditor, TestApp1, and RenderTest are executable targets. Separate dynamic-library manifests and their release commands are documented in SharedLibraries/README.md.

VEditor currently provides the initial workspace shell: Project Explorer on the left, Main Content and Inspector across the upper work area, and a full-width Log pane below them. Its File, Edit, View, Tools, Window, and Help menus are structural placeholders; project loading, editing, build execution, scene/asset tools, and a 3D viewport are later editor-domain work. Sources/VEditor/Core owns all UI-independent editor code, including editor models, operations, services, persistence, and engine integration; Sources/VEditor/UI owns the VUI-only application shell and calls Core or the engine's public API. Core code must not import or depend on VUI.

Platform success is established per host and SDK; a successful macOS or Apple cross-build does not imply a Windows or Linux runtime pass. Use the native toolchain and prerequisites listed above for each platform.

---

Samples

The UI Framework

Declarative UI - Similar to SwiftUI, but also runs on Windows.

Note

This UI framework is built for game development, not app development, and is designed to work on top of game engines.

A very simple glTF viewer

It reads glTF resources and renders with a graphics API similar to Apple's Metal.

Note

requires C++ Interoperability for reading glTF

👷 We still have a long way to go.