Jump to content

Robin Patenall

Members
  • Posts

    125
  • Joined

  • Last visited

Everything posted by Robin Patenall

  1. Reported Version: v0.2.1 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 11 (64 bit) | CPU: AMD Ryzen 9 5900X 12-Core Processor | GPU: NVIDIA GeForce RTX 3070 | RAM: 65450 Mb Description: I believe (99.9%) that I caught the Starlab producing samples / data for the wrong biome during time warp. I had a Starlab in a low polar orbit of Kerbin (about 113km) I had done the experiment for Water, Ice and Desert biomes successfully I was doing the experiment for the Moutains biome ("Running requires Mountains") I was at 10x time warp The experiment timer reached zero when I was in a region where the biome changed rapidly Instead of getting data / samples for the Mountains biome I got data / samples for the Highlands biome I had not been running the experiment for the Highlands biome. I was able to repeat the experiment for the Mountains biome and complete it successfully. I suspect that there may be an issue with the Starlab producing data / samples for the biome that the vessel is currently over when the timer reaches zero, rather than the biome that it was running the experiment for and my vessel changed biome at the very last instant, giving me the erroneous science. This is likely to be very difficult to replicate, so I am submitting this in hope that a dev may have a quick inspection to see if there is anything obvious and if anybody else notices the issue they can add to this post.
  2. If you mean my Moho probe, then yes, the decouples were cross-feed enabled and I went around manually moving fuel from the outer tanks to the inner core after every burn (I wish they'd fix the bug in the resource transfer UI as I'm running unmodded at the moment). I didn't use fuel lines much in KSP1 (cross-feed and fuel priority did a lot of the work) and may not have even unlocked them when I launched it. You only really need them if you are doing things in a hurry, if you have time between burns they are unnecessary. I did have issues with dV calculations in the VAB and spent some time building it without decouples, checking the dV, reducing the fuel levels to reduce the dV to each post-burn level and removing the drop tanks to simulate decoupling. There were actually another pair of the 2.5m small tanks on the top of the side tanks that help fuel the initial orbital insertion and the first 250m/s of periapsis kick. It's on it's way back to Kerbin now, I did the initial Moho to Kerbin orbital height burn and the inclination burn at Kerbol AP to put it in Kerbin's plane but It's having to do a couple of Moho / Kerbin orbit loops to get everything aligned for the final rendezvous burn.
  3. Ah, I realise I should have been clearer. It's my first in KSP2, so not as impressive. I had quite a station around Moho in KSP1 (ISRU and everything), but not having any mods running in KSP2 (specifically anything to make the manoeuvre plans easier to adjust) it was harder than I remember
  4. Today I reached my first non-Kerbin celestial body ... (Editedd for clarity: in KSP2, I've done most places in KSP1) Moho! Don't judge me, I'd just unlocked nuclear engines and I was coming up on the annual reliable Moho transfer window with an age to go before any window for anywhere else (i.e. Duna). All I have on board is environmental science so I'm only going to get 540 science points, and I'm going to have to get it back for even that, but I'm pretty tapped out for Kerbin. I did include a relay satellite to support future missions. (Objects in image are closer than they appear)
  5. The Kerbal Space Centre press department presents... "Mun Lab 1" This is a very basic space station used to support a detailed survey of the Mun and recovering science and samples from a variety of sites across the surface. This is possible as the station was placed in a polar orbit, allowing landings to be performed anywhere. It is based around a MK1-3 command pod that has been reconfigured as sleeping quarters, a MK2 lander can reconfigured as living / work space and tanks holding the Methalox fuel for the lander, which you can see is docked to the forward spinal docking port. Docked to the dorsal and ventral docking ports are two crew return modules that can return a kerbal back to Kerbin. One of these has just been brought up by the latest refuelling mission which you can see in the background. This is the first flight of the V2 refueller model which added a parachute and the ability to detach the command bay so it should be able to act as a sample return system so we don't need a kerbal to hand deliver any collected samples. With the current refuelling mission the tanks are about 75% fuel giving Mungee Kerbal, the current occupant, the capacity for about 16 landings. Mungee Kerbal was joined for a short time by Bob Kerbal to help set up all the systems and for Bob to test the lander. Bob did this by landing in an area of the Mun that was extremely boring, so boring in fact that no kerbal should ever go there again. Any data and samples he collected while on the surface, and immediately returned to Kerbin with (in the crew return module he came up in), were just as boring and, according to public records, were immediately thrown out before anybody else saw them. Since Bob left, Mungee has visited the surface four times, collecting vital scientific data from diverse regions of the Mun.
  6. I've done a couple of docks recently and the only actual bug I noticed was that on one attempt my craft suddenly flew away from each other, which I'm not sure is a docking issue but a 'craft in close proximity' issue. I did find the markers on the navball a lot more jittery than in KSP1 which is a problem with my style of slow approach docking (<0.3m/s) and SAS target lock did send me spinning. Docking without mods (in KSP1 I used "Navball docking alignment indicator", "NavHud" and a docking camera) was a bit more difficult and took me a couple of tries, but I'm out of practice. I'm more surprised by the "teleport a meter and adjust attitude by 30 degrees" style of docking that KSP2 has over the bouncy magnets of KSP1. I do think the minimum KSP2 should have is the "parallel to docking port" marker on the navball that "Navball docking alignment indicator" generates, that makes it much easier to learn the skill.
  7. Reported Version: v0.2.1 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 11 (64 bit) | CPU: AMD Ryzen 9 5900X 12-Core Processor | GPU: NVIDIA GeForce RTX 3070 | RAM: 65450 Mb Low priority issue that Kerbals (or at least Bob) appear to twerk when in shallow water. What I did: Flew simple rocket West from KSC and splashed down in shallow water (in beach region) EVA'd kerbal and took crew report and surface sample (splashed down / beach) Swam to water line to repeat science on dry land (landed / beach) Kerbal stood up when water was shallow (knee to waist height) When not controlling kerbal, it would perform squats / twerk Probably cycling between "I'm in water so I need to switch to swim mode" and "The water is too shallow so I need to switch to walk mode" Walking to dry land or deeper water stopped the issue What I'd expect: The kerbal to make up it's mind whether it needs to swim or stand Or Situational music to be added that the kerbals can dance to. Included Attachments: KSP2Bug1.mp4
  8. Perhaps for Eve there should be a couple of missions before the "Land and return 10 Kerbals" one. I'm thinking of "Land a probe on Eve and send back data" and "Retrieve surface samples from Eve" which would at least provide a few stepping stones in the difficulty levels.
  9. I had a contract pack in KSP 1 that did something like this and I hated them. It was always "take a surface sample at this point" a few km from a Kerbal, then "take a surface sample at that point" a few km further away and so on. More than once I had to go rescue a Kerbal that didn't have enough EVA fuel to return or got annoyed that I'd started off with a rover to get to the first few spots but needed a lander to get to the last one, where it would have been better to do them all with a lander if I had known. A contract / mission really needs to be upfront about what needs to be done to be completed so the player can choose whether they want to track it.
  10. Generally, if you are having problems affecting a small part (which doesn't have other parts attached) using EVA construction it is because it is the root part of the vessel. This is particularly an issue with docking ports and decouplers as if you detach a section of a vessel that has the root part in it then the root part of the other half tends to be the decoupler / docking port. The big problem is that there is no easy way to re-root your vessel while in EVA construction, the closest thing is to dock / grapple it with another vessel that has a higher priority (so the root part of the combined vessel is the original root part of the other vessel) and then you should be able to affect the part you were trying to, but this is a bit of a hit of miss thing. Yes, do make sure that you have that all correct. I managed to get to Jool to find that I'd left my spare parts (including several negative gravioli detectors) behind. Of course I noticed this as I realised that I'd accidentally put two barometers instead of a barometer and a gravioli detector on one of my landers. It was recoverable but I would have been really annoyed if I'd left one of the biggest sources of science behind.
  11. It's normal. Somewhere in the settings, there are commnet occlusion modifier settings that sets the size of the commnet occluder based on the planet/moon size. By default the settings allow the commnet links to pass through the edge of the planets/moons slightly as you've noticed. You can change the settings (one for bodies with atmosphere, one for bodies without) to 1.00/100% if you want to stop this happening.
  12. I seem to be missing the small icons / wingdings all over the forums (e.g. the alert bell and the messages envelope). I suspect that this is because I'm getting 404s for all the Font Awesome files https://forum.kerbalspaceprogram.com/uploads/set_resources_17/6124cbf62e7d0ac97bcb319cb54179a7_fa-solid-900.woff2 https://forum.kerbalspaceprogram.com/uploads/set_resources_17/6124cbf62e7d0ac97bcb319cb54179a7_fa-brands-400.woff2 https://forum.kerbalspaceprogram.com/uploads/set_resources_17/6124cbf62e7d0ac97bcb319cb54179a7_fa-regular-400.woff2 https://forum.kerbalspaceprogram.com/uploads/set_resources_17/6124cbf62e7d0ac97bcb319cb54179a7_fa-solid-900.ttf https://forum.kerbalspaceprogram.com/uploads/set_resources_17/6124cbf62e7d0ac97bcb319cb54179a7_fa-brands-400.ttf https://forum.kerbalspaceprogram.com/uploads/set_resources_17/6124cbf62e7d0ac97bcb319cb54179a7_fa-regular-400.ttf https://forum.kerbalspaceprogram.com/uploads/set_resources_17/6124cbf62e7d0ac97bcb319cb54179a7_fa-brands-400.ttf I'm running Chrome (Version 119.0.6045.105 (Official Build) (64-bit)) under windows and I've tried disabling my cache, with no change
  13. Somewhat annoyingly (but I understand the reason why), the mod hard-codes the profession for each named character and Applejack is an engineer. It's not even the obvious Unicorn = Scientist, Pegasi = Pilot, Earth pony = Engineer mapping and I spent hours trying to why Fluttershy didn't want to be a pilot and The Great and Powerful Trixie wasn't a scientist. Alas, I needed 3 scientists, 2 pilots and an engineer so I'd have 5 mission specialists in the of pilot / scientist combinations and more than 6 crew would have necessitated a different set of emergency return pods in the event that I didn't have the fuel to capture and circularise when they returned to Kerbin.
  14. Thank you for the clarification. I didn't end up using it in the end, leaving the extra fuel in my Laythe lander's long range tanks, which gave me the opportunity to land on Laythe near the pole, then take off again, re-dock to the tanks, refuel and then land at the planned landing spot near the equator. I really didn't need to be as miserly with the fuel as I was (as will become rather obvious by the end, I'm pretty sure I've seen people start with less dV that I ended with), it was the oxidizer I'd have preferred to have more of.
  15. I certainly hope its not against the spirit, as in my recent run I was very careful to run every experiment three times if possible, twice for return to Kerbin and once for loading into a mobile processing lab (which didn't count towards my score as it was transmitted). The fact that you get some extra science for re-runs of some experiments has never been hidden, it just needs planning in bringing something that can store the science (say multiple experiment storage containers or remote guidance units) and bring it home. I got quite practised at running science bay / mystery goo / surface sample storing it all in one container, restoring the experiments and doing it again (twice) for the other containers. Doing this for all the Bop and Pol biomes and four landed / splashed down situations on Laythe were a significant contribution to my final total.
  16. Hi @JacobJHC I’ve eventually completed my Jool 5 entry. I believe it matches the criterion for a Jebediah level DLC entry. I’ve done a mission report thread and the imgur album can be found here. I apologise for the length Summary Which game versions did you use? KSP 1.12.5.3190 Breaking Ground (BreakingGround-DLC 1.7.1) Making History (MakingHistory-DLC 1.12.1) What mods did you use, if any? Visual, sound and informational only, so I hope I’ve managed a DLC rating. Full list in the spoiler. How many Kerbals are on the mission? None Okay, how many crew are on the mission? Six, from left to right: Pinkie Pie, engineer and astrodynamics Twilight Sparkle, scientist and mission specialist for Laythe. Landed on Laythe. Fluttershy, scientist and mission specialist for Bop. Landed on Bop and Pol. Bon Bon, scientist and mission specialist for Vall. Landed on Tylo and Vall. Rarity, pilot and mission specialist for Pol. Landed on Vall, Bop and Pol Rainbow Dash, pilot and mission specialist for Tylo. Landed on Tylo and Laythe How many launches were needed to start your mission from Kerbin? Seventeen (half of which were fuel) How much did your mission cost? 2,380,480.70 funds Did you need a refuelling mission? Oh God, no. The mission was seriously overbuilt, 8.6km/s in deltaV for the return. Did you bring additional stuff like satellites, rovers, etc? Three relay satellites with RA-100 antennas Science satellite to get science near Jool and flying high at Jool Important photos Random Notes The stock deltaV / TWR calculator really didn’t like the ship, the one in KER was much more reliable (which is why I tended to leave that tab open) I got better at keeping the resources tab open, but I did keep forgetting. I hope there’s enough info, I do have more screenshots if needed. The Mobile Processing Lab is very OP if you have time. I was surprised by the amount of science I recovered. I put this down to: Collecting each experiment twice for return Taking the telescope with me Being completionist on Pol and Bop Doing polar orbits of Laythe and Vall “Landing” in four of Laythe’s biomes / situations I can think of dozens of ways I could have done better.
  17. Epilogue So there we are, with our hooves back on Kerbin (metaphorically, we have a metre and a bit to go once they wheel a set of stairs across to us). We’ll be spending some quality time in quarantine to recover from our trip and build back our immune systems. Twilight managed to not run off when the technicians from the research and development department unloaded the samples and experimental results. She was making puppy dog eyes in their direction (the samples, not the techs) and will probably be burning up the communication channels between medical and R&D as soon as the doctors stop prodding her. We did get one piece of new. The technicians did a quick inventory of the science that we returned and came up with a total of 61174.6
  18. Going Home (Landing) Being back in LKO after eleven and a half years is an amazing experience. Seeing Jool’s moons up close was wonderful, but being home is something special. We could land with the emergency return capsules, they are good enough that we could probably bullseye the KSC, but we’d have to dump all the fuel onboard (they were designed that we could perform a breaking burn and safely re-enter Kerbin’s atmosphere from the Jool-Kerbin transfer orbit). It would be very wasteful, so the KSC is sending up a remote piloted passenger SSTO to pick us up. A quick flight and a boost put the space plane in a 76km orbit. The space plane was rendezvoused with what’s left of the Emerald Star. We didn’t have a compatible docking port, so the SSTO was just parked nearby and our crew went on EVA to board it. During this, Twilight very carefully transferred the two boxes of samples and experimental results to the space plane. If we send people back up (and Twilight said “We’d better, I’d barely started analysing the third set of data in the lab”) we’ll have to send up a docking port that will match the one on the space plane, or possibly a new segment and use the Emerald Star’s habitation module as the core of a space station. A push back using RCS and a quick retrograde burn sent us back into Kerbin’s atmosphere. A few minutes later, we touched down and we were home.
  19. Going Home (Travelling) 1 year, 368 days after departing Laythe Once we left Jool’s sphere of influence, the pilots and I went into hibernation for the journey home. The science nerds Bon Bon, Fluttershy and the Science Nerd stayed awake so that they could begin processing the extra results and samples in the lab. At the moment Rainbow Dash and Rarity are still asleep, but I’m up to make an inclination change to make the Emerald Star’s orbital plane match Kerbin’s. I’m not sure that Twilight actually noticed that I’ve been hibernating as all I got was a “Morning Pinkie” when she saw me. I’ve got some maintenance to do before I re-enter hibernation for about 150 days when we need to for the major deceleration burn. 2 years, 98 days after departing Laythe Big burn time, we knocked off just under 1500m/s and brought our apoapsis down to just outside Duna’s orbit. This is easier to do in deep space as our TWR is still quite low and reducing out velocity now will make it easier to capture at Kerbin once we loop around Back to hibernation for another year and a half. 3 years, 378 days after departing Laythe We’re home. After almost four years after leaving Laythe, we are back. We did an initial capture burn at Kerbin periapsis and brought our apoapsis to within the Mun’s orbit. Then performed a few burns to bring us into a circular 100km orbit.
  20. Going Home (Jool) So, we’ve left. Technically, we could have dropped the SSTO to Laythe again, but unless I wanted to test if Rainbow Dash can manage a water take off (I don’t) there isn’t anywhere to land that would have been interesting. For a minimum deltaV return, we could have waited for a launch window to Kerbin, but as we had so much fuel we used a slightly more expensive “launch now” plan. One thing I did do was to fit the Clamp-o-Tron docking port to the node of the drive truss we undocked the habitation module from. This was to allow us to move the SSTO there and better balance around the thrust vector generated by the drive core that we are leaving behind. The manoeuvre plan is to eject from Jool retrograde, lowering our periapsis with respect to the sun until it meets Kerbin’s orbit. A burn there will set us up for a Kerbin rendezvous and lower the velocity that we will have to capture at. Note, that we are splitting the ejection burn and the 264m/s burn we had queued up is just the initial kick. We waited to get into position and burned, first to raise out Laythe apoapsis and then to eject from the Jool system Tylo was in a position to give us a slight helping hoof as we left. What was left behind Before we left Jool, we used the relay satellites to remote control the SSTO, undocking it from the ventral docking node and moving it to the new forward node. The drive truss, the SSTO, the lander and the engineering module were all pushed into a much neater 250km circular orbit by the drive core using some of its remaining fuel. This will make it easier if future missions want to make use of it.
  21. Science on Crater Island With the total amount of fuel we have left over, I gave Twilight the option of a second extra science mission. I noticed that, on Laythe, there is a crater with an island in the centre that Twilight had highlighted as having two interesting biomes, the bay itself and the island. It’s about 15 degrees above Laythe’s equator, which is beyond the SSTO’s ability to adjust its inclination. It might be able to reach it going down using its ability to fly but there wouldn’t really be enough deltaV once it returned to orbit to guarantee that it could match inclination with the Emerald Star and rendezvous again. The solution I had was to undock the drive core and engineering module and have me fit a docking port that was compatible with the SSTO to the front. It wasn’t pretty but it allow the drive core to do the inclination change for the SSTO (about 400m/s) to allow its orbit to pass over crater Island and, once Twilight and Rainbow Dash landed, undo the inclination change and rendezvous with the Emerald Star. Once the inclination change was made a descent was plotted that would bring the SSTO down at its most northerly point and our intrepid team needed to wait a few orbits for the island to reach the target point near local dawn. The descent went fine and Twilight was able to run some of the science experiments while flying over the bay. Rainbow had learnt her lesson about unexpected landings and managed to make a short touchdown on the shores of the island Twilight ran her last set of science experiments quickly so that Rainbow Dash could take off again before they drifted too far from the orbital plane of the drive core. Once in orbit, Rainbow rendezvoused with the drive core. Now docked, they used the drive core to match inclination with the Emerald Star, rendezvous and dock.
  22. Science near Jool Having discussed it with Twilight, I okayed the mission to near Jool space with the restriction that nopony is to be on untethered EVA below 500km altitude, everypony must be in the engineering module or strapped into a command seat. This means no resetting of science experiments. Once given the go ahead, Twilight spared no time in grabbing Rainbow (apparently the great water landing debacle had been forgiven), getting in the lander and undocking. Rainbow plotted an ejection that would take them down and just scrap Jool’s upper atmosphere. Once done she’ll raise the periapsis slightly and wait a few orbits until they intersect Laythe again. Once they reached near Jool space, Twilight ran all the science experiments while Rainbow did crew reports. After they had finished, they were nearing the altitude at which Jool’s upper atmosphere starts so Twilight got strapped in and set up the experiments to run. After the lander’s altitude passed 500km, Twilight unstrapped herself and moved to the engineering module to pass a few days until they intersected Laythe’s SOI and Rainbow could show off by repeating Rarity’s aerobraking manoeuvre and redocking with the Emerald Star.
  23. Squeezing out more Science Now that all the parts of the planned mission are complete and everypony is in one place, it is time to take stock of what resources we need to get home and what resources we have in addition to that. The first step was to reconfigure the Emerald Star for the return trip. The least obvious change was that the habitation module has been rotated to make ‘forward’ towards the drive truss, this allowed us to take the full drive core and move it into a position to push the habitation module home. All the LFO tanks on the emergency return capsules were topped off as were the LF tanks in the drive core. Some quick calculations show that we have plenty of fuel to get home, in fact we have just a shade under 8.6km/s. We could probably get home with half that amount and not be overly concerned. The remaining fuel comes to 5300 units of liquid fuel, 1423 of oxidizer and 1300 units of monoprop. This comes to enough to fuel the SSTO to design limits, the lander to about 2/3rds full and have enough liquid fuel in the last drive core to give it 2.5km/s of deltaV. I did do a bit more engineering work. I moved the telescope back to the science satellite and took the RCS thrusters that I originally took off the SSTO’s long range tanks and fitted them to the back of the drive core we’ve been using to ferry the lander about. We have massive amounts of monoprop on the drive truss, which we will be leaving here at Jool, and the drive core usually uses LFO for RCS which we have a limited amount remaining. Switching to monoprop (assuming the engineering module with its tanks is left attached) will allow more use out of it. We do need to decide if we use any of the resources we have left for more science. My thoughts were: Pol and Bop were studied pretty much completely by Rarity and Fluttryshy. Tylo is right out, we might be able to land but we’d never take off again and doing anything off equatorial, even in space, is probably beyond us. The SSTO can visit Laythe again but anything too inclined may be a problem and there isn’t much left on the equator unless we want to see if Rainbow Dash can launch from the ocean. We might be able (pulling some LFO from the return capsules) to return to Vall and land somewhere on the equator (specifically not he Vall henge site) So I’m off to see what Twilight thinks. Addendum Looks like Twilight had another idea. Use the current lander configuration and launch it toward retrograde to allow her to collect science from the space near Jool, that seems reasonable and doable, and she wants the periapsis to be low enough to scrape Jool’s atmosphere. That needs thinking about.
  24. Pol Anomaly and Science Apparently, it’s not just Griffins that have eagle eyes. While helping Rarity with running the Pol science experiments, Fluttershy spotted the anomaly halfway up the mountain. If you have good eyes, you might be able to see it just above the top of Rarity’s helmet. Given the low gravity of Pol, it was at least conceivable that Rarity might be able to put the lander down on the side of the mountain but it wasn’t all that far, so Rarity hooked up the extra EVA fuel tanks to her EVA pack and just flew over there. When she arrived, she looked for a good landing point just up from the anomaly and found a very interesting rock sticking out from the ground that she could alight on. Well, Rarity found the anomaly, Rarity documented the anomaly, Rarity took samples from the anomaly and Rarity decided to otherwise ignore that the anomaly existed. Something I agree with. Once Rarity returned from the thing that she was pretending didn’t exist, she and Fluttershy took off and biome hopped to the nearby highlands and lowlands to check them out and then a longer hop to the north pole. Once they completed all the science on Pol, they took off and rendezvous with the drive core. Returning from Pol It turns out that both of our pilots are crazy. Once Rarity and Fluttershy had re-docked the lander to the drive core, they planned a reduced deltaV plan to arrive at Laythe using a gravity assist at Tylo to lose energy. Once they arrived at Laythe, Rarity did a burn at periapsis to capture into an elliptical orbit. It was at this point that Rarity showed her inner Rainbow Dash and decided to save some more detlaV by aerobraking using Laythe’s atmosphere. Now, she did this very carefully, taking many shallow passes and nothing showed anything other than slight temperature warnings. Admitally, I’d have preferred that the infrared telescope didn’t hang out in a plasma stream for a few minutes every hour or so for a couple of days, but it wasn’t needed anymore and it wasn’t damaged in any way. Eventually Rarity reduced the orbital apoapsis down to match the Emerald Star’s orbit and then raised the periapsis to rendezvous with it. The docking was rather tight and I’m glad that Rarity was piloting rather than Rainbow Dash. Rainbow would have managed the docking but I don’t know how long I would have had to be out on EVA touching up the paintwork. Even with Rarity in control, it was a tight squeeze.
×
×
  • Create New...