valley.scene
- .build.state16 B
- .metadata17 B
- README.md2.4 KB
- build.luau10.2 KB
- entrypoint.luau6.3 KB
- scene.json106 KB
This package holds more than this page lists. See all of its files in its world.
README.md
valley
Torque Valley, the driving sandbox: a 720 m valley of meadow-painted terrain ringed by hills, assembled entirely from installed parts. Every joining player gets their own car (a rally car by default; G opens the garage to change kind, look, paint, engine, gearbox, diff and tyres).
- A 1.3 km country-road loop with a roundabout, a highway spur and a dirt rally loop (roadPieces).
- A proving ground of eleven 128 m surface lanes (tarmac to ice) with puddles, an oil patch and rumble strips on its apron (driveSurfaces) — the braking-distance test bed.
- A frozen lake on a snow field, a concrete skid pad, a stunt park (ramps, kicker, banked turn, sand landing pit) and a crash zone (wall, guardrail, tyre wall).
- Seven AI cars with different personalities on the loop (aiDrivers), engine voices on every car (engineVoices), switchable cameras (driveCams), a gauge cluster (gaugeClusters), minimap (navUiKit), touch/gamepad racing controls (controlsKit), crash shake (juiceKit), music (soundstage) and driver progression (driveProgress: XP, levels, the valley's challenges, a barsKit XP bar and damage bar).
build.luau states all of it; torqueValley.layout holds the positions.
Performance
Measured on the native desktop engine inside the editor, in a freshly restarted engine, with the player car and seven AI cars driving the loop: 29–45 fps, typically ~35 (a 27 ms frame). Where it goes: physics 5.4 ms (soft-body shells 1.8 of it), the eight car controllers in the physics step 3.7 ms (AI cars beyond 60 m run theirs every other step), scripts 3.7 ms (cars 1.2, AI drivers 1.0, minimap 0.6, gauges 0.5, engine voices 0.45), rendering 11.4 ms of which 4.4 ms is UI preparation that includes the editor's own panels. 60 fps with eight cars is not reached in the editor; a standalone player without the editor panels saves part of the render and UI time, but that was not measured here.
Web (#20946, not run here): open the published world in a desktop browser with WebGPU,
let the AI field spread out (about 20 s), then read the frame rate with renderer.framePacing()
in the console (or the browser's FPS meter). Check also: engine voices start after the first click
(browser audio unlock), the touch controls appear on a phone, and Physics.worldState().step.softBodyMs
stays under ~5 ms.