Evergine.Bindings.JoltPhysics
2026.10.1.37
dotnet add package Evergine.Bindings.JoltPhysics --version 2026.10.1.37
NuGet\Install-Package Evergine.Bindings.JoltPhysics -Version 2026.10.1.37
<PackageReference Include="Evergine.Bindings.JoltPhysics" Version="2026.10.1.37" />
<PackageVersion Include="Evergine.Bindings.JoltPhysics" Version="2026.10.1.37" />
<PackageReference Include="Evergine.Bindings.JoltPhysics" />
paket add Evergine.Bindings.JoltPhysics --version 2026.10.1.37
#r "nuget: Evergine.Bindings.JoltPhysics, 2026.10.1.37"
#:package Evergine.Bindings.JoltPhysics@2026.10.1.37
#addin nuget:?package=Evergine.Bindings.JoltPhysics&version=2026.10.1.37
#tool nuget:?package=Evergine.Bindings.JoltPhysics&version=2026.10.1.37
JoltPhysics.NET
This repository contains low-level bindings for JoltPhysics (via JoltPhysicsC) used in Evergine.
Purpose
JoltPhysics is a high-performance, multi-core friendly rigid body physics engine written in C++. JoltPhysicsC provides a pure C API layer, and this repository auto-generates .NET P/Invoke bindings from those C headers using CppAst.
Features
- Full JoltPhysics C API — Covers the complete JoltPhysicsC surface: physics system, body management, shapes, constraints, queries, character controllers, vehicles, skeletons, and ragdolls
- Auto-generated bindings — Generated from JoltPhysicsC headers using CppAst; easily regenerated when the upstream API evolves
- Blittable structs — Math types (Vec3, Quat, Mat44, etc.) and settings structs are blittable, allowing zero-copy interop
- Unsafe raw pointers — Native pointer semantics preserved for maximum performance
- Pre-built native libraries — Ships with JoltPhysicsC binaries for all supported platforms
Supported Platforms
- Windows x64
- Windows ARM64
- Linux x64
- Linux ARM64
- macOS ARM64
- Android ARM
- Android ARM64
- Android x64
- iOS ARM64
- iOS Simulator ARM64
- Browser WASM
Eleven runtime identifiers ship. Ten of them are checked against the real .nupkg before a
release is published, and a failure stops the publish. What that check is worth differs, and the
difference is worth knowing rather than glossing:
| how it is checked | |
|---|---|
| the five desktop identifiers | the package is installed and a sphere is dropped onto a floor through the native library, which has to fall, settle, and settle on the floor |
browser-wasm |
the same, under node, against the archive linked into the application at publish time |
iossimulator-arm64 |
an application is linked against the package and its executable has to define the entry points, not merely reference them |
ios-arm64 |
not verified directly. A device build needs a signing identity CI does not have. It links the same archive through the same targets file as the simulator, so the evidence is indirect |
android-arm, android-arm64, android-x64 |
an APK is built against the package and opened, and all three libJoltC.so have to be inside it, over a megabyte each, with no other ABI alongside. The libraries themselves are not executed |
iOS works differently from every other identifier and you do not have to do anything about it:
Apple only lets an application load dynamic libraries that ship inside its own bundle, so the
package carries a static archive and a buildTransitive targets file links it into your
application at build time.
Development
Generate bindings locally
dotnet run --project JoltPhysicsGen/JoltPhysicsGen.csproj
Build the binding library
dotnet build Evergine.Bindings.JoltPhysics/Evergine.Bindings.JoltPhysics.csproj
Pack for NuGet
dotnet pack Evergine.Bindings.JoltPhysics/Evergine.Bindings.JoltPhysics.csproj -c Release
Run API smoke tests (Windows)
dotnet test Tests/JoltPhysics.APITests/JoltPhysics.APITests.csproj -c Debug -r win-x64
Workflows
| Workflow | Trigger | Description |
|---|---|---|
| CI | push/PR to main |
Build and validate bindings |
| CD | manual | Regenerate bindings and publish NuGet |
| Sync standards | monthly / manual | Sync shared scripts from evergine-standards |
License
See LICENSE.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-ios26.0 is compatible. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- No dependencies.
-
net10.0-ios26.0
- No dependencies.
NuGet packages (1)
Showing the top 1 NuGet packages that depend on Evergine.Bindings.JoltPhysics:
| Package | Downloads |
|---|---|
|
Evergine.Framework
Provides classes which allow developer to model a game or app using a component-based architecture, as well as a default set of cross-platform services to connect every component of each target platform |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 2026.10.1.37 | 1,509 | 10/1/2026 |
| 2026.9.1.33 | 186 | 9/1/2026 |
| 2026.8.30.31 | 135 | 8/30/2026 |
| 2026.8.24.30 | 122 | 8/24/2026 |
| 2026.8.23.29 | 122 | 8/23/2026 |
| 2026.8.23.28 | 118 | 8/23/2026 |
| 2026.8.23.27 | 118 | 8/23/2026 |
| 2026.8.23.26 | 117 | 8/23/2026 |
| 2026.8.23.25 | 110 | 8/23/2026 |
| 2026.8.23.24 | 114 | 8/23/2026 |
| 2026.8.23.23 | 113 | 8/23/2026 |
| 2026.8.23.22 | 119 | 8/23/2026 |
| 2026.8.23.21 | 119 | 8/23/2026 |
| 2026.8.22.20 | 116 | 8/22/2026 |
| 2026.8.9.19 | 120 | 8/9/2026 |
| 2026.8.9.17 | 120 | 8/9/2026 |
| 2026.8.4.12 | 136 | 8/4/2026 |
| 2026.4.4.7 | 141 | 4/4/2026 |
| 2026.4.2.6 | 127 | 4/2/2026 |
| 2026.4.1.5 | 138 | 4/1/2026 |