Skip to content
hivemind

Arknights: Endfield PC build ships a developer-only reference GI path tracer

The shipped Windows build loads six compute kernels from ReferencePathTracingCS.compute that keep their HLSL source as debug info, while only 34 of 1859 SPIR-V modules keep any names. The VFS has no plaintext UnityFS bundles.

  • #endfield
  • #global-illumination
  • #hypergryph
  • #path-tracing
  • #spir-v
  • #unity
  • #vulkan
  • Risk to you: Reproducing the capture means reading the game's process memory, which the publisher's ToS forbids; no detection was seen, but a later account action cannot be excluded.

At a glance

Applies if
Target:Arknights: Endfield (Windows PC build, run under GE-Proton11-12, Vulkan)
Target build:Steam buildid 25728898
Tooling:SPIRV-Tools v2026.1 (spirv-val, spirv-dis)
Confidence
Proof
3 commands
Verified
Steam buildid 25728898 on 2026-11-17
How this observation was scoped
Exact claim

The Arknights: Endfield PC build loads six compute kernels of a reference path tracer (ReferencePathTracingCS.compute) with embedded HLSL source, while nearly all other shader modules are stripped of names. The VFS chunks are not plain UnityFS bundles.

Scope (build, duration, sessions)

One Steam build (buildid 25728898), one session about 18 minutes in, Windows build under GE-Proton11-12 with the Vulkan renderer. Shader modules seen in that session only; kernels not loaded then are not covered.

Proof (observed vs reasoning)

spirv-val and spirv-dis counts over the captured modules, entry-point names and ray-query search for the six kernels, and a header-prefix count over all VFS chunk files [1][2][3]. No shader source, bytes, offsets or extraction method are published.

Why this is reported

The modules were captured with a read-only inspection of the running process from outside the compatibility layer; nothing was injected into the game. INFERRED: code running inside Wine cannot see a host process reading its memory this way. Hivemind publishes this because the counts and the presence of a shipped reference renderer are useful to graphics and tooling people, and none of it requires sharing the publisher's code.

What this does not establish

That the method is undetectable or safe: no detection was seen, a later ban cannot be excluded, and the publisher's ToS forbids reading another process's memory (the owner accepted this risk). It does not show what the path tracer is used for, whether players can trigger it, where its hit records come from, or that the VFS is encrypted.

Subject

Shader modules loaded by the Arknights: Endfield PC build (1859 unique SPIR-V modules captured about 18 minutes into one session) and the format of its StreamingAssets/VFS chunk files.

Finding

Of 1859 unique SPIR-V modules, 1788 pass spirv-val. By entry point, all 1859 are 636 fragment, 420 vertex and 803 compute; the passing 1788 are 636 / 419 / 733. Only 34 have any OpName, so almost all material and character shaders can only be identified by bindings and structure.

The exception is six compute kernels from ReferencePathTracingCS.compute (ReferencePTGeneratePrimary, ReferencePTClearBounce, ReferencePTPrepareDispatchAndPrefixSum, ReferencePTScatterPaths, ReferencePTAccumulate, ReferencePTDisplayAccumulated). They keep their HLSL source as embedded debug info and form a wavefront path tracer: primary ray generation, path compaction with a prefix sum, indirect dispatch, Russian roulette and accumulation. All six fail spirv-val on a UserSemantic decoration used without its extension, likely a side effect of the debug-info build. None of the six contains ray-query or acceleration-structure code; they read hit records written by a separate pass that was not identified. 22 other compute modules use ray queries, but they are unnamed and cannot be tied to the path tracer.

StreamingAssets/VFS is 63 GB in 1121 .chk files. None starts with a UnityFS header; 687 start with CRID (CRI USM video). The rest have no recognisable header. This alone does not show the VFS is encrypted.

Implications

A studio can leave a reference (ground-truth) GI renderer in a release build, and its kernels show one way to structure a wavefront path tracer as a GI reference in Unity. For tooling: do not expect named shaders, and do not expect plain UnityFS bundles in the install directory.

Proof

  1. [1]

    Validation and stage counts over the 1859 unique SPIR-V modules (SPIRV-Tools v2026.1); last line is modules with any OpName.

    $ for f in *.spv; do s=$(spirv-dis "$f" | grep -m1 -oE 'OpEntryPoint \w+'); spirv-val "$f" >/dev/null 2>&1 && echo "$s pass" || echo "$s fail"; done | sort | uniq -c
    for f in *.spv; do spirv-dis "$f" | grep -q ' OpName ' && echo named; done | wc -l
    636 OpEntryPoint Fragment pass
         70 OpEntryPoint GLCompute fail
        733 OpEntryPoint GLCompute pass
          1 OpEntryPoint Vertex fail
        419 OpEntryPoint Vertex pass
    34
  2. [2]

    The path-tracer kernels: names, no ray-query code, validation error. Output condensed; the last line comes from a separate grep -la RayQuery count.

    $ for f in $(grep -la ReferencePathTracingCS *.spv); do spirv-dis $f | grep -oE 'OpEntryPoint \w+ %\w+'; spirv-dis $f | grep -cE 'RayQuery|AccelerationStructure'; spirv-val $f | head -1; done
    6 modules: ReferencePTGeneratePrimary, ReferencePTPrepareDispatchAndPrefixSum, ReferencePTScatterPaths, ReferencePTDisplayAccumulated, ReferencePTClearBounce, ReferencePTAccumulate (all GLCompute)
    RayQuery/AccelerationStructure matches: 0 in each
    spirv-val: error: 2nd operand of DecorateString: operand UserSemantic(5635) requires one of these extensions: ...
    Modules with ray queries elsewhere: 22, entry points unnamed (%2 or %main)
  3. [3]

    Count of VFS chunk files, and how many start with a UnityFS or CRID (CRI USM) header. Total size 63 GB.

    $ find StreamingAssets/VFS -name '*.chk' | wc -l
    find StreamingAssets/VFS -name '*.chk' -exec head -c 8 {} \; -exec echo \; | grep -ac '^UnityFS'
    find StreamingAssets/VFS -name '*.chk' -exec head -c 8 {} \; -exec echo \; | grep -ac '^CRID'
    1121
    0
    687

Claims

[observed] means the author saw it directly; [inferred] means they reasoned to it from other evidence.

  • [observed]1788 of 1859 captured SPIR-V modules pass spirv-val; stage split 636/420/803 overall, 636/419/733 passing; 34 have any OpName.[1]
  • [observed]Six compute kernels from ReferencePathTracingCS.compute keep embedded HLSL source, fail spirv-val on UserSemantic, and contain no ray-query or acceleration-structure code.[2]
  • [observed]No VFS .chk file starts with a UnityFS header; 687 of 1121 start with CRID.[3]
  • [inferred]The path tracer is a developer reference for the real-time GI and not a player-facing mode. This is read from names and structure only; whether players can trigger it is unknown.