viveleroi

Hot damn I am eager to try the update! I wish it worked on 1.10 as I'm currently early into an RP-1 play.

Is this working on 1.12?

Why does my flex tube look glitched? I attached one flex tube to my scout lander, the crew hatch faces out, another flex tube to my ball hub (crew hatch also faces out). When I link them, it lets me, but the tube itself looks all messed up.

Learning MKS. I setup a ranger hab which has a "logistics consumer" component, and I have a 3.25m tank of supplies about 80m away. I can manually transfer supplies via the logistics GUI but the wiki says the consumer should be pulling stuff as needed, but no supplies are ever pulled from what I can see. Also, when my kerbal enters the crew hatch of the ranger hab module, whatever is in their KIS inventory is destroyed. Also, how can I tell how much life is left in the ranger scout-200 power pack. MKS Version 1.4.1 on KSP 1.11

New user here, been reading the wiki and watching recent tutorials trying to get a good handle on things. Unfortunately the videos I found just walk you through the parts, no one seem to cover how to actually start building the base outside of sped-up/multi-hour let's play vids. Most of them just jump to a pre-made base. From my understanding, the process is: Find a spot you want to use. Using stock/SACNsat to find resources can help if you want to land somewhere convenient for mining. Ship in inflatable modules, and MaterialKits/engineers you need to actually inflate them? Use the Scout Landing Module to land stuff. EVA your engineer and use the Kerbal Attachment System to pickup, move, and place modules? (I assume nothing works with the 1.11 construction mode yet) How do you actually connect modules together?

I guess it could be, the stock ones don't have this issue but they don't have extra bits. Unfortunately I need to problem solve, got a mission to minmus I can't undock. May need to abort and use them LEM to push the whole ship home. Ok well moving the ship around and starting my time-warp to my maneuver node was enough I guess. the ships finally came apart, although they shook enough it looked like things could go kraken any time.

I launched a ship with a lander pre-docked. But when I decouple the nodes in orbit they won't actually detach, the bumpers seem stuck on each other. Nothing I do will let them separate. I tried extending the bumpers on both vessels but they're just locked together. Used RCS to reverse on ship and it just catches on the port and won't move. Any advice?

I'm eager to try this out! But I'm on 1.11 and reports that the planets are invisible are worrisome.

I'm using mods in 1.11 that support KIS. Does KIS work with the stock alternative or am I going to have a lot of problems? I scanned the most recent pages on this thread and didn't see any clear info.

So the FAQ says this doesn't work with KSPIE - does that mean using both will break things? Or does that mean it just doesn't integrate? I've spent the past month learning KSPIE and have a love/hate relationship with it. I'm considering starting a new play through and am tempted to use this mod instead. It not only looks better than KSPIE but it doesn't look like it throws as many variables at you. Is there a good tutorial anywhere? I assume it's not as complicated as KSPIE either. Same... I just went "Oh..." while watching the vid. I've been saying "Ner-tee-a"

I must have grabbed the log post-reboot. My bad. Next time it happens I'll grab it immediately. I tried the same flight process again last night but before the moment things broke the past two times, I quit to the tracking station and re-loaded my lander. When I docked with the mothership this time, it was not broken.

Cool that's what I posted

Log: https://botsko.s3.amazonaws.com/KSP.log Mod List: https://botsko.s3.amazonaws.com/mods.txt Craft: https://botsko.s3.amazonaws.com/Mothership Nuria.craft Not sure where a cache is for the module manager, so here's the config cache which seems like it might be what you want: https://botsko.s3.amazonaws.com/ModuleManager.ConfigCache I've never had this problem until I made this craft. I'm not 100% sure it's NF at fault for the UI problem, but the RCS "effect" playing for that part only means it's at least affected in a way nothing else was. I launched the ship, went to the Mun, undocked the "lander", landed on the Mun, launched back to Mun orbit and rendezvoused with the ship. At that point I saw it's RCS thrusters firing. I've never seen that happen for ships I wasn't switched to, and I worried it was draining all my monopropellant. It was just a visual thing, but at this point I also noticed the UI buttons were broken too. I couldn't save, go back to the space center, or quit. Every time I tried, I'd get the error in the console I posted above. I force-quit the game, re-launched, had to rendezvous again, and it worked fine. But, everything broke again after I undocked and repeated the steps above.

I have an issue I think is related to near future. I made a new "mother ship" that carries a lander. I undocked my lander and when I came back to the mothership for docking, I noticed that A) the RCS jets on the callisto heavy command pod were firing, except no rcs was being used and B) I couldn't click UI buttons any more. Something broke, and I get this error in the log: Bear Future Spacecraft Version 1.4.1 for KSP 1.11.1 [LOG 15:50:14.280] Game Paused! [LOG 15:50:14.281] [UIMasterController]: ShowUI [EXC 15:50:15.044] NullReferenceException: Object reference not set to an instance of an object PartModule.get_HasAdjusters () (at <f8bc9e2b903e48a5b248ab0083c07c62>:0) PartModule.Save (ConfigNode node) (at <f8bc9e2b903e48a5b248ab0083c07c62>:0) ProtoPartModuleSnapshot..ctor (PartModule module) (at <f8bc9e2b903e48a5b248ab0083c07c62>:0) ProtoPartSnapshot..ctor (Part PartRef, ProtoVessel protoVessel, System.Boolean preCreate) (at <f8bc9e2b903e48a5b248ab0083c07c62>:0) ProtoPartSnapshot..ctor (Part PartRef, ProtoVessel protoVessel) (at <f8bc9e2b903e48a5b248ab0083c07c62>:0) ProtoVessel..ctor (Vessel VesselRef, System.Boolean preCreate) (at <f8bc9e2b903e48a5b248ab0083c07c62>:0) ProtoVessel..ctor (Vessel VesselRef) (at <f8bc9e2b903e48a5b248ab0083c07c62>:0) Vessel.BackupVessel () (at <f8bc9e2b903e48a5b248ab0083c07c62>:0) FlightState..ctor () (at <f8bc9e2b903e48a5b248ab0083c07c62>:0) Game.Updated (GameScenes startSceneOverride) (at <f8bc9e2b903e48a5b248ab0083c07c62>:0) Game.Updated () (at <f8bc9e2b903e48a5b248ab0083c07c I had to force-quit the game. Next time I tried undocking and came back, and the same situation happened again.

I added this mod into an existing save, maybe not wise, I wanted it from the beginning but tweakscale needed updates. It's changed the list of fuels that are available for cryo tanks from other mods. This really doesn't affect any in-flight ships, but I'm wondering if there's a way to fix that. For example, this tank had LH2+Oxidizer but after I added Interstellar the fuel list has a bunch of new entries but only allows LH2 or Ox, not both.

Awesome! I really appreciate your time and damn if that wasn't a fast and helpful reply! I will try this soon.

I am getting this warning when using the latest 2.4.4.0 version from github. Here is the log: https://botsko.s3.amazonaws.com/KSP.log

I assume this isn't working on 1.9? I installed it, don't see errors, but also don't see the button on the science menu. I can only keep or transmit.

It seems like this issue was fixed in the github repo but no work has been done in months. Can someone fork it and release a binary? I'd really rather not use hacky ocean patches to fix this problem when the at fault code was removed in the repo. Edit: Hours after I posted this, the mod officially had an update released.

Are there any known issues with remotetech on 1.7.3? I've got both installed and everything was fine inside the kerbin SOI but I just launched my first vessel for duna and can no longer control it. I've got the J15-D comm dish. I have two on a vessel inside the kerbin SOI as my "relay". It's connected to KSC with one dish, and to my active vessel/duna vessel (tried both) with another. The distance shows my duna vessel is well within the range. Yet when I switch the duna vessel, I have no control. I have electricity, the dish itself says "connected", but I can't control my vessel anymore. It's as if the SOI is a boundary. I'm going to try next time with official remotetech dishes and see what happens. Edit: I tried with a remote-tech Communotron HG-55 and do not have the same issue. I put a new relay satellite up with one pointed at a new test probe with the same dish and even after I left SOI I had signal. The moment I switched to the satellite with the J15-D I lost connection. I immediately switch to that J15-D sat and it was powered, had signal, and said my test probe was in range. Definitely appears to be related to the J15-D, unless I'm missing something.

You're right. Sorry I missed that. I found it. I tried the QuickSearch mod but it did nothing helpful.

I haven't unlocked it yet. I'm trying to find it in the tech tree.

https://helion3.s3.amazonaws.com/KSP.log Which node is it usually in? I've focused on all of the command module/science/habitation nodes but even poked around in the aero/nuclear/probe nodes. I'm trying to get the QuickSearch mod working so I can search the tech tree, but I've never had this much trouble finding something.

Has the Hokulani science lab been removed? I added Bluedog to a new 1.7.3 install with some other mods and I can't find it anywhere. It's possible I've missed it but I spent an hour looking through every node.

In 1.7.3, craft with Bluedog probe parts bug out when they explode due to re-entry. I started a new playthrough and freshly installed some mods and when a craft with a Bluedog probe gets too hot it doesn't actually explode. I noticed that the staging UI on the left vanishes, the map view no longer shows a vessels, the craft no longer slows down due to drag, but the graphics start glitching (clipping and vertex weirdness) and it will continue into orbit forever. I can't say for sure it's a Bluedog bug, I have other mods, but so far it's only parts that do it. The vanilla probe cores don't have this issue.