Author Topic: Whee...Campaign Background  (Read 3913 times)

0 Members and 1 Guest are viewing this topic.

Offline NGTM-1R

  • I reject your reality and substitute my own
  • 213
  • Syndral Active. 0410.
Whee...Campaign Background
This might be better suited to the General Freespace forum, but maybe not. Anyways, I wrote up a gigantic amount of background info for Police Action, and I'd hate for it never to see the light of day.

I'll toss it out over a few weeks...like I said, it's a gigantic amount to read at once.

GTVA Military Organization

Terran Fleet Organization
Terran fleets are subdivided into a Destroyer Battlegroup and several cruiser-corvette Striking Forces. Before the Second Shivan Invasion, the Destroyer Battlegroup consisted of the destroyer and whatever fighters were escorting it. Tactical thought has since changed drastically and commanders are far less cavalier with their destroyers then they once were. It has become almost mandatory that any more elderly cruisers falling under the fleet commander’s jurisdiction accompany the destroyer, making the Destroyer Battlegroup actually qualify for its title.

The wisdom of this new arrangement was proved at the Battle of Regulus Five, where the Leviathan-class cruisers GTC Ness and GTC Serpent are primarily credited with keeping the Orion-class GTD Orestes in the battle by keeping it safe from the NTD Vengence’s bomber wings. The Orestes was able, with the cruisers’ cover, to move into posistion to support 2nd Fleet’s attack with her beams. The Orestes then destroyed the NTCv Lud and NTCv Cromwell, leading to the total collapse and destruction of the NTF 9th Battlegroup, finally securing Regulus two months after the end of the Second Shivan Invasion.

The cruiser-corvette Striking Forces are meant to take the offensive place of destroyers, delivering several groups which have destroyer-level firepower to various places across a contested system while the destroyer stands back and provides fightercraft support. Operationally they were a success against the NTF, and while not strictly speaking a success against the Shivans (few things are), they offered a much better chance of survival to the ships involved then operating independantly.

In the original concept a Striking Force would muster two corvettes and a variable number of cruisers, not less then three, with each Fleet having three or four Striking Forces. Close to 60% of these groups were wiped out in Capella, however, and the rest are understrength because of losses. Only 2nd Fleet fields a full-strength Striking Force, thanks to the recent entry into service of several Aeolus Block 2 cruisers.

Finally, each fleet has its attached aerospace group, the fightercraft of its destroyer, divided up into squadrons by their respective types. The aerospace group is largely an adminstrative rather then an operational unit. While it is rare for a whole squadron to deploy, they do so on occasion. An aerospace unit primarily draws its identity from its squadron, while larger craft do so from their fleet.

Vasudan Fleet Organization
The Imperial Vasudan Navy is divided into Battlegroups, each functionally analogous to a Terran Fleet, but smaller (or, normally smaller; the losses taken in Capella have reversed this.). A Vasudan Battlegroup contains a destroyer, two or three corvettes, a variable number of cruisers not less then four, and the destroyer’s aerospace group. By calling up reserve units and reactivating older ships, the IVN has managed to get most of its battlegroups to minimal strength, although the majority of their ships are the older, less effective Aten-class following the near-extinction of the Mentu-class in Capella. A program is currently under way to upgrade the Atens to the new Mark II standard, but as it has only just begun the majority remain unupgraded.

A Battlegroup is, in theory, the smallest operational unit of Vasudan capital craft. In practice Battlegroups are subdivided as the need arises. Normally the majority of the group remains with the destroyer, but two or three ships will be absent on detached duty at any one time.

The concentrated firepower of a Battlegroup when all ships are present is formidible, and such units are often used to make, or break, node blockades. Terran fleets are designed to provide tactical and strategic flexiblity, while a Vasudan Battlegroup is meant for situations that require the application of large amounts of force, in either defensive or offensive roles. As such, the Vasudan Battlegroups were on the forefront of the middle action of the NTF Rebellion, but it was Terran Fleets that lead the rapidly-moving counterattack at the end. Similarly the Vasudans were used for the Nebular Campaign in its middle and end stages, but the opening blitz was made by Terran craft.

System Defense Force Organization
By their nature, System Defense Force units tend to be less apt to organization then Terran fleets or Vasudan battlegroups. They employ a greater variety of ships and units then either, and have a greater variety of concerns.

A System Defense Force is generally composed of an older destroyer, a number of corvettes and cruisers, an aerospace group that is somewhere between double and triple the size of that to be found onboard a regular fleet destroyer, and a mid-sized collection of marine and military police units, usually no more then three regiments. They are divided into a Destroyer Battlegroup, several Striking Forces, a set of semi-independent fightercraft squadrons, and what is referred to by tradition as “the Landing Force”. In the day-to-day functioning of an SDF, these are adminstrative rather then operational distinctions, but in the event of an invasion by a major armed force, they become operational. In extremely dire circumstances a System Defense Force may be called upon to serve outside it’s home system: in such cases it behaves as would a Terran Fleet.

The day-to-day functioning of an SDF sees most of its units operating across the system as single ships or fighter wings, patrolling or guarding installations and convoys as they go about the task of protecting GTVA citizens and their property from attack. They are also charged with providing security for major public events that do not take place on an inhabited world, enforcing GTVA laws in space and on GTVA installations, protecting notable personalities both government and civilian who are transiting from place to place via spacecraft, and the exploration and mapping of their home system.

SDF pilots and crews are not to be underestimated. They are technically considered reserve units, but they are professional, full-time military personnel. Their equipment is up-to-date (SDF equipment sees constant use, and so needs to be replaced more often) and their skills with it well-developed thanks to continual use. Pilots, ranks, and ratings are often transferred back and forth between regular fleet and System Defense Force units, considerably blurring the line between them. SDFs’ direct ties to their home system and familiarity with it make them truly formidible on the defensive in their home system, as the Deneb and Epsilon Pegasui System Defense Forces demonstrated against the NTF.

Defense Forces are the most integrated units in the GTVA. All SDFs contain ships and units both Terran and Vasudan, though the exact balance varies. The only outward sign of this is the designation of their aerospace groups, which are invariably given the designation “Combined Aerospace Group” followed by their group number. The generally smooth functioning of the integrated SDFs had resulted in a trial plan for an integrated regular battlegroup/fleet shortly before the Second Shivan Invasion. Such plans have had to be placed on hold for the foreseeable future.

Due to the extremity of Capella, most System Defense Forces had most of their ships and squadrons called in to back up the regular fleet, and suffered losses on a scale similar to regular fleet units. All are understrength. The Vasuda and Capella System Defense Forces suffered worst, with the Vasuda SDF being nearly wiped out (entering Capella at full strength, only six fighters and a lone bomber survived) and the Capella SDF being reduced from full strength to only two cruisers, the GTCs Kraken and Champlain.
"Load sabot. Target Zaku, direct front!"

A Feddie Story

 

Offline NGTM-1R

  • I reject your reality and substitute my own
  • 213
  • Syndral Active. 0410.
The histories of some of the major ships in the campaign this time around.

GTD Soyakaze
The Soyakaze has a long history of service behind her. She was the fourth of the Orion class to be launched, serving the GTA with distinction during the Terran-Vasudan War and fighting the Shivans during the Great War. It was a strike group from the Soyakaze that destroyed the Jotenheim installation and ended GTI’s hopes of conquest by destroying the Hades superdestroyer. The Soyakaze remained faithful to the GTA throughout the factional period that followed. In the end she was placed in mothballs in Vega following the reorganization of Terran fleets after the formation of the GTVA. There she stayed, until the NTF Rebellion, when the GTVA began upgrading its old Orions and putting them back in service.

The Soyakaze entered the recomissioning cycle shortly after the destruction of the GTC Viligant signaled the beginning of the Second Shivan Invasion. Work on her was considerably slowed by Vega dealing with a constant stream of damaged ships from the Nebular Campaign that Capella’s shipyards could not handle. When the plan for closing the Capella nodes came about, the Soyakaze was one of three mothballed Orions in Vega considered for Meson Bomb deployment (the others were the Nereid, actually selected, and the GTD Intrepid), but her drives had deteriorated since she was mothballed during the Reconstruction period and would have required a complete overhaul. Time factors were critical, and the Soyakaze was not selected.  

As the farthest along in refitting of several mothballed Orions in Vega (which isn’t saying much) when the SD Famine crisis came up immediately after Capella, the Soyakaze was rushed through recomissioning to help deal with the threat. With beam cannon already fitted and the drives partially overhauled, this meant the installation of the new reactor, which was accomplished in record time. However, little else was done, and the destroyer was in mothballs for over a decade. Under any other circumstances the ship would be considered “By no stretch of the imagination ready for or capable of operations,” in the words of her current commander, Captain Racheal Burke. The Soyakaze is currently operating with about 45% of her normal crew complement and needs major work on the life-support systems before she can support any more crew. (This is why she carries only a single fighter squadron, the 329th “Devils” Interceptor Squadron, which is itself short some of the normal support staff.) Much of the electrical wiring and electronic equipment not absolutely vital to fight the ship still needs to be replaced, and her jumpdrive’s functioning is not stable enough for intersystem jumps.

Vega’s pirate problem is so bad, however, the Soyakaze is unlikely to get the full refit she needs for at least another two weeks.


NTD Undaunted
The sole remaining NTF destroyer, the Orion-class NTD Undaunted was originally known as the GTD Sovereign. Completed during the Great War, the Sovereign was rushed into action to help defend Ribos. Present at Tombaugh Station, she was the only capital craft to survive the attack, and had sustained two hits from the Lucifer's main battery, completely destroying her flight deck and much of her drive array. By the time the massive damage done to her was repaired, the Great War was over. The Sovereign served briefly during Operation Templar, then was mothballed in Polaris during the reorganization of Terran fleets following the GTVA's formation.

When the NTF Rebellion began, the Polaris boneyard became the major source of capital craft for the NTF. The Sovereign, rechristened Undaunted, was being reconditioned from the Polaris boneyard when the GTVA Colossus smashed the NTF blockade of the Polaris-Epsilon Pegasui node and signaled the end of the NTF.

The Undaunted was briefly engaged by the GTD Master, but fled rather then offer battle; based on this and its subsequent tendancy to flight when faced with so much as a bomber wing, it is believed the Undaunted did not in fact finish reconditioning and may not be battleworthy. The Undaunted managed to lay low in Polaris until the Colossus left, then somehow slipped into Deneb. She is accompanied by two corvettes (the NTCvs Pompey and Spartacus), two cruisers (the NTCs Invidious and Invincible, both Leviathan-class), a Faustus science cruiser (the NTSC Hinton), and an Argo transport (NTT Skua), representing the entire remaining strength of the Neo-Terran Front.

While the Undaunted, Spartacus, and the noncombat craft have been reluctant to offer battle when challenged, and completely quiet when left alone, the other ships have been a constant thorn in the side of the Deneb System Defense Force and the GTVA in general. Similarly some of the Undaunted’s fighter squadrons have been very active, and some have not. What this means is anyone’s guess, but it could stem from a lack of supplies.


GTFf Vandal
During the storming of Polaris, the GTD Master was assigned to capture the small orbital shipyards of Polaris V. During this operation she encountered two vessels, apparently of the same class as the NTF Iceni, under construction. One proved to be operational and was destroyed during the action, but the other was not operational, and was captured intact. A complete set of blueprints was captured in the shipyard itself as well.

The Iceni was a highly effective combat vessel, as the GTVA had quite painfully learned. It was also based on an old proposal, made during the Great War, for a cheap yet powerful “pocket destroyer” as an answer to powerful Shivan cruiser groups and destroyers. The old Tribal-class project, once shelved by the Ursa-Harbinger combination, was resurrected, now working from the partially completed Iceni hull. Numerous alterations were made to the weapons fit and other details, but the the basic hullform remained unchanged.

Because of the alterations required for the partially completed Iceni, the second ship of the new class was completed at roughly the same time as the first. The ship constructed from the partially completed hull was christened Visigoth, while the new-construction ship was named Vandal.

The Vandal is armed with a formidible array of anti-captial beam weaponry, mounting two large Type 3 beam mounts forward, and two of the new Type 3 Block 2 mounts (nicknamed “Pulsars” by the crew) on each broadside. She also carries four Maxim cannon and an array of flak guns and plasma emitters for defence against enemy fightercraft. Currently undergoing shakedown and operational trials alongside her sistership Visigoth, the Vandal has proved to be formidible in exercises, and the future of both the ship and her class look bright.


PVD Prophecy
The Prophecy is quite likely the most hated enemy of the Imperial Vasudan Navy that still survives. Never destroyed despite numerous efforts before, during, and after Operation Templar, it has reappeared several occasions since the fall of the Hammer of Light, reaching out to upset things and create disaster from situations that otherwise would have turned out well. These attacks have been against Vasudan targets, in contrast to other remnant ships of the Hammer of Light.

Somehow the Prophecy has acquired a modern weapons fit along the way. How this happened is a mystery to GTVI, but the Prophecy has beam cannon and flak guns regardless. Its fighter wings somehow have survived as well, though it seems to exclusively deploy Thoths.

Among the list of the Prophecy’s crimes are the destruction of Altair II’s orbital installation and a bombardment of the excavations there, destruction of the GVCv Sobek on that ship’s maiden voyage, a bombardment of civilian settlements on Deneb V, and an unsuccessful attempt to attack the GTVA Colossus while it was in the early stages of construction.

Institutional memory, like all Vasudan memories, is long, and several units have claims upon the Prophecy. The oldest belongs to the 33rd Heavy Fighter Squadron, whose original namesake was destroyed by wings from the Prophecy shortly before the Siege of Vasuda Prime during the the Great War. Such grudges transcend mere destruction and rebuilding, and the 33rd’s hatred for the Prophecy is far more visceral then many Terrans believe a Vasudan capable of. Several other ships and squadrons, both Terran and Vasudan, have special reason to hate the rogue destroyer.

The Prophecy has been quiet for some time now, with no attacks since slightly before the start of the Second Shivan Invasion. The most recent sighting, an unconfirmed one, was five months ago in Deneb. GTVI would like to think the Prophecy has finally met it's demise in some fashion, but considering the ship's track record, no one is willing to declare the Prophecy dead yet.
« Last Edit: October 15, 2005, 12:58:29 am by 2191 »
"Load sabot. Target Zaku, direct front!"

A Feddie Story

 
Whee...Campaign Background
I salute your hard work and attention to detail sir.  If I ever get around to actually making a campaign, I hope I can at least put as much thought into it as you have here.

Once again :yes:
GTI Rebellion FREDer

Dissident Theory

Permissum sacramentum non exsisto infractus , per fides exsisto led.

 

Offline Singh

  • Hasn't Accomplished Anything Special Or Notable
  • 211
  • Degrees of guilt.
Whee...Campaign Background
Signifcant amount of details, sir - very well done! :yes:

One could quite easily base a campaign simply off that last remaining wing of fighters and the last two surviving cruisers from Capella, to say nothing of the Prophecy or the Undaunted
"Blessed be the FREDder that knows his sexps."
"Cursed be the FREDder that trusts FRED2_Open."
Dreamed of much, accomplished little. :(

 

Offline Nuclear1

  • 211
Whee...Campaign Background
If you did make a campaign around this, I, for one, would find it highly-involving and enjoyable. Great work on the details--they really add to a campaign. :yes:
Spoon - I stand in awe by your flawless fredding. Truely, never before have I witnessed such magnificant display of beamz.
Axem -  I don't know what I'll do with my life now. Maybe I'll become a Nun, or take up Macrame. But where ever I go... I will remember you!
Axem - Sorry to post again when I said I was leaving for good, but something was nagging me. I don't want to say it in a way that shames the campaign but I think we can all agree it is actually.. incomplete. It is missing... Voice Acting.
Quanto - I for one would love to lend my beautiful singing voice into this wholesome project.
Nuclear1 - I want a duet.
AndrewofDoom - Make it a trio!

 

Offline Mongoose

  • Rikki-Tikki-Tavi
  • Global Moderator
  • 212
  • This brain for rent.
    • Steam
    • Something
Whee...Campaign Background
I really like the idea of the Prophecy hanging around for so long and causing problems for the GTVA.  I always wondered what happened to the Prophecy after The Great Hunt:  did the Bastion and her remaining fighters take it out, or did it leave the battlefield?  Having it lurk around as a kind of HOL "ghost ship" is pretty cool. :)

 

Offline NGTM-1R

  • I reject your reality and substitute my own
  • 213
  • Syndral Active. 0410.
A bit of insight into the Vasudan military.

Named Vasudan Units
It is rare for a Vasudan unit to be named as most Terran units are. Such names are granted only for exceptional service, by direct Imperial decree, and never posthumously. In the history of the Imperium, dating back thousands of years to when Vasudans fought wars amongst each other with crude melee implements and bows, only forty-six units have been granted a name. Vasudan unit names are not generally nouns as those of Terran squadrons, but rather adjectives, qualities or concepts the unit has demonstrated or upheld to earn its name.

Names are generally granted at the regimental level for ground units, and the squadron level for aerial or aerospace craft, though exceptions exist to the first rule. By type, the forty-six units granted names break down as sixteen infantry, four marine (spaceborne) infantry, seven armored, four atmospheric fightercraft, one naval, one artillery, two battlegroups, and eleven aerospace fightercraft. A unit has not been granted a name since the 112th “Steadfast” Fighter Squadron was given one for their heroic efforts covering the evacuation of Vasudan civilians during the Siege of Vasuda Prime in the Great War. (This was itself the first name granted in slightly more then a decade.)

A named unit recieves the best equipment, personnel, and training, as they are considered the elite of the elite and the best the Imperium has to offer. So long as a single fighting member of a named unit survives, the unit will be rebuilt should it suffer losses in combat. Should it be wiped out, the unit is disbanded and its unit number permanently retired. The names of its members at the time of its destruction are inscribed upon the stone walls of the Hall of Martyrs in the Imperial Palace, alongside those of the greatest heros of the Imperium. This has not happened often in Vasudan history, but the Great War exacted a heavy toll and seven named units were completely wiped out during the Shivan conflict. Another rebelled and joined the Hammer of Light; that unit, upon its destruction, had its name and the names of its members completely erased from all Vasudan records, as if they had never existed.

4th Vasudan Battlegroup
The GVD Memphis came back from Capella with the remains of a Shivan Lilth cruiser sticking out of her bow, a massive hole in her left stern that showed where a Ravana destroyer had scored a direct hit with its entire main and secondary battery, and close to 65% of her crew killed or wounded. Of her escorts, the GVCv Luxor escaped with only minor damage she could repair herself, but the GVCv Bahiti lost thirty percent of the ship off her bow to Shivan bombs and the GVCv Hathor had her keel broken; it is a minor miracle that the Hathor didn’t fold up as it entered subspace to leave Capella or while exiting subspace when it arrived in Vega. Two of the Memphis’ cruiser escorts were lost in the Nebular Campaign; the other four did not survive the massed bomber attacks the battlegroup suffered en route to the Capella-Vega node. As for the Memphis’ aerospace group, it came off Capella actually slightly overstrength, having absorbed fightercraft and pilots from the destroyed GVD Psamtik and GVD Apothesis. These were integrated into the Memphis’ own squadrons, and more then made up her losses.

Despite truly heroic, round-the-clock efforts on the part of her remaining crew and repair crews from the Vega Installation, the Memphis could not be rendered battleworthy again in time to assist with the final assault on the SD Famine. The GVCv Luxor’s light damages meant that she was able to assist GTVA forces during the Famine crisis, but she played no major role in the campaign, serving to reinforce the escort groups of various convoys. The Hathor and the Bahiti were too badly damaged and could not be made operational in time to assist either; indeed, the Bahiti was not ready for service again for another two months.

The Memphis is still short by 15% of her normal crew complement, but otherwise is fully operational. The Luxor, Bahiti, and Hathor, the latter two now completely repaired though still slightly undercrewed, continue to operate with the Memphis in Vega. To replace her lost cruisers, three Atens and a Mentu were assigned to escort the Memphis. They are the GVCs Re, Abtu, Sanura, and the GVC Somtus, respectively. The Re has been upgraded to the Mark II standard; the Abtu is next in line as soon as she can be spared from escort duties.

Mentu-class Cruisers
The Mentu-class currently hovers on the brink of extinction. The class entered the Second Shivan Invasion seventy-three ships strong: it came out of it with only seven, a casuality rate of 90.4%, the worst of any ship class in GTVA service. With weaponry similar to the Aeolus, but lacking the fire arcs of the Aeolus, Mentus were consistantly targeted first by Shivan fighter and bomber wings, but were not able to defend themselves as well as the Aeolus and racked up nothing like the incredible kill score the Aeolus did. Their lack of anti-capital beam cannon also counted heavily against them, and many fell to Shivan corvettes or cruisers they might otherwise have been able to fend off.

In the end, despite its early successes against the NTF, the Mentu failed in its original design purpose: to combat the Shivans. Vasudan Command’s disillusionment with the design has resulted in the scrapping of the five cruisers that were under construction, and a search for a new front-line cruiser for the Imperium.

A search that may have been abortive, as it turns out.

Aten-class Cruisers
The GVC Aten class of cruisers has a long and varied history of service with the GTVA and the PVE before it. Despite this, it has always been universally despised by crews and commanders alike. Nevertheless, the Aten has in a sense been the salvation of the IVN. Many corners were cut in the Aten’s design, for one purpose: to keep the crew down. As a result the Aten can be crewed with only 300, as opposed to 750 for a Terran Fenris. The tradeoff was probably not worth it in the end, but when the crunch came after Capella, the numerous mothballed Atens could be put back into service rapidly to replace the near-extinct Mentu class.

While this gave the Imperial Vasudan Navy back its cruiser arm, it also lead to much profanity and agony of mind among the IVN’s commanders, as the Aten was simply not effective in a modern combat environment. It was the 4th Vasudan Battlegroup that threw in the towel on using stock Atens first, handing over one of theirs to the civilian shipyards orbiting Vega V. There the unfortunate GVC Re was subjected to more “cut to fit, bend to match, weld to suit” outright butchery then any other GTVA warship has ever been, but the results were gratifying.

With more turrets, two small Type 3 beam mounts for anti-capital work, a new collapsed-core molybendum armor plate, and a desperately needed overhaul of the drives and electronics, the new Atens, dubbed “Mark II”, are formidible combat craft and easily the equal of the Aeolus-class. The Admirality has issued orders that all serving Atens be refitted to the Mark II standard ASAP, but the conversion is a time-consuming process, and most battlegroups or system defense forces only field one or two converted ships.

Vasudan Scout-Bomber Squadrons
In essence, a scout-bomber squadron is a self-contained reconnaissance and attack force, able to operate completely independently of other squadrons. They are expected to be their own escort on all missions, to conduct standard reconnaissance and recon-in-force, and to do all this while maintaining a medium or light bomber capablity to be exercised if presented with a target of opportunity. They are also often called upon to perform a more traditional light or medium bomber role.

While the last Terran units with a scout-bomber designation were retired in the mid-20th century long before the GTA was formed, Vasudan forces have maintained the concept. Vasudan scout-bomber squadrons are considered elite units, and provided with some of the best pilots, support staff, and equipment the Imperium can muster. They have earned their reputations; during the early stages of Terran-Vasudan War, Terran Command was often left scratching its collective head when attempting to figure out how a Vasudan scout-bomber unit could accomplish as much as it did. Deprived of their beloved Ptolemy fighter-bombers in the second half of the T-V War and during the Great War, they were forced to use modified Seth fighters that severely compromised their capablities.

The modern scout-bomber squadron makes use of the GVB Bakha exclusively; in fact, the need for a new ship for the scout-bomber pilots was one of the driving forces behind the design and production of the Bakha. Since being reequipped with the new bomber they have proved they still deserve their reputations; among their feats were the destruction of an NTF destroyer and three NTF corvettes, two Shivan destroyers and seven Shivan corvettes, and having successfully performed critical strikes against the first Shivan Sathanas.

To serve with a scout-bomber unit, no matter one’s posistion in the squadron’s hierarchy or support staff, is an honor considered second only to service with a named unit or the Imperial Guards. Vasudan units are rarely given names, but of the eleven squadrons that have been so graced in the history of Vasudan aerospace flight, seven of them are scout-bomber units.
« Last Edit: October 23, 2005, 03:49:04 am by 2191 »
"Load sabot. Target Zaku, direct front!"

A Feddie Story

 

Offline Thor

  • Captain of the GTD Sparta
  • 29
Whee...Campaign Background
well its good that something from Police Action is kicking around still.  excellent stuff.
I can't believe my profile is still active... member since  July 25, 2002

 
Whee...Campaign Background
whoa.....very impressive story....hopefully theirs a campaign going on into this....

 

Offline NGTM-1R

  • I reject your reality and substitute my own
  • 213
  • Syndral Active. 0410.
Whee...Campaign Background
Quote
Originally posted by Thor
well its good that something from Police Action is kicking around still.  excellent stuff.


It's not the campaign you think it is.
"Load sabot. Target Zaku, direct front!"

A Feddie Story

 

Offline TopAce

  • Stalwart contributor
  • 212
  • FREDder, FSWiki editor, and tester
Whee...Campaign Background
I already released your Police Action, Thor. I think I even sent you an E-mail or PM that I did.
My community contributions - Get my campaigns from here.

I already announced my retirement twice, yet here I am. If I bring up that topic again, don't believe a word.

 

Offline Thor

  • Captain of the GTD Sparta
  • 29
Whee...Campaign Background
yeah you did.  The ole mind is slipping :p

anyways, its still good stuff
I can't believe my profile is still active... member since  July 25, 2002

 

Offline NGTM-1R

  • I reject your reality and substitute my own
  • 213
  • Syndral Active. 0410.
Re: Whee...Campaign Background
Why you don't live through attacking a GTVA-held planet in a capital ship.

Tyr Surface-to-Space Missiles
Terran-designed during the Reconstruction, subjected to constant upgrades since, the Tyr is the GTVA’s only current surface-to-space missile design, and the weapon on which the GTVA has staked much of its ablity to defend inhabited worlds. (Ground-based beam cannon are much more rare and have significantly shorter range.) With a range in excess of 500,000 kilometers, Tyrs can keep enemy ships well away from GTVA planets and provide safety not only to the world itself but ships and installations in orbit.

The Tyr is the most powerful weapon the GTVA has that is suitable for tactical deployment. Two are enough to take out a destroyer, and one is generally enough for lesser ships. They are fast (more then half the missile’s total mass is its drives) enough to outrun any non-interceptor fighter design currently known, and interceptors can only catch them on afterburner. They are also lightly armored, making them difficult to destroy with antifighter defenses. Unfortunately, they have no consideration whatsoever towards stealth, and their sensor signature is large enough that they can be targeted with heavy anticapital beam cannons. If these weapons do not destroy the missile outright they will certainly burn out the missile's infrared terminal guidance system. The missile will continue to head for the last known location of the target, and generally it will hit given its speed, but occasional misses have occured.

The Tyr’s size prohibts deployment from spacecraft; it has roughly the same dimensions as a Boanerges bomber and nearly twice the mass, making the handling and launching of a Tyr something best achieved on the ground.

The Tyr was first fired in anger in the defense of Deneb V against the NTF. Original doctrine for Tyr batteries was to use three missiles for a cruiser or corvette target, four for a destroyer, and to have them approach from multiple vectors. This was the point at which the ability of anticapital beam cannon to target the Tyr was discovered, when the first salvo of Tyrs from plantside was swatted out of space by the NTF Third Battlegroup. Most of the launch sites on Deneb V were silenced by fire from the NTDs Vengence and Vasa before the second salvo was finished launching, although this one succeeded in destroying a pair of cruisers. Deneb III’s Tyr defenses faired better, appraised of the need for a change in tactics, and destroyed several NTF ships before the NTF abandoned attempts to supress them via orbital bombardment.

Capella II had a permanent launch complex near the capital city, and two mobile Tyr batteries; Capella III had three mobile batteries. During the Battle of Capella all of them shot out their supply of missiles. They inflicted horrific casualities on the Shivans, more then twenty Shivan cruisers falling to Battery B of Capella II’s permanent launch complex alone. The Tyr batteries of the Capella SDF are credited with saving hundreds of thousands of lives by denying Shivan capital ships entry to local space around Capella II and III.

Experiments have been conducted with fitting the Tyr with an intrasystem subspace drive; the original design specifications called for the capablity, although it was not tested until several years after the acceptance trials. These experiments have been somewhat less then successful. The fault lies not with the drives but rather with the missile’s extremely limited ability to do its own target detection and acquistion. Future upgrades may rectify this via improved sensors and software, or the addition of the ability for mid-course guidance correction by a ship already in the area.
« Last Edit: March 01, 2006, 03:25:40 am by ngtm1r »
"Load sabot. Target Zaku, direct front!"

A Feddie Story

 

Offline Mehrpack

  • 28
  • Flying Monkey
Re: Whee...Campaign Background
hi,
i dont have read all of your post, but the half and its a very good work  :yes:.

Mehrpack
Nobody is Perfect.
attention: this english is dangerours and terrible, runaway so fast you can!