JoltPhysics
A multi core friendly rigid body physics and collision detection library. Written in C++. Suitable for games and VR applications. Used by Horizon Forbidden West and Death Stranding 2.
Runssource: GitHubC++MITcommit 439c2b61214a
C++, MIT licensed. The project labels itself: c plus plus, cpp, game development, game engine, physics, physics engine, physics simulation and simulation.
JoltPhysics runs. An Argusic agent installed it in 1.5 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
Jolt Physics v5.6.0 builds from source with g++ on Linux; UnitTests pass all 585 tests; HelloWorld example executes a full physics simulation cycle with collision detection.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
- Install time
- 2 minutes
- Cold machine to finish
- 3 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- cd /work/repo/Linux_Release && ./UnitTests exited 0, 585 passed / 0 failed / 0 skipped, 514630 assertions passed; ./HelloWorld ran 48 simulation steps of a falling ball landing on a ground plane
- Model tokens used
- 77,476
- Exact commit tested
- 439c2b61214a
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
All tasks completed successfully with zero errors. Here's the summary: **Build**: CMake configured and built in 1.5 minutes. g++ 13.3.0, no compilation errors, no warning… **HelloWorld**: Ran successfully — a simulated ball falls, contacts the ground, and comes to rest (… **UnitTests**: 585 test cases passed, 514,630 assertions passed, 0 failed, 0 skipped. Status: SUCCE… No third-party keys were required. This is a standalone C++ physics engine with no external depende… tokens used 77,476 All tasks completed successfully with zero errors. Here's the summary: **Build**: CMake configured and built in 1.5 minutes. g++ 13.3.0, no compilation errors, no warning… **HelloWorld**: Ran successfully — a simulated ball falls, contacts the ground, and comes to rest (… **UnitTests**: 585 test cases passed, 514,630 assertions passed, 0 failed, 0 skipped. Status: SUCCE… No third-party keys were required. This is a standalone C++ physics engine with no external depende…
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 1.5 minutes, faster than the median of the 5 comparable projects Argusic has measured.
- Nothing broke on the way: zero errors between clone and running.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 6 c-plus-plus projects Argusic has installed and timed, JoltPhysics was the 1st fastest to reach a running state, and 5 of 6 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 1.5 minutes after the clone.
- Following its own README: the documented path worked with nothing to fix.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
c-plus-pluscppgame-developmentgame-enginephysicsphysics-enginephysics-simulationsimulationvr
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/joltphysics)Questions
- Does JoltPhysics run?
- Yes. JoltPhysics runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test JoltPhysics?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 439c2b61214a. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test JoltPhysics?
- The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does JoltPhysics take to install?
- 1.5 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does JoltPhysics need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing JoltPhysics?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does JoltPhysics compare with the alternatives?
- Of the 6 c-plus-plus projects Argusic has installed and timed, JoltPhysics was the 1st fastest to reach a running state, and 5 of 6 reached one at all.
- Where is the evidence for JoltPhysics?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.