Stage 1 of #125: prove or disprove real hardware ray-tracing support without touching the client renderer. The probe pins the same wgpu 30.0.1 stack as the engine, including its vendored third_party/wgpu-hal patch, builds one BLAS/TLAS and traces a 16x16 ray-query compute frame, checking every ray against a CPU point-in-triangle expectation. Verified on macOS aarch64, Apple M5 / Metal: BLAS/TLAS and the ray-query pipeline build, 32 hits and 224 misses all match, exit 0. RT_PROBE_BACKEND=gl reports no RT adapter and exits 2; RT_PROBE_NO_OPTIN=1 shows request_device rejects EXPERIMENTAL_RAY_QUERY without the experimental opt-in and exits 2. tools/rt-probe/target/ is ignored; the probe is a standalone workspace and is not wired into the game build. Co-Authored-By: Kimi Code <noreply@moonshot.ai>
This commit is contained in:
@@ -2,6 +2,7 @@ run-home/
|
||||
.horizon-cache/
|
||||
airdef-mod/target/
|
||||
airdef-core/target/
|
||||
tools/rt-probe/target/
|
||||
__pycache__/
|
||||
/out/
|
||||
.DS_Store
|
||||
|
||||
Reference in New Issue
Block a user