No description
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
2026-05-30 00:03:43 +01:00
crates Update vg-csg float-stable geometry keys 2026-05-30 00:03:43 +01:00
state Focus VibeGeometry on vg-csg 2026-05-29 14:22:43 +01:00
.gitignore Focus VibeGeometry on vg-csg 2026-05-29 14:22:43 +01:00
.gitmodules Replace vg_csg with submodule 2026-05-07 22:59:42 +01:00
AGENTS.md Focus VibeGeometry on vg-csg 2026-05-29 14:22:43 +01:00
Cargo.lock Update vg-csg CultCache geometry artifacts 2026-05-29 23:25:13 +01:00
Cargo.toml Focus VibeGeometry on vg-csg 2026-05-29 14:22:43 +01:00
README.md Focus VibeGeometry on vg-csg 2026-05-29 14:22:43 +01:00

VibeGeometry

VibeGeometry is now the working shell around vg-csg.

The previous scene-generation research era is gone from the live tree. It can stay in git history, where failed experiments are useful without being allowed to hold a steering wheel.

The live mission is narrower and sharper:

domain/tree intent
-> LOD-aware CSG hierarchy
-> camera/frustum selected cut
-> triangle and collider output in milliseconds

The actual work surface is the Rust crate at:

  • crates/vg_csg
  • upstream: https://github.com/GameCult/vg-csg

What This Repo Owns

  • The vg-csg submodule pointer.
  • A minimal Rust workspace that builds that crate.
  • Thin operating notes that keep future work pointed at runtime CSG, not legacy scene-generation scaffolding.

What vg-csg Owns

  • Brush and CSG tree APIs.
  • RealtimeCSG-shaped public seams where useful.
  • Parity fixtures for claimed public behavior.
  • Dirty rebuild and demand-frontier experiments.
  • Mesh/triangle output and receipt examples.
  • The future LOD-aware selected-cut runtime.

Commands

git submodule update --init --recursive
cargo test
cargo clippy --all-targets --all-features
cargo run -p vg_csg --release --example csg_perf_fixture

If a future task needs domain-tree DSL work, put it in vg-csg unless there is a proven reason it must live outside the crate. The default answer is simple: the geometry machine belongs where the geometry machine runs.