Author Topic: The battle of Gliese 784  (Read 233 times)

0 Members and 1 Guest are viewing this topic.

Offline superstrijder15

  • Leading Rate
  • *
  • Posts: 11
  • Thanked: 2 times
    • View Profile
The battle of Gliese 784
« on: July 19, 2017, 03:21:53 PM »
This is my first AAR for this game, done in my first ever campaign.   Feedback is welcome, both on writing and on gameplay.   

Late november and early December 2104:
It was now almost 30 years ago, that the first expedition to Gliese 784 had been sent.   It should have been a completely normal system: the carrier would carry the fleet from Sol to the system, it would launch the GeoFighters, and then commence research of the gravitational survey points in the system.   After a few months, the fighters would return, and the ship would spend another year or so flying around and doing gravitational surveys. 
But it wasn't to be this way.   After the fighters were launched, the commander sat back, but after a day he suddenly got a bunch of messages: Multiple hostile contacts, hiding behind planets or on moons, suddenly attacked the fighters.   They ran, but to no avail.   Then enemy had huge battleships, simply able to outrun our best couriers, to say nothing of the slow research fighters.   Distress messages were flooding the system, but, even more worrying, they then went silent.   
The commander of the carrier turned his ship around, slowing to a crawl so as to evade detaction, attempting to reach the JP of Lacaille 8760.   The ship took a month, but reached the new colony of Lacaille.   From there it returned to Earth, with the news that an incredibly hostile force was encountered.   The full fleet was shuttled over, using the ability of the carrier to take two other ships with her on each jump to be shuttled in pairs.   The fleet waited for the imminent invasion at the Lacaille colony*, but it never came.   In the meantime, communication experts probed the system and tried to start communications.   From their research, they found that the enemy was old, and probably robotic.   No signs of civilisation existed on the planet.   In the meantime, the military geniusus of Earth rushed to create something that could be effective against these battleships, while building missile boats able to outpace, outrange and outlast the older laser warships around Lacaille, yet would be no match against the enemy warfleet.   This class was called the
MB Flower**.   
As there was no space for big sensors or jump drives on these ships, the BattleRider** class command carrier was designed.   It had large sensors, a squad jump drive and hangars for scouts or FACs.   The final ship designed, still having techs in research while the other were already being produced, was the Audacious class FAC**.   It was the only class so far to be faster than the opponent, using the best engines available and a lot of box launchers.   
Twelve Flower, three BattleRider and three Audacious were built, and then the fleet started moving.   

After almost a month of travel, the fleet reached Lacaille 7860.   It refueled, and moved over to the JP.   They were accompanied now by the original carrier, which had been taken off of system surveys to bring in more scouts**.   After the fleet jumped in, it wen't into formation quickly.   One of the battleriders served as the formation anchor.   The scouts were posted on the maximum 100 million km from the anchor***, formed an arc of 80 degrees with about 8 pairs, and turned on their actives.   The battlegroup formed up with 3 groups: The FAC formed in the center, 100 million km from the anchor, and the missile boats formed up 20 degrees offset, each group of 6 with a Battlerider for sensors.   These kept their sensors off however, allowing the enemy to charge through the middle, right through the Alpha strike of the FAC and then a barrage from the missile groups, at the sensor boat.   The first enemy sighted were 4 enemy FAC, charging at only 6000km/s at the center of the formation.   The first barrage of missiles from the FAC took out 1 ship, while the others seperated and tried to attack scouts.   While the FAC went to the missile group to reload, the center scouts pulled back to let the enemy come closer.   However, due to the enemy small size, the fleet couldn't attack from a longer range, so only the FAC were an effective weapon.   Three more barrages were needed to take the enemy down, but no casualties were sustained.   
The fleet resumed formation and moved on, certain of an easy victory now.    But then, the signal from the BattleRider 003 went down, being replaced by a distress signal as it got hit by a salvo of missiles.   Choas and confusion, and then the actives of one of the Flower came online, and the task group scattered.   Tens of salvoes flew less than a minute away from the group, which tried to survive by splitting up.   As the Anti-clockwise TG got hit, the captain of the clockwise one hurried to get the sensors working, and saw a daunting picture: At least 15 salvoes were flying at his TG.   In the distance, but well within sensor range, there was a fleet of multiple battleships, charging in at 10Mm/s.   He quickly coordinated a AMM defense, telling units to just fire at will at the salvoes.   Slowly the salvoes of ASM and AMM grew closer. 
On the anti-clockwise front, the situation was a lot more drastic.   The fleet scattered, and although many actives went up, the FC failed to react quickly enough (read: i forgot to turn on auto fire and when i did the ships didn't fire for unknown reasons) to take out the missiles.   The last to go was the Flower 016, which managed to take out 2 salvoes and wheather a third before succumbing.   In only three minutes, the fleet was halved. 
The FAC had now also started moving, going for the enemy battleship.   The ranges of combat were long however, and the next happening was well over an hour later, when the ASM and AMM clashed.   Each salvo took out about half on enemy salvo, so lot's of them were needed.   After another hour, most salvoes had been dealt with, and it seemed like the TG would surive unscathed. 
In two more hours, the FAC finally reached firing distance, and opened fire on the enemy.   The first barage did nothing, but they returned.   In the meantime, all ASM were destroyed, and the enemy had stopped firing.   Which was good, as there were only about 100 AMMs left in all the stocks.   The fleet was woefully unprepared.  .  . 

However, nothing dangerous happened.   It would take multiple days for the FAC to whittle down the armour on the enemy ships, which barely even tried to escape.   Obviously better missiles would be needed in the future.   When the enemies were finally taken down, the fleet moved for the Lacaille 8760 JP, taking on survivors on the way and regrouping at the point.   A salvager was called in, and the fleet retreated to Earth. 

*I play without maintenance, so the fact there are no facilities is no problem
** Schematics:

Flower:
Off-Topic: show
Flower class Missile Boat    8 950 tons     212 Crew     1928.  8 BP      TCS 179  TH 200  EM 0
2234 km/s     Armour 4-38     Shields 0-0     Sensors 1/1/0/0     Damage Control Rating 11     PPV 21
Maint Life 0.  19 Years     MSP 135    AFR 640%    IFR 8.  9%    1YR 704    5YR 10564    Max Repair 300 MSP
Intended Deployment Time: 24 months    Spare Berths 1   
Magazine 543   

100 EP Internal Fusion Drive (4)    Power 100    Fuel Use 38%    Signature 50    Exp 10%
Fuel Capacity 750 000 Litres    Range 39.  7 billion km   (205 days at full power)

S3 ML (50% SRed) (6)    Missile Size 3    Rate of Fire 225
Size 1 Missile Launcher (12)    Missile Size 1    Rate of Fire 15
Missile Fire Control FC14-R1 (3)     Range 14.  4m km    Resolution 1
Missile Fire Control FC230-R100 (70%) (1)     Range 230.  4m km    Resolution 100
S3 ASM (90)  Speed: 30 800 km/s   End: 124.  8m    Range: 230.  7m km   WH: 4    Size: 3    TH: 102/61/30
S1 AMM (273)  Speed: 35 000 km/s   End: 7m    Range: 14.  8m km   WH: 1    Size: 1    TH: 140/84/42

Active Search Sensor MR14-R1 (1)     GPS 240     Range 14.  4m km    MCR 1.  6m km    Resolution 1
Active Search Sensor MR144-R100 (70%) (1)     GPS 24000     Range 144.  0m km    Resolution 100

Missile to hit chances are vs targets moving at 3000 km/s, 5000 km/s and 10,000 km/s

This design is classed as a Military Vessel for maintenance purposes

BattleRider:
Off-Topic: show
BattleRider class Command Carrier    20 000 tons     457 Crew     3900.  2 BP      TCS 400  TH 500  EM 0
2500 km/s    JR 5-250     Armour 2-65     Shields 0-0     Sensors 110/110/0/0     Damage Control Rating 0     PPV 0
Maint Life 0 Years     MSP 0    AFR 4000%    IFR 55.  6%    1YR 10623    5YR 159340    Max Repair 640 MSP
Intended Deployment Time: 60 months    Flight Crew Berths 0   
Flag Bridge    Hangar Deck Capacity 3000 tons     

J20000(5-250) Military Jump Drive     Max Ship Size 20000 tons    Distance 250k km     Squadron Size 5
100 EP Internal Fusion Drive (10)    Power 100    Fuel Use 38%    Signature 50    Exp 10%
Fuel Capacity 3 100 000 Litres    Range 73.  4 billion km   (339 days at full power)

Active Search Sensor MR70-R1 (1)     GPS 640     Range 70.  4m km    MCR 7.  7m km    Resolution 1
Active Search Sensor MR704-R100 (1)     GPS 64000     Range 704.  0m km    Resolution 100
Thermal Sensor TH10-110 (1)     Sensitivity 110     Detect Sig Strength 1000:  110m km
EM Detection Sensor EM10-110 (1)     Sensitivity 110     Detect Sig Strength 1000:  110m km

Strike Group
2x WatcherR100 Recon Fighter   Speed: 6000 km/s    Size: 10
2x WatcherR20 Recon Fighter   Speed: 5000 km/s    Size: 10

This design is classed as a Military Vessel for maintenance purposes


Audacious:
Off-Topic: show
Audacious class Fast Attack Craft    1 000 tons     25 Crew     357.  5 BP      TCS 20  TH 125  EM 0
12500 km/s     Armour 1-8     Shields 0-0     Sensors 1/1/0/0     Damage Control Rating 1     PPV 4.  5
Maint Life 9.  56 Years     MSP 223    AFR 8%    IFR 0.  1%    1YR 4    5YR 66    Max Repair 187.  5 MSP
Intended Deployment Time: 3 months    Spare Berths 2   
Magazine 30   

FACE 250 EP MagFusDrive (1)    Power 250    Fuel Use 161.  22%    Signature 125    Exp 20%
Fuel Capacity 100 000 Litres    Range 11.  2 billion km   (10 days at full power)

S3 Box Launcher (10)    Missile Size 3    Hangar Reload 22.  5 minutes    MF Reload 3.  7 hours
Missile Fire Control FC245-R50 (1)     Range 245.  0m km    Resolution 50
S3 ASM (10)  Speed: 30 800 km/s   End: 124.  8m    Range: 230.  7m km   WH: 4    Size: 3    TH: 102/61/30

Missile to hit chances are vs targets moving at 3000 km/s, 5000 km/s and 10,000 km/s

This design is classed as a Military Vessel for maintenance purposes

scout:
Off-Topic: show
WatcherR100 class Recon Fighter    500 tons     12 Crew     141.  6 BP      TCS 10  TH 60  EM 0
6000 km/s     Armour 1-5     Shields 0-0     Sensors 1/1/0/0     Damage Control Rating 0     PPV 0
Maint Life 0 Years     MSP 0    AFR 100%    IFR 1.  4%    1YR 29    5YR 430    Max Repair 80 MSP
Intended Deployment Time: 24 months    Spare Berths 0   

FE 30 EP Internal Fusion Drive (2)    Power 30    Fuel Use 109.  13%    Signature 30    Exp 15%
Fuel Capacity 80 000 Litres    Range 26.  4 billion km   (50 days at full power)

Active Search Sensor MR64-R100 (1)     GPS 8000     Range 64.  0m km    Resolution 100

This design is classed as a Fighter for production, combat and maintenance purposes


Off-Topic: show
WatcherR20 class Recon Fighter    500 tons     12 Crew     176.  1 BP      TCS 10  TH 25  EM 0
5000 km/s     Armour 1-5     Shields 0-0     Sensors 1/1/0/0     Damage Control Rating 0     PPV 0
Maint Life 0 Years     MSP 0    AFR 100%    IFR 1.  4%    1YR 40    5YR 600    Max Repair 105 MSP
Intended Deployment Time: 3 months    Spare Berths 1   

FE 50 EP MagFusDrive(Sig50%) (1)    Power 50    Fuel Use 29.  4%    Signature 25    Exp 10%
Fuel Capacity 95 000 Litres    Range 116.  3 billion km   (269 days at full power)

Active Search Sensor MR51-R20 (1)     GPS 2100     Range 51.  7m km    Resolution 20

This design is classed as a Fighter for production, combat and maintenance purposes


***It would be massively appreciated if this limit could be increased, or if someone could give a click by click guide to letting ship A escort ship B while ship B escorts ship C
« Last Edit: July 19, 2017, 03:24:01 PM by superstrijder15 »
 

Offline superstrijder15

  • Leading Rate
  • *
  • Posts: 11
  • Thanked: 2 times
    • View Profile
Re: The battle of Gliese 784
« Reply #1 on: August 08, 2017, 04:20:27 PM »
After the battle of Gliese 784, a jump gate to the system has been constructed, a salvager has salvaged the enemy wrecks, which sadly didn't contain any unknown technology.   The fleet took it's time to return, mainly because the fleet had lost a third of it's hangar and jumping capabilities, while it had taken a lot of survivors from the destroyed ships.   For unknown reasons, all survivors absolutely had to be stationed on the Battlerider 002, overloading life support all the time*.   Even when the ship reached port and, together with most of the battleships, went into overhaul and had all men go on shore leave, something kept on blowing up in the system.   Eventually this was traced to a Aurora fail software failure leading to superheating of critical components. 

While all was sorted out, research was going on, and an expedition was sent to research the system.   By 2107 it was getting obvious that the current expedition forces were insufficient for continuation of exploration as it was taking a year to survey just the one system, and a new ship class was needed**.   The concept for the exploration would be close to that of the old fleet: During exploration, a Poeper class carrier will carry 16 Optimist class survey fighters to an unexplored system, 8 of the Geo variety and 8 of the Grav one, they will be deployed with survey orders, and after a while they return.   
Unlike with the earlier designs, the carrier stays on the jump point, ready to flee.   Also unlike the earlier plans, this fleet won't need to return after each system, instead having sufficient fuel to continue to another system once the fleet is done in one system.   Instead of returning, this fleet has a bit of extra hangar space for miniscule, on a spacecraft scale, courier drones able to connect with the system of jump gates to notify the command of findings. 

In the near future, it is expected that a new fleet doctrine will be developed, with gauss fighters instead of missile FAC and quite possibly dedicated beam defense platforms and new, better missiles. 

Some more details on the ships:
The Poeper*** class Exploration Mothership, coming in at 20 kilotons, can move almost 2 thousand km/s.   The better part of it's interior consists of hangars, followed by engines and living space.   It has enough space to house the crews of all the fighters comfortably.   It's terribly efficient engines give the ship a technical range of 2 billion megameters, although it would take 41 years to expend all fuel, the more intensive fighter engines might use up a bit of that fuel though. 
The Poeper carries 16 survey fighters of the Optimist*** class.   These fighters can go over twice the speed of their carrier, but with a shorter range and deployment time.   They swarm out in a wave to take over a whole system for a few weeks, and then dissapear from whence they came. 



*Other ships had the capacity to handle the amount of survivors if cooperating, but IDK how to move the survivors, so I just SM repaired. 
**OOC: I had been on a sailing camp, and I really wanted to design something today, and as it will take a while for the techs for Gauss to get better and I want to give my military ships the engine tech I will have in a few years, I got to the explo service instead.   Naming in the near future is likely to be inspired by Dutch smaller sailing classes. 
***Poeper: an old class of cargo barge, I lived on one of these and a 'polyvalk' for a week a week ago. 
Optimist: the smallest class of sailing boat, used by children of up to 12-14.   It's a crude and simple construction, cheap and easy to mass-produce or learn to control. 
****Schematics:
Poeper:
Code: [Select]
Poeper class Exploration Mothership    20 000 tons     279 Crew     1943.125 BP      TCS 400  TH 625  EM 0
1562 km/s    JR 5-250     Armour 1-65     Shields 0-0     Sensors 1/1/0/0     Damage Control Rating 1     PPV 0
Maint Life 0.02 Years     MSP 61    AFR 3200%    IFR 44.4%    1YR 2849    5YR 42731    Max Repair 471 MSP
Intended Deployment Time: 120 months    Flight Crew Berths 197   
Hangar Deck Capacity 7375 tons     

J20000(5-250) Military Jump Drive     Max Ship Size 20000 tons    Distance 250k km     Squadron Size 5
312.5 EP Commercial Magnetic Fusion Drive (2)    Power 312.5    Fuel Use 0.47%    Signature 312.5    Exp 2%
Fuel Capacity 1 100 000 Litres    Range 2105.7 billion km   (15602 days at full power)

Strike Group
8x Optimist R Survey Fighter   Speed: 4347 km/s    Size: 9.2
8x Optimist E Survey Fighter   Speed: 4347 km/s    Size: 9.2

This design is classed as a Military Vessel for maintenance purposes
Optimists:
Code: [Select]
Optimist E class Survey Fighter    460 tons     12 Crew     192 BP      TCS 9.2  TH 40  EM 0
4347 km/s     Armour 1-5     Shields 0-0     Sensors 1/1/0/2     Damage Control Rating 0     PPV 0
Maint Life 0 Years     MSP 0    AFR 92%    IFR 1.3%    1YR 59    5YR 886    Max Repair 150 MSP
Intended Deployment Time: 24 months    Spare Berths 0   

FE 20 EP Internal Fusion Drive (2)    Power 20    Fuel Use 39.6%    Signature 20    Exp 10%
Fuel Capacity 50 000 Litres    Range 49.4 billion km   (131 days at full power)

Improved Geological Sensors (1)   2 Survey Points Per Hour

This design is classed as a Fighter for production, combat and maintenance purposes
Code: [Select]
Optimist R class Survey Fighter    460 tons     12 Crew     192 BP      TCS 9.2  TH 40  EM 0
4347 km/s     Armour 1-5     Shields 0-0     Sensors 1/1/2/0     Damage Control Rating 0     PPV 0
Maint Life 0 Years     MSP 0    AFR 92%    IFR 1.3%    1YR 59    5YR 886    Max Repair 150 MSP
Intended Deployment Time: 24 months    Spare Berths 0   

FE 20 EP Internal Fusion Drive (2)    Power 20    Fuel Use 39.6%    Signature 20    Exp 10%
Fuel Capacity 50 000 Litres    Range 49.4 billion km   (131 days at full power)

Improved Gravitational Sensors (1)   2 Survey Points Per Hour

This design is classed as a Fighter for production, combat and maintenance purposes
« Last Edit: August 08, 2017, 04:23:11 PM by superstrijder15 »
 

Offline superstrijder15

  • Leading Rate
  • *
  • Posts: 11
  • Thanked: 2 times
    • View Profile
Re: The battle of Gliese 784
« Reply #2 on: August 18, 2017, 12:53:55 PM »
From the Exploration Force High Command to the Government and the Press:
It is now July 2023. This is an early decade report from the exploration service to the public. This report was made early due to the overwhelming success of the Poeper-Optimist combo in exploration. This report will quickly guide all newcomers through the most important things since 2117. For information on the precursor infestation found in 2115, we would like to redirect all readers to the 2114-2117 Poeper-Optimist quality report, now declassified, which goes into detail on how the ships handled during that period.
In 2117, multiple new systems were explored, notably R Coronae Australis, which is so large our current fighters could only reach the first few planets, and which once again threw apart theories on solar system development. Another special: In early November, an expedition was sent into the jump gate which was found in GJ 1002. They discover Tau Ceti, otherwise unremarkable.
The year 2118 mainly shows a lack of administration: Although the Risico spent most of the year flying, there is no knowledge of where it went anywhere in the command post.
In 2119, the Poeper 2 goes from Tau Ceti into Heintz 299 in February, and then to the new system of HIP 113296 on July 16th. Within 24 hours, an active sensor pinged one of the fighters so strongly, the enemy showed up on our scanners. He was approaching fast, and even if all fighter dashed back, would easily take out the carrier before they reached it. The Poeper prepared a jump, while ordering the fleets to scatter. There was one confirmed beam kill before the Poeper jumped out, and what happened to the rest of the crews is unknown. By the 25th, construction of a replacement squadron is started on Earth, which will take almost two years.
During 2120 the exploration service mainly sent missions to the ‘north’ on our maps. Starting at GJ 1286, they went on and discovered these systems: EG 453, an empty, Gliese 908, EQ Pegasi on the 10th of march, 2 jump point there are still unexplored, WISE 2056+1459 the 16th of June, GJ 1256 in the beginning of august with two remaining jump points to check. Then came a dead end with the systems of Gliese 740 and Luyten 997-21. The survey of this branch was finished by May 2121.
EQ Pegasi is special, as an unknown installation was found, which made our researchers find out things really quick. It is advised to build labs here for further study of this ‘hyperlearn’ effect. Another special: in June 2120, the colony of Lacaille 9352 A-II was opened to public import of migrants. Today it stands at 5.8 million inhabitants.
From the moment we finished that branch, the service has now aimed at the area around HIP 86961, which contains one planet considered easily colonisable. One jump away, Gliese 615 and WISE 1741+2553 were discovered. WISE quickly proved precursor infested, although all ships managed to escape without casualties. Gliese seems to be something of a hub, with 4 jump points. 2 of those have been explored and lead to 41 Arae and 36 Ophiuchi. 41 Arae seems to be a hub again, with 4 jump points of its own. This sector will need a lot more exploration. Currently, the fleets are still finishing up the expeditions to these two systems.

Map of the known systems:
Off-Topic: show



In the computer of Optimist R 011:
July 17th, 2119: We are running like hell, each of us to a different location. The pings of the enemy sensors show where his missile combatant is, but the E 016 reported a large vessel approaching to melee range before her signal cut. The enemy beam vessel has been classed as a ‘Brilliant Carpace’. Will we get out of his scan range?
July 25th: 2 more fighters have been lost, and a third is currently under attack. Until now, it has only been the E’s which have been attacked, possibly because the R went out and they went in when the scatter came. We have decided to go into silent running, and are advising others to do the same.
August 2nd: Our low power messages have slowly jumped through the system, moving at the speed of light, but often failing to be received. By now, we are all picketing out original survey targets awaiting rescue. We have emergency food for a year, but in that time we need to be rescued or we need to create cryo pods somehow. We got quite some tools here, and a lot of electronics and special hardware in the sensor. I think we can do this.
December 5th: We succeeded, after a long process of trial and error. We coordinated attempts between the different fighters, using all computers and making sure to conserve as many differnet parts as possible on each ship for the final designs. Now the E 018 has a working design, we only need to duplicate it.
December 24th: Today we ate some extra for Christmas, and now everyone has a cryo pod. Tonight we will go to sleep. I will now order the computer that if we are attacked, or in 25 years, it will beam this log in the direction of Lacaille 8760 with full power, hopefully someone on Heeg will pick it up after its journey of a century.


On fleet design:
The past years have seen a lot of focus going to exploration, however another important thing happened. I started modernising the fleet. As I basically needed to research techs for things like beams and armor, and I need ridiculous amounts of new sensors, engines and weapons, this process is not yet complete. However, some ship classes are already close to completion. The new fleet is fighting with bigger warships utilizing better tech, with the goal of eliminating precursor nests with minimal losses. To this goal, the new fleet has 3 classes of sensor scouts, a (unfinished) sensor boat/carrier, a pure carrier/jump tender, a beam FAC and PD Gauss fighters. Yet to be designed are the missile cruisers and possibly accompanying PD cruisers. Battle formation will be a sensor boat in the back, taskgroups containing PD, missile strike and sensor boats so far front that the missiles can hit at the edge of my active detection, and scouts forming a line at that edge to check for incoming fire and smaller ships. The beam FAC will fly just behind this line, ready to charge at any enemy FAC trying to break through, or to chase enemy missile ships which ran out of ammo. Here come the schematics:

2,4m Rx: The 2,4m is a small type of sailing boat used in competition. Here, it’s a scout fighter, with the addition Rx to the name, with x being the sensor resolution. Three variants have been designed: the R1, R15 and R100:
Code: [Select]
2,4mR1 class Scout Fighter    500 tons     14 Crew     274.5 BP      TCS 10  TH 25  EM 0
5000 km/s     Armour 1-5     Shields 0-0     Sensors 1/1/0/0     Damage Control Rating 0     PPV 0
Maint Life 0 Years     MSP 0    AFR 100%    IFR 1.4%    1YR 114    5YR 1714    Max Repair 216 MSP
Intended Deployment Time: 3 months    Spare Berths 3   

FE 50 EP MagFusDrive(Sig50%) (1)    Power 50    Fuel Use 29.4%    Signature 25    Exp 10%
Fuel Capacity 50 000 Litres    Range 61.2 billion km   (141 days at full power)

Active Missile Search Sensor MR4.2-R1 (1)     GPS 216     Range 38.9m km    MCR 4.2m km    Resolution 1

This design is classed as a Fighter for production, combat and maintenance purposes

Bergumermeer: Named after the full name of the BM class sailing vessel, this is a PD gauss fighter. It’s unknown whether I’ll actually use it, as this would require a massive amount of carriers.
Code: [Select]
Bergumermeer class Point-Defense Fighter    500 tons     9 Crew     191 BP      TCS 10  TH 80  EM 0
16000 km/s     Armour 1-5     Shields 0-0     Sensors 1/1/0/0     Damage Control Rating 1     PPV 3
Maint Life 23.48 Years     MSP 239    AFR 2%    IFR 0%    1YR 1    5YR 12    Max Repair 120 MSP
Intended Deployment Time: 0.5 months    Spare Berths 3   

160 EP Inertial Fusion Drive (1)    Power 160    Fuel Use 50.31%    Signature 80    Exp 12%
Fuel Capacity 35 000 Litres    Range 25.0 billion km   (18 days at full power)

Gauss Cannon R3-50 (1x3)    Range 30 000km     TS: 16000 km/s     Accuracy Modifier 50%     RM 3    ROF 5        1 1 1 0 0 0 0 0 0 0
FTR Beam FC R32k TS20k (1)    Max Range: 64 000 km   TS: 20000 km/s     84 69 53 37 22 6 0 0 0 0

This design is classed as a Fighter for production, combat and maintenance purposes

Laser Pico: called after the Laser Pico sailing vessel, this is a laser equipped FAC:
Code: [Select]
Laser Pico class Fast Attack Craft    1 000 tons     19 Crew     371 BP      TCS 20  TH 100  EM 0
10000 km/s     Armour 4-8     Shields 0-0     Sensors 1/1/0/0     Damage Control Rating 0     PPV 8
Maint Life 3.58 Years     MSP 116    AFR 16%    IFR 0.2%    1YR 14    5YR 209    Max Repair 150 MSP
Intended Deployment Time: 0.5 months    Spare Berths 6   

FE 200 EP InertFusDrive(Sig 50%) (1)    Power 200    Fuel Use 49.79%    Signature 100    Exp 12%
Fuel Capacity 50 000 Litres    Range 18.1 billion km   (20 days at full power)

25cm C5 Far Ultraviolet Laser (1)    Range 64 000km     TS: 10000 km/s     Power 16-5     RM 5    ROF 20        16 16 16 16 16 13 0 0 0 0
Beam FC R32k TS10k (1)    Max Range: 64 000 km   TS: 10000 km/s     84 69 53 37 22 6 0 0 0 0
InertConFus Reactor  PB-1 P6 HS0.5 (1)     Total Power Output 6    Armour 0    Exp 5%

This design is classed as a Military Vessel for maintenance purposes

Schoener: Called after the big ships known in English as Schooners, this is the carrier supposed to take scouts to the battlefield:
Code: [Select]
Schoener class Carrier    30 000 tons     440 Crew     4111.4 BP      TCS 600  TH 2520  EM 0
4200 km/s    JR 6-500     Armour 4-86     Shields 0-0     Sensors 1/1/0/0     Damage Control Rating 20     PPV 0
Maint Life 0.07 Years     MSP 2043    AFR 14400%    IFR 200%    1YR 28746    5YR 431191    Max Repair 823 MSP
Intended Deployment Time: 60 months    Flight Crew Berths 190   
Hangar Deck Capacity 10000 tons     

J30k(6-500) Military Jump Drive     Max Ship Size 30000 tons    Distance 500k km     Squadron Size 6
840 EP Inertial Fusion Drive (3)    Power 840    Fuel Use 9.5%    Signature 840    Exp 7%
Fuel Capacity 4 950 000 Litres    Range 312.6 billion km   (861 days at full power)

This design is classed as a Military Vessel for maintenance purposes

« Last Edit: August 18, 2017, 01:12:15 PM by superstrijder15 »
 

 

Sitemap 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51