Star wars republic commando crash on startup

#STAR WARS REPUBLIC COMMANDO CRASH ON STARTUP SOFTWARE#

It also had a flexible video sensor unit that allowed the R2 unit to examine hard-to-see workspaces via a 360-degree rotational joint, with a maximum reach of. The line also possessed a retractable jack that allowed the unit to plug directly into Imperial-standard computer ports, thus allowing it a direct hard-wired connection to most computers. The droid also had a fully maneuverable video sensor, deployed from its domed head, allowing it to inspect enclosed spaces or peer over obstacles. Its sensor package was equally impressive, with a full-spectrum transceiver and electromagnetic, heat, motion, and life form indicators.

#STAR WARS REPUBLIC COMMANDO CRASH ON STARTUP SOFTWARE#

Likewise, its built-in telecom software also allowed it to communicate with computers under the jurisdiction of both the Imperial Navy Transmission and the Corporate Sector Standard communications systems, as well as being given custom communications software. The center of the droids' success could be attributed to its Intellex IV computer, which featured at least 700 different spacecraft configurations and could do over 10000 MPF operations every second. R2 units were equipped with a holographic recording mode. The R2 operated flawlessly in the vacuum of interstellar space. The unit could store up to ten sets of hyperspace vector coordinates in the RAM of its astrogation buffer (thus allowing for even ships with limited navicomputers to make hyperspace jumps and also acting as a backup in the event of navicomputer malfunctions), and many had the intelligence and experience to perform engine startup and pre-flight taxiing. Its ROM library had reference and repair designs for well over seven hundred starship models to ensure it was able to do its functions in repairwork, with its Intellex IV internal computer scans technical files also co pinpointing potential problems as well as finding data patterns or debug computer codes, allowing it to conduct over 10,000 MPF operations a second. When plugged into a T-65 X-wing starfighter, Eta-2 Actis-class interceptor, or similar starfighter, the R2 monitored flight performance, pinpointed and corrected technical problems, and performed power management, optimizing shipboard systems.

The droid was equally popular with Galactic Republic fighter jocks as it was with the general public. This was a radical departure, as previously all such droids had been dedicated government models. But unlike the clunky R1-series or the overly large P2-series, this rounded, waist-high droid was made specifically to fit in military starfighter astromech slots. Like its forerunners, the R2 astromech was designed to work in and around space vessels as a diagnostic and repair unit. The main difference was in their height - at 0.96 meters, the R2-series was less than half as high than the hulking P2. When not compared to each other, the R2-series shell was near-indistinguishable from that of the P2-series astromech droid, prototype of the entire R-series. Technical schematics of an R2 unit from one of IA's HoloNet advertisements.

Star wars republic commando crash on startup