Star Wars Roleplay: Chaos

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Approved Tech H3 Ship Control Computer

Status
Not open for further replies.
2iiTXMt.png

[Image Unavailable]

OUT OF CHARACTER INFORMATION
  • Intent: To provide the galaxy with an effective means to partially automate star destroyers.
  • Development Thread: [X] [X]

PRODUCTION INFORMATION
  • Designer: Hannibal Oryen
  • Manufacturer: Hegemonic Automaton
  • Model: Hermaeus-Series Supercomputer
  • Affiliation: Customers
  • Modularity: No
  • Production: Minor
  • Material: Durasteel, Circuitry, Gabonna Memory Crystal, Xylen

DESCRIPTION

For the final phase of the Hermaeus Series, it was time to push the envelope over just how many tasks on a star destroyer or similarly sized ship could be automated. The result was another kind of supercomputer, only one that comes with a gargantuan network of specifically modified J2 Droid Brains that are integrated directly into vessels. This system was prototyped with Titan Industries’ Maladi-Class Strike Frigate to huge success.

While the Maladi was a success, it wasn’t the farthest that could have been gone. Partial automation of small vessels was, for Hegemonic Automaton, child’s play. Similar slave rigging systems had already been in practice for centuries prior. However, the practice of slave rigging vessels has fallen out of practice since its initial introduction millennia ago. Most would say there are too many risks, such as heightened possibility of theft or point out the unfortunate incident with Katana fleet so many years ago. Some would also point out how poorly many Recusant-Class Light Destroyers performed in battle during the Clone Wars some years ago, crashing into allied ships and failing to prioritize properly. Where most see failure, Hegemonic Automaton seems room for improvement.

The H3 SCC is much like the H1 DCC in terms of appearance, but is instead optimized to coordinate the functions of ships rather than independent droids. As such, it is substantially larger than the H1 so that it can process the even greater amounts of information needed to keep a ship not only operable, but fully competent. The H3 SCC is typically installed alongside and connected to a large network of J2 Droid Brains that independently operate many of the ships systems and, through which, the H3 SCC coordinates everything- everything.
An H3 SCC cannot fully control a ship. After all, there is still need for a physical crew in most vessels, which the H3 SCC is not capable of coordinating due to its specialized nature. In most cases, the H3 SCC can only account for up to 87% reduction in necessary physical crew. To push any further without a sufficiently powerful and specialized Artificial Intelligence would be unnecessarily risky. There must also be a minimum of thirty personnel monitoring the various functions of the H3 SCC in whichever location it is stored, though this number could be higher depending on the size of the ship.

As always, it accomplishes these things through the unique Hegemonic Automaton microsynapse system found in both Julianos Series Droid Brains and the preceding Hermaeus Series Supercomputers. The introduction of large, nearly human-sized Gabonna Memory Crystals also allows the H3 to process a nearly unprecedented amount of information for a supercomputer of its size. This system already enjoyed marked success as part of the Julianos Series. Now amplified to a less restricted size, the system’s effectiveness is completely unleashed.

It’s rather dangerous to allow a system designed to automate vessels to grow in self-awareness. H3s that have undergone simulations that result in sapience tend to style themselves as admirals, naval officers, or pirates throughout history. Several H3s have been witnessed to repeatedly say such things as “good, our first catch of the day,” “it’s a trap,” and "cannon to the right of them, cannon to the left of them" regardless of relevance to the situation. Regardless of this seemingly benign (if a bit silly) behavior, sapient H3s may attempt to hijack ships, torment, or even assault crews if they feel they are being mistreated. Regular, consistent, and thorough memory-wipes are urged.

Also like the H1 Droid Control Computer, H3 SCCs consume a fragrantly large amount of power. People seeking to utilize them should take care as to not overload the systems of their vessel by installing it. Vessels with reactors of insufficient power will not be able to sustain an H3 SCC or the system of J2 Droid Brains installed with it.

Technically H3 SCCs can be constructed anywhere and are capable of coordinating buildings, fortresses, space stations, and so forth just as well as ships. Its name is more a reflection of what it was intended for rather than its limitations.

Hegemonic Automaton is not responsible for H3 Ship Control Computers that obtain sapience.
 
Status
Not open for further replies.

Users who are viewing this thread

Top Bottom