Jump to content

HorusKol

Members
  • Posts

    61
  • Joined

  • Last visited

Reputation

23 Excellent

Profile Information

  • About me
    Rocketeer

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. The SCANsat contracts aren't unlocking for me. KSP 1.3.x SCANsat 18.0 I've also got ContractConfigurator installed There are 5 contracts available in the mission control building, but they have red x's and I can't accept any of them. I've unlocked the first radar scanner for the low resolution contract. The contract says all conditions are "met" - but no rewards are listed, and there is not accept/decline option.
  2. I started naming my remote probes "Tian-can" (pronounced Tin-can)...
  3. I was trying to not get overly technical. In any event - regardless of if the heat generated is from friction or compression, the outcome is the same: the faster your travel and the more dense the air you travel through will result in more heat being generated.
  4. Here's a non-mathematical description of what's happening: First - heating is from moving through the air. The amount of heating is determined from the speed of your craft through the air, and also the thickness of the air it is travelling through. But if you're entering at the same angle and starting at the same speed, why does the heavier craft heat more? Because it takes longer for a heavier craft to slow down - it has more momentum, so needs more time or denser air to slow down. So, your heavier craft takes longer to slow down when you first start into the atmosphere - this means more time at high speed to heat up your shield. It also means you are going faster as you pass further down through the atmosphere, so you are hitting thicker air at higher speed. At the end of it all - more time to decelerate plus travelling faster through thicker air means more heat buildup over time.
  5. Career with mods like ScanSat and RemoteTech, and contract packs for those and also space stations...
  6. From my view - NASA isn't much of a leader... especially not these days. It has always been subject to the direction of the government, and has been reliant on contracts with the Army, Air Force and Navy, as well as private contracts, to bolster it's public funding. Even with things like Voyager and Pioneer - a lot of those projects had a huge amount of input from outside NASA proper. That said, you can play the career game how you say - for example, I have my own progression I want to follow - and I pick the contracts that support that, so I am setting my own agenda. I do use Remote Tech and ScanSat, and the contract packs - I just figure that contracts for setting up communications networks are more like the guvmint providing funds to advance the space program rather than a private contract. I've not read much about the stock inclusion of communication networks or scans - I'm not sure how they will differ from the mods, but I like these mods and their restrictions/caveats/behaviours.
  7. But career doesn't force you to do any of that - it says "Move 3 kerbals, and get some funds and reputation for it" - it says "Click on this part there, and get some science for it". There is always the choice not to to do all the contracts offered. In fact, many of the contracts can be avoided (cue arguments of "well, what's the point"). Granted - I do feel there is something missing from career mode - that's why I use RemoteTech, and get contract packs, and the like. Maybe there needs to be a fourth mode added - either rename the current career mode to "contracts" or something, and bring in a new "space programme" mode... but then, that could easily end up being a highly restrictive sequence of launches and tests and missions... End of the day - there are many ways to play KSP - in fact, many ways to play each mode. The only wrong way to play KSP is to not have fun when doing so.
  8. I killed Jeb... Going for a Mun landing, and I realised in Kerbin orbit that I had no batteries and no solar panels... so, the attempt was aborted, and Jeb deorbited the return vehicle. All seemed good, with a pretty standard reentry, when suddenly the lander yawed crazily and ended up nose first doing about 2000 m/s at 30,000 m. Kerblooey Val bravely stepped up - she's in MunLander II (with solar panels and batteries) and is ready to leave low Mun orbit with a stackful of science. On the other hand - I discovered that I can get science from analyzing my ScanSat data (full scans of Kerbin, Mun, and Minmus).
  9. After much trial and error throughout the weekend, I finally got a Kerbin communications network running, and a dish pointing at Mun. I still haven't completed the contract for the communications network, though - because the 4th satellite is between the wrong ones (I thought between 1 and 3 - but the contract says between 2 and 3), so I'm having to wait for it to shift its apoapsis a bit before re-circularizing. It's taught me a lot about MechJeb, though - and I'm ready for getting networks around the Mun and Minmus. Meanwhile - Jeb's returning from a science-gathering flyby of Mun so I can unlock some more tech (like, bigger batteries and solar panels!)
  10. You could go further - like, tag ships as "Duna" to show only those craft you are sending or have orbiting Duna...
  11. Yeah - that's pretty much my tourist taxi design there - and your strategy of using body lift is something that I seem to have been honing in on by trial and error. Even when going at high-speed with the flames, I've angled my craft a little flatter than my retrograde velocity, and then more so as I start to slow down - this is all with SAS on, and Jeb seems to be able to hold it tight. Once I'm not longer supersonic, I turn SAS off and let the craft tumble a bit more - but maybe I should try and just flatten my trajectory even more to get more lift. Anyway - successful return last night, though it was close as I was at 2,000 metres before I'd slowed to 260 m/s. Might have more success now - thanks
  12. So, I had yet another a ship break up in the water because I was still going too fast to deploy chutes almost right down to the surface. I was coming in from an AP of about 80 km, and a PE of about 35-40 km, which seems to have worked most of the time before (although, in hindsight, those successful attempts might have been anywhere up to 100km/30km AP/PE) - with pretty much the same ship (capsule, crew compartment with tourists, and a heatshield). So I'm wondering if there's a decent rule of thumb to follow for re-entry to make sure my vertical speed drops to below 250m/s with enough time (altitude) for my chutes to deploy and slow me to 6m/s.
  13. ack - to late... oh well, I'm already in orbit and only one fly by the Mun needed to catch up to where I was...
  14. Well - ended another career last night. I was getting impatient with Kerbal Construction Time delaying new parts from research (yeah, I know I can warp - but then, that's 180 days of game time with the Kerbonauts twiddling their thumbs) - so I removed the module. When I restarted, the research was not unlocked, but the science had still been spent... So, career 4 begins.
  15. not as often as i'd like - my old gaming rig isn't doing well with KSP or some other games, and needs replacing. probably would get a launch in most nights, if I could
×
×
  • Create New...