LHACK4142

When: 1. You're 1 out of 3 people attending an optional talk at your robotics club on SolidWorks CAD 2. The "Move With Triad" function immediately reminds you of KSP.

When loading a save, save the game before reverting it. To explain more clearly, if it's day 1, you create save A, you advance to day 2, and load save A, day 2 should be saved.

n-18

As cool as this is, and as much as I want to like it, my cellist brain is crying out in tears... I've heard even more songs that have similar chord progressions to this one, such as Baby by justin bieber. I guess I should pick up my music theory book again.

Nice to see you back!

I can't- it's grayed out as if the rover's a probe without a KSC connection. That's why I mentioned the pilot and the connection.

I've tried switching away from it and back to it, to no avail.

I feel like the narrow band scanner has that functionality? IDK maybe I'm misremembering.

Isn't weather semi-confirmed already? (I'm pretty sure we saw something about wind, hurricanes, etc in some background footage)

Dream of the Desert Wanderer Mission Specifications: The ship uses an Apollo-style format, with a lander and a service module. They are separately launched, due to their heavy weight. The lander has space for 5 kerbals, and the tug is an unmanned probe that uses NERV atomic engines. One kerbonaut will be manning the ship on the outbound trip for repairs and to control the ship if needed, hence the extra crew capacity. The two modules will dock in LKO, and transfer to Duna. Once there, the ship comprised of the two modules puts itself into a parking orbit around Duna, potentially through aerocapture. Then, the lander will undock and land using its descent stage and parachutes. The descent stage is made of 4 fuel tanks with 4 "Terrier" engines, and will detach for ascent. The two modules will again join and escape from Duna, returning to Kerbin, where yet another ship will rendezvous with the DODW and fly its crew down to Kerbin's surface. The lander, formally called the Dream of the Desert Wanderer, launched without problems: As did the launch of the tug: The two modules met and docked successfully: Almost immediately after the rendezvous and docking, the sole crewman reported that the flight computer's Delta-V readings were significantly less than necessary for the mission. Mission Control directed the crew to test-fire the engines to ensure proper functioning of the fuel tank sensors, and those sensors were confirmed to be functional. The cause for this was found to be a faulty seal between the tug, which contained most of the fuel, and its launch vehicle. This caused some fuel reserved for the transfers to be used to accelerate to orbital velocity. An emergency mission carrying fuel, spare parts, and an engineer was then launched to refuel the tug and supply it with spare parts. This went successfully except for some damage to solar panels, and the DODW was ready for Duna transfer. The engines ignited for the transfer, and it was performed successfully. Due to the long burn time, the ship was not facing totally prograde for part of the burn, which may have increased the amount of fuel consumed unnecessarily. The fuel levels were observed to be suboptimal following this burn, so the decision to perform an aerocapture was made, necessitating a mid-course correction manuever. Some communications and computer systems were nonfunctional, likely due to a burst of solar radiation. This caused the engines to be unable to throttle for the maneuver, and firing all four at maximum thrust caused unacceptably low accuracy. Therefore, three of four engines were shut down, and the RCS thrusters, usually used for docking, were also used for fine-tuning. The Duna aerocapture was performed very well, without any overheating or damage whatsoever to any components. The ending orbit had an apoapsis of about 120 km and a periapsis of about 12 km. Because fuel levels were somewhat lower than expected, the decision was made to undock the tug, have it place only itself into a stable orbit, and allow the lander to re-enter the atmosphere for a landing. This was done without any problems. The lander experienced some non-fatal problems in its ultimately successful descent and landing. Reentry was performed without a problem, and so the heat-shield was jettisoned. After being jettisoned, it collided with the ascent engine. No damage was done to the engine, but something could have easily happened. Following this, parachutes were deployed, and these performed much better than expected, slowing down the lander to 20 m/s. Ignition of the descent stage failed, with the ascent stage's engine igniting instead. This appears to be the result of faulty electronics. The ground underneath the lander was observed to be very steep, but near a plateau, so the ship was steered there. It then landed on the plateau with no problems. Overall, the outbound mission was a success, and taught the agency many valuable lessons for the next missions. I was listening to Mendelssohn for most of this mission- I've hardly heard any of his pieces and wanted something romantic, so I decided to give it a go. I was specifically listening to his 1st symphony, and it's very pleasant.

I had a feeling it'd open today! CLICK!

Since KSP2's coming out in February, I wanted to see if I could visit all the CBs with a kerballed craft and bring all kerbals back home before KSP2 releases, to give my KSP1 save a grand sendoff. The self-imposed rules are: No exploits, unlimited quicksaves and reverts (although I'll try to do as few as possible) and mostly stock+dlc except for some invaluable and not-overpowered modded parts (like Near Future Construction's 2.5m to 3.75m structural adapter. I'll also present each mission like a mission report, and try to explain bugs and my errors as malfunctions and stuff. Before I thought of doing this challenge, I'd already visited the Mun and came back, but forgor to take photos. For my next landing, still before I thought of the challenge, I had wanted to visit one of Duna's valleys, so I flew a 4-Kerbal rover there. Unfortunately, I landed very far from a valley, so I needed to make a looong drive. So with those missions described, I'll go on to my first, in-progress mission after I thought of the challenge, which will fully abide by all my rules and stuff: The Dream of the Desert Wanderer, a rescue mission for these 4. (they have no way to get home) Another goal of this endeavour is to improve my writing skills, so if anybody has any criticisms or advice at all, please do tell me! I'm also trying to get to know more classical composers, and I don't have enough patience to just sit in my chair for 2 hours listening to music, so I'll be listening to it while doing these missions. I'll write down which pieces I listened to also.

Thanksgiving's coming up everyone!! Yesterday we received the turkey and today we're making the stuffing and cranberry chutney. This year we're doing a spatchcocked turkey for the first time, so I'm excited to see how that's going to come out. What are all of you doing?

n-6

n70

n70

n 62

Banned for watching red notice while having more blue than red in your pfp.

The point is to stop people from posting things in finished discussions, and if something hasn't been discussed since summer, I think the conversation's pretty much wrapped up.

Can we have fireworks? Aside from being cool and fun to look at, they can be used many creative ways like Orion drives (although that might not be neccessary), colored smoke, and weapons. Also faster, more intense music for reentries or fast atmospheric flights would be really cool. Also, I had an idea that's probably very, very hard to implement: Lots of functional switches in IVA. What I mean by that is the game would automatically set whatever it decides are the most important options in the PAWs of the parts on the rocket to correspond with switches in the IVA view.

Welp, looks like SLS launched before KSP2... I wonder if @whatsEJstandfor bet any kidneys on that.

I haven't been able to see those boxes that show distant craft and their distances. I don't remember when it started (and therefore what mods might be causing it). If you don't know what I mean, they're the magenta boxes with text under them in this gif: I'll upload the player.log later if it's helpful; I cursorily looked through it myself and saw nothing that might be related.

KSP isn't known because it's got Elite: Dangerous type physics. It's known for its reasonably realistic physics that demonstrate to people intuitively how things work. I see no distinction between saying "We can't have realistic aerodynamics" and "We can't have realistic physics". Aerodynamics is a very important aspect of rocket design, and it just makes no sense to me to say "Yes orbital physics, no realistic aerodynamics". KSP's physics (and real physics) say that you can't make an X-wing fighter with as much Isp and thrust as the real thing, and that's not a problem- nobody says that it kills the spirit of the game, but when aerodynamics say you can't make something, it's taking away the goofy spirit of the game? I strongly agree with this. Many people are saying that FAR is too hard, things behave weirdly, and there's no documentation. That's not a problem with the realistic aero, that's a tutorial problem. If there weren't any tutorials for stock KSP, people would say "Why does going forward make my rocket slow down?". Also you can build and fly grand pianos in FAR.

I watched this video about how it is possible to decode the golden record on Voyager, and it mostly makes sense, except at 3:56 the video uses hertz to decode the record. Looking at Wikipedia, it seems that hertz are defined based on seconds, which in turn are based on "The duration of 9192631770 periods of the radiation corresponding to the transition between the two hyperfine levels of the ground state of the caesium-133 atom". This doesn't seem to be stated anywhere on the record, so how would aliens (if they somehow decide that that one specific bit of space junk is worth sending an entire mission to) decode the record? Edit: The Wikipedia page for the golden record says that all the times are defined based on the time period associated with a fundamental transition of the hydrogen atom. So basically the video was translating that into human units for clarity.

So they actually did a mock-engagement with jets in the air? At Miramar, where I get my yearly air-show supply, they have a thing where they drop troops and vehicles while bombing the ground to simulate taking over an area, but there's no air-to-air fighting. Must be a spectacle.