Superluminal: launch and inspect a native CPU target

This guide covers the Reckfell native CPU workflow on Windows. Consult the vendor documentation for Superluminal platforms/availability/terms; profiler support on another platform proves no corresponding Reckfell build.

Prepare the target

Use executable/symbols from the same build; see C++ profiling. Retain its hash, renderer and reproducible action. C# PDB files do not replace native symbols, and CPU capture is no GPU measurement.

Launch and capture

1. Set Application to the Reckfell executable, Working Directory to the project, and explicitly supply --path to the directory containing project.reckfell in Commandline Arguments. Add --editor for editor work.
2. Use Start profiling immediately for startup, or begin after equal warmup for steady-state. For a child game process configure Enable child process profiling, or select its PID through Attach.
3. Finish capture with Start analyzing and save the session. Check process-termination behavior in your profiler version and save project changes beforehand. See the Run/Attach workflow.

Use --quit only for the first startup iteration; omit it for ordinary gameplay. Equal working directories do not prove the intended game was recorded. Verify executable path, command line and process in the resulting session.

Analyze

Select the reproducible action interval and relevant threads first. Reconcile execution with waiting: a long interval can reflect waiting rather than computation. Inspect the native function and callers before editing it.

Respect measurement boundaries: import/loading and editor processes differ from steady-state game frames. Compare equal renderer, camera, settings and absolute time over several repetitions; one percentage change is insufficient. Resolve binary/symbol mismatch before acting on unknown addresses.

Verification limits

Procedure reviewed against official documentation and Reckfell 1.0.0 CLI/build settings. Local execution covered only headless target selection and --quit. Superluminal capture/service, GUI, symbols, child-process recording and project speedups remain untested. Engine source, Runtime and SDK unchanged.