Rust game engine for huge physics scenes: 10,000 GPU-simulated cubes at 2,000+ FPS on an RTX 3060. Vulkan, editor, deterministic replay, agent-friendly CLI.
Repo RustingStudio/RustingEngine, read from GitHub 1 min ago. RustingStudio has not joined Take My Repo.
GameScene::exiting(): game code gets one last update, with no tick and exiting() true, when the window closes, after scene.quit(), and when a dedicated server gets Ctrl+C or SIGTERM (a console close on Windows), so it can write its save. App::run_exit_update runs it for custom loops. save_data already writes through a temporary file and a rename (WILDROOT F25).rusting run --bench --json reports passes_p50_ms, and rusting test --json reports perf.render.passes_ms: GPU milliseconds per pass, per shadow cascade, and per opaque, terrain, foliage and sky part of the scene pass. The plain bench: output names the three costliest passes (WILDROOT F15).rusting.terrain layers take optional normal (OpenGL-style normal map), roughness (red channel) and tiling (metres per repeat; 0 uses the terrain's) fields. Layers without them look as before (WILDROOT F3).NetSession::set_seed(scene.seed()), a client reads NetSession::seed() after joining, directly or through a relay, and applies it with the new GameScene::set_seed. The wire protocol is now version 4, so hosts, clients and relays must all be updated together (WILDROOT F21).rusting.terrain takes a terrain-wide tint (linear rgb, default white) multiplied into every layer and a roughness (default 1) that scales every layer's roughness. Changing only these two updates the terrain material without rebuilding chunk meshes, LOD groups or layer arrays, and GameScene::set_terrain_look(name, tint, roughness) sets them without a trip through JSON. A material color on a terrain now tints the blended layers instead of skewing the splat weights (WILDROOT F23).net::interpolate::Track blends a remote object's plain (tick, position) samples for games that send their own snapshots, without a replica or NetTransform: push(tick, position) in any order, at(tick) with a fractional tick, newest() (WILDROOT F18).rusting asset import --linear (and reimport --linear) marks an image as data and cooks <name>-linear.rtexture beside it, which the reference field points at. A plain image in a material's normal, metallic-roughness or occlusion slot now loads as linear data, from scene files and from the Inspector. AssetServer::load_linear_texture and assets::cook_linear_texture expose both paths (WILDROOT F24).rusting.foliage takes conform (default false), which sets each copy on the heightfield below it so a scatter follows hills, and layers (default empty), terrain layer indices a copy must stand on, such as grass but not sand. Copies are placed again when the object, heightfield or terrain changes (WILDROOT F12).sway block (MaterialSway: amplitude, frequency, height) that bends every mesh using them in the rusting.force_field winds at its origin, in the vertex shader, so tree crowns sway for no CPU cost. frequency adds gusts phased by position and height keeps the base rooted while the crown curves. The editor material inspector shows it, and cooked scenes move to format version 11; version 10 scenes load without sway (WILDROOT F13).rusting.water takes optional deep_color, depth_fade, shore_foam, ripples and ripple_length: the surface fades to the deep color by the metres of water the view crosses, draws white foam where the ground nears the surface, and lights small scrolling waves. They read the opaque scene depth, which the renderer now copies for water even with reflections off. The defaults keep the plain one-color surface (WILDROOT F7).KHR_texture_transform: the offset, rotation and scale the material's textures share are folded into TEXCOORD_0, and textures with different transforms fail with an error naming the material instead of Unsupported extension (WILDROOT F8).PlayerController::step(physics, body, shape, position, input, water, floor_pose, dt) runs one fixed tick of player movement from a PlayerInput (forward, right, jump, jump_held, sprint, crouch) instead of the global player.* actions, so a host can move every peer's body, and a client can replay its own inputs for prediction, with the same code as rusting.player_controller. It returns the dynamic body walked into as a PlayerShove (WILDROOT F16).rusting asset bake-foliage <model> [--cards N] [--impostor] [--node NAME] [--tint RRGGBB] [--atlas PIXELS] [--out PATH] bakes a tree's MASK or BLEND foliage into crossed alpha-tested cards with one RGBA atlas (4 triangles per card), and with --impostor a crossed-billboard impostor of the whole tree for the last LOD. It prints the source, foliage and card triangle counts. foliage_bake::bake_foliage exposes it to code (WILDROOT F9).rusting asset import and asset reimport record every file they cook beside a model (its .rmesh meshes, .lodN.rmesh levels, .rlod groups and .rtexture textures) in the new optional .rmeta field cooked, and the report's new meshes list gives each mesh's triangle count and its LOD triangle counts, so a 4-million-triangle tree shows up at import time instead of in a frame-time capture (WILDROOT F1).rusting docs show api/net, api/net::predict, api/net::input, api/net::interpolate and api/procgen list each module's public items, and every type, function, constant and type alias there has its own api/<name> page with its signature and docs, such as api/PeerId, api/NetSession, api/fbm2 and api/RandomStream. Smoothing::correct now says which position to pass as shown (WILDROOT F17, F18, F2).rusting lint warns LINT_TERRAIN_CHUNKS when a terrain draws more than 300 chunks (WILDROOT F11).start_cooldown(name, ..) keeps its end tick in the counter cooldown:<name>, so a counter called name is a separate value and a cooldown no longer overwrites it. Saves and scenarios load as before; a game that saved a cooldown through save_counters passes cooldown:<name> instead. Statuses keep their <object>/<effect> counters (WILDROOT F26)."realtime": true scenario times NetSession::simulate delays from each tick's planned time instead of the wall clock, so a slow capture frame no longer changes the tick a held message arrives on, and a copy of the scenario without its captures sees the same arrivals (WILDROOT F22).rusting asset reimport of a glTF recooks its .rtexture files next to the project copy, not only its .rmesh files, so a changed source texture shows. Reimport without --from keeps a project copy that was edited after the last import instead of overwriting it with the recorded original, warns ASSET_EDITED_COPY, and records the copy as the new original (WILDROOT F24).tick function and every FixedUpdate system) sees FrameTime::delta equal to fixed_delta, so code that steps movement by delta_seconds() in a tick moves at the same speed whatever the frame rate. Update still sees the frame's time (WILDROOT F19).texture, normal and roughness paths are relative to the scene file, like every other scene asset path. Paths relative to the project root still load, with a deprecation warning. rusting lint and validate report a missing layer image (SCENE_MISSING_ASSET) and a project-root path (SCENE_TERRAIN_ROOT_PATH), and a run logs once per path when a layer image fails to load instead of painting it white silently (WILDROOT F4).rusting.foliage copies runs in the scene and shadow vertex shaders instead of on the CPU, so a wind field no longer re-uploads every copy's transform each frame. Custom force fields no longer lean foliage (WILDROOT F13).rusting.terrain chunk_cells 0, the new default, picks the chunk size from the heightfield so a terrain makes at most about 150 chunks (a 1501 x 1501 island draws 144 instead of 2,209); an explicit size still wins (WILDROOT F11).TriangleMesh and Heightfield colliders test only the triangles under the other body's bounds through the mesh's box tree; one ball on a 1501 x 1501 heightfield steps in 0.05 ms instead of 40 ms (WILDROOT F10).Full Changelog: https://github.com/GoingRusting/RustingEngine/commits/v1.0.0