Jump to content

Hotel26

Members
  • Posts

    1,823
  • Joined

  • Last visited

Reputation

2,725 Excellent

7 Followers

About Hotel26

Profile Information

  • About me
    Mad Scientist
  • Location
    Krakpotistan

Recent Profile Visitors

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

  1. Found a possible use for asteroids finally... Real estate development:
  2. I grounded my Minmus Dandelion fleet when a new pod arrived with an SSM (Surface Scanner Module) upgrade. So I needed to land a Nerfjet to pick up the 9 crew...
  3. Someone once scoffed at my equipping an improved version of Zephyr with wings. I thought, "yeah, you know, those wings only weigh 1t all-up." That's one less ton of payload possible. So what? I have a range of boosters; just pick the next biggest size!
  4. Bologna was a "working title", probably originating because my VAB team are perennially taking snack breaks... I hadn't come up with a more "official" sounding name by publication time, so.... If you want to take a look at what is inside, here's the link: Bologna. Heck, fly it to space!
  5. 12 hours without a post...? "My turn!" Project Bologna (zona non fumatori)
  6. The answer is "yes". But the question and answer would be more helpful if you also described your intention/purpose. Otherwise we're shooting in the dark. ("As an aircraft designer, I want to achieve... so how do I construct... so as to...?") This craft controls deployment angle of control surfaces: Hot Dog 2. In this case, those surfaces are the whole "wing", with the wing "angle of incidence" controlled via "Deployment Angle", similar to the usage of control surfaces as flaps. (Can provide more information if this is an unfamiliar area.) In the SPH, you can "Remove from Symmetry" if you wish to have asymmetric/independent control of e.g. control surfaces. Then bind whatever keys you want to each. You still have the option to bind a single key to a pair of independent surfaces such that that key then operates both simultaneously/equally. (I don't recommend doing this, but I don't know what you're trying to achieve.) For bigger wings (usual parts, non-control surfaces and this is how I interpreted your question), you'd have to use Breaking Ground (DLC) servos. It gets complicated fast from there...
  7. Easily. Orbital speed is around 550 m/s. You will need more than that, but not double. Or, see this: cheat sheet (scroll down to "Kerbal Space Program dV Map"), it says 580 m/s with an excellent ascent.
  8. Right. The Prospector had crew but the crew lines were deleted. The M700 Surveyor, for another example, was only a probe. Neither worked. I thought I had restart because the engines responded, but still no SAS. So, no cigar. What I've done instead is thrown in the towel and simply moved a replacement vehicle into position a few meters away. Now transferring crew and refueling from the ORB miner (pictured above). I'll destroy the dud and then Carry On Dauntless, as we say in the Space Force. (I do have to check it wasn't something to do with GUIDs somehow...)
  9. I can now report some success. The shot below shows a Scout Prospector in the foreground that I have now been able to revive. I deployed a Scout Mk2 expedition to LKO and stripped it down to just a similar Prospector component. Extracted that VESSEL from the save file. Diffed it with the broken one. First interesting difference was 'ctrl = False' in the broken one, which was 'ctrl = True' for the operational one. I don't know how it got that way, but possibly a ramification of the Time Travel. Yet to confirm that this is the case, the only case, for all of the rest of the 70, but I'm happy for the moment. If there's more to report, I'll post again here. You are correct; my error. The fresh save file contained all the assets contiguously, as I expected. (There were Space Objects in there, but not interspersed.) I selected those 70 in one slab and wrote them into an assets file. Those contents were then simply inserted into the Lab and Orbit save files at the end of the FLIGHTSTATE section for VESSELS. Copy-and-paste from one save file to two other save files. Just another day in the Operating Room -- until you slip with the scalpel and nick an aorta...
  10. About the OP, the mission is not being counted a failure at this time. Each targeted body (9) has received: 3x pBeep RA-2 polar relays 3x eBeep RA-2 equatorial relays 1x RA-100 'Meerkat' relay, polar elliptic 1x M-700 Surveyor, polar (with a couple of exceptions). All of the Commnet relays are operational with no further need for maneuvering. The M-700 Surveyors are able to Toggle Overlay (requirement). They do not need to maneuver. An Orbital Survey is to be re-performed in the new world (oversight), but my new Tardis ship is able to beam out (we are doing time-travel here, after all, folks) and dock to perform rectification. A number of those worlds have Scout Prospectors (M-4435 Surface Scanner equipped) which were expected to perform bonus missions and those are, sadly, unserviceable, although also considered dispensable.
  11. Overview: A fresh Sandbox world was created; Commnet activated; nine (9) expeditionary missions dispatched to a selection of bodies ranging from Moho out to Eeloo; creating a total of seventy (70) assets far out into a (highly-warped) future. Objective: Splice the 70 assets (relays & surveyors) into a) a Lab world (with Commnet) and b) an Orbit world (with Commnet) to provide both worlds with full relay capability, end-to-end. Problem: A small sample of assets shows they operate and are controllable in the Lab world but not in the Orbit world. Specifically, an M700 Surveyor, equipped with battery and OKTO is able to Toggle Overlay on demand in both worlds, but [T] will not activate SAS in the Orbit world. The Orbit world is showing Full Probe Control and 96% Signal Strength relayed to Kerbin. It is expected to work. Insight: current UT in the Lab world (which is a highly-warped system) may be in advance of the original, fresh world in which the missions were run. By comparison, the Orbit world UT has only advanced to Y3, D304. The spliced craft are finding themselves suddenly in the Far Antiquity. Comments: I suspect this problem is related to splicing craft far back in time. One effect of inter-world splicing I expect and have verified/confirmed is that the EPH (epoch) orbital parameter for the craft in question will get set to a near-current value (with a concomitant shift in orbital position for the craft) and that lastUT will also be updated sensibly. There should be no problem there. Crew members were removed in the operation. Science commentary, for example, has also been omitted. Only the VESSEL object itself in the craft file was beamed across. I am unable as yet to identify any specific failure related to the time-shift. The problem may be something else, e.g. difference in how the three worlds are configured? I will get to the bottom of this, I hope, but if anyone meanwhile is able to offer some clues or insights, I would be deeply appreciative. (And, yes, I do know this is a self-inflicted wound. In the name of Mad Science, you see...)
  12. Airport: Narita (NRT) Download: Narita to ./GameData/<your name>/Airports/Narita.zip and unzip. Body: Kerbin Lat: 47.57S Long: 127.85W Elev: 61m Description: An international gateway to the Far West. Welcome to the Occident. Notes: If ATC directs you to make a landing on "2-7-Right", please do ensure you use the one on the right -- and not the "other" 27R. Yoroshiku onegaishimasu.
  13. Yes, compare with Knowing that it can be done in KSP helps a lot (motivationally), but I still haven't pulled it off. I'll keep trying though. It seems all about horizontal motion < 1 m/s not more than about 1m or so above the ground.
  14. That's what I wanted: a very helpful existence proof! Thank you. Conclusion: It Can Be Done.
×
×
  • Create New...