Module balls 

The balls: dropping them, giving each one a render instance and a physics body, and publishing where they are.

This is the scene’s busiest object. Every drop spawns a Ball entity of its own and then asks the two other worlds for the halves that make it visible: the render world creates an instance, the physics world a body, and both answer with the ball entity they were asked for, so an answer that no longer finds its ball is cleaned up instead of leaking. A ball the camera loses sight of is put away whole: the render world despawns the instance and reports it, and the body and the ball entity go with it.

Every answer names the ball, never a place in a parallel list, so two answers arriving in either order land on the same ball. A ball counts as shown once the render world confirms the instance wears its assets, not when the job is queued: a job a full queue turned away is simply sent again on the next tick.

Re-exports

use std::sync::Arc; 🔒

use glam::Vec3; 🔒

use unlit_ecs::Bundle; 🔒

use unlit_ecs::DynamicBundle; 🔒

use unlit_ecs::Entity; 🔒

use unlit_ecs::Scope; 🔒

use unlit_ecs::World; 🔒

use unlit_ecs::bundle; 🔒

use unlit3d::components::Transform; 🔒

use super::Scene; 🔒

use super::shapes::BALL_COLORS; 🔒

use super::shapes::SHAPE_KINDS; 🔒

use super::shapes::shape_body; 🔒

use super::shared::SceneState; 🔒

use super::shared::create_instance; 🔒

use super::shared::look; 🔒

use super::tick::advancing_in; 🔒

use super::GamePhysics; 🔒

use super::ScenePoses; 🔒

use super::pose_job; 🔒

use super::world_ended; 🔒

use crate::render::BallInstance; 🔒

use crate::render::RenderEntity; 🔒

use crate::render::despawn_instances_job; 🔒

use crate::render::show; 🔒

use crate::render::sweep; 🔒

use unlit3dx::prelude::*; 🔒

Structs

Ball

One ball, on an entity of its own in the gameplay world.

BallDrops 🔒

The balls and the tick that drops, poses and sweeps them, spawned together.

Balls

The balls, living on their own entity in the gameplay world.

ShowCandidate 🔒

A ball whose two halves have both landed, waiting to be shown.

Enums

BallPhase

How far a ball has come through its flow.

Waiting 🔒

What a tick does with a ball that has not been shown yet.

Constants

PENDING_TIMEOUT 🔒

How long a ball may wait for its two halves before its instance and body are reclaimed, in seconds.

SPAWN_HEIGHT 🔒

Where balls spawn, in metres above the ground.

SPAWN_PERIOD 🔒

How long between automatic ball drops, in seconds.

SPAWN_SPREAD 🔒

How far from the centre a ball may spawn, in metres.

STATUS_PERIOD 🔒

How often the ball flow reports its own status, in seconds.

SWEEP_PERIOD 🔒

How often live instances are tested against the camera’s view, in seconds.

Functions

live_poses 🔒

The poses a tick publishes: one per shown ball, at the pose the physics snapshot names for its body. A ball the snapshot has not named yet is left out, keeping the transform the show job gave it.

waiting 🔒

What a tick does with a ball.