5f00a2a16b
The replay's sounds, the raid map's counts and the struck objects now read the recording's event and scene journals by time instead of every pass over the whole journal: partition points over the journals (with a stable time index built at close only when a journal is out of order), the map's kill and hit prefix indices, each object's first hit, and marker/time-line paths that stop at the map's shape cap. Blasts, smoke, debris and the fire replay read bounded windows back from the moment. The sets, order and names stay exactly as they were: tests compare every reader against the full journal filter, including tied times, out-of-order journals and arbitrary forward and back seeks. The replay_bench example measures a 10-minute raid with nearly full journals (playback, reverse seek, pause, MP4); its result is docs/measurements/issue-150-replay-ranges.json. Co-Authored-By: Kimi Code <noreply@moonshot.ai>
28 lines
654 B
TOML
28 lines
654 B
TOML
[package]
|
|
name = "airdef"
|
|
version = "0.2.0"
|
|
edition = "2024"
|
|
publish = false
|
|
description = "AirDef: long-range drones and air defence for the AirDef fork of Horizon"
|
|
|
|
[lib]
|
|
crate-type = ["cdylib", "rlib"]
|
|
|
|
[features]
|
|
# Counts the events the by-time readers hand out (the `replay_bench` example); off in the mod build.
|
|
bench-counters = ["airdef-core/bench-counters"]
|
|
|
|
[dependencies]
|
|
airdef-core = { path = "../airdef-core" }
|
|
horizon-mod-sdk = { path = "../horizon/crates/horizon-mod-sdk" }
|
|
glam = "0.30"
|
|
|
|
[dev-dependencies]
|
|
airdef-core = { path = "../airdef-core", features = ["test-fixtures"] }
|
|
|
|
[profile.release]
|
|
opt-level = "s"
|
|
lto = true
|
|
|
|
[workspace]
|