Struct Airships

pub struct Airships {
    pub routes: DHashMap<u32, AirshipRoute>,
}

Data for airship operations. This is generated world data.

Fields

routes: DHashMap<u32, AirshipRoute>

The airship routes between sites.

Implementations

impl Airships

const AIRSHIP_PORT_OFFSET: Vec2<f32>

const AIRSHIP_STARBOARD_OFFSET: Vec2<f32>

const AIRSHIP_TO_DOCK_CENTERLINE_OFFSET: f32 = 18f32

const AIRSHIP_TO_DOCK_FORE_AFT_OFFSET: f32 = 3f32

const DEFAULT_DOCK_DURATION: f32 = 90f32

const ROUTES_NORTH: Vec2<f32>

const STD_CRUISE_HAT: f32 = 300f32

const TAKEOFF_ASCENT_ALT: f32 = 150f32

pub fn docking_duration() -> f32

pub fn takeoff_ascent_hat() -> f32

pub fn std_cruise_hat() -> f32

fn all_airshipdock_positions( sites: &mut Store<Site>, ) -> Vec<AirshipDockPositions>

Get all the airship docking positions from the world sites.

pub fn generate_airship_routes( &mut self, sites: &mut Store<Site>, world_sim: &mut WorldSim, seed: u32, )

Generate the network of airship routes between all the sites with airship docks. This is called only from the world generation code.

After world sites are generated, the airship operations center creates a network of airship routes between all the sites containing an airship dock plot, and there are airships placed at each docking position that will be used for an airship route. Each airship travels between two sites. This is the airship’s route (out and back). When an airship is created, the ops center internally assigns the airship a route based on the airship’s home docking position and the airship routing network. Since a route is between two sites, and therefore between two docking positions, there are two airships flying in opposite directions.

Todo: On longer routes, it should be possible to determine the flight time and add airships to the route to maintain a schedule. The airships would be spawned midair so that they don’t appear our of nowhere near the ground.

Airships are assigned a flying height based on the direction of travel to deconflict as much as possible.

pub fn airship_route_for_docking_pos( &self, docking_pos: Vec3<f32>, ) -> Option<(u32, usize)>

Given a docking position, find the airship route and approach index where the approach endpoint is closest to the docking position. Return the route id (u32) and the approach index (0 or 1).

pub fn should_spawn_airship_at_docking_position( &self, docking_pos: &Vec3<i32>, site_name: &str, ) -> bool

Given a airship dock docking position, determine if an airship should be spawned at the docking position. Some airship docks will not have the docking positions completely filled because some docks are not connected to the maximum number of sites. E.g., if there are an odd number of sites with airship docks. Another reason is the way the routes are generated.

pub fn airship_vec_for_docking_pos( docking_pos: Vec3<f32>, airship_dock_center: Vec2<f32>, docking_side: Option<AirshipDockingSide>, ) -> (Vec3<f32>, Dir)

Get the position and direction for the airship to dock at the given docking position. If use_starboard_boarding is None, the side for boarding is randomly chosen. This assumes that the edge of the docking position is perpendicular to vector from the dock plot center to the docking position. The center of the airship position with respect to the docking position is an asymmetrical offset depending on which side of the airship will be used for boarding.

fn docking_approach_for( depart_center: Vec2<f32>, dest_center: Vec2<f32>, docking_pos: &AirshipDockingPosition, depart_to_dest_angle: f32, map_center: Vec2<f32>, max_dims: Vec2<f32>, site_id: Id<Site>, ) -> AirshipDockingApproach

fn airship_approaches_for_route( world_sim: &mut WorldSim, route: &AirRouteConnection<'_>, dock1_position_id: u32, dock2_position_id: u32, ) -> [AirshipDockingApproach; 2]

Builds approaches for the given route connection. Each docking position has two possible approaches, based on the port and starboard sides of the airship. The approaches are aligned with the docking position direction, which is always perpendicular to the vector from the airship dock plot center to the docking position. The airship can pivot around the z axis, but it does so slowly. To ensure that the airship is oriented in the correct direction for landing, and to make it more realistic, the airship approaches the docking position pre-aligned with the landing direction. The approach consists of two positions, the initial point where the airship will turn toward the final point, at the final point it will turn toward the docking position and will be aligned with the docking direction.

fn angle_between_vectors_ccw(v1: Vec2<f32>, v2: Vec2<f32>) -> f32

Returns the angle from vec v1 to vec v2 in the CCW direction.

fn angle_between_vectors_cw(v1: Vec2<f32>, v2: Vec2<f32>) -> f32

Returns the angle from vec v1 to vec v2 in the CW direction.

Trait Implementations

impl Clone for Airships

fn clone(&self) -> Airships

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Default for Airships

fn default() -> Airships

Returns the “default value” for a type.