ferravexOriginal engine implementation
Every package in the Cargo workspace uses zero external Cargo packages, including all optional features and platform targets. The audit checks the complete resolved graph, not a selected subset. See the dependency policy.
The local catalog contains fifteen examples: thirteen original games/labs recovered from this repository and ported to first-party APIs, plus Courtyard and Orbit Breaker. Browser hosts use standard APIs directly; Rust std and browser/system APIs are the platform boundary. This recovery has not been pushed or deployed, and validation is being repeated against the new renderer and physics code.
Run the examples locally
python3 scripts/audit-owned.py
cargo test --workspace --all-features --offline --locked
cargo run --release -p owned-lab --bin owned-lab -- --frames 640 --output /tmp/courtyard.png
cargo run --release -p owned-orbit -- --autoplay --screenshot /tmp/orbit.png
python3 scripts/build-web.py release
python3 scripts/serve-web.py --port 8000Open the local root page for all fifteen examples. /owned/ is Courtyard and /owned-orbit/ is Orbit Breaker. The thirteen restored games/labs use the shared direct-WebGL2 host and original ferravex-render runtime: Rust records clip-space triangles with CPU vertex lighting/fog and built-in text glyphs. This immediate path has no shadow map. Courtyard retains persistent WebGL2 mesh buffers, instancing, a shadow map and Rust visibility tests. Orbit writes an original RGBA framebuffer to Canvas2D. No external runtime libraries, fonts or CDN loaders are used.
Courtyard: WASD, mouse aim, click fire, Space jump, R reload, Escape menu. The inspector edits positions and collision geometry, saves edits locally, exports input recordings and reloads GLSL after validation. Ground height is fixed by the FPS motor. Detailed props are decorative; only the authored collision solids block players. Browser context restoration rebuilds GPU resources.
The restored examples have an original Linux X11/GLX window/GPU host. Run, for example, cargo run --release -p neon-swarm or cargo run --release -p marble-run with an X display and compatible OpenGL driver. Courtyard and Orbit retain their native headless PNG paths. Native Windows/macOS/iOS window and input bindings and native audio output are not implemented. Cross-target Rust compilation does not establish interactive device support.
Twenty feature tracks
Each row describes working code and the material work still required. These are initial implementations, not a claim that twenty production systems are finished.
| # | Feature | Working implementation | Remaining work |
|---|---|---|---|
| 1 | Profiling and budgets | Fixed-size CPU samples, budget flags, p99; browser CPU frame and asynchronous GPU timer measurements; binary size/audit scripts | Allocator instrumentation, trace timelines, device budgets |
| 2 | Retained rendering | CPU mesh handles/generations; Courtyard WebGL static buffers/instancing and transformed bounds/frustum culling; headless clipped depth rasterizer | General LOD policy, shared retained submission, Windows/macOS/iOS GPU hosts, GPU-driven submission |
| 3 | Character movement | Owned sphere slide/step/snap helper; existing shared FPS AABB motor and prediction | Unified capsule motor, slopes, moving platforms, body pushing |
| 4 | Input actions | Bounded remappable action map, deadzones, buffered edges; browser keyboard/mouse/gamepad/touch adapters; Linux host events for restored games | Interactive rebinding UI and physical-device testing |
| 5 | Spatial audio | Strict PCM16 WAV decoder, bounded resampling stereo mixer, distance attenuation/panning; browser AudioWorklet output | Occlusion, streaming/compressed audio, native sinks and authored footsteps |
| 6 | Reliable events | Actual UDP v2 session-bound event/ACK codec, retry/order/dedup, bounded queues and slow-peer disconnect; typed gameplay event delivery | Congestion-aware scheduling and long-running Internet tests |
| 7 | Lag compensation | Bounded authority history, clock estimator, opt-in historical-hit damage with current-wall occlusion and lifecycle checks | Validated shot timestamps in the UDP wire format and automatic clock integration |
| 8 | Compact replication | Bounded sparse/full snapshot byte deltas with exact baselines and centimeter quantization | Baseline ACK integration, quantized wire snapshots, adaptive interest/bandwidth scheduling |
| 9 | Secure multiplayer | Browser WebRTC DTLS/SCTP adapter; host authority, guest prediction/reconciliation and input redundancy | Native encrypted transport, service identity, accounts, NAT relay/discovery and session resumption |
| 10 | Tactical rounds | Authoritative buy/live/plant/defuse/round/match state, teams, economy, armor, kits and interruption/range validation | Integrating these rules into the playable shooter, full spectator/buy UI |
| 11 | Asset cooking | Bounded OBJ importer, cooked binary mesh codec, PCM WAV validation, deterministic compressed bundles, ferravex-cook tool | glTF, image/font pipelines, richer compression and dependency tracking |
| 12 | Scenes and prefabs | Generational scene graph, cycle checks, hierarchical transforms, clone-subtree prefabs, strict binary scene codec | Asset references, scene streaming and game-specific schema evolution |
| 13 | Editor | Courtyard browser scene inspector with live position editing, save/load and reset | Viewport picking/gizmos, undo/redo and full prefab/property editing |
| 14 | Hot reload | Transactional live asset bundles; Courtyard last-valid GLSL replacement with visible errors | Native filesystem watchers, full content dependency invalidation |
| 15 | Animation | Scalar/vector/quaternion tracks, sprite clips, skeleton world poses and inverse-bind skin palettes | GPU skinning, blend/state graphs, event tracks and importer integration |
| 16 | Low-poly lighting | Flat normals and CPU directional vertex lighting/fog in the restored renderer; Courtyard separately retains vertex AO and browser PCF shadows | Baked lightmaps/probes, cascades and platform quality tiers |
| 17 | Navigation and AI | Weighted deterministic A*, no corner cutting, arrival/separation steering | Navmesh baking, perception, behavior/state tooling and bot integration |
| 18 | VFX | Bounded particle pool, constant-acceleration integration, lifetime/color/size curves; shot impacts in Courtyard | GPU simulation, trails and effect authoring |
| 19 | Responsive UI | Anchor layout, clipping/hit tests, focus/capture, browser safe areas; original bitmap text glyphs in the immediate renderer | General text shaping/font loading, retained UI renderer and richer accessibility |
| 20 | Replay and regressions | Bounded checksummed input files; scene save/load; corruption, gameplay, dropped-input, event-loss, rewind regressions | Full server-event replay, replay viewer, device farm and long soak tests |
Browser multiplayer
Open Courtyard in two browsers/tabs on machines with a direct network route. Open Scene tools → Two-player LAN session. The host generates an offer token; the guest pastes it and selects Join offer. The guest sends its answer back; the host pastes it and selects Accept answer. Both then enter training.
The browser negotiates encrypted DTLS/SCTP using SDP certificate fingerprints. Exchange the tokens over a trusted channel: this prototype provides no account identity or matchmaking. It configures no external STUN/TURN service, so connections through restrictive NAT/firewalls can fail. Session tokens contain connection candidates and should be treated as private connection information. The host owns movement, health, shots and bots. The guest predicts its own movement and reconciles against host snapshots. One guest is supported. The browser transport currently sends full snapshots at up to 20 Hz; native reliable UDP events and historical rewind are separate capabilities.
Native UDP protocol v2 remains a trusted-development transport without encryption. No custom cryptographic primitive was invented or substituted for a secure native transport. See the FPS/net READMEs for exact APIs and validation limits.
Offline cooking
cargo run --release -p owned-lab --bin ferravex-cook -- /tmp/assets.ferravexpak model.obj shot.wav config.binOBJ becomes validated GMSH0001 mesh data; WAV is validated PCM; other files are bounded opaque bytes. The packer rejects duplicate basenames and unsafe asset names. Bundles use sorted names, a versioned envelope, per-file and whole-file checksums and an original RLE codec only where it reduces size. Checksums detect corruption and are not authentication. The packer does not execute asset code.
See each crate README for numerical, allocation and feature limits. ferravex-dynamics remains a translational solver for circles/spheres and axis-aligned boxes. The restored physics games use separate original ferravex-physics: dynamic balls/oriented boxes, angular impulses, static/kinematic capsule rails and cylinders against balls, contact events/layers, rays and bounded sphere CCD. Dynamic capsules/cylinders, their contacts with boxes, joints, mesh collisions and swept box TOI remain unsupported; consult its README for numerical and CCD limits. It is not a claim of production-engine feature parity. Run the recovered game tests and interactive checks before relying on prior results.