R'ea'kuk-pattern command shuttle
| R'ea'kuk-pattern command shuttle | |
|---|---|
 An overview of the command shuttle, from the rear angle. | |
| Technical specifications | |
|
Length: |
74 meters (244 ft)[1] |
|
Width: |
63.7 meters (208.9 ft)[1] |
|
Height: |
22.1 meters (72.5 ft)[1] |
|
Other system(s): |
|
| Usage | |
|
Role(s): |
|
|
Affiliation: |
|
The R'ea'kuk-pattern command shuttle is a large command-scale dropship employed by the Covenant.[2]
OverviewEdit
Design detailsEdit
The R'ea'kuk displays many outward similarities to the Spirit family of troop carriers; in particular the Dextro Xur-pattern. It shares a number of features with the Dextro Xur such as the twin pronged hulls, though is equipped with additional capital ship-scale proselytization network relays and defensive augur arrays.[2]
UsageEdit
Befitting its name, the command shuttle served in a role comparable to the larger transport shuttles employed by the United Nations Space Command (UNSC) or various human megacorporations, working to ferry high-value Covenant military officers or political figures (such as Hierarchs, Minor Prophets, Ministers, San'Shyuum and Sangheili High Councilors etc) on their deployments outside of High Charity. In this role, they had many features such as capital scale proselytization network relays and specialty defensive augur arrays.[2]
Due to this usage, the R'ea'kuk was rarely deployed on the front lines during the Human-Covenant War, and the rare occasions in which it did make contact with human forces saw the UNSC devote considerable effort to target analysis and tracking of the individual shuttles encountered.[2]
Production notesEdit
The command shuttle is one of many vehicles cut during the production of Halo 2. In the original storyboards, the command shuttle had a very different visual look, and was intended to be used to deploy the Arbiter and his Special Operations Sangheili during the level The Arbiter. It was later to be used at the end of deltatemple as the personal transport of the Prophet of Regret, before finally being seen in the final epilogue cutscenes.
The model for the command shuttle was unearthed by the Digsite project, and officially canonised in an issue of Canon Fodder[2] The dropship reuses the textures of the original Halo: Combat Evolved Spirit in a similar fashion to the Brhi Xur-pattern Leech boarding craft, though was developed extremely early during the development cycle of Halo 2 - during the era in which the game was still mostly the Combat Evolved engine.
During the original production of Combat Evolved, the Spirit dropship was originally intended by concept artist Shi Kai Wang to fly with the cockpit section facing forward, and the troop bay twin hulls following in the back. While an animation miscommunication caused the ship's direction to be reversed into the form now-familiar today,[3] the command shuttle as-developed for Halo 2 was originally designed to retain this original intent. As such, the craft's bow is the armoured middle pod, while the aft sections are the troop bay housing.
GalleryEdit
|
Browse more images in this article's gallery page. |
StoryboardsEdit
Storyboards of a command shuttle inserting the Arbiter's team into the gas mine.
Storyboards of a command shuttle inserting the Arbiter's team into the gas mine.
Storyboards of a command shuttle inserting the Arbiter's team into the gas mine.
Storyboards of a command shuttle inserting the Arbiter's team into the gas mine.
A command shuttle can be seen in storyboards for the game's original ending.
ScreenshotsEdit
A blockout of the storyboard command shuttle design produced in Halo 2 development, that went unfinished.
View of the shuttle's front.
A three-quarters angle on the shuttle's front.
A side orthogonal view of the shuttle.
The ventral surfaces of the shuttle.
SourcesEdit
- ^ a b c Based on the orthographic view here
- ^ a b c d e f g h i Halo Waypoint, Canon Fodder - Cutting Room Lore (Retrieved on Jul 26, 2022) [archive]
- ^ Twitter, Shi Kai Wang (@shiekthegeek): "So I'll state this upfront; the Spirit was always concepted with the tuning forks as the back. A miscommunication on direction for animation and 3D made it so the tuning fork faced forward. Ultimately we all agreed that felt more aggressive so we left it :)" (Retrieved on Jan 9, 2023) [archive]
| |||||||||||||||||||||||||||||||||||||