bigyihsuan

This I want. This also. Why not edit the Wikipedia page yourself (with sourcing)?

New manned Mars landing architecture just dropped, I wonder if it's possible to recreate with mods?

This is the last time I did a Lunar Gemini. I modified the lander a bit to add surface experiments.

There's always taking a Titan, tacking on a Centaur, and slapping on larger SRBs The mission profile I run is this: Launch the lander to the moon of your choice, with an Agena transfer stage. Park it in orbit around the moon. Launch the lunar transfer module, which is a Centaur D with a GATV passive docking port on top of the avionics unit. Launch a Gemini capsule. rendezvous, and dock with the Centaur. Transfer to the moon. Once in lunar orbit, rendezvous with the lander. Undock Gemini from the Centaur, dock to the lander, transfer crew. Then dock the Gemini back to the Centaur. (optional) Detach the Agena and begin deorbit. Land on the moon. Return to orbit. Gemini-Centaur rendezvous with the lander can, dock to it, transfer, dock back to the Centaur. Dispose of the lander, leave lunar orbit back to Kerbin. Reenter, and enjoy. The first time I did it I had a Titan LDC launch an Agena-Centaur to orbit, but I found that was massively overkill and you could use just the Centaur instead.

The fun part is actually needing to do Lunar Gemini if you wanna land on the Mun Thankfully Lunar Gemini has enough dV to do either Mun and Minmus Follow history and spam science probes into every corner of the system as launch windows come up. Considering you've got Mariner at this point, you should be somewhere around Gemini and its lander (tier 7). Use that, slap a bunch of science parts, bring some deployable surface experiments if you've got the DLC, and go to town.

I'll mark this as SOLVED for now, setting LEGACY_ORBIT_TARGETING to True in settings.cfg hasn't lead to crashes.

I'm getting direct-to-desktop KSP crashes when using a maneuver node to transfer to Jool. I note that KSP.log has a lot of MechJeb spam at the bottom, so I thought to repost here. KSP.log and mod list in this thread:

KSP is crashing directly to desktop when focus-viewing Jool, while a maneuver node is active, with a transfer into Jool. The game doesn't open the usual Unity crash handler window, it just closes instantly. KSP.log, and mod list: https://gist.github.com/bigyihsuan/3c5917efa57645db83a54e51ab36aec1 Direct link to the KSP.log: https://gist.github.com/bigyihsuan/3c5917efa57645db83a54e51ab36aec1/raw/12c754a2a9641dc1a1d245210939b43de707948b/gistfile1.txt I note that the bottom of the log has many lines similar to the ones below, right before KSP crashes. [LOG 23:20:19.740] CheckEncounter: failed to find any intercepts at all [LOG 23:20:19.741] CheckEncounter: failed to find any intercepts at all [LOG 23:20:19.757] [PR] MechJeb wrapper.Active 1 [LOG 23:20:19.757] [PR] MechJeb wrapper.Active 2 [LOG 23:20:19.757] [PR] MechJeb wrapper.Active 3 [LOG 23:20:19.757] [PR] MechJeb wrapper.Active 4 [LOG 23:20:19.757] [PR] MechJeb wrapper.Active 5 [LOG 23:20:19.757] [PR] MechJeb wrapper.Active 1 [LOG 23:20:19.757] [PR] MechJeb wrapper.Active 2 [LOG 23:20:19.757] [PR] MechJeb wrapper.Active 3 [LOG 23:20:19.757] [PR] MechJeb wrapper.Active 4 I've found multiple threads (Reddit thread, another Reddit thread) and all say to set LEGACY_ORBIT_TARGETING to True in the settings.cfg? What does this option do?

I was trying to increase the fuel capacity of the Voyager Mars probe, and apparently the service module doesn't allow fuel crossfeed: (Red line is where the fuel flow graph stops. I've added the fuel line to connect them.)

Any parts that don't have an RO/RP1 config is by-default hidden by RO/RP1. It's likely the mods you mentioned don't have RO configs yet (I'm not sure who makes the RO configs for other mods, you'll have to ask around about that).

What's the main difference between your fork and stock HabTech2?

The capsule is also in the staging bar, so you can right-click it from there.

Not inflatable, it's a bunch of cargo inventory parts and a ladder for storing deployable experiments.

Another Skyhawk run, another Gemini Munar mission to get up to Apollo (I forgot to plant a flag so I need to do another launch to complete the Mun Program strategy contract Thankfully I've fixed some problems I had with the mission before launching the next mission)

Nice, what changed?

Another fix is going into the MandatoryRCSPartPack/Parts/RCS_RV105Variants/DepreciatedRV105Fix.cfg file, and editing the path to the RCS texture. Change "@texture = rcs, Squad/Parts/Utility/rcsBlockRV-105/rcs" to "@texture = rcs, Squad/Parts/Utility/rcsBlockRV-105_v2/rcs". Note the added "_v2".

I want to be able to build really really tiny probes in my JNSQ game. When I say small, I'm talking cubesat/SpaceX rideshare small: Are there any mods that would let me do this? (I know RP-1 has their probe core system that lets you stuff a bunch of things into a single probe core, but I don't know what mod that is)

I saw that CKAN had updates for the Real Names, Methalox, and CCK extras. What changed?

Some folks on the /r/KSP discord said that using node_attach would fix it. Would this work? @PART:HAS[@MODULE[ModuleEngine*]]:FINAL { @attachRules[1] = 1 &attachRules = 1,1,1,0,0 %node_attach = #$node_stack_top$ }

How compatible is it with Kerbal Construction Time? I had multiple different versions of the same-named ship and it considered it the same bloc.

I've managed to get the engines surface attaching with the following patch: @PART:HAS[@MODULE[ModuleEngine*]]:FINAL { @attachRules[1] = 1 &attachRules = 1,1,1,0,0 } However, some modded engines have their "grab point" in the middle of the part, as seen below. The left engine is a correct Restock engine, but the right one is an incorrect BDB engine. Is there a way of fixing this?

I wouldn't trust it just yet.

I see, thanks! So Kerbin (and other aired bodies) will have their losses/multipliers reduced, but everywhere else will be in line with the rescaled multiplier (subtracting getting to LKO).

I'm using the JSNQ_Rescale10x addon patches and trying to make sense of Astrogator's dV readout. It says that it takes ~8554 m/s to Kerbin orbit. The provided, stock 2.5x dV map says it takes 4900 m/s. The rescale factor of stock JNSQ is 2.5x, so its dV values should be sqrt(2.5) = ~1.58x as much as 1x scale (4900/sqrt(2.5) = 3100m/s). (which is accurate, though undershooting it a bit. The community dV map says it takes 3400 m/s to orbit.) The difference in scale between stock JNSQ and rescaled JNSQ is 10/2.5 = 4, so the dV should be about sqrt(4) = 2x as much. But, getting to Kerbin orbit, using the 4900 number, says that it takes 9800 dV to get to low orbit, while Astrogator (and experience) says you need less than that. Is there something going wrong in my calculations?

I'm wanting to make a MM patch such that all engines are surface attachable, like the engines in ROEngines. I also want to make a copy of the top node (or move the bottom node) so that I can attach interstages to engines close to their attachment point, rather than to the engine bell. Currently, I have this. It (should) set the attachRules such that it will allow surface attachment to other parts, and moves the bottom node to the top one. Would this work? @PART:HAS[@MODULE[ModuleEngines]]:FINAL { @attachRules = 1,1,1,0,0 %node_stack_interstage = #$node_stack_top$ }