Skip to content

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

59 Commits

Folders and files

Repository files navigation

engine

Agent-first game engine in Rust. CLI-first, zero external crates (std only). Window, input and graphics are raw FFI written in-house.

Run it

Install Rust (https://rustup.rs), then from this folder:

cargo run --release -- run

Controls: WASD move, mouse look, Shift sprint, Tab release or recapture the mouse, Esc quit.

macOS: the first launch may ask for no permissions; if the window opens behind the terminal, click its Dock icon.

Renderers

--renderer auto|cpu|metal|vulkan (default auto):

  • macOS: Metal. Linux and Windows: Vulkan. auto falls back to the CPU renderer if the GPU backend cannot start.
  • The CPU renderer is the reference. cargo test renders the same frames with the CPU and GPU backends and checks they match.
  • The Vulkan loader is opened at runtime, so building needs no Vulkan SDK. Shaders are checked-in SPIR-V; regenerate with shaders/build.sh (needs glslangValidator).
  • engine run --frames N exits after N frames (used by CI smoke tests).
  • Linux: libX11 and the Vulkan loader are opened at runtime, so building needs no dev packages.
  • Headless GPU render: engine render --renderer vulkan --out frame.ppm.

For agents

cargo run --release -- render --out frame.ppm --pos 0,1.7,8 --yaw 30 --pitch -5
cargo run --release -- run path/to/my.scene

render draws one frame headlessly to a PPM so an agent can check its own output. Scenes are plain text, see scenes/default.scene.

Starting a game (agent workflow)

Games live in games/NAME, each a small crate that depends on engine and implements the Game trait (src/runtime.rs: setup, tick at a fixed 60 Hz, draw, optional report and finished).

cargo run --release -- new my-game          # scaffold games/my-game (Cargo.toml + src/main.rs)
cargo run --release -p my-game -- play      # open a window
cargo run --release -p my-game -- sim --ticks 600 --seed 1            # headless run: state, event log, audio levels, determinism checksum
cargo run --release -p my-game -- shot --out shot.png --ticks 120     # headless frame to PNG, so an agent can look at it
cargo run --release -p my-game -- world     # dump the entity world as text
cargo run --release -- package my-game      # release build + assets + launcher into dist/my-game

Every game gets play, sim, shot and world from engine::cli::game_main. sim accepts --script FILE (scripted input) so behaviour can be tested without a human. Same seed gives the same checksum.

Procedural assets: engine asset list, engine inspect NAME --out DIR (turntable renders), engine check NAME (layout gate) and engine probe NAME --json (measurements). CI scaffolds, simulates, captures and packages a throwaway game on every push, which keeps this workflow working.

Layout

  • src/math.rs, camera.rs, scene.rs, input.rs: platform-independent core
  • src/render.rs: software rasterizer (clipping, z-buffer, shading, fog)
  • src/gfx/: engine-owned Renderer trait with cpu.rs, metal.rs, vulkan.rs
  • src/platform/: macos.rs (AppKit via the Objective-C runtime), win32.rs, x11.rs
  • src/app.rs: game loop and first-person movement with box collision

Status

Verified on Linux: CPU renderer, X11 window, and the Vulkan backend (software Vulkan, window and headless, matching the CPU renderer). The macOS (window + Metal) and Windows backends type-check but have not been run on real machines. There is no D3D12 backend yet; Windows GPUs ship Vulkan drivers, so Vulkan covers them.

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages