Pulsar-Native
The next-generation game engine that you deserve implemented in rust https://pulsarnative.com/ Developer_Blogs: https://pulsarnative.com/blog/ Research: https://pulsarnative.com/Research/ UI-Framework: https://pulsarnative.com/UI/ Discord_Server: https://discord.gg/BXyZDMeUJc Formerly_Twitter: https://x.com/PulsarEngineRS
Not yet verifiedsource: GitHubhomepageRustMPL-2.0commit 3186dc0f1359
Rust, MPL-2.0 licensed. The project labels itself: engine, game, game engine, gpui and rust.
Pulsar-Native has not been verified yet.
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 20 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 most recent recorded attempt, which did not reach a verdict. Every line is a recorded value, not an estimate.
- Cold machine to finish
- 62 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- Exact commit tested
- 3186dc0f1359
- 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.
- Install time
- the run did not report one
- How the result was proved
- runs before 2026-09-07 did not record the command used to check the result
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Model tokens used
- not recorded for this run
- 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
- Whether it works at all
- this run verified nothing, so this page makes no claim either way
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
Compiling html5ever v0.27.0
Compiling url v2.5.8
Compiling winit v0.30.13
Compiling hyper-rustls v0.27.9
2026-10-22T02:33:48.637700Z ERROR codex_core::tools::router: error=write_stdin failed: Unknown proc…
exec
/bin/sh -lc 'cd /work/repo && . "$HOME/.cargo/env" && cargo run -p pulsar_engine -- --help 2>&1 | t…
succeeded in 86049ms:
= note: collect2: fatal error: ld terminated with signal 7 [Bus error], core dumped
compilation terminated.
warning: `asset_viewer_plugin` (lib) generated 15 warnings
error: could not compile `asset_viewer_plugin` (lib) due to 1 previous error; 15 warnings emittedReplay 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.
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
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Did not run | 20.00 | 0.50 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/pulsar-native)Questions
- Does Pulsar-Native run?
- Pulsar-Native has not been fully verified yet. No recorded run has produced a verdict yet.
- How did Argusic test Pulsar-Native?
- On a fresh, disposable machine, with every command recorded. One attempt is recorded, and the full method is on the methodology page.
- Where is the evidence for Pulsar-Native?
- 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.