Author Topic: The Northern Coalition (AAR)  (Read 70120 times)

0 Members and 1 Guest are viewing this topic.

Offline Paul M (OP)

  • Vice Admiral
  • **********
  • P
  • Posts: 1438
  • Thanked: 63 times
Re: The Northern Coalition (AAR)
« Reply #60 on: February 26, 2013, 10:21:41 AM »
Interesting stuff, you have clearly put a lot more thought into your design considerations than I ever have!

Thank you.  I enjoy the building aspects of these games probably far more than the "blow stuff up" parts.  The problem for me at the moment is balancing "big picture" and "small picture" research priorities.  It just isn't clear to me how to set them.
 

Offline Paul M (OP)

  • Vice Admiral
  • **********
  • P
  • Posts: 1438
  • Thanked: 63 times
Re: The Northern Coalition (AAR)
« Reply #61 on: February 27, 2013, 09:28:01 AM »
AD 2277 (October 15)  2nd Battle of HIP 51317

Wolf 358

The ships of TG1 had been at the jump point to HIP 51317 for 10 days.  As the Navy had no idea what was going on in HIP 51317 they elected to be conservative.  This meant waiting for 10 days to give the ships trapped inside the system some more time to reach whatever waypoint they decided on.  Navy Intel was fairly certain the 3 ships would be waiting 140m km at a bearing of 330-350° from the jump point, from there it would take them 32 hours to travel to the jump point due to the speed of the Oberons.  Their worst case estimates put them nearly double that distance out.  Cpt. Morgenrot had divided his Task Group into 3 groups for the initial transit.  The missile frigates Bloodhound, Beagle and Airedale, the Guardian class Watchman and the two London Escorts Dorset and Cheshire would transit in the first wave.  The missile frigate Borsoi and the Guardian class Picket would follow in the second wave.  The three Edmonton class jump tenders Edmonton, Banff and Perryvale would carry the force through.  The Edmonton would remain on station and the Banff and Perryvale would jump back, with the Banff returning with the second wave of ships.  Three further Guardian class frigates and 3 Resupply ships would remain in Wolf 358.

(October 15) 01:15  HIP 51317 Jump Point to Wolf 358

One moment space was empty then at three points scattered around it 9 ships flashed into existance each surrounded by a corona of flickering lightning as potential energy bled away as photons and and arcing to the local space plasma.  Onboard the Bloodhound Cpt. Morgenrot's repeater station was blank as the ships passive sensors absorbed information bombarding the ship.  The false acceleration of the jump drive's wormhole left both humans nervous systems and electronics "disturbed."  He resisted the urge to call out for an update.
"Contact!  Two Thermal Contacts!"  The blood red blips appeared in his repearter, tenative ID was Tama class.  Range was approximately 1.5m km.  It was the best case of the Navy's worse case situation.  Limited numbers of Enemy ships deep in the NC Navy's missile envelope, and in this case inside the range of their Hawk's fired in AS mode.
"Sensor Pings.  Active sensors.  Positive ID is Tama class.  They have us localized."  His electronics was still recovering from the shock of transit.
"Targets are boosting, course is relative 82°."  They were moving away from the human ships.  "Velocity is 8379 km/s."   That was four times the speed of the ships in TG1 and twice the speed of their missiles.
"Sensors are up Sir.  We have them localized."
"Guns, target is Tama 2."  He keyed a switch.  "Command to Task Group.  Target is Tama 2.  Standbye to engage all launchers."  He glanced at the clock, the timer had started at 258 seconds and it was dropping.  The time was for the first possible missile impact from the Wolver's fire.
"Sir they are foxing our targetting same as the Hiyru's.  Can't lock them at this range with the Hawks."
"Sir, debrie fields!"  They began to appear on his repeater, three relatively large fields all near the last reported position of 3rd Squadron Battlegroup.  Then a pair of smaller ones further from the jump point but seperated by 90°.  Peter felt his blood run cold as his repeaters resolution auto changed.  Three more debrie fields were marked with 80% likelyhood of being human in origin.  The gamma and xrays emitted clearly came from neutron activated TN materials.  60m km from the jump point at 5° were 3 distinct fields of debries.
"Command to Task Group.  Mission abort.  All ships remain at jump-in position."
"Command to Airedale.  Dina you see those debrie fields?"
"Airdale to Command.  Yes.  What now?"
"We get as much tactical intel as we can on the Tama's and then jump out."
"Yes sir."  Both officers had known their only real chance of getting the trapped ships out safely had been if there had been no Wolvers on the jump point.

Peter stared at the plot thinking furiously.  The situation was different now, both better and worse for him.  Since he had no reason to stay in system and he had no desire to add to the losses the Navy had suffered in this system he wanted to be able to withdraw quickly.  That meant; however, he could not launch his pinnance and detach his escorts.  So he could not extend his missile detection envelope.  An action that he needed to do if he wanted a chance to stop the Wolver fire.  Luckily his arrival pattern had put the ships recently refit with the longer range antimissile sensors slightly closer to the enemy.

"Command to Task Group.  All ships assemble at jump point for jump.  Jump Tenders to spindle drives."

(October 15)  01:17
"Command to Task Group.  Stand by to Engage enemy with Javelins."  He switched the channel. "Guns fire when ready."
"Aye aye sir.  Firing now." The ships shudders as the missiles lauch booster shoves it down the tube.  "Beagle has launched.  Airedale has a computer problem."  [ooc]Actually I had a interface problem.  Hint: after refits ships will have their combat board reset, so no missiles were loaded on the Airedale.  Plus I had a hellish time getting ships to fire after hitting "Fleet Open Fire" eventually having to go through each ship individually and allocate fire and so on.  But this took a while.  Learning experience me.[/ooc]
"Sir.  Airedale reports computer problem solved."  The pair of missiles was trailed at 80000 km by a singleton.  The range to the enemy was now 3.6m km.  According to his tactical update the Tama's were the same size as the Hiyru's at approximately 8950 tons.  What remained a mystery was if they were armed.  Peter glanced at the timer; they would learn shortly.

(October 15) 01:18

"All ships standing by at jump point, Sir."
"Thank you."  His Task Group was now clustered around the jump point and he could leave inside of 60 seconds.  It was not an ideal fighting formation but it should mean the task group would not suffer ship losses.  His missiles were fruitlessly chasing the enemy who showed no sign of slowing down.

(October 15) 01:19

"Contact!  Vampire One!  Vampire Two!  Range 50k!"  Beagle and Bloodhound salvo 3 Hawks each at the inbound Wolver missiles.  
Moments later the target became clear as a missile detonated near the Airedale.  A large fraction of the plasma spume was deflected away by her shields as they collapsed and her armour weathered the brunt of the strike.  However, the spalling metal blocked her main launch tube as part of the bay doors buckled under the attack.  Cpt. Nimm orders her damage control teams to clear the damage but her main launcher is out of the action.

[ooc]Nordion Arbalist ASM Launch System destroyed on Airedale after receiving 1 points of damage. 4 Casualties.
Strength 9 Nuclear Detonation x1 detected![/ooc]

"Sir.  Airedale has lost her main tube."
Peter hit his arm rest in frustration.  No sense wasting fire.  "Command to Task Group.  Cease offensive fire."  He knew now that the Tama's were armed and their salvo's were apparently only a single missile from each ship.  He had as much information as he was going to get.  "Command to Task Group.  Make ready to jump."  Time to get out.

(October 15) 01:20

"Contact!  Vampire 3!  Vampire 4!  Range 60k km!"  Peter assumed the target was Airedale.  But for the first time the human's had detected the missile at a range outside of what the missile could easily cover before they could react.  Seimen's had earned their money for the Vigilant Plus counter missile sensor.  Watchman and Airedale salvo 3 Hawk's against each inbound missiles the other two ships counter missiles are still 5 seconds from being ready to fire.
"Dorset has engaged!  Cheshire reports malfunction in targetting array!"  Peter swore as the Wolvers much faster missiles avoided the Hawk's interception attempts and the Dorsets YAG laser fire at 10k km was ineffective.  [ooc]The Cheshire kept loosing its point defence setting...though eventually sufficient use of clear target eventually got it to accept the damn setting.[/ooc]  The Airedale's shields had barely started to reform before the missile expanding plasma wavefront hits.  The effect was much worse without the shield to blunt the blow; the ship shuddered and scewed in space under suddenly unbalanced thrust as one engine lost all control and fuel connection, cut off valves slamming shut to prevent fuel venting.  The electrical surge blew appart the recently installed equipment in the sensor room for the Counter Missile suite and chunks of spalling armour smashed parts of the ships living area cutting off several compartments.

[ooc]Crew Quarters destroyed on Airedale after receiving 1 points of damage. 0 Casualties.
Rolls Royce NP E-M40S destroyed on Airedale after receiving 2 points of damage. 2 Casualties
Seimens SCMS Vigilant Plus 51/4-0050 destroyed on Airedale after receiving 1 points of damage. 2 Casualties.
Strength 9 Nuclear Detonation x1 detected!
[/ooc]

Cpt. Morgenrot had no intention of loosing the Task Group's second in command.  "Command to Task Group.  All ships jump!"

While the Task Groups various ships computers talked to each other coordinating the ships exit from the system the enemies vollies continued to come in, one every 20 seconds.

"Vampire 5!  Vampire 6! Range 20 k km."  Just at the ships were slipping through the jump portals Hawk's and Wolver missiles passed through each other with the human counter missiles warheads always being several km too far distant as they detonated.  The Dorset's barbettes sprayed coherent light as the lasers Q-switches were triggered but the swift moving targets were illusive.  As proved the Airedale.  The ship flashing out of HIP 51317 local space mere moments before the missiles arrived at her location.  Unfortunately they then acquired the Watchman, stuck in the system due to a system glitch in her drive software.  [ooc]Due to a problem where a launched pinnace was not showing up as a seperate squadron on my squadron list but as part of the task group and I was getting a message that I didn't understand about 4 ships in the task group.  Vastly annoying![/ooc]

[ooc]
Fuel Storage destroyed on Watchman after receiving 1 points of damage. 0 Casualties.
Strength 9 Nuclear Detonation x1 detected!
[/ooc]

The Watchman's shields worked as intended reducing the intensity of the plasma shockwave.  Her plates buckled and one fuel storage cell burst spraying sorium fuel into space.  Her engineers worked to get rid of the Blue Screen of Death that was blocking her main thrusters from engaging but within 15 seconds her helm responded and 5 seconds later the last human ship group jumped clear of HIP 51317.  Three Javelin missiles remained but without targetting updates the missiles soon self destructed as their onboard thermal sensors found no targets near the last location they had for the Tama they were targeted on.

(October 16) 03:40  Bloodhound, On course for jump point to AD Leonis

"Captain, the Airedale reports they have completed all repairs they can make without a ship yard."
"Thank you."  The Task Group was making the full speed of the tankers and according to his supply officer they would not need to refuel as there was sufficient fuel on the three tankers to take them home.  They would arrive on November 27th.  This battle had brought the NC Navy some important information and lessons.  Their new missile sensor system was now battle proven to work.  Twice in the battle the human's defences had worked as intended with a mix of laser fire and counter missiles attempting to take down the inbound missiles, unsucessfully it is true but still it was a marked increase in effectiveness.  The task group had lost 12 crewmen and had two damaged ships but it represented the first time a human force had engaged the enemy and survived.  Albiet by running like rabbits...but it was clear until the Navy got a missile that moved at least 9000 km/s they could not engage the Wolvers in a battle with any expectation of hitting the enemy.  The puzzeling thing was the wrecks of the three ships the task group had come to rescue.  Cpt. Morgenrot had flagged that for extensive effort by Naval Intel.  
« Last Edit: February 28, 2013, 04:47:15 AM by Paul M »
 

Offline Paul M (OP)

  • Vice Admiral
  • **********
  • P
  • Posts: 1438
  • Thanked: 63 times
Re: The Northern Coalition (AAR)
« Reply #62 on: February 28, 2013, 07:30:46 AM »
[ooc]I will probably fold in the logistics with the next one as this update is more about the outcomes of the last battles for the emerging story.[/ooc]

AD 2277 December Sidestepping the Freight Train

The political crissis started by the loss of Hudson and Ericson had been put on slow boil during Operation Poet.  The ships docked at Earth on the 28th of November and the various power blocs took stock of their position.  The three trapped ships had been lost, but the Navy had not lost any ships in the attempt to recover them.  This was for the Government bad but not as bad as it could be.  Polls showed the, not unexpected, drops in both the popularity of the Government but also the Navy.  Due to strong market performance the NCC was relatively speaking untouched by this.  The UN, BuSurvey and the NCC negotiations got tougher due to yet more university losses and the UNs view hardened on what it considered sufficient improvement to allow its people to rejoin survey efforts.  

The Right Honorable PM Ron Getti had learned something from the last time and made his announcement of the results of Operation Poet as soon as possible on the 27th.  He also "accentuated the positive, such as there was, and downplayed to a cautious extent the negative"...the speach was not particularily well recieved due to the nature of the news it contained.  The Government had two years on its mandate but a non-confidence vote was voted by the members conscience and Getti knew there were back benchers in his party that were still upset over Beauchamp's resignation.  He could legally call an election...and thus define the timing.

The Official Opposition was also somewhat at odds with the fringe parties, due to the fact that on mature deliberation they realized that they had to be very careful about essentially shooting themselves in the foot should they win.  They could; however, call for a vote of confidence and, if enough of the government back benchers could be swayed over, they might bring down the government and trigger elections.  They just  needed an issue that would carry them through the campaign.  Operation Poet had failed, but the review boards were not producing tractionable material.    The economy of Sol was booming, and worse the latest shipment of TN materials from Faewald had caused a ripple in the markets.  Shipyards were in full production as well.  Accountability made good news, but the fact was FTL communication was impossible.  Keeping tabs on things going outside of Sol was, well, not easy.  Making a big deal about this would give any opposition they faced as the Government, should they win, basically a free cheap shot.  Worse the diversion of construction capacity to fort refits and new fort pre-fabrications was slowing down things like terraformers for Mars.  Mars had a population of 10% of Earth, and the Opposition had supported the re-priortization.  The Navy was no ones favorite organization at the moment but it also was clearly doing things.  It was hard to find a subject they could claim to be able to improve things on, outside of the removal of Frasier...and with the possibiltiy of either Morgenrot (considered politically a loose cannon) or worse Nimm (who was a noted orator) taking over; leaving well enough alone was a self evident winning strategy.

To put it mildly the top levels of the Government and Opposition were both unhappy, if for different reasons.  To the surprise of his advisors the PM wanted to call an election; he was talked out of it to the general relief of his cabinet.  The Opposition was upset to discover that they would probably have to vote for the government should one of the fringe parties start demanding a vote of no confidence.  This was something that went down not-at-all-well.  The Government hoped that time would smooth things over and that in 2 years they would face the election with a vastly different situation.  The Opposition, while it could find no issue to build a winnable election on, had a lot of general dissastifaction it didn't want to let go to waste.  Biding their time and hoping for a crisis that they could pounce on directly was, at least for the Official Opposition, seen as their best option.  This lent the fringe parties ammunition against both major power groups but that seemed unavoidable and nothing to worry about.  [ooc]If anyone has a suggestion for how the opposition should exploit this situation I'm all ears...but while the numbers in the Polls are low they didn't drop that much when the news was announced so both sides realize the situation has hit bottom.  The Government thinks they can only improve in poll results from this point and they can lay a lot of blame on previous administrations while claiming to have been ontop of this crisis.  But the opposition, and more to the point a good fraction of the more radical elements, are basically circling watching for blood.[/ooc]

The Naval Inquest over the HIP 51317 Incident

The Navy due to a lack of staff packs all incidents together into one and reviews it publically.  The fact that Cpt. Wells did not survive lends the part focussing on the loss of the Ericson a sense of anti-climax.  The true shocking part of the inquest was the analysis by a Lt. T.D. Shoe who discovered most likely "why" for the loss of the Sentinal Flottila.  His findings though caused a surge in popular discontent against the Navy and allowed the typical Raff and Riff of the interweb to speculate wildly on the Navy senior brasses parentage.  When Cpt. Morgenrot revealed that, had they found the Sentinal Flottila still in system, he would have ordered in all available ships, including the 3 Guardian's in the support groups, there was, putting it mildly: an inteweb stir.  This alone fixed his "loose cannon" reputaton in the eyes of most politicans.  The surprise for most; however, was both that the inquest moved relatively quickly and what its findings were.

Finding 1:  The board finds that Cpt. M. Wells battle plan was based on an incorrect assumption the Hiyru class was a short range combat vessel but finds nothing to indicate it was not a reasonable assumption to make given his knowledge at the time.  It is clear that he felt he could withdraw safely from the position he adpoted.  His disposition was also clearly intended to protect his jump tender.
Finding 2:  The board finds that Cpt. M. Wells mishandled parts of the battle by not detaching his escort and by sending his EW pinnance too far forward to effectively screen his force.
Finding 3:  The board finds that the tactical intellegence gathered by Cpt. M. Wells was of invaluable help to the Navy.
Finding 4:  The board finds that his order to the support group to jump from HIP 51317 was in the highest tradition of any military service.
Finding 5:  The board finds that there was a computer error in the evaluation of Wolver sensor ranges.  This error would result in a factor 2 to 3 underestimate in the range  of their sensors.  The board agrees with the conclusion put forth by Lt. T.D. Shoe that this was the most probable cause for the loss of the Sentinal Flotilla.
Finding 6:  The board finds that it has insufficient evidence to hold Lt. Cmdr. B. Byran responsible for the loss of the Sentinal, Copernicous or Kepler.  Based on the location of the wreckage the board finds the argument compelling that he would have believed himself outside the Wolver sensor reach.  Once localized his force would not have been able to stop a Wolver attack.
Finding 7:  The board finds that it supports Cpt. Morgenrot and Cpt. Nimm in their contention that the only chance to have recovered the Sentinal Flottila was for no Wolver ships to be present at the jump point.  Their contention that the Wolvers could have incercepted the inbound ships, was also supported by the increased sensor range they would have had.  The ships of Task Group 1 could not have prevented the Wolvers from intercepting the Sentinal Flotilla.    The board also finds compelling the contention by both Captains that the survival of Task Group 1 on the jump point for 30-60 hours was, even if they faced only the two Tama's, realistically unlikely.
Finding 8:  The board finds that it is in agreement with the assesment of the battle re-creation report that credits the Vigilant Plus CM sensor with the improved performance of the task group in combat.

Recommendation 1:  The board recommends that the highest priority be given to developing an anti-ship missile capable of catching a Wolver ship.  It also agrees with the assesment of both Captains Morgenrot and Nimm that such a system be field tested as soon as possible.  The improvement to the Hawk series of Counter Missiles can not be accomplished with existing technology and the board endorses the recommendation that a true upgrade to the Hawk series requires both the development of implosion warhead technology but also more advanced engines.
Recommendation 2:  That a specific probe ship be developed that mounts a EM array capable of detecting the Wolver sensors outside the range where the sensor can detect the ship.  The current EM arrays can not guarrentee this to be the case.  This means that even the George Vancouver class is incapable of being used as a probe ship.
Recommendation 3:  A clear priority in research be set that emphises improvements to the current offensive systems over the existing defences.  The development of the implosion fission warhead, improvements in turret tracking speed, longer ranged and faster firing lasers should be the short term research priorities of the Navy for new research effort.  Long term the board also endorses the previous findings that enhancing the Navy's sensor technology is a critical a branch of research.  The board recommends that the current emphisis on propulsion technology must not be hindered.
Recommendation 4:  That the Navy proceed with development of the Heavy Frigate and Destroyer classes based on current technologies.
Recommendation 5:  That further exploration efforts be concentrated where we know that no Wolver threat exists.

Cpt. Wells was both critized for his handling of the battlegroup and previous decisions but also lauded for his courage in battle.  Ensign Standish and the crew of the Überwachter became legendary on the interweb.  The Navy was stuck with the existing demand to update the forts of Earth and provide more point defence bases for Luna and Mars.  This put on hold their plans to expand their training facilities and most importantly the construcition of a Naval yard of two slips and the capacity to build ships of 3000 tons or less in size.   The NCC was persuaded to turn over lab space to the Javelin IIIA development and negotiations are ongoing over the development of enhanced passive EM sensors for the probe ship.  Given that without it the chances of loosing an exploration flottila has not decreased; it is unlikely the approval will not be given.  The overall public reception of this inquest was mixed, and if the polls for the Navy as an organization dropped people increasingly felt positive about Cpts. Morgenrot and Nimm.  If nothing else it gave the newsies much to comment on at the time when the Government and Opposition were relatively un-news worthy; both were eyeing the other to see which way the wind was blowing.

NCC Fuel Board

The NCC Fuel Board was pretty much unknown to anyone who wasn't a procurment officer in BIC or the NC Navy.  While the public "oohed and awed" over the newest Navy ship designs [ooc]or in the case of the Aurora Board public wondered what drugs I was on when designing them :) [/ooc] the response of the NCCFB was vastly different.  The mildest thing said when they first saw the Navy's proposals was: "Do they think we have a bloody fuel fairy hidden somewhere?"  The NCCFB had managed the fuel crisis and if from time to time in the past years fuel levels in Earth's farm had gotten low, at least they had avoided a total system collapse.  The yearly production at the moment was 3m l on Earth and ~1 m l outsystem in Alpha Centauri and AD Leonis.  A further ~2m l of fuel per year would be available from exisiting civillian harvesters.  BIC used 1.5m l per year for support of Faewald, that value would drop as around ~0.5m would be available in Alpha Centauri.  Doubling the number of harvesters in Alpha Centauri would cut the fuel demand on Earth's farm down to 0.8m l per year.  A new colony in Giesse 408 should be able to be sustained at the same cost if 2 FHGs were stationed at its minable gas giant.  Survey operations use about 0.6m l per year, leaving the military with 0.6 m l plus a further 1.2m l from AD Leonis.   In general for low tempo operations fuel was almost always an issue but it could be found.  Operation Poet had consumed well over 2 m l of fuel and had left the system struggling to cope but by defering fueling of the support groups the NCCFB had met the immediate needs without flat lining the farm.

Currently a squadron of frigates require 1.1m l of fuel to bunker completely.  A squadron of heavy frigates would require 3.3m l of fuel to bunker completely.  Each destroyer takes 0.6m l of fuel to bunker, which is the yearly output of a fuel harvester group.  Clearly to sustain operations of the new ships more FH Groups would be needed plus expansion of the existing system and most importantly increasing the output of refineries and enhancing fuel efficiency.  For this reason the NCCFB resisted the attempts of the Navy to raid its research labs.  They felt there was little value to warship that didn't have the fuel to leave the orbit of earth no matter how high tech its weapons.  A Navy fights on its fuel tank was their view.  
« Last Edit: February 28, 2013, 11:34:16 AM by Paul M »
 

Offline IanD

  • Registered
  • Commodore
  • **********
  • Posts: 725
  • Thanked: 20 times
Re: The Northern Coalition (AAR)
« Reply #63 on: February 28, 2013, 02:49:32 PM »
I am really enjoying the AAR. However your comment below may be a little misplaced. Have you looked at the RN Type 15 conversions? They were a pure A/S warship and could not have stood up to an attack by USSR aircraft or destroyers of the period but were never meant to, that's what the aircraft carriers were for ;D .
I understand this flys in the face of "gamer" optimization but I start from the assumption that this is real.  If you look at a modern small combat ship they all have a basic level of sensors.  It takes space yes but I find over specialized ships from a perspective of a real navy a bit absurd.

I fear the Northern Coalition Navy may have opted for the IR laser far too soon. I guess you went for the range?

A gauss cannon may have been more effective, firing once every 5sec, although shorter ranged, and can be turret mounted, and no reactor. The laser has three times the range but still only gets to fire once every 15 seconds.
Code: [Select]
Damage Output 1     Rate of Fire: 1 shots every 5 seconds     Range Modifier: 1
Max Range 10,000 km     Size: 3    HTK: 1
Cost: 6    Crew: 6
Materials Required: 6x Vendarite
This weapon has a penalty to accuracy. Chance to hit is multiplied by 0.5
Development Cost for Project: 60RP

Or even a rail gun, same short range but four shots to hit, disadvantage cannot be turret mounted but that's not really much of an issue at your current tech level. In addition you could have mounted two or three  for the same mass as the laser turret.

Code: [Select]
Damage Per Shot (4): 1     Rate of Fire: 15 seconds     Range Modifier: 1
Max Range 10,000 km     Railgun Size: 3 HS    Railgun HTK: 1
Power Requirement: 3    Power Recharge per 5 Secs: 1
Cost: 1    Crew: 9
Materials Required: 0.2x Duranium  0.2x Boronide  0.6x Neutronium

Development Cost for Project: 150RP

The Cheshire kept loosing its point defence setting...though eventually sufficient use of clear target eventually got it to accept the damn setting.

I have had the same problem, 6.21 is nowhere near as stable as 5.56  :(
« Last Edit: February 28, 2013, 03:33:16 PM by IanD »
IanD
 

Offline TheDeadlyShoe

  • Vice Admiral
  • **********
  • Posts: 1264
  • Thanked: 58 times
  • Dance Commander
Re: The Northern Coalition (AAR)
« Reply #64 on: February 28, 2013, 03:34:21 PM »
gauss cannon would actually be much less effective than the laser with only ROF1 tech.   

railguns would be more effective but only as long as NC beam fire controls are totally pants.  the lasers will be fine as soon as the NC can develop a better BFC. ;)

 

Offline Paul M (OP)

  • Vice Admiral
  • **********
  • P
  • Posts: 1438
  • Thanked: 63 times
Re: The Northern Coalition (AAR)
« Reply #65 on: February 28, 2013, 03:51:04 PM »
I am really enjoying the AAR. However your comment below may be a little misplaced. Have you looked at the RN Type 15 conversions? They were a pure A/S warship and could not have stood up to an attack by USSR aircraft or destroyers of the period but were never meant to, that's what the aircraft carriers were for ;D .
I fear the Northern Coalition Navy may have opted for the IR laser far too soon. I guess you went for the range?

A gauss cannon may have been more effective, firing once every 5sec, although shorter ranged, and can be turret mounted, and no reactor. The laser has three times the range but still only gets to fire once every 15 seconds.
Code: [Select]
Damage Output 1     Rate of Fire: 1 shots every 5 seconds     Range Modifier: 1
Max Range 10,000 km     Size: 3    HTK: 1
Cost: 6    Crew: 6
Materials Required: 6x Vendarite
This weapon has a penalty to accuracy. Chance to hit is multiplied by 0.5
Development Cost for Project: 60RP

Or even a rail gun, same short range but four shots to hit, disadvantage cannot be turret mounted but that's not really much of an issue at your current tech level. In addition you could have mounted two or three  for the same mass as the laser turret.

Code: [Select]
Damage Per Shot (4): 1     Rate of Fire: 15 seconds     Range Modifier: 1
Max Range 10,000 km     Railgun Size: 3 HS    Railgun HTK: 1
Power Requirement: 3    Power Recharge per 5 Secs: 1
Cost: 1    Crew: 9
Materials Required: 0.2x Duranium  0.2x Boronide  0.6x Neutronium

Development Cost for Project: 150RP

I'm glad you are enjoying it.  On the first comment, my main point was that navy ships today carry AS and SS radars, plus Radar Detectors and some form of IR system.    

As for the laser the reasoning for its use is based on the fact it is dual purpose (AS/AM) and thus more bang (or zap if you will) for the research buck not the range.  Because of the extreme limits on their research base at the time they never had an option to go for Guass Cannon or Rail Guns.  I also decided to do something different and not develop either as they seemed the "standard solution."  But that OOC thinking was largely trumped by the strong limitation of available research complexes.  

At the moment the Navy is stuck with the problem they are looking up a rather large technological hill and trying to decide what is realy the best way to go forward.   The Javelin IIIA (Assault) is a result of them looking for ways to exploit their existing systems to gain an advantage.  For the moment they just can't afford to branch out into different weapon systems.  The Navy is also in a period where the available lab space is about as small as it will ever be for them.  6 labs are tied up in researching fuel refining efficiency, 2 labs are researching advanced terraforming and this leaves the navy with 3 currently tied up in propulsion research.  As time goes on every other lab complex will be added directly to that Navy pool, with the other one boosting the CP research, while the 2 labs for terraforming are the 20% investment in "things that we need long term"...they did this with logistics and ground forces before.  It hurts the navy short term but is good overall for the NC economic base in the long term.
 

Offline IanD

  • Registered
  • Commodore
  • **********
  • Posts: 725
  • Thanked: 20 times
Re: The Northern Coalition (AAR)
« Reply #66 on: March 01, 2013, 02:33:44 AM »
gauss cannon would actually be much less effective than the laser with only ROF1 tech.  

The gauss cannon example above has ROF 1 tech and a Gauss Launch Velocity 1 tech, so its as basic as it can get and would still get 3 shots to an single IR laser's one, but with a third the range. The laser is a twin turret, but the gauss cannon could be twin turreted, or you might even be able to squeeze a triple in.

I'm glad you are enjoying it.  On the first comment, my main point was that navy ships today carry AS and SS radars, plus Radar Detectors and some form of IR system.  
No complaints with that, the Type 61 Aircraft direction frigate was primarily a radar platform, but still mounted 2x2 4.5" guns, Seacat, Squid and associated fire controls and sonars.
Looking forward to the next installment.
« Last Edit: March 01, 2013, 02:39:12 AM by IanD »
IanD
 

Offline Paul M (OP)

  • Vice Admiral
  • **********
  • P
  • Posts: 1438
  • Thanked: 63 times
Re: The Northern Coalition (AAR)
« Reply #67 on: March 01, 2013, 05:21:19 AM »
The laser turret is actually a single laser in the turret.  There are just two of them on the Lake class corvettes.  I have to admit what sort of bothers me when I look at my combat results is that when 3 counter missiles engage a missile I see results from each missile (#1 missed, #2 missed, #3 missed) but when the London's fire I just see "missed" yet the London's mount two laser systems.  I assume it takes two shots but I can't confirm this is happening.

Also it isn't a question of if the Guass Cannon and or Rail Gun would be better.  The laser is used because of: limited research options and it being dual purpose.  The combination of Rail Guns and Guass Cannon are more research intensive than continuing down the path of lasers.  I won't say "never" but at the moment convincing anyone in the Navy to go for an untested weapon system as opposed to any of a dozen other things they need desperately would stand the same chance of getting approved as the idea of adopting skintight spandex for their shipboard uniforms (sorry to all seven of nine fans* out there but Diana Nimm's uniform is much more akin to a pilots flight suit than anything remotely stripperific).

I freely admit the only reason I watched Voyager was 7of9 myself...
 

Offline Paul M (OP)

  • Vice Admiral
  • **********
  • P
  • Posts: 1438
  • Thanked: 63 times
Re: The Northern Coalition (AAR)
« Reply #68 on: March 03, 2013, 04:04:45 PM »
[ooc]This is a largely logistics update.  Another "battle" is in the offing...in game time it will start in 15 min or so but I wanted to get the rest of the stuff caught up.[/ooc]

AD 2277 (December) to 2278 (August)

The NCCFB had its hands full juggling the fuel situation from December to April.  The farm went into a Critical state (<500k l) and then plunged down to Extremely Critical (<100k l).  The NCCFB was able to keep it from flatlining completely only by tapping into the fuel on the two tankers Husky and Petrocan, and refueling them from civillian harvesters at Jupiter.   The situation arose out of both Operation Poet's large fuel demands but also several ships completing construction in a short time period and the arrival of a near empty ICG from Faewald.  However, by the spring of 2278 the fuel farm was out of a critical state.  It was interesting that at the time Earth was struggling to meet high priority fuel needs Forge's farm contained over 1m l of fuel.

After the Navy's needs were met by raiding again the NCCFBs research resources to produce a dedicated long range EM array the NCC put its foot down.  The situation that had arrisen over the last months indicated that the research could not be indefinitly postponed by a death of a thousand "quick" projects.  But the Navy was satisfied they had gotten two critical projects completed and Cpt. Morgenrot was granted permission to plan a raid into HIP 51317 for the purpose of field testing the new Javelin missiles.  Construction of the missiles plus the state of the fuel farm delayed the start of the operation until the summer. 


Earth's Industrial Efforts

Missiles/Fighters (The fighter production is pretty much ongoing as the new forts will require pinnaces but missiles are built depending on the state of the stockpile)

AD 2277 (June 25) Construction of Javelin III Anti-Ship Missile completed
AD 2277 (July 15) Construction of Hawk II Counter Missile completed
AD 2278 (May 20) Construction of Javelin IIIA Anti-ship Missile completed; sufficient are produced for operation Riposte and a slight reserve on Earth.
AD 2278 (June 5) Construction of Hawk II Counter Missile completed

AD 2277 (June 30) Fairmile B2(EW) 006 is built
AD 2277 (November 20) Fairmile B2(EW) 007 is built
AD 2277 (December 19) 8 Fairmile A(EW) pinnances are scrapped
AD 2278 (April 10) Fairmile B2(EW) 008 is built and work on Fairmile B2(EW) 009 is started

Primary Industrial Efforts (Big ticket items are generally split by a number of smaller work packages of useful infrastructure)

AD 2277 (July 20) Construction of Deep Space Tracking Station completed
AD 2277 (August  5) Construction of two Maintenance Facilities completed, now ships up to 4000 tons can be maintained
AD 2278 (January 8 ) Construction of Refit of Fort Detroit to the Fort Rostock class PDC is completed
AD 2278 (February 20) Construction of three Maintenance Facilities completed, now ships up to 4600 tons can be maintained
AD 2278 (March 20) Construction of a pair of Deep Space Tracking Stations is completed, one will be transported to Faewald.
AD 2278 (May 15) Construction of a new Terraforming Installation for Mars is completed and construction of a new research complex is started.

Secondary Industrial Efforts (aimed at the conversion of existing mines, construction of infrastructure for BIC and new fuel refineries)

AD 2277 (August 10) A Mine is converted to robot/teleoperated control
AD 2277 (September 23) Construction of 24 units of Infrastructure completed
AD 2277 (December 30) Construction of a Fuel Refinery completed
AD 2278 (February 10) Construction of 24 units of Infrastructure completed
AD 2278 (June 15) A Mine is converted to robot/teleoperated control
AD 2278 (July 25) Construction of 24 units Infrastructure completed and construction of a new Fuel Refinery is begun


Northern Coalition Army

AD 2278 (February 30) The "Fighting Second" Bn completes advanced infantry training and the graduating soldiers are soon replaced by the raw recruites that will for the "Sightseeing Sixth" Bn.


BIC Operations in Alpha Centauri

Over the year from July 2277 to July 2278 the construction factories on Faewald turn out enough infrastructure for nearly an extra 40,000 colonists [ooc]Infrastructure x11[/ooc].  Based on the performance of the colony and its rate of growth BIC intends to expand its mining sector to a total of 15 mines (currently 13) and then build its industrial base to 5 factories (currently at 2).  From the July 8th, 2277 til June 2278 the crews of the three ships of FHG I (1 Loch and 2 Petrol class harvesters) work at Alpha Centauri 5 to refine fuel.  With their tanks nearly full the three ships return to Faewald and add 680k l of fuel to the colonies tank farm bring it up to 730k l.  Sufficient fuel for two ICGs refueling needs.  In that same time period 3 ICGs arrive at Faewald: ICG I on July 29, 2277 (departing on August 20), ICG II on November 11, 2277 (departing November 30), and ICG III on February 15, 2278 (departing March 5).  The colony grows from around ~950,000 to just below 1.1 million over the year, taking it from slighly below Ganymede to decively larger.  BIC plans to send at least one large infrastructure delivery on a yearly basis.


BIC Operations in AD Leonis

ICG V makes 3 trips to Forge over the time period, transfering 3000 new colonists, the equipment to set up a second automated mine and a large quantity of building materials for the colony expansion.  As part of Operation RIPOSTE on July 7, 2278 Mr. Þórhallr Hægwinson the new colonial governor from the NCC is dropped off by the Pious Antonius during refueling operations.  The tank farm at the colony is constantly filled by the FHGs stationed in the system and reaches a maximum of around 1.3m l of fuel.  After refueling both the Pious Antonius and the Paul Bunyon as part of Operation Riposte the farm still has 700k fuel remaining.  ICG V is currently on the way back to Earth to pick up more infrastructure and a load of colonists.  FHG II and FHG III are onstation at the nearby gas giant but FHG II will this month start back for Earth as its crew have been deployed currently for 21 months, FHG III will remain for another 5 months and will put around 300k l fuel into the tanks at Forge before it leaves for Earth.  FHG IV and V are in Sol currently.  FHG III and IV are full sized groups with 1 Loch and 2 Petrols.


Research Efforts

AD 2277 (July 20) Dr. Morgan Fowler's team has develops the plans for the Seimens SCMS Vigilant Plus 51/4-0050 and immediatly starts working on the heavy frigate version (Seimens SCMS Extra Vigilant 52/3-0050).  The system is immediately incorporated into the Terrier 1.3 series of refits.
AD 2277 (September 13) Dr. Morgan Fowler's team completes the Seimens SCMS Extra Vigilant 52/3-0050 and begins work on the destroyer versions (Seimens SCMS Super Vigilant 53/3-0050)
AD 2277 (November 5) Dr. Kevin Schmitz joins the NCC scientific establishment.  His Research specialization is defensive systems.
AD 2277 (November 25) Dr. Morgan Fowler's team completes the plans for the Seimens SCMS Super Vigilant 53/3-0050.  The lab resources are returned to Dr. C. Rowley working on fuel refinery efficiency improvements.
AD 2277 (December 10) Dr. Stephanie Rees joins the NCC scientific establishment.  Her speciality is Power and Propulsion technology and she is immediatly assigned to head up the development of the Alpha series of jump engines.
AD 2277 (December 25) Dr. Stephanie Rees team completes the plans for the Saab JA3-90 a few days before the original planned delievery date and starts to work on the destroyer sized version with Saab engineers (Saab JA3-180).
AD 2278 (May 15) Dr. Kevin Schmitz completes the development of the Bell Phased Array P5-25 and returns the borrowed labs to Dr. C. Rowley working on fuel refinery efficiency improvements.



Civillian Operations in Sol

AD 2277 (June 20) Burns Freight and Logistics has launched a new Burns H2 class Fuel Harvester
AD 2277 (July 20) The civilian mining colony on Encke has been expanded to 10 civilian mining complexes
AD 2277 (August 5) The civilian mining colony on Haumea has been expanded to 6 civilian mining complexes
AD 2278 (January 25) The civilian mining colony on Haumea has been expanded to 7 civilian mining complexes
AD 2278 (April 5) The civilian mining colony on 2004 NT33 has been expanded to 5 civilian mining complexes
AD 2278 (July 20) Burns Freight and Logistics has launched a new Burns H2 class Fuel Harvester


Civillian Yard: Litton-Ingalls Ship Building Corp., Sol

AD 2277 (June 20) Emerald and Diamond are refit to the Bauxite Long Range (HP) class
AD 2278 (January ) Mithril and Obsidian, two new Bauxite Long Range (HP) class freighters, complete construction
AD 2278 (April 20) Garnet and Iridium are refit to the Bauxite Long Range (HP) class.  They are the last of the original series that needed to be refit.  All ICGs are capable of 334 km/s now.

Civillian Yard: Robert Napier & Sons, Sol

AD 2277 (September 7) Hi-Octane, Petrol (HP) class, is built
AD 2278 (March 10) Disel, Petrol (HP) class, is built
AD 2278 (June 30) Gasolin, Petrol (HP) class, is built

Navy Yard: Victorias Esquimalt Graving Dock, Sol

AD 2277 (June 20) Perryvale (Edmonton Mod1.2 class) and Paul Bunyon (Protecteur Mod2.2 class) have the damage they recieved in the battle in HIP 51317 repaired.
AD 2277 (July 25) Retooling for the Terrier Mod1.3 flight of frigates completed
AD 2277 (August 5) Airedale, and Borsoi are refit to the latest Terrier Mod1.3 class in preparation of Operation POET
AD 2277 (August 10) Dorset completes refit to the London Mod1.3 class for Operation POET
AD 2277 (November 30) Watchman (Guardian Mod1.1 class) and Airedale (Terrier Mod1.3 class) have the damage they sustained in Operation POET repaired.
AD 2277 (December 10) Picket (Guardian Mod1.2 class) finishes refit
AD 2277 (December 15) Bloodhound and Beagle are refit to the latest Terrier Mod1.3 standard
AD 2277 (December 25) Watchman (Guardian Mod1.2 class) finishes refit
AD 2277 (December 30) Guardian (Guardian Mod1.2 class) and Cheshire (London Mod1.3 class) are refit to the latest standards.
AD 2278 (January 20) Sentry and Warder are refit to the Guardian Mod1.2 standard
AD 2278 (January 30) Shetland (London Mod1.2 class) finishes construction and enters refit
AD 2278 (February 15) Shetland (London Mod1.3 class) completes the refit to the newest standard.
AD 2278 (March 5) Mastiff and Foxhound the two replacement Terrier Mod1.2 class ships finish construction and then immediately enter into refit
AD 2278 (March 20) Foxhound Mastiff are refit to the latest Terrier Mod1.3 standrd
AD 2278 (July 13) Retooling for George Vancouver class completed the SV Thor Hyerdal and SV John Franklin enter the yards to be refit while the SS George Vancouver and SS James Cook are laid down.  The refits to the Amundson class science vessels are so extensive that they will be completed only a month or so before the new builds.  A few days later the yard starts re-tooling for the Scout class.

Code: [Select]
Scout class Scout    3,000 tons     85 Crew     503.7 BP      TCS 60  TH 63  EM 0
1400 km/s     Armour 1-18     Shields 0-0     Sensors 15/25/0/2     Damage Control Rating 3     PPV 2
Maint Life 9.34 Years     MSP 315    AFR 24%    IFR 0.3%    1YR 7    5YR 98    Max Repair 100 MSP
Intended Deployment Time: 24 months    Spare Berths 1   
Magazine 12   

Rolls Royce NP E-M28S (3)    Power 28    Fuel Use 31.16%    Signature 21    Exp 7%
Fuel Capacity 200,000 Litres    Range 38.5 billion km   (318 days at full power)

Nordion Buckler CM Launch System (2)    Missile Size 1    Rate of Fire 30
Grumman SCMFC 52-50 (1)     Range 3.0m km    Resolution 1
Hawk II Counter Missile (12)  Speed: 4,000 km/s   End: 21m    Range: 5.1m km   WH: 1    Size: 1    TH: 25 / 15 / 7

Seimens SCMS Vigilant Plus 51/4-0050 (1)     GPS 14     Range 700k km    Resolution 1
Seimens SSS 53-3000 (1)     GPS 1800     Range 11.6m km    Resolution 60
NorTEL IR Array 0-3 (1)     Sensitivity 15     Detect Sig Strength 1000:  15m km
Bell Phased Array P5-25 (1)     Sensitivity 25     Detect Sig Strength 1000:  25m km
Geological Survey Sensors (2)   2 Survey Points Per Hour

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

The Scout is the dedicated probe ship for BuSuvery.  It is a sister ship to the George Vancouver and has the same range, endurance and weapons package.  It is also capable of system body surveys to assist the Vancouver class once the probe is completed.  The ship carries the Bell P5-25 phased array capable of detecting a Hiryu at over 100m km.  This is several million km outside the extrapolated sensor range of the Hiryu.  Against any other known Wolver sensor the ship will pick up considerbably beyond the sensors range.   The ship is thus capable of performing a probe of a new systems bodies with a high chance of detecting the enemy at a range beyond where it can be seen.  It suffers from the same overall range limitation as does the Vancouver but improvements in engine technology will benefit both classes.

Navy Yard: Deschimag A.G. Weser, Sol

AD 2277 (September 13) Ceylon (Ceylon class) is built
AD 2278 (February 15) Hong Kong (Ceylon class) is built
AD 2278 (July 20) Singapore (Ceylon class) is completed.  The yard is in the process of retooling for the Tribal class destroyer.



Operation RIPOSTE

Commander:  Cpt. P. Morgenrot
Objective:  test effectiveness of the Javelin IIIA weapon system and gain tactical intellegence on the Wolver ships
Location:  HIP 51317
Forces:  2nd Squadron TG1 (12 Javelin IIIA+6 Javelin IIIA on RS)
             3rd Squadron TG1 (12 Javelin IIIA+6 Javelin IIIA on RS)


Enemy Forces (suspected): Two Tama Class Wolver vessels are likely to be near the jump point.  3 Hiyru class Wolver vessels are known to be in system and presumed to be available as reinforcements.

Operations Plan:  TG1(-) will proceed to jump point to lalande 21185 in AD Leonis.  The two tankers will be dispached to Forge to refuel.  After the tankers rejoin the task group it will proceed to Wolf 358 and the jump point to HIP 51317.  An Assault force composed of the 4 Terrier class frigates and the two jump tenders will be formed.  That force will enter into HIP 51317.  It will reform on the jump point and when Wolver ships are localized fire a single Javelin IIIA from each frigate.  The assault force will remain in system long enough to evaluate the missiles performance and then jump out.  Based on the situation the option to return is under local TG CO discretion.

Note:  NC Naval vessels are to remain near to the Jump Point and are not to pursue the Wolver ships.


TG1(-) Movement:

AD 2278 (June 19) TG1(-) leaves Earth orbit for jump point to Lalande 21185
AD 2278 (June 23) TG1(-) enters the Lalande 21185 system and sets course for the jump point to AD Leonis
AD 2278 (July 7) TG1(-) enters the AD Leonis system and dispatches the RS Pious Antonius and RS Paul Bunyon to Forge, the remainder of the TG stays at the jump point to Lalande 21185
AD 2278 (July 10) Both RSs arrive at Forge.  The RS Pious Antonius drops off Civilian Administrator Þórhallr Hægwinson.  Refueling of the two ships commences.
AD 2278 (July 13) The two RS vessels rendevous with the task group.  TG1(-) sets course for the jump point to Wolf 358.
AD 2278 (July 23) TG1(-) enters Wolf 358 and sets course for the jump point to HIP 51317
AD 2278 (August 11) TG1(-) arrives at jump point to HIP 51317 and starts to re-organize for the planned operation
« Last Edit: March 04, 2013, 02:30:43 AM by Paul M »
 

Offline Stardust

  • Warrant Officer, Class 1
  • *****
  • S
  • Posts: 84
  • Thanked: 2 times
Re: The Northern Coalition (AAR)
« Reply #69 on: March 06, 2013, 06:33:28 AM »
Thoroughly enjoying this.  Thanks Paul M.
 

Offline Paul M (OP)

  • Vice Admiral
  • **********
  • P
  • Posts: 1438
  • Thanked: 63 times
Re: The Northern Coalition (AAR)
« Reply #70 on: March 06, 2013, 07:48:02 AM »
Thoroughly enjoying this.  Thanks Paul M.

Your welcome.  Thank you for stopping by and saying so.
 

Offline Rastaman

  • Azhanti High Lightning
  • Sub-Lieutenant
  • ******
  • R
  • Posts: 144
  • Thanked: 8 times
Re: The Northern Coalition (AAR)
« Reply #71 on: March 06, 2013, 04:15:51 PM »
Very good read. From very humble beginnings, a civilization is born, bock by friggen block.
Fun Fact: The minimum engine power of any ship engine in Aurora C# is 0.01. The maximum is 120000!
 

Offline Paul M (OP)

  • Vice Admiral
  • **********
  • P
  • Posts: 1438
  • Thanked: 63 times
Re: The Northern Coalition (AAR)
« Reply #72 on: March 07, 2013, 03:42:13 AM »
Very good read. From very humble beginnings, a civilization is born, bock by friggen block.

I'm glad you are enjoying it, the next update will probably be friday or the weekend as I have to do a lot of short in game time turns.  Block by block on the backs of the CMCs...they were my salvation as they currently have 300 or so mines feeding the beast.  Their fuel harvesters are getting routinely slurped down to the level of dregs.  As things stand slightly over 40% of the total budget is paying for civillian minerals.  But currently stuff is getting built that say 10 years back in game time would have caused ROFL in any meeting it was suggested that they would be built.  The single biggest nightmare is fuel; the last few game months proved that I have it under control but I am skating on thin ice.

One other thing that I have noticed is that my internal economy could be far better but I have too much overlap between what Earth produces and what the colonies produce.  Venus for example produces 50 tons of precious metals...but Earth produces 2000 tons.  This limits the amount of money that can be made shipping stuff around.  It would be good if Io and Ganymede get a bit better luck in terms of what their import/export needs are.
 

Offline Conscript Gary

  • Lt. Commander
  • ********
  • Posts: 292
  • Thanked: 27 times
Re: The Northern Coalition (AAR)
« Reply #73 on: March 07, 2013, 04:19:21 AM »
Remind me, have you put any research towards ion drives yet? Starting from bare nuclear pulse tech they and some minimum power modifier tech cost as much RP as going from the base fuel consumption tech to 0.6 L/EPH. The latter will give you fuel savings across the board, but with improved drive technology you can exchange the speed boost for a lowered power modifier on your commercial vessels. Going from x0.5 to x0.35 will still give you a miniscule speed boost, but it'll more than halve their fuel consumption, not to mention the innate speed boost for the navy. Or considering the dismal speed of some of your commercial fleet you could split some of the difference. Also not to mention that more modern engines means better missiles. You know where the real fuel-guzzlers are in your fleet better than I, and you are strapped for labs, but something to think about.
 

Offline Paul M (OP)

  • Vice Admiral
  • **********
  • P
  • Posts: 1438
  • Thanked: 63 times
Re: The Northern Coalition (AAR)
« Reply #74 on: March 07, 2013, 05:13:40 AM »
I wish to agressively push engine technology as over all, as you point out it, gives an a massive bang on the research buck.  The current plan is: develop 1.5x multiplier technology (under way), and while that is going on develop the jump engines I need for the next generation of ships (under way), then get 0.6 fuel efficiency technology and better capacitors.  Develop a series of engines that use the higher fuel efficiency and also a new series of missile engines that are both smaller to allow more optimization in missile designs and with a higher multiplier.

After this though the emphisis will change to other fields that have been somewhat neglected, once a basic round of improvements to weapons, defences, and maybe if I get a scientist that can do it sensors is completed the priority goes back to better engines.  I got lucky in that the new P&P scientist is 25% so she is a girl genious when it comes to engines.  What threw a kink in stuff was the retirement of my first gen scientists as they all were like 60% in their specialties...and replacing a 60% researcher with 10% or 20% researcher is a massive change.

Also the slow but steady increase in research complexes will do a lot to help the sitauation out.  2 years from now the reasearch situation will be markedly better.  The current time is the worst it can be as far as the Navy'd dedicated research situation is concerned.

Fuel guzzlers at the moment are the ICGs, each take 750,000 l to fuel.  But when the new navy ships come into play ...a single DD takes 600,000 litres and a heavy frigate 350,000 l.  They will stress the fuel system something fierce.

I'm keen to get the better engines though.  It would make colonization far less painful but on the other hand the current relatively slow speed means the fuel load of the ships is spread out over a long time.  In that sense the slow speed is "helpful." 

Thanks for the comment better engines are a priority.  I don't know that I can reduce the power of the commerical engines any more without investing in tech to allow that.  But it is an interesting idea.  If you look at the design for the scout you will see it is using the efficiency military engine (75% power) and that makes a massive difference in range as its fuel efficiency is more than a factor of 2 greater than the regular military engine.  I use it on my support ships and survey vessels.  I am thinking about making a larger version of each engine as well as a 10 HS engine is 5% more fuel efficient than 2x5 HS engines.

As fuel is so critical I throw resources at it to get it from every different direction.  And it is still skating on thin ice...