smotheredrun

Nice... something to add to my list...

@Angel-125, it's been a while since I've even logged on, looks like CONGRATULATIONS DSEV!!! are in order. And you have a Kopernicus? *goes and dusts off neglected gaming computer (my gig laptop... I know... I really need to separate work from play) and installs 1.3.1 * I could have sworn I've seen triangular KIS containers somewhere a very long time ago... Anyone know what happened to them?

Wha.... wow! It has been a very long time since I looked into this thread. Love it! Maybe just spray paint the garden in a very Kerbally style?... or you could add a sign reading "End user to install garden. No warranties inferred or implied by Wild Blue Industries regarding Ranch House building performance when said garden is installed."

Nnnnnnooooooooo!!!!!!!!! This is such a neat planet pack! Maybe a break will be a good thing to get the juices flowing again, but I hope that one day you do get back into it. Even if you currently lack motivation, please know that it is modders like you that make this game keep its appeal over time; there is always something new to discover around that next hill, across that lake or sea, and behind that next planet.

Yes, yes it is.

Will this work in 1.2.2? I am sticking with that install until I'm finished some forum challenges

I would like to say that I keep multiple backups of my important data, but nope... I do not. just like everyone else

Did Chaka supply the orange foam for all of the tanks? The colour-match us uncanny!

Is the user asking for a space toilet? That's pretty much all I can get out of that....

It "works" as is... mostly. Still working on some balance issues (cost, mass, output, etc) and some small bugs. Station parts work -- just need some balancing (working on it). Another user and I are patching (them) and testing (us) the shuttles. Reaction wheels are bloody crazy.

Angel needs to beg the Evil Empi... uh I mean merciful Disney for special permission to have (slightly Kerbalized) Lando yell that every time something breaks.

@ xyphos, I routinely launch sections of larger space noodles totalling when assembled an average of 200 parts, including landers, satellites, and kickers. So far I haven't seen any serious slowdown due to autostrutting - the only things that seem to slow my mid level laptop are the log spams from the WBI, FF and I believe OMS mods I have installed.... Most of those issues seem to be fixed in 1.3, and I'm just slow at updating - still in 1.2.2. In fact, autostrutting seems to be the only thing that keeps my nervas attached to my ships!

Oooohhhh please don't texture that! Looks like it just needs lasers to be complete! Just kidding.... sort of.... looks fantastic!

????? !!!!! Thanks!

@Angel-125 While waiting for silicone to dry, I started poking around GitHub because I have run into the docking port issue Grumby referenced back in May. So...... If I understand GitHub and pull requests correctly, would I be able to take Grumby's DR 375 dock o tron fix and slap it into my (sorry) 1.2.2 save? As in can I copy the Green text field into a new config file to overwrite/patch the DR 375 config in the DSEV 2.0 version I'm running? Or something to that effect? Sorry, not at my laptop, so i can't actually open anything, but it sort of makes sense in my head..... I forgot about the "not able to dock issue" until earlier today.... If that's not going to work I have a couple very Kerbal ideas for fixing my ship; using only a little bit of KIS/KAS explosives.

Haha. Yeah I did a google search after taking a look through Angel's wiki. Seems legit. Don't forget the carpenter whom takes the safety key and a hostage enginerd down range so the carpenter can wedge the 2x4 with the igniter into the engine bell - before something goes wrong.

I've been horsing around with a Buffalo "Mun Explorer" using Buffalo Drill, ISRU, and 1 or 2 chassis pieces set as Ore tanks. This setup works well in KSP 1.2.2 for me with no issues, well not quite: the first version exploded beacause I overheated everything... So here are my notes and fixes: 1- Buffalo ISRU processes ore (at low surface concentrations) way faster than a single Buffalo drill can extract it. Added more drills in Mun Explorer Mk iii. 2- Heat is an issue! have scads of radiators! Like Stock Mediums or several Hotplates from DSEV or grab a bunch from CX Aerospace. Like 2 per device seems to work. I prefer the Hotplates due to their size and they had a look I liked. 3- Bring a S.A.F.E.R reactor (all of Angel's mods have it included). 4- Are you running BARIS? I yes, maybe disable it and check to see if your setup works. BARIS thread has and awesome wiki linked to it. Let me know what happens

@Angel-125 Thanks for reopening. Also, thank you for updating your OP with the nice big friendly link to the manual. Looks like I have some reading to do as there are now Tigers? - guessing that they aren't what I'm thinking of.... Upon reading a couple lines in the wiki and OP... Yeah not the tigers I was thinking of... I finally have a nice clean 1.3 up and running. Going to drop this in with MOLE and DSEV..... ah I probably won't have it very clean after all, my essentials list is like 60 mods.

@The-Doctor This looks very promising. I'm excited to see where it goes and that you've thought of the "search other mods for tech tree location and change to make sense with this tech tree" program. Also, is this tech tree bigger on the inside too?

@ Hotaru, I'm pretty sure that the KAC timers stopping early can be changed in the KAC window.

Very cool.

Ok thanks linux. Always wanted to learn what "recompile dll for x version" involved. I will try to do that. To the Google-machine!

Nice!!!!!!!!!!!

@linuxgurugamer Looking through the version updates on SpaceDock, I noticed that the Astronaut Complex performance issues were addressed for the KSP 1.3 versions. I've grabbed the latest version. Provided I can "open/read" the dll in what google tells me to use (MS Visual Studio?), is it possible to copy the astronaut complex fix and add it into the last KSP 1.2.2 version of Crew R&R? Is that a thing? Or, can I just copy what looks like the fix from GitHub into a config file? Or am I way out in left field here? Reason being I'm not quite ready to jump into 1.3 yet....