Aurora 4x
C# Aurora => Development Discussions => Topic started by: db48x on April 16, 2020, 10:20:47 AM
-
I seem to recall doing this in the old days, but I think I'm missing something, or possibly there's a bug. I've launched missiles with geosurvey sensors at waypoints attached to planets, but when the missiles arrived they didn't survey the planet, and then they disappeared on the next 5-day tick. What am I doing wrong?
-
Might not be actually implemented in C#? Or do you mean by old days in a C# version?
As far as VB went I think it as just as you said: launch geo missile at WP attached to a planet and have enough fuel for them to survive long enough to generate the geo points. I personally never did it just read how it's done so can only help with heresay
-
Maybe they just don't have enough fuel. I made them small with efficient engines for long range, but perhaps have to make them large with efficient engines for endurance.
-
I've never messed around with geosurvey missiles - I'm more of a geosurvey carrier with survey LACs kind of guy myself - but I'm going to try it on my latest test game. I think the answer might be you need to make a larger than usual missile that can fly for more than a couple of days so it can survey an a small body.
-
I just had this issue. You probably need stronger sensors. I designed a first probe and it did nothing, but as soon as I designed a second one with a more powerful geo sensor, it worked. They will stay on the body until either the survey is complete, or they run out of fuel, only when they finish surveying and disappear you'll know the minerals. You need either more powerful sensors or more fuel.
-
I've done it once in VB6 and it is extremely inefficient. You need a big missile so that it can have plenty of MSP dedicated to the geosurvey sensor AND it needs a lot of fuel to stay alive while on planetary orbit - expect Mars survey to take at least a week.
-
I've done it once in VB6 and it is extremely inefficient. You need a big missile so that it can have plenty of MSP dedicated to the geosurvey sensor AND it needs a lot of fuel to stay alive while on planetary orbit - expect Mars survey to take at least a week.
It's more useful for small bodies like asteroids. (Collecting 5-20 SP is easy, even with tiny sensors) That way a small ship can just zip through a system dropping buoys on every little rock. The problem is, aurora doesn't automate this very well, so it's easier to use normal survey ships.
-
I've done it once in VB6 and it is extremely inefficient. You need a big missile so that it can have plenty of MSP dedicated to the geosurvey sensor AND it needs a lot of fuel to stay alive while on planetary orbit - expect Mars survey to take at least a week.
You don't need that much fuel for endurance. Engineless buoy had almost unlimited lives in the VB6 version and can be used as second stages.
I was using long duration sensor buoys as second stages of missiles back on the day, as it was very convenient for zero risk scouting of suspicious planets :
B/AS-1 Sensor Buoy
Missile Size: 0.947 MSP (0.04735 HS) Warhead: 0 Armour: 0 Manoeuvre Rating: 10
Speed: 0 km/s Engine Endurance: 0 minutes Range: 0.0m km
Active Sensor Strength: 0.1504 Sensitivity Modifier: 80%
Resolution: 100 Maximum Range vs 5000 ton object (or larger): 120,000 km
Thermal Sensor Strength: 0.1375 Detect Sig Strength 1000: 137,500 km
EM Sensor Strength: 0.1 Detect Sig Strength 1000: 100,000 km
Cost Per Missile: 0.621
Chance to Hit: 1k km/s 0% 3k km/s 0% 5k km/s 0% 10k km/s 0%
Materials Required: 0.2331x Boronide 0.3879x Uridium Fuel x0
and the 2 carrier missiles were :
MRSD-1 "Blink" Medium Range Sensor Deployment system
Missile Size: 2 MSP (0.1 HS) Warhead: 0 Armour: 0 Manoeuvre Rating: 10
Speed: 3700 km/s Engine Endurance: 150.2 hours Range: 2,000.9m km
Cost Per Missile: 0.6534
Second Stage: B/AS-1 x1
Second Stage Separation Range: 50,000 km
Overall Endurance: 6 days Overall Range: 2000.9m km
Chance to Hit: 1k km/s 37% 3k km/s 10% 5k km/s 7.4% 10k km/s 3.7%
Materials Required: 0.2106x Boronide 0.3504x Uridium 0.0924x Gallicite Fuel x1100
LRSD-1 "Beacon" Long Range Sensor Deployment system
Missile Size: 4 MSP (0.2 HS) Warhead: 0 Armour: 0 Manoeuvre Rating: 10
Speed: 3500 km/s Engine Endurance: 1,591.8 hours Range: 20,056.1m km
Cost Per Missile: 0.7342
Second Stage: B/AS-1 x1
Second Stage Separation Range: 50,000 km
Overall Endurance: 66 days Overall Range: 20056.1m km
Chance to Hit: 1k km/s 35% 3k km/s 10% 5k km/s 7% 10k km/s 3.5%
Materials Required: 0.2106x Boronide 0.3504x Uridium 0.1732x Gallicite Fuel x3375
I remember trying geosurvey sensors in the same fashion, but it took ages to survey anything... A carrier with a fleet of geosurvey fighters was far more efficient for most endeavours.
Of course, don't forget to change the second stage separation range to 0 for geosurvey buoys.
-
Try this using a two stage missile as Cocyte did, I think that may be your problem. (I've done the following with active and thermal sensors, though not yet geo/grav, it's a bit too micromanagy for my taste)
First design a bouy to hold your geo/grav sensors, check the "No Engines" checkbox.
Second design a delevery system with an efficent engine and the above bouy as a second stage, set the seperation range to 0.
load up the missile in whatever ship you're using, place a waypoint on the planet. target the waypoint, tell the FC to open fire, advance time a couple of seconds, and remember to tell the FC to cease fire so you don't waste those expensive missiles by firing your whole wad at one waypoint.
-
it was very convenient for zero risk scouting of suspicious planets
Just for reference, what does a suspicious planet look like? Is it the shifty eyes? Trench coat? Dark glasses?
-
I never tried this for one simple reason (well, maybe two..?)... Asteroids, possibly comets. Surveying them via missiles might kill most players, having to do the chore of waypoint and firing missile at tens of targets.
it was very convenient for zero risk scouting of suspicious planets
Just for reference, what does a suspicious planet look like? Is it the shifty eyes? Trench coat? Dark glasses?
Clothing and accessories are personal matter (even for planets)! I guess something like the cost 2 terrestrial world with liquid hydrosphere and Ammonia-Methane atmosphere I just found in a new system. Prime candidate for bad stuff!
Edit:
And now I found Alien installation there... so while not really suspicious anymore, it was really fishy (literally, there is liquid hydrosphere so I assume fish), 8) ;D
-
I've done it once in VB6 and it is extremely inefficient. You need a big missile so that it can have plenty of MSP dedicated to the geosurvey sensor AND it needs a lot of fuel to stay alive while on planetary orbit - expect Mars survey to take at least a week.
You don't need that much fuel for endurance. Engineless buoy had almost unlimited lives in the VB6 version and can be used as second stages.
That's true but requires one to do 2-stage missiles. It might be easier to make a single-stage missile with enough fuel that the missile doesn't expire before surveying is done.
it was very convenient for zero risk scouting of suspicious planets
Just for reference, what does a suspicious planet look like? Is it the shifty eyes? Trench coat? Dark glasses?
Did I drunk-edit my post or what the heck? Because I didn't type that or at least it doesn't show up in my post.
I mean, that is true. A sketchy planet, wearing a fedora, shades, and a trench coat, is safer to be scoped out farther away. But yeah, any CC:0 planet you could send a missile at - even if it gets intercepted, at least you then know that the neighborhood is busy.
-
it was very convenient for zero risk scouting of suspicious planets
Just for reference, what does a suspicious planet look like? Is it the shifty eyes? Trench coat? Dark glasses?
nah, its the colony cost 0. that spells angry NPR
-
But yeah, any CC:0 planet you could send a missile at - even if it gets intercepted, at least you then know that the neighbourhood is busy.
That's actually a good point.
If the intent of sending a geo survey missile is merely to avoid risking the loss of an expensive geo survey ship, you can achieve the same thing by sending a much-cheaper missile instead.
Just put the minimum possible thermal sensor on it.
If it makes it to the planet, you'll know if the planet is hot or not.
If it doesn't make it to the planet--well, now you know that the planet is hot.
-
Yep, I ended up making a small active sensor buoy as a second stage. This has saved the lives of hundreds of crewmen and, more importantly, dozens of officers. (I turned up the ruin generation chance and turned down the distance between NPRs so that I would have more excitement earlier.)
Next time I do this, I'll make the active sensor smaller. I wasn't really thinking very hard when I designed it, and it ended up being size 3 with 1.3 million km of range, which is a bit silly. Any defensive ships will be right on top of the planet most of the time, or they'll be a lot further away from it than that at a different planet.. The missile ended up being size 5, which could have been a lot better. Worked perfectly though.
-
But yeah, any CC:0 planet you could send a missile at - even if it gets intercepted, at least you then know that the neighbourhood is busy.
That's actually a good point.
If the intent of sending a geo survey missile is merely to avoid risking the loss of an expensive geo survey ship, you can achieve the same thing by sending a much-cheaper missile instead.
Just put the minimum possible thermal sensor on it.
If it makes it to the planet, you'll know if the planet is hot or not.
If it doesn't make it to the planet--well, now you know that the planet is hot.
If a missile doesn't have a warhead, will it still be interpreted as an act of war?
-
If a missile doesn't have a warhead, will it still be interpreted as an act of war?
Only if it does damage to a ship. Without a warhead I don't think it will actually hit anything; it just goes to the same position as the target.
-
Depends on whom it was shot at, a player might see it as hostile, an AI will probably not consider it a threat.
-
But yeah, any CC:0 planet you could send a missile at - even if it gets intercepted, at least you then know that the neighbourhood is busy.
That's actually a good point.
If the intent of sending a geo survey missile is merely to avoid risking the loss of an expensive geo survey ship, you can achieve the same thing by sending a much-cheaper missile instead.
Just put the minimum possible thermal sensor on it.
If it makes it to the planet, you'll know if the planet is hot or not.
If it doesn't make it to the planet--well, now you know that the planet is hot.
If a missile doesn't have a warhead, will it still be interpreted as an act of war?
I don't know.
But a missile like this, with a minimum-size sensor and no warhead, is not intending to absolutely provoke a response.
Instead, it is intending to tell you if it is safe to approach the target body for a geo survey.
If the missile makes it to the target, you will see if there is any thermal signature on the planet.
If a thermal signature is present, then you should assume it is not safe for a geo survey.
If the missile is shot down before reaching the target, you can also assume it is not safe for a geo survey.
-
Only damage and active sensors cause a negative impact with NPRs.
If they have claimed a system, then anything and everyhing present in that system will also cause a negative impact.
-
I like 'em, with reduced sized launchers you can very much get more sensor per ton over ship-mounted Geological Survey Sensors. That said, they're a bigger PIA and not exclusively better. I'm not sure if Geosurvey Missiles scale with Geological Survey Sensor tech... might make those missiles a lot less useful in the long run.
-
with reduced sized launchers you can very much get more sensor per ton over ship-mounted Geological Survey Sensors.
But a missile can only be used once. The ship-mounted sensors are reusable indefinitely.
-
with reduced sized launchers you can very much get more sensor per ton over ship-mounted Geological Survey Sensors.
But a missile can only be used once. The ship-mounted sensors are reusable indefinitely.
Eh, indeed. While they are interestig, I am not particularly a fan of geosurvey missiles because then you also have to produce the missiles and go back to reload once you're empty...
I am a fan instead of the thermal sensor long range missile... to be launched at low colony cost planets with atmosphere....
You know, rather than risk a survey ship, check if the planet is HOT... ;D
-
So I've decided that I want to test out some different sensor/survey missile concepts because I like the concept, even if it is inefficient. I tested this previously in v195 but have not yet confirmed the same problematic behaviors I observed in v195 with v1100. I will post back shortly.
-
First Test: 2 Stage Active Sensor Buoy Targeted and Launched using MFC Commands
In this test I created 2 player races on Earth in a new game, Red Team and Blue Team. Red Team and Blue team are identical and both located on Earth, and both posses 2 shipyards and a single spaceport as their only orbital facilities. Blue Team, via SM, was given the following space station in Earth orbit:
Skylab class Orbital Research Base 111,733 tons 3,758 Crew 16,907.6 BP TCS 2,235 TH 0 EM 0
1 km/s Armour 1-206 Shields 0-0 HTK 1282 Sensors 250/250/0/0 DCR 560 PPV 4
Maint Life 50.13 Years MSP 222,017 AFR 182% IFR 2.5% 1YR 173 5YR 2,598 Max Repair 500 MSP
Magazine 19 Cargo Shuttle Multiplier 1
Commander Control Rating 1 BRG
Intended Deployment Time: 600 months Morale Check Required
Blue Team Size 1 Missile Launcher (1) Missile Size: 1 Rate of Fire 30
Blue Team Size 3.0 Missile Launcher (1) Missile Size: 3.0 Rate of Fire 55
Blue Team Missile Fire Control FC56-R1 (1) Range 56.4m km Resolution 1
Blue Team Missile Fire Control FC447-R500 (1) Range 447.8m km Resolution 500
Blue Team Missile Fire Control FC261-R100 (1) Range 261.9m km Resolution 100
Blue Team Active Search Sensor AS223-R500 (1) GPS 250000 Range 223.9m km Resolution 500
Blue Team Active Search Sensor AS130-R100 (1) GPS 50000 Range 130.9m km Resolution 100
Blue Team Active Search Sensor AS28-R1 (1) GPS 500 Range 28.2m km MCR 2.5m km Resolution 1
Blue Team Thermal Sensor TH50-250 (1) Sensitivity 250 Detect Sig Strength 1000: 125m km
Blue Team EM Sensor EM50-250 (1) Sensitivity 250 Detect Sig Strength 1000: 125m km
This design is classed as a Military Vessel for maintenance purposes
Blue Team developed the following spy satellite and scout missile:
Blue Team Spy Satellite
Missile Size: 2.0 MSP (5.00 Tons) Warhead: 0 Radiation Damage: 0 Manoeuvre Rating: 10
Speed: 0 km/s Fuel: 0 Flight Time: 1 seconds Range: 0 km
Active Sensor Strength: 0.2 EM Sensitivity Modifier: 5
Resolution: 1 Maximum Range vs 50 ton object (or larger): 564,189 km
Cost Per Missile: 0.32 Development Cost: 32
Chance to Hit: 1k km/s 0% 3k km/s 0% 5k km/s 0% 10k km/s 0%
Materials Required
Boronide 0.12
Uridium 0.2
Blue Team Scout Missile
Missile Size: 3.00 MSP (7.500 Tons) Warhead: 0 Radiation Damage: 0 Manoeuvre Rating: 10
Speed: 67 km/s Fuel: 1,975 1st Stage Flight Time: 36,202 hours 1st Stage Range: 8,692.9m km
2nd Stage Flight Time: 1 seconds 2nd Stage Range: 0k km
Cost Per Missile: 0.32 Development Cost: 32
Second Stage: Blue Team Spy Satellite III - Active x1
Second Stage Separation Range: 0 km
Chance to Hit: 1k km/s 0.7% 3k km/s 0.2% 5k km/s 0.1% 10k km/s 0.1%
Materials Required
Boronide 0.12
Uridium 0.2
Fuel: 1975
Attached is a screenshot of the tactical map following deployment of 3 different scout missiles. All 3 missiles deployed their second stage satellites as expected. The first missile, identifiable by it's active sensor on the tactical map as 'Blue Team Scout Missile II - Active Waypoint #1 (Luna)' utilized an older 2nd stage design that was identical to the one posted above except that it had a higher resolution sensor equipped. This missile was targeted at Luna from Skylab by manually placing a waypoint on Luna, setting the waypoint as the target of Skylab's missile fire controls, and setting Skylab's missile fire controls to 'open fire'. This missile successfully transited to Luna and deployed it's second stage satellite. However, as Earth and Luna continue to orbit Sol, the satellite was left behind and does not orbit Luna.
The second missile was another of the older, higher resolution design 2nd stage, and was launched from Skylab by targeting Red Team's population on Earth using Skylab's missile fire controls and setting Skylab's missile fire controls to 'open fire' as was done with Luna. This time, the missile again properly closed to it's target and deployed the 2nd stage sensor satellite, however this time the satellite remained in orbit around Earth even as Earth continues to orbit Sol.
The third missile was of the design posted and launched in the same manner as the second missile with the same results.
-
Second Test: 2 Stage Active Sensor Buoy Targeted and Launched using Fleet Commands
Alright, this test had an unexpected and surprising result. Instead of targeting a waypoint on Luna with Skylab's MFC, instead I gave the Skylab fleet the order to 'launch ready ordnance' on Luna. Note that Skylab is not equipped with engines.
The result of this order was that Skylab fleet transited to Luna, and upon entering orbit, launcher her single scout missile.
Skylab has been ordered to return to Earth, but is too slow to catch it. Possibly it will be able to intercept Earth after an orbit or two. The missile launched at Luna is also too slow to catch Luna it seems, and is actually moving at 0k km/s despite what the tactical map displays.
Attached are relevant screenshots.
-
Second Test: 2 Stage Active Sensor Buoy Targeted and Launched using Fleet Commands
Alright, this test had an unexpected and surprising result. Instead of targeting a waypoint on Luna with Skylab's MFC, instead I gave the Skylab fleet the order to 'launch ready ordnance' on Luna. Note that Skylab is not equipped with engines.
The result of this order was that Skylab fleet transited to Luna, and upon entering orbit, launcher her single scout missile.
Skylab has been ordered to return to Earth, but is too slow to catch it. Possibly it will be able to intercept Earth after an orbit or two. The missile launched at Luna is also too slow to catch Luna it seems, and is actually moving at 0k km/s despite what the tactical map displays.
Attached are relevant screenshots.
If a ship is too slow to catch a body and misses on the first try then it won't ever catch up on its own. What you have to do is calculate an intercept course and set a way-point.
-
Second Test: 2 Stage Active Sensor Buoy Targeted and Launched using Fleet Commands
Alright, this test had an unexpected and surprising result. Instead of targeting a waypoint on Luna with Skylab's MFC, instead I gave the Skylab fleet the order to 'launch ready ordnance' on Luna. Note that Skylab is not equipped with engines.
The result of this order was that Skylab fleet transited to Luna, and upon entering orbit, launcher her single scout missile.
Skylab has been ordered to return to Earth, but is too slow to catch it. Possibly it will be able to intercept Earth after an orbit or two. The missile launched at Luna is also too slow to catch Luna it seems, and is actually moving at 0k km/s despite what the tactical map displays.
Attached are relevant screenshots.
If a ship is too slow to catch a body and misses on the first try then it won't ever catch up on its own. What you have to do is calculate an intercept course and set a way-point.
That is what I am attempting to do now.
I have also discovered that if you very carefully position a waypoint directly on top of a planet, the waypoint will move with the planet as the planet orbits it's star. So once I get Skylab back into Earth orbit I am going to do some more tests.
What is most strange is that when Skylab first decided to leave Earth orbit it appeared to traveling at a much higher speed than the 1 km/s it seems to be limited to now.
-
The crew of Skylab has returned safely to Earth orbit. There was much rejoicing at their return. And now for more testing...
-
It seems that eventually the missile that was launched at Luna by unintentionally relocating Skylab to Luna has run out of fuel and deployed it's second stage spy satellite. The satellite is working normally but remains in a solar-synchronous orbit at approximately 1 AU from Sol.
-
By carefully placing waypoints on planetary bodies, Skylab has successfully deployed 2-stage scout missiles to all bodies in the inner solar system. The final stage of each missile was armed with an engineless active sensor buoy and all are apparently operating properly. Next test will be passive sensor buoys followed by geo and grav survey buoys.
-
Again, using waypoints carefully placed on planetary bodies and setting said waypoints as targets for Skylab's MFC, I have succeeded in deploying thermal and EM sensor satellites to all bodies in the inner solar system.
Next, Red Team will test the effectiveness of Blue Team's sensor satellites while Blue Team continues research into geo and grav survey sensors.
-
Fearing Blue Team's comprehensive satellite network, Red Team has developed the following interplanetary survey vessel:
Alexei Leonov class Survey Ship 24,999 tons 297 Crew 1,310.3 BP TCS 500 TH 75 EM 0
150 km/s Armour 3-76 Shields 0-0 HTK 134 Sensors 0/0/0/1 DCR 37 PPV 57
Maint Life 9.03 Years MSP 3,004 AFR 185% IFR 2.6% 1YR 66 5YR 995 Max Repair 135.16 MSP
Hangar Deck Capacity 375 tons Cryogenic Berths 400
Kapitan vtorogo ranga Control Rating 2 BRG SCI
Intended Deployment Time: 84 months Flight Crew Berths 60 Morale Check Required
Red Team Conventional Engine EP18.75 (4) Power 75.0 Fuel Use 30.81% Signature 18.75 Explosion 7%
Fuel Capacity 1,400,000 Litres Range 32.7 billion km (2524 days at full power)
Quad Red Team Gauss Cannon R200-100 Turret (1x8) Range 20,000km TS: 1000 km/s Power 0-0 RM 20,000 km ROF 5 1 1 1 1 1 1 1 1 1 1
Red Team Beam Fire Control R20-TS1250 (1) Max Range: 20,000 km TS: 1,250 km/s 95 90 85 80 75 70 65 60 55 50
Red Team Active Search Sensor AS10-R500 (1) GPS 500 Range 10m km Resolution 500
Red Team Active Search Sensor AS1-R1 (1) GPS 1 Range 1.3m km MCR 113.5k km Resolution 1
Red Team EM Sensor EM0.1-0.5 (1) Sensitivity 0.5 Detect Sig Strength 1000: 5.6m km
Red Team Thermal Sensor TH0.1-0.5 (1) Sensitivity 0.5 Detect Sig Strength 1000: 5.6m km
Geological Survey Sensors (1) 1 Survey Points Per Hour
Strike Group
1x Krivak SA Scout Speed: 40 km/s Size: 2.48
1x Krivak SE Scout Speed: 40 km/s Size: 2.48
1x Krivak ST Scout Speed: 40 km/s Size: 2.48
This design is classed as a Military Vessel for maintenance purposes
Each parasite scout craft carry a copy of their mothership's sensor array. The -SA variant carries an active sensor, the -SE carries an EM, and the -ST carries a thermal sensor. The Alexei Leonov class was designed to perform a comprehensive geological survey of the Sol system and only a single ship will be constructed. Results of the AL's survey, and detection of any potential Blue Team targets, is pending...
-
Red Team has deployed the Alexei Leonov to Earth orbit. Leonov's active sensors have been engaged and all of Blue Teams sensor satellites (1x each of active, thermal, and EM) are clearly visible to Leonov as well as Blue Team's shipyard complex, Skylab, and ground populations. Leonov can also detect Blue Team's active sensor satellite in orbit around Luna, however the passive sensors also in orbit around Luna remain undetected.
Due to a planning oversight, Alexei Leonov must remain docked in overhaul until additional ground-based maintenance facilities can be completed and orbital shipyards expanded. Once capable of leaving Earth orbit, Leonov will begin a geological survey of the solar system.
Meanwhile, Alexei Leoniv is clearly visible on Blue Teams active, thermal, and EM sensors. Plans are in motion to develop and deploy a network of geological survey satellites while Leoniv remains in overhaul. Blue Team may yet complete surveying the Sol system before Red Team. More to follow...
Attached are screenshots of Red and Blue teams tactical maps near Earth orbit.
-
Much to the dismay of Red Team and the crew of the Alexei Leonov, Blue Team's Skylab has successfully deployed geosurvey scout missiles to all major planetary bodies in the inner solar system. The crew of the Leonov could do nothing but watch as the missiles raced away from Earth, and quickly lost sight of the missiles on their onboard sensors. Blue Team also deployed a geo-scout missile to the asteroid Ceres in hopes of finding mineral deposits on this unusually large asteroid. It is expected to take several years for these geo-scout missiles to complete their surveys.
Unfortunately, Blue Team will not be able to continue to use it's geo-scout missiles to survey the planets in the outer solar system. While the missiles have more than sufficient range and endurance, Blue Team cannot develop a longer ranged missile fire control than that already installed on Skylab. Therefor, a mobile survey ship must be developed to complete the surveys of the outer planets. Blue Team will next develop it's own interplanetary survey craft to compete with Red Team's Alexei Leonov.
-
Red Team has completed overhauling the Alexei Leonov, and the ship prepares to depart Earth orbit for a year long geological survey tour throughout the inner solar system as well as Jupiter and Saturn.
Blue Team's geosurvey satellites are beginning to return survey data. So far, significant mineral deposits have only been found on Mars, however not all satellites have yet completed their surveys. Blue team has begun development of it's own interplanetary survey ship, Discovery II, which will complete the geological survey of the solar system. This ship will also mount gravitational survey sensors in addition to geological sensors, a technology which Red Team has yet to develop. Provided that a suitable jump point can be located, Blue Team next plans on developing a jump engine capable of propelling a ship to a distant star system. Further surveys will then commence in whatever new systems can be reached.
-
Alexei Leonov has successfully completed surveys of the inner solar system as well as Jupiter and Saturn. Red Team confirmed Blue Teams reports of mineral deposits on Mars and also new major deposits on Venus. Blue Team confirmed Red Teams survey results on Venus within a month. Red Team also discovered several minor mineral deposits on several of the moons of Jupiter and Saturn.
Blue Team lost tracking of Leonov beyond the orbit of Mars due to limitations of Skylab's sensor arrays. Red Team noticed this and plans on conducting additional probing tests of the capabilities of Skylab's sensors in future missions, particularly with Leonov's complement of scout ships.
Blue team continues to develop their new survey ship Discovery II.
-
I don't think fire control range matters when targeting waypoints. You have to have a fire control to set the target, but the tiniest little 5 ton FC can launch a missile at any waypoint at any distance (at least a few versions ago when I did it, don't think it's changed)
-
I don't think fire control range matters when targeting waypoints. You have to have a fire control to set the target, but the tiniest little 5 ton FC can launch a missile at any waypoint at any distance (at least a few versions ago when I did it, don't think it's changed)
I will test and post back. I need a grav survey ship no matter what though since I can't mount grav survey sensors on a missile.
-
Blue Team has finalized their design of the new Discovery II survey ship:
Discovery II class Survey Ship 25,000 tons 741 Crew 3,619.3 BP TCS 500 TH 160 EM 390
320 km/s Armour 2-76 Shields 13-325 HTK 126 Sensors 250/250/1/1 DCR 25 PPV 4
Maint Life 7.61 Years MSP 14,342 AFR 200% IFR 2.8% 1YR 436 5YR 6,544 Max Repair 500 MSP
Hangar Deck Capacity 250 tons Troop Capacity 250 tons Drop Capable Magazine 19 Cryogenic Berths 1,000
Captain Control Rating 3 BRG ENG SCI
Intended Deployment Time: 60 months Flight Crew Berths 40 Morale Check Required
Blue Team Commercial Nuclear Pulse Engine EP80.0 (2) Power 160.0 Fuel Use 5.76% Signature 80.0 Explosion 4%
Fuel Capacity 400,000 Litres Range 50 billion km (1808 days at full power)
Blue Team Alpha S13 / R325 Shields (1) Recharge Time 325 seconds (0 per second)
Blue Team Size 1 Missile Launcher (1) Missile Size: 1 Rate of Fire 30
Blue Team Size 3.0 Missile Launcher (1) Missile Size: 3 Rate of Fire 55
Blue Team Missile Fire Control FC2-R1 (2) Range 2.5m km Resolution 1
Blue Team ICBM (2) Speed: 200 km/s End: 47.4m Range: 0.6m km WH: 1 Size: 1 TH: 1/0/0
Blue Team IPBM (2) Speed: 200 km/s End: 26.7d Range: 460.8m km WH: 1 Size: 1 TH: 0/0/0
Blue Team Scout Missile IV - Active (1) Speed: 67 km/s End: 1,508.4d Range: 8,692.9m km WH: 0 Size: 3 TH: 0/0/0
Blue Team Scout Missile IV - EM (1) Speed: 100 km/s End: 1,508.4d Range: 13,032.8m km WH: 0 Size: 2 TH: 0/0/0
Blue Team Scout Missile IV - Thermal (1) Speed: 100 km/s End: 1,508.4d Range: 13,032.8m km WH: 0 Size: 2 TH: 0/0/0
Blue Team Spy Satellite II - EM (2) Speed: 0 km/s End: 0m Range: 0m km WH: 0 Size: 1 TH: 0/0/0
Blue Team Spy Satellite II - Thermal (2) Speed: 0 km/s End: 0m Range: 0m km WH: 0 Size: 1 TH: 0/0/0
Blue Team Spy Satellite III - Active (2) Speed: 0 km/s End: 0m Range: 0m km WH: 0 Size: 2 TH: 0/0/0
Blue Team Active Search Sensor AS130-R100 (1) GPS 50000 Range 130.9m km Resolution 100
Blue Team Active Search Sensor AS223-R500 (1) GPS 250000 Range 223.9m km Resolution 500
Blue Team Active Search Sensor AS28-R1 (1) GPS 500 Range 28.2m km MCR 2.5m km Resolution 1
Blue Team EM Sensor EM50-250 (1) Sensitivity 250 Detect Sig Strength 1000: 125m km
Blue Team Thermal Sensor TH50-250 (1) Sensitivity 250 Detect Sig Strength 1000: 125m km
Geological Survey Sensors (1) 1 Survey Points Per Hour
Gravitational Survey Sensors (1) 1 Survey Points Per Hour
Strike Group
1x Stiletto Boarding Transport Speed: 1921 km/s Size: 5
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 Discovery II is a considerable improvement over Red Team's Alexei Leonov. The Discovery II travels at over twice the speed of the Leonov, has 5/3 the range, is capable of conducting both geological and gravitational surveys, mounts a more capable weapon system, much better sensors, and can also carry troops for ground based geosurvey operations. Additionally, Blue Team developed the Stiletto boarding transport to accompany the Discovery II should the Alexei Leonov attempt any aggressive maneuvers:
Stiletto class Boarding Transport 250 tons 6 Crew 22.2 BP TCS 5 TH 10 EM 0
1921 km/s Armour 3-3 Shields 0-0 HTK 1 Sensors 0/0/0/0 DCR 0 PPV 0
Maint Life 19.34 Years MSP 25 AFR 5% IFR 0.1% 1YR 0 5YR 2 Max Repair 6 MSP
Troop Capacity 100 tons Boarding Capable
Lieutenant Commander Control Rating 1
Intended Deployment Time: 1 days Morale Check Required
Blue Team Nuclear Pulse Engine EP9.60 (1) Power 9.6 Fuel Use 876.85% Signature 9.60 Explosion 15%
Fuel Capacity 2,000 Litres Range 0.2 billion km (23 hours at full power)
This design is classed as a Fighter for production, combat and planetary interaction
The Stiletto can transport a boarding party of well armed marines onto any ships similar to the Leonov, should tensions between Red and Blue team escalate. Combined with the potent missile armament of the Discovery II, it is expected that the Leonov will maintain a safe distance.
Additionally, Blue Team discovered that by targeting it's missiles at waypoints placed on distant planetary bodies, even those located outside of MFC range, it can successfully deploy sensor satellites to distant locations. As a test of this deployment scheme, Blue Team launched several geosurvey missiles at Jupiter and the Galilean moons. All 5 sensors deployed flawlessly and have started providing useful survey data to Blue Team.
With these developments, Red Team is scrambling to advance it's knowledge of jump point theory and gravitational survey sensors. Perceiving a significant lack of defensive capability with the deployment of Discovery II, Red Team is beginning development of several new fighter-sized ships with various weapon systems and combat capabilities. In the meantime, Alexei Leoniv will continue geological surveys of the remaining un-surveyed bodies in the solar system, avoiding Discovery II when necessary.