Geonovast

You don't need a mod to fix this, you need the re-root tool. Once you've done the merge (or grabbed a subassembly), you can use the re-root tool when it's shadowed red. Once you set the root to a part with an open node, you'll have an attachment point. The re-root tool is up next to the rotate tool. It's the Z shape with a box on each end.

I doubt it considering the FH is fully expendable. It wouldn't need the landing pads. It was also supposed to launch days ago. Sending the boat out isn't something you can do on a whim. Takes days to get out there.

I just had a very interesting computer troubleshooting experience. Went to turn on my main rig this morning. Acted normal for a couple seconds, then nothing on the screen except what looked like a cursor (but wasn't) in the upper left. Diag lights on mobo lit up VGA. Initial though was "oh no, did my < 1 year old GPU die?" Two more reboots and no change. So I start poking. Things that didn't work: Different GPU The other x16 PCIe slot (with both cards) BIOS clear Swapping in my Ryzen 7 2700 from another computer Removing all but one stick of RAM Putting the remaining stick of RAM into another slot Removing CMOS battery Reseating power cables At this point I unplugged every single thing from the board that wasn't required to boot... and I got to the BIOS. So I start adding things back in, first with my boot drive, booted. Then I plugged the USB cables back into the back of the machine... no boot. It was at this point I had a stupid thought that turned out to be the problem. Yesterday I had wanted to pull a video from my dashcam (saw a fox running in the road), so I had hooked up my USB SD card reader. This was still hooked up. While the machine was still at its cursor-not-a-cursor state with the VGA light on, I unplugged the card reader (which did not have a card in it). Screen blinked off, then back on and the BIOS splash screen came up, and continued to boot. It's wasn't even set to boot from USB. It just wouldn't even POST. So now it's all back together and I have thermal paste schmu on a couple textured black parts inside the case that won't get clean. About 2 hours of me freaking out I was going to need a new motherboard (and initially a new CPU [Although I can get a 5800X3D right now for less than I paid for my 5800X...]) and thermal paste goopies in the case when all I needed to do was unplug an apparently wonky USB device.

Nice fireball on depress there..

You don't need fire for an explosion. FTS may have been what triggered it, but it still exploded from the fact that it was pressurized. This is why it breaks up into an incomprehensible number of pieces, not like... 3.

B1050, the first Falcon 9 (non-heavy) I watched live... which they did recover, it just never flew again. I think there's a pretty good argument against having the staging latches and the grid fins on the same hydraulic loop. One system is mission critical, the other is not. Adding a "non-essential" system to an essential one will open up more points of failure for the essential system.

At this point, I'm not a fan of the stock LES. It's waaaaay too spinny. I do like the concept of playing with abort systems, however, which is why I made a mod that adds a couple stock-alike pusher abort systems that can still function as RCS tanks if you make it to orbit just fine.

Welcome to the forum, @sqreNicolai! I have removed the log file from your post as embedded log files can cause page loading issues for some users, even when in spoilers. Please upload your file to a file sharing site such as google drive or similar, make sure it has public permissions, and share the link to that file. Thank you!

I wonder what their definition of "inactive" is. Hotlinking, so loading while viewing a forum, may be considered activity and so the only images on the forum that would go poof are in threads that literally aren't even read anymore.

I think there's a whole lot of "it depends" there. Mass of payload, target orbit, which engines are lost, when they're lost...

An off-topic discussion regarding a topic not appropriate for this forum has been removed. The date of the next launch attempt is nothing more than the date of the next launch attempt. Please keep unrelated topics assigned to happenstance numbers elsewhere. Thank you.

New addition today.

64 bit operating systems can run 32 bit applications. It's going the other way that you have problems.

Did I miss a planned fully expended FH or do they stick the recovery bits on after the three are tied together?

When shopping for our Easter meal, we (mainly me) wanted a honey glazed spiral cut ham, because those things are so good it's almost unreal. Store did not have a 3-4 pound one that we wanted. So we compromised and bought a 12 pound one instead. For 3 people. One of whom can't eat too much pork at once and also a teenager who is too good for leftovers. So that leaves my diet for the forseeable future to be: Breakfast: Ham Lunch: Ham Dinner: Ham Late-night snack: Ham I'm about to enlist the cats to help out with this.

Refreshed YouTube, saw the live stream. "Oh yeah, there was a launch this morning". Click on it. T-0:10 "Woot!" Perfect timing. T-0:02 Abort Abort Abort. Aw.

Moved from S&S to KSP 1 Discussion (I'm assuming KSP 1)

I'm just now able to start watching, how long's the window?

The engine plates don't appear to have nodes. It looks like the engines will all surface attach, so the nodes aren't needed, would be my guess.

I've been playing with it a bit and I found a way to run the game in Proton 7.0-6 and without the WINED3D launch option. I went to Games->Add a Non-Steam Game, and pointed it to the KSP2_x64.exe file. Ran just fine without switching to Experimental or adding the PROTON_USE_WINED3D=1 option. Skips the launcher and ran better. Slightly smoother (at least less stuttery), and the planet's no longer disappearing when I launch.

I've run into this issue with a lot of games, even running multiple monitors. Try going into the graphics settings and switching it from Fullscreen to Borderless Fullscreen (or whatever it's called.)

Having similar issues. Haven't tried any planes yet, but going to space causes some pretty funny issues.

Thought I'd create a specific place for my fellow Linux users to share their issues with proton and what/if they did any tweaking to get it running. To my surprise, it didn't just run out of the box. I appear to have gotten it working after some small tweaks. If you're running the game in Steam's Proton, feel free to share your system specs, proton version, and any tweaks you might have had to do? Ryzen 7 5800X 64 GB DDR4-3600 AMD RX6700XT Linux Mint 20.3 MATE Proton Experimental Launch Options: PROTON_USE_WINED3D=1 %command% Experimental would get the launcher to.. launch, but when I clicked play I got an error saying it couldn't initialize graphics. The WINED3D option seems to have fixed that. I'll report back if I have to make any more adjustments.

Steak knives down, everything else up. But I have a terrible, horrible, no good, very bad tabletop dishwasher....