Author Topic: How Will C# Effect Carriers?  (Read 11777 times)

0 Members and 1 Guest are viewing this topic.

Offline Desdinova

  • Lt. Commander
  • ********
  • D
  • Posts: 280
  • Thanked: 280 times
Re: How Will C# Effect Carriers?
« Reply #30 on: August 06, 2019, 06:57:27 PM »
Being able to operate separate task forces was a luxury made possible by American numerical superiority. And ships operated in separate groups/squadrons because before computers, an admiral commanded a battle from the bridge - if you depend on being able to look out and see what's going on in order to give orders, there's a limit to how many ships you can command effectively. If you want a real world example of how splitting your force can backfire spectacularly, look at what happened to the Japanese at the battle of Leyte gulf.

Another thing, that no one mentioned yet, is that wars in Aurora are highly linear. It seems like there's usually only one jump point in or out of enemy territory; once you know the jump point route to the enemy, the most effective defense is to concentrate everything you have on that jump point. If you want to make things like separate task groups and diversionary attacks viable, the number of interconnections between systems needs to be boosted again so the Galaxy map is less linear.
 

Offline Jorgen_CAB

  • Admiral of the Fleet
  • ***********
  • J
  • Posts: 2837
  • Thanked: 673 times
Re: How Will C# Effect Carriers?
« Reply #31 on: August 06, 2019, 08:07:46 PM »
Being able to operate separate task forces was a luxury made possible by American numerical superiority. And ships operated in separate groups/squadrons because before computers, an admiral commanded a battle from the bridge - if you depend on being able to look out and see what's going on in order to give orders, there's a limit to how many ships you can command effectively. If you want a real world example of how splitting your force can backfire spectacularly, look at what happened to the Japanese at the battle of Leyte gulf.

Another thing, that no one mentioned yet, is that wars in Aurora are highly linear. It seems like there's usually only one jump point in or out of enemy territory; once you know the jump point route to the enemy, the most effective defense is to concentrate everything you have on that jump point. If you want to make things like separate task groups and diversionary attacks viable, the number of interconnections between systems needs to be boosted again so the Galaxy map is less linear.

Everyone did this in WW2, not just the Americans. Also, the Japanese did not loose the battle of Layette Gulf because they had many battle groups (as did the Americans too), they simply were outmatched to begin with.

Fleets operate like this today as well and computers have very little to do with it, real world political and military goals and needs does. The real world are way more complex than any game can even hope to simulate. You could try a game like Command modern Air/Naval combat to understand how modern fleets actually operate and why they deploy in task-forces.

I do agree in some sense that jump points can make wars quite linear as there are only one possible approach. But that might certainly not be true if you play with a multi-faction Earth start though. You can also have potential enemies in more than one front and you never know when and if these enemies work together or not.

In any way... no one would ever be in their right mind in the real world to pool all their ships in a fleet in one giant fleet and head out to sea, there are many reason for why this is a bad idea.

If the game can make more realistic strategies viable with changes to some of the mechanics this is a good thing and carriers certainly will play an important roll in this. Or basically any ship with a hangar... you don't need dedicated carriers to use fighters and FAC effectively.
 

Offline Desdinova

  • Lt. Commander
  • ********
  • D
  • Posts: 280
  • Thanked: 280 times
Re: How Will C# Effect Carriers?
« Reply #32 on: August 06, 2019, 08:50:25 PM »
Being able to operate separate task forces was a luxury made possible by American numerical superiority. And ships operated in separate groups/squadrons because before computers, an admiral commanded a battle from the bridge - if you depend on being able to look out and see what's going on in order to give orders, there's a limit to how many ships you can command effectively. If you want a real world example of how splitting your force can backfire spectacularly, look at what happened to the Japanese at the battle of Leyte gulf.

Another thing, that no one mentioned yet, is that wars in Aurora are highly linear. It seems like there's usually only one jump point in or out of enemy territory; once you know the jump point route to the enemy, the most effective defense is to concentrate everything you have on that jump point. If you want to make things like separate task groups and diversionary attacks viable, the number of interconnections between systems needs to be boosted again so the Galaxy map is less linear.

Everyone did this in WW2, not just the Americans. Also, the Japanese did not loose the battle of Layette Gulf because they had many battle groups (as did the Americans too), they simply were outmatched to begin with.

They were never going to win, but they didn't do themselves any favors by sending all their carriers off to die alone as a diversion, and splitting their battleships and basically throwing two of them away.

Quote
Fleets operate like this today as well and computers have very little to do with it, real world political and military goals and needs does. The real world are way more complex than any game can even hope to simulate. You could try a game like Command modern Air/Naval combat to understand how modern fleets actually operate and why they deploy in task-forces.

I've played it. I also have real-world military experience.

Quote
I do agree in some sense that jump points can make wars quite linear as there are only one possible approach. But that might certainly not be true if you play with a multi-faction Earth start though. You can also have potential enemies in more than one front and you never know when and if these enemies work together or not.

In any way... no one would ever be in their right mind in the real world to pool all their ships in a fleet in one giant fleet and head out to sea, there are many reason for why this is a bad idea.
Except that this was standard practice from ancient times, through the age of sail, into the Russo-Japanese War and World War I. Ships of the line, all the way into the dreadnought era, would operate in the largest formations possible whenever possible, with frigates and eventually cruisers delegated for colonial defense, commerce raiding and protection, screening the battleline, and scouting duties.

The only good reasons to divide your forces are: you're fighting on multiple fronts; something (like a supply depot or jump point) absolutely must be defended; some of your ships are too slow or obsolete to operate with the main force; some of your ships are unready due to training/maintenance/fuel/ordnance levels.

Quote
If the game can make more realistic strategies viable with changes to some of the mechanics this is a good thing and carriers certainly will play an important roll in this. Or basically any ship with a hangar... you don't need dedicated carriers to use fighters and FAC effectively.
The game doesn't represent reality, but a hypothetical simulation of superscience space warfare. An effective strategy within the game is by default "realistic" in the sense that, if somehow the laws of physics changed to match trans-Newtonian physics as depicted in Aurora, the same strategies would emerge, because people do what works. You're not asking for more "realistic" tactics, but more "interesting" tactics.
« Last Edit: August 06, 2019, 08:54:47 PM by Desdinova »
 

Offline Jorgen_CAB

  • Admiral of the Fleet
  • ***********
  • J
  • Posts: 2837
  • Thanked: 673 times
Re: How Will C# Effect Carriers?
« Reply #33 on: August 07, 2019, 05:46:28 AM »
Being able to operate separate task forces was a luxury made possible by American numerical superiority. And ships operated in separate groups/squadrons because before computers, an admiral commanded a battle from the bridge - if you depend on being able to look out and see what's going on in order to give orders, there's a limit to how many ships you can command effectively. If you want a real world example of how splitting your force can backfire spectacularly, look at what happened to the Japanese at the battle of Leyte gulf.

Another thing, that no one mentioned yet, is that wars in Aurora are highly linear. It seems like there's usually only one jump point in or out of enemy territory; once you know the jump point route to the enemy, the most effective defense is to concentrate everything you have on that jump point. If you want to make things like separate task groups and diversionary attacks viable, the number of interconnections between systems needs to be boosted again so the Galaxy map is less linear.

Everyone did this in WW2, not just the Americans. Also, the Japanese did not loose the battle of Layette Gulf because they had many battle groups (as did the Americans too), they simply were outmatched to begin with.

They were never going to win, but they didn't do themselves any favors by sending all their carriers off to die alone as a diversion, and splitting their battleships and basically throwing two of them away.

Quote
Fleets operate like this today as well and computers have very little to do with it, real world political and military goals and needs does. The real world are way more complex than any game can even hope to simulate. You could try a game like Command modern Air/Naval combat to understand how modern fleets actually operate and why they deploy in task-forces.

I've played it. I also have real-world military experience.

Quote
I do agree in some sense that jump points can make wars quite linear as there are only one possible approach. But that might certainly not be true if you play with a multi-faction Earth start though. You can also have potential enemies in more than one front and you never know when and if these enemies work together or not.

In any way... no one would ever be in their right mind in the real world to pool all their ships in a fleet in one giant fleet and head out to sea, there are many reason for why this is a bad idea.
Except that this was standard practice from ancient times, through the age of sail, into the Russo-Japanese War and World War I. Ships of the line, all the way into the dreadnought era, would operate in the largest formations possible whenever possible, with frigates and eventually cruisers delegated for colonial defense, commerce raiding and protection, screening the battleline, and scouting duties.

The only good reasons to divide your forces are: you're fighting on multiple fronts; something (like a supply depot or jump point) absolutely must be defended; some of your ships are too slow or obsolete to operate with the main force; some of your ships are unready due to training/maintenance/fuel/ordnance levels.

Quote
If the game can make more realistic strategies viable with changes to some of the mechanics this is a good thing and carriers certainly will play an important roll in this. Or basically any ship with a hangar... you don't need dedicated carriers to use fighters and FAC effectively.
The game doesn't represent reality, but a hypothetical simulation of superscience space warfare. An effective strategy within the game is by default "realistic" in the sense that, if somehow the laws of physics changed to match trans-Newtonian physics as depicted in Aurora, the same strategies would emerge, because people do what works. You're not asking for more "realistic" tactics, but more "interesting" tactics.

If Leyete had played out differently then the Japanese tactics would have been praised as bold and innovative... ;) ...we look at things from a different perspective and have all the facts, they never did when it happened. The US almost bought the Japanese feint manoeuvre but they could not capitalise on it.

As communication and weapon lethality have advanced so have the deployment of military assets both tactically and strategically become more dispersed as information is key to successful military operations. The one who have the information advantage is at a huge advantage over the one that doesn't. This is somewhat how the new sensor model will be changed from the old one. Before you only needed basically two size 50 active sensor one res 1 and one larger resolution, that will no longer be very effective from a research or practical perspective unless you are allot more advanced than an opponent.

Unless you talk about small nations in ancient or medieval times then fleets have almost never been focused into one giant fleet of doom. Sure, large fleet battles require allot of ships and sometimes had the majority of some nations ships in them, that does not mean that fleets was structured and used like this in wartime most of the time. These battles are rather the exception not the rule. In real life there are no do overs and trial and error tactics can be harsh learned experiences. In real life there is logistical nightmares as well as keeping information about troop/fleet movement hidden as big problems.
If you look at ancient and historic events then logistics is what sets high constraint on huge fleets or concentration of forces. These forces require huge investment in resources and good management so often are time caped. So unless you can use them to good effect in a certain time frame it is wasted time and resources. This is one good reason for why large concentration of forces are more the exception than the rule, even historically. Just look at the Roman operational campaigns in ancient times and the Romans had the most advanced logistical and available resources the world had ever seen. Most of the historical battles we read about in history are the exception to the rule, not the norm.

In C# Aurora you are not going to be able to station an infinite number of 10.000t ships at a specific place just because you have 10.000t maintenance capacity. This will force you to have many fleet bases if you have a big sprawling empire. If you play a multi-faction game then dispersed forces might be a must, just as in real life. Against the AI and regular NPR things obviously are more black and white and simplistic.
 

Offline Garfunkel

  • Registered
  • Admiral of the Fleet
  • ***********
  • Posts: 2791
  • Thanked: 1052 times
Re: How Will C# Effect Carriers?
« Reply #34 on: August 07, 2019, 12:31:42 PM »
Another thing, that no one mentioned yet, is that wars in Aurora are highly linear. It seems like there's usually only one jump point in or out of enemy territory; once you know the jump point route to the enemy, the most effective defense is to concentrate everything you have on that jump point. If you want to make things like separate task groups and diversionary attacks viable, the number of interconnections between systems needs to be boosted again so the Galaxy map is less linear.
We're still talking about two different things, I'm like 90% sure that this argument is unnecessary. Linear on the strategic scale is fine, I don't mind fighting a campaign across a line on the galactic map against a single opponent. But I would much rather have more interesting and immersive operational doctrine on the tactical scale, inside a system. Obviously it makes sense to focus most of your ships for a JP assault - but I would prefer game mechanics that encourage that fleet then to spread out in the system, instead of staying as blob in a single, infinitesimal point.
 

Offline Triato

  • Warrant Officer, Class 1
  • *****
  • T
  • Posts: 82
  • Thanked: 7 times
Re: How Will C# Effect Carriers?
« Reply #35 on: August 07, 2019, 07:32:14 PM »
The main avantage of big fleets in one spot is shared defense against missiles, reduce that and you will have more small formations.
 

Offline Garfunkel

  • Registered
  • Admiral of the Fleet
  • ***********
  • Posts: 2791
  • Thanked: 1052 times
Re: How Will C# Effect Carriers?
« Reply #36 on: August 08, 2019, 12:03:33 PM »
Yeah and that's what seems to be happening with C# - it's no longer crucial to keep all ships together. Scouts are much more important and powerful since it'll be far more difficult to have a single sensor ship with all-powerful active/passive sensors that can see most of the system. It'll be easier to spot and destroy incoming missiles. And perhaps most importantly, the new GUI will make it so much easier and quicker to detach elements of your fleet than what we're used to.
 

Offline Jorgen_CAB

  • Admiral of the Fleet
  • ***********
  • J
  • Posts: 2837
  • Thanked: 673 times
Re: How Will C# Effect Carriers?
« Reply #37 on: August 08, 2019, 02:54:29 PM »
Yeah and that's what seems to be happening with C# - it's no longer crucial to keep all ships together. Scouts are much more important and powerful since it'll be far more difficult to have a single sensor ship with all-powerful active/passive sensors that can see most of the system. It'll be easier to spot and destroy incoming missiles. And perhaps most importantly, the new GUI will make it so much easier and quicker to detach elements of your fleet than what we're used to.

Yes... the point in general is scouting and how that works. Since you need to detach scouting forces you also need to protect said scouting forces. It you don't then the one that does will likely win the scouting war in the end. This also means splitting forces up in tactical operations.

This does not diminish the importance of concentration of force in any way, just change some aspects of it.

So even if it is more important to have ships in one spot so they can benefit from shared point defence it is better of you can avoid being hit in the first place by proper scouting and strike the opponent without retaliation.

This is obviously where carriers have a big advantage over say regular missile ships. Carriers can still coordinate joint strikes against an enemy force with relative ease even if they are a fair distance apart from each other in more than one task-force.
 

Iranon

  • Guest
Re: How Will C# Effect Carriers?
« Reply #38 on: August 09, 2019, 03:33:21 AM »
On the plus side, the new system should support all sorts of interesting hide-and-seek games between humans if diverse fleets are a given.
On the minus side, it seems less robust. A few things, most notably tiny fighters, will be shooting fish in a barrel unless facing exact and technologically sophisticated counters with absolutely no room for error.
 

Offline Steve Walmsley

  • Moderator
  • Star Marshal
  • *****
  • S
  • Posts: 11668
  • Thanked: 20440 times
Re: How Will C# Effect Carriers?
« Reply #39 on: August 09, 2019, 05:07:29 AM »
On the plus side, the new system should support all sorts of interesting hide-and-seek games between humans if diverse fleets are a given.
On the minus side, it seems less robust. A few things, most notably tiny fighters, will be shooting fish in a barrel unless facing exact and technologically sophisticated counters with absolutely no room for error.

It is easier to detect small fighters in C# than VB6. It is also easier for small fighters to have reasonable sensors, so it will depend on the balance. One other major factor I have already run into in my current campaign is that you no longer know the range of hostile sensors - only their total output for detection by EM. To know range and resolution you will need to study them with ELINT. Until then, you are sending in fighters and hoping the enemy can't detect them. I aborted a strike because I was concerned about that exact problem.

New Active Sensor Model: http://aurora2.pentarch.org/index.php?topic=8495.msg102701#msg102701
New Passive Sensor Model: http://aurora2.pentarch.org/index.php?topic=8495.msg103085#msg103085
 
The following users thanked this post: SpikeTheHobbitMage

Offline Jorgen_CAB

  • Admiral of the Fleet
  • ***********
  • J
  • Posts: 2837
  • Thanked: 673 times
Re: How Will C# Effect Carriers?
« Reply #40 on: August 09, 2019, 09:53:06 AM »
On the plus side, the new system should support all sorts of interesting hide-and-seek games between humans if diverse fleets are a given.
On the minus side, it seems less robust. A few things, most notably tiny fighters, will be shooting fish in a barrel unless facing exact and technologically sophisticated counters with absolutely no room for error.

It is easier to detect small fighters in C# than VB6. It is also easier for small fighters to have reasonable sensors, so it will depend on the balance. One other major factor I have already run into in my current campaign is that you no longer know the range of hostile sensors - only their total output for detection by EM. To know range and resolution you will need to study them with ELINT. Until then, you are sending in fighters and hoping the enemy can't detect them. I aborted a strike because I was concerned about that exact problem.

New Active Sensor Model: http://aurora2.pentarch.org/index.php?topic=8495.msg102701#msg102701
New Passive Sensor Model: http://aurora2.pentarch.org/index.php?topic=8495.msg103085#msg103085

In some sense they are but small sensors are also more effective now so you will need a very large low res to paint a fighter at a decent distance, so I guess that will mostly be done by forward scouts as well. A 300t res 100 is roughly equal with a 2000t res 5 at equal tech level.

The benefit with fighters or FAC is that you can easily paint the same target from several vectors and alternate between them so they can't be engaged easily with missiles from a long range unless some form of interceptors are used. But then we are back to the splitting up of forces to guard your own scouts from such threat and kill incoming interceptors etc... Sure you might not know if your missile fighters missile and fire-control range is outside the enemy active range and that might actually be more restrictive than the active sensor itself, will be interesting to find out.

I also feel that passive sensors, especially thermal sensors will be more important than before for scouting and reconnaissance.

In my opinion there seem to be a nice balance between the need for larger more capable ships since fighters will still need carriers to do any sort of deep space missions and larger ships will in general be vulnerable to fast low range fighters and decently fast scouts with a bit more endurance. I for one are quite pleased that having a wide variety of ship sizes and classes will be important for an effective fleet.
 

Offline chrislocke2000

  • Captain
  • **********
  • c
  • Posts: 544
  • Thanked: 39 times
Re: How Will C# Effect Carriers?
« Reply #41 on: August 09, 2019, 10:14:53 AM »
I have to say trying to shadow an enemy ship for 100 odd days in order to get the ELINT module to work is certainly going to be "interesting". I assume that for a lot of engagements you simply won't know the capabilities of the enemy sensors.

Does the intelligence on a sensor attach to the sensor or the ship contact? 

Very much looking forward to reading the next campaign update to see all of this in action.
 

Offline Steve Walmsley

  • Moderator
  • Star Marshal
  • *****
  • S
  • Posts: 11668
  • Thanked: 20440 times
Re: How Will C# Effect Carriers?
« Reply #42 on: August 09, 2019, 11:01:31 AM »
I have to say trying to shadow an enemy ship for 100 odd days in order to get the ELINT module to work is certainly going to be "interesting". I assume that for a lot of engagements you simply won't know the capabilities of the enemy sensors.

Does the intelligence on a sensor attach to the sensor or the ship contact? 

Very much looking forward to reading the next campaign update to see all of this in action.

To the sensor. If another ship has the same sensor, you will see the same ELINT data.
 

Offline Jovus

  • Lt. Commander
  • ********
  • J
  • Posts: 220
  • Thanked: 81 times
Re: How Will C# Effect Carriers?
« Reply #43 on: August 09, 2019, 01:05:31 PM »
I'm kind of curious if a new optimum 'meta' will pop up around disabling the enemy's engines and then keeping the ship around for ELINT to go over.

Probably not, because at that point a more effective solution would be Marines. But it might be funny.
 

Offline Steve Walmsley

  • Moderator
  • Star Marshal
  • *****
  • S
  • Posts: 11668
  • Thanked: 20440 times
Re: How Will C# Effect Carriers?
« Reply #44 on: August 10, 2019, 07:29:24 AM »
I have to say trying to shadow an enemy ship for 100 odd days in order to get the ELINT module to work is certainly going to be "interesting". I assume that for a lot of engagements you simply won't know the capabilities of the enemy sensors.

Does the intelligence on a sensor attach to the sensor or the ship contact? 

Very much looking forward to reading the next campaign update to see all of this in action.

I also should have mentioned that you don't have to follow the same ship around. Any ELINT detection of that sensor on any ship that carries it will add to the total for the sensor.
 
The following users thanked this post: SpikeTheHobbitMage