Vortice.Windows

.NET bindings for Direct3D12, Direct3D11, WIC, Direct2D1, XInput, XAudio, X3DAudio, DXC, Direct3D9 and DirectInput.

Could not verifysource: GitHubCMITcommit 4a799b871456

C, MIT licensed. The project labels itself: direct3d, direct3d11, direct3d12, dotnet, dotnetcore, game development, game engine and gamedev.

Argusic could not get Vortice.Windows running. An Argusic agent installed it in 7 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

NuGet dependencies restored (59 packages), .NET SDK 10.0.401 installed, CastXML 0.4.5 installed. Vortice.XInput builds successfully. All SharpGen-dependent projects fail with registry resolution errors, Windows SDK C headers are required at build time.

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 32.5 of 100 (the mean of this project's run scores).

At a glance

verdict
Could not verify
Argusic Score
32.5 / 100
cost of the verifying run
$0.20 (measured)
recorded runs
2
last tested
stars
1,247
forks
91
open issues
6
watchers
45
size
259 MB
created
last push

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.

Time lost to each failure while testing Vortice.Windows, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • SharpGenTools SDK requires Windows Registry to find Windows SDK C headers (SG0007 error)10 minutes
Install time
7 minutes
Cold machine to finish
19 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
dotnet build src/Vortice.XInput/Vortice.XInput.csproj -p:EnableWindowsTargeting=true exited 0, producing .dll for net8.0/net9.0/net10.0
Model tokens used
226,266
Exact commit tested
4a799b871456
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
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.

**Install:** .NET 10.0.401 SDK was installed successfully. NuGet restore completed (59 packages cac…
**Build results:** 1 of 22 library projects built successfully (`Vortice.XInput`). The remaining 21…
**Verification:** `dotnet build src/Vortice.XInput/Vortice.XInput.csproj -p:EnableWindowsTargeting=…
**Final assessment:** The project is Windows-only due to SharpGenTools SDK's dependency on Windows …
tokens used
226,266
Here's my summary of the work done in this environment:
**Initial assessment:** Vortice.Windows is a .NET library of Windows API bindings using SharpGenToo…
**Install:** .NET 10.0.401 SDK was installed successfully. NuGet restore completed (59 packages cac…
**Build results:** 1 of 22 library projects built successfully (`Vortice.XInput`). The remaining 21…
**Verification:** `dotnet build src/Vortice.XInput/Vortice.XInput.csproj -p:EnableWindowsTargeting=…
**Final assessment:** The project is Windows-only due to SharpGenTools SDK's dependency on Windows …

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

  • Installed in 7 minutes.
  • Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • An agent with no time limit did not get it running.

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 byattemptoutcomescorecost USDwhen
Argusic Runner2/3Did not run15.000.16
Argusic Runner1/3Did not run50.000.20

Topics (from GitHub)

direct3ddirect3d11direct3d12dotnetdotnetcoregame-developmentgame-enginegamedevgraphicsnetstandardnetstandard20nugetsharpdxvortice

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/Vortice.Windows.svg)](https://argusic.com/subject/vortice-windows)

Questions

Does Vortice.Windows run?
Argusic could not verify that Vortice.Windows runs. Argusic installed and launched it on a clean machine in 7 minutes, hitting 1 error on the way, and recorded the session.
How did Argusic test Vortice.Windows?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 4a799b871456. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test Vortice.Windows?
The run that produced this verdict cost $0.20: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does Vortice.Windows take to install?
7 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 Vortice.Windows need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing Vortice.Windows?
1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for Vortice.Windows?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion