Post reply

Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.

Note: this post will not display until it's been approved by a moderator.

Name:
Email:
Subject:
Message icon:

shortcuts: hit alt+s to submit/post or alt+p to preview

Please read the rules before you post!


Topic Summary

Posted by: Anarade Relle
« on: February 11, 2016, 04:36:38 PM »

Another idea to help preserve the maintenance cost of your exploration survey fleet: put the military jump drives on your commercial geological ships instead. Or at least have a commercial geo ship that accepts it. Makes it a lot easier to deal with maintenance, as that's tonnage that doesn't need to be maintained due to being a commercial component on a commercial ship. Before you ask, yes, military jump drives are commercial components, and can transit both commercial and military vessels.

That's pretty damn amazing! I'll have to try that! Thanks.
Posted by: iceball3
« on: February 11, 2016, 09:34:50 AM »

If you are aiming for efficiency in maintenance for survey vessels I always feel it works best to use survey carriers. You have a main vessel that has a long deployment life and plenty of MSP, then design survey work craft that have little else other than a high efficiency commercial drive, and the required sensor type. The survey craft never suffer any failures due to only being out a few months or so, and the carrier can be designed to go for a good few years with no issues and have enough MSP to solve any possible problems. In addition you get to survey systems fast and with a few clicks using subordinate TG's.
Though, it's worth noting that putting a jump drive on any military design incurs extra cost due to maintenance, it may be negligible due to the lack of mass-production of said vessel.
Though, in that vein, it reminds me of an idea I played around with, the hangar vessel as you mentioned, but rather than make gravity survey ships at all, make "Gravity Sensor Modules", which are designed essentially like so.
Code: [Select]
Tone class Sensor Platform    282 tons     2 Crew     104 BP      TCS 5.64  TH 0  EM 0
1 km/s     Armour 1-3     Shields 0-0     Sensors 1/1/1/0     Damage Control Rating 0     PPV 0
Maint Life 0 Years     MSP 0    AFR 56%    IFR 0.8%    1YR 47    5YR 705    Max Repair 100 MSP
Intended Deployment Time: 0.1 months    Spare Berths 2   


Gravitational Survey Sensors (1)   1 Survey Points Per Hour

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

The reason being for this is that you can load them in to the hangars of the vessel and:
-They won't contribute to the maintenance cost via their huge-expense sensors.
-They will contribute to the task group's gravity survey capabilities and speed.
-They are easier to build, in the sense that you shift the cost of one of the most expensive components of a ship into fighter factories.

The only particular downsides I see is potential problems with nested-parasite management, and decreased flexibility in the sense that you can't split the task group to scan multiple points simultaneously, though you will be able to use more efficient engines, at least.
That said, in general, I tend to avoid putting jump engines on military designs unless they're specifically designed as some form of assault craft.
Posted by: Rich.h
« on: February 11, 2016, 05:05:11 AM »

Another idea to help preserve the maintenance cost of your exploration survey fleet: put the military jump drives on your commercial geological ships instead. Or at least have a commercial geo ship that accepts it. Makes it a lot easier to deal with maintenance, as that's tonnage that doesn't need to be maintained due to being a commercial component on a commercial ship. Before you ask, yes, military jump drives are commercial components, and can transit both commercial and military vessels.

If you are aiming for efficiency in maintenance for survey vessels I always feel it works best to use survey carriers. You have a main vessel that has a long deployment life and plenty of MSP, then design survey work craft that have little else other than a high efficiency commercial drive, and the required sensor type. The survey craft never suffer any failures due to only being out a few months or so, and the carrier can be designed to go for a good few years with no issues and have enough MSP to solve any possible problems. In addition you get to survey systems fast and with a few clicks using subordinate TG's.
Posted by: iceball3
« on: February 11, 2016, 12:27:19 AM »

These days I put commercial engines on grav survey ships. I used to use regular military engines favouring fuel efficiency over speed but after a certain point I find it's just easier to cut down on the number of foreward fuel depots I have to set up to support exploration efforts.

Slower ships, but whenever a hostile NPR or spoilers found my grav ships they died. So it's not like survivability has been effected.
Another idea to help preserve the maintenance cost of your exploration survey fleet: put the military jump drives on your commercial geological ships instead. Or at least have a commercial geo ship that accepts it. Makes it a lot easier to deal with maintenance, as that's tonnage that doesn't need to be maintained due to being a commercial component on a commercial ship. Before you ask, yes, military jump drives are commercial components, and can transit both commercial and military vessels.
Posted by: Anarade Relle
« on: February 10, 2016, 06:09:08 PM »

These days I put commercial engines on grav survey ships. I used to use regular military engines favouring fuel efficiency over speed but after a certain point I find it's just easier to cut down on the number of foreward fuel depots I have to set up to support exploration efforts.

Slower ships, but whenever a hostile NPR or spoilers found my grav ships they died. So it's not like survivability has been effected.
Posted by: Steve Walmsley
« on: February 10, 2016, 04:12:17 PM »

Some might disagree - but I learned to love to build a single survey vessel class, putting a Geo and Grav sensor on it.  The flexibility makes it much simpler to just survey out a system.   That and I can pump them out constantly and have a easy to manage survey fleet that only gets upgraded (Sometimes) with new engine technology, as I scrap out older designs with my fuel efficient designs, those surplus engines end up in the survey fleet.   

Most games my survey fleet consists of two classes - A jump scout with a jump drive and some passive sensors that does the first look inside systems, and then the grav-Geo scanning ships.

I've long been a fan of having specialised grav and geo survey ships. However, with so many races in my current campaign I decided to experiment and I have been pretty happy with the flexibility of the joint geo/grav designs.
Posted by: Drgong
« on: February 10, 2016, 02:03:33 PM »

Some might disagree - but I learned to love to build a single survey vessel class, putting a Geo and Grav sensor on it.  The flexibility makes it much simpler to just survey out a system.   That and I can pump them out constantly and have a easy to manage survey fleet that only gets upgraded (Sometimes) with new engine technology, as I scrap out older designs with my fuel efficient designs, those surplus engines end up in the survey fleet.   

Most games my survey fleet consists of two classes - A jump scout with a jump drive and some passive sensors that does the first look inside systems, and then the grav-Geo scanning ships.   
Posted by: bean
« on: February 10, 2016, 09:29:59 AM »

Then less missiles would hit because either hit chance is to low or they were slow enough to be taken out by anti-missile fire.
Neither point is true.  First, I should clarify that I was talking about AMMs, not regular missiles, so the issue of AMM fire is largely moot.  Second, Iranon demonstrated (and I subsequently confirmed, both mathematically and in-game) that there is an optimum speed for AMMs, and it's certainly slower than I was building my AMMs.  I cut speed about 40%, and got 10-ish percent improvement in hit chance. 
The math behind this is fairly simple.  I have two missiles with similar hit chances, one with a speed of 140,000 km/s and the other with 100,000 km/s, and both having a range of 14 mkm.  Obviously, it takes Missile 1 100 seconds to reach max range and Missile 2 140 seconds.  Assume my limiting factors are missile range and number of launchers/launch cycles, not magazine space or fire control.  For the first missile, I can begin engaging when the enemy missile hits 19 mkm (380 seconds out), while the second lets me start at 21 mkm (420 seconds out.)
Posted by: 83athom
« on: February 10, 2016, 07:54:21 AM »

Then less missiles would hit because either hit chance is to low or they were slow enough to be taken out by anti-missile fire.
Posted by: bean
« on: February 09, 2016, 07:18:14 PM »

On the other hand, if missile range is your limiting factor, slower missiles of the same range actually means you can start shooting sooner, and thus get more missiles out overall. 
Posted by: TheDeadlyShoe
« on: February 09, 2016, 05:55:48 PM »

if enemy missiles are faster than your AMMs this can end up being a problem for several reasons.  Most notably, offset AMM escort tactics and last-ditch AMM salvos will not work very well.
Posted by: bean
« on: February 09, 2016, 01:10:15 PM »

I've done some poking around, and the only case in which faster-than-optimum missiles seem to work is when you're operating in shoot-look-shoot mode, and the faster missiles get more opportunities to shoot.  A 20-25% above-optimum speed missile seems to work well here.  In cases where you're limited by magazine size or launcher ROF, the missile with the highest chance to hit is the best choice.
(And this probably isn't that useful.  1v1 is only a good idea when you have high odds of a hit.  Going from 1.5% chance of a given leaker to a 1% chance isn't a big improvement, particularly when it means you need to fire more missiles overall.  Have one ship in your fleet set its fire control for short range and go 2v1 there.)
Posted by: bean
« on: February 09, 2016, 11:10:13 AM »

I retract my earlier comment on your math not working.  I worked through the same math, and got the same equation.  It's beyond weird that the engine power drops out, but it does.
The equation I got is P=5S/A+C/2 where P is the space allotted to propulsion, S is the size of the missile, A is agility per MSP, and C is the space allotted to (propulsion+agility). 
This is a tremendously useful equation for designing AMMs, and probably fairly useless for everything else.  Thanks.
I should include the standard caveats.  First, this was derived under the assumption that speed is directly proportional to the propulsion fraction.  This is probably not a good assumption in most design cases.  If you're building an AMM, you probably have a certain range you want, and then you want as high a hit possibility as possible at that range.  A first approximation would be to include fuel in the (S-C) space, normally allocated to warhead.  This assumes that fuel consumption remains constant, but bigger engines will need less fuel.  I'm not sure there's a good way to deal with this analytically. 
I'm currently looking into quantifying the performance advantage of these optimized missiles over the significantly faster missiles I've been using to date.
Posted by: bean
« on: February 09, 2016, 09:46:38 AM »

I keep reading this hoping that it will make sense. So perhaps an example will help me make sense of it. Assuming a size 6 engine with 1MSP dedicated to warhead, how big should my engine and my fuel be for your formula?
Basically, you allocate a certain amount of propulsion space on the missile (P) which is equal to engine space (E) + fuel space (F).  For the best speed/range (one is maximized while the other is fixed) E= .7609*P and F= .2391*P.  So if you're allocating P=6, then E=4.57 and F=1.43. 
The one caveat is that this assumes there is no cap on the power multiplier you can use.  You may very well need more engine than these numbers would indicate, particularly for things like AMMs.  The most important rule is that you shouldn't have a missile that doesn't have max-size engines and has more than a third of the engine space in fuel.

Quote
What do you put on your decoys? I've never played with multi stage missle designs before, but that sounds interesting.
My basic missiles are all size 1, and I have the tech to make this work. (In fairness, I was as concerned with getting missiles through really heavy defenses as I was with raw damage, which may not have been the absolute optimum.)  The standard missile does about 150,000 km/s, and has a size-4 warhead with a range of 17 mkm, IIRC.  I mount from 1 to 3 of them on a size 4 bus which has a much more efficient and less powerful engine, and then fire them at targets at ranges up to around 1,000 mkm.  The bus doesn't need to go fast as it doesn't have to get through defenses.  Each stage can be optimized for its own job.  The decoys are set up to be very slightly faster than the actual warhead missiles, and are released at the same time.  Each fire control has one tube of decoys and usually about 5 tubes of regular missiles.  The decoys separate at the same time, and double the number of different targets, which helps saturate fire control on the receiving end.  They're also a bit ahead of the regular missiles, so they get shot at first.  As the difference in speed is usually 100 km/s, they normally arrive on the same increment as the attack missiles, and draw off all the beam PD.
The decoys have a slightly different (more powerful) engine than the regular missiles, fuel to have the same range, and everything else is armor.

Can't have too many things at once fixed.

If E is engine tonnage, S is size of the missile, A is Agility points per MSP.
Ideal fuel is  0.4E if using maximum-size engines already, 0.3182*E otherwise.
Ideal agility to maximise to hit chance on a given budget for engine and agility is E-10S/A (this requires fine-tuning to avoid losses to rounding, and ignores possible fuel savings by larger engines).

Subbing numbers for a size 6 missile with 1 MSP warhead (which I assume you meant), we put in the numbers of non-warhead space of 5:
 5=2.3182E-60/A
If you have a missile agility tech of 80:
5=2.3182E-0.75, for an engine size of 2.4803, and corresponding fuel of 0.7892 and agility of 1.7304 with 1/10000 of a MSP lost in rounding
We don't care, as agility will need some adjusting to avoid rounding losses.
Something seems off with your math.  I can't see where that equation comes from, and I definitely don't see a factor for engine power per MSP in there, which would be an important part of the trade.  In some cases, making the missile faster is better than adding agility, because it has other benefits, too.

Quote
In practice, this beautiful precision is unnecessary to counterproductive as there may be other considerations:
I never have enough engine multiplier tech to hit the ideal without excessive range (if I do, I messed up research priorities).

This is pretty common, particularly for AMMs.

Quote
Also, bigger lower-power engine and less fuel is cheaper.
I'm not so sure about this.  I may have to play with numbers.

Quote
I usually want more engine and less agility than the theoretical optimum: faster to better evade PD, better range for free if we can increase engine size, and again usually cheaper.
This I will agree with.  My second stages have no agility at all, while the AMMs use the same engine and have a smaller warhead.

Quote
In practice, 40% engines, 30% warhead+sensors, 20% agility, 10% fuel is my guideline for general-purpose missiles. If you're set on a different payload, the 4:2:1 ratio of engine to agility to fuel remains useful.
That's going to give you about 95% of the efficiency of a proper optimum.  Which is decent, but not perfect.
Posted by: Iranon
« on: February 09, 2016, 05:19:46 AM »

Can't have too many things at once fixed.

If E is engine tonnage, S is size of the missile, A is Agility points per MSP.
Ideal fuel is  0.4E if using maximum-size engines already, 0.3182*E otherwise.
Ideal agility to maximise to hit chance on a given budget for engine and agility is E-10S/A (this requires fine-tuning to avoid losses to rounding, and ignores possible fuel savings by larger engines).

Subbing numbers for a size 6 missile with 1 MSP warhead (which I assume you meant), we put in the numbers of non-warhead space of 5:
 5=2.3182E-60/A
If you have a missile agility tech of 80:
5=2.3182E-0.75, for an engine size of 2.4803, and corresponding fuel of 0.7892 and agility of 1.7304 with 1/10000 of a MSP lost in rounding
We don't care, as agility will need some adjusting to avoid rounding losses.



In practice, this beautiful precision is unnecessary to counterproductive as there may be other considerations:
I never have enough engine multiplier tech to hit the ideal without excessive range (if I do, I messed up research priorities). Also, bigger lower-power engine and less fuel is cheaper.
I usually want more engine and less agility than the theoretical optimum: faster to better evade PD, better range for free if we can increase engine size, and again usually cheaper.

In practice, 40% engines, 30% warhead+sensors, 20% agility, 10% fuel is my guideline for general-purpose missiles. If you're set on a different payload, the 4:2:1 ratio of engine to agility to fuel remains useful.