K3-Chris

Stock drills only extract Ore don't they? Does ore convert to life support in some way?

Btw does any of the UKS drills extract anything from asteroids for use with space station life support? like water, minerals, substrate etc to turn into stuff?

Well has anyone made that MM.cfg? I have to strap supply storage to everything and it's somewhat tedious. What mods fill that gap? Does any other mods than UKS/MKS interact with this one? Don't get me wrong, having self sufficient bases shouldn't be simple or easy or low tech, but at some point having to send supplies all around the kerbol system to bases and stations elsewhere becomes a massive undertaking making manned missions outside the kerbin SOI unfeasible. First post mentions stuff about combining water and substrate to make more supplies but I don't know what modules you need to make that possible or if it is. Actually U2 pressure suits have a multi-layer grommet that allows the wearer to insert a straw-like plastic tube into their mouth and squeeze a tube of liquid or mushy food: could work in a vacuum if thermally regulated (part touching your lips needs to be body temperature, food/drink needs to be +60c to +15c~ without some way to control the temperature either directly or by being stored in a controlled environment it would get too hot in the sun and too cold in the shade.

Has anyone made a MM .cfg that adds a certain amount of supply storage to manned pods based on number of seats? Should be a base feature of the mod imo but until then an mm.cfg would be appreciated. Is there a flowchart anywhere of how resources interact? Trying to figure out how to make a self sufficient base on say duna, but it seems supplies can only be recycled from mulch at a loss? How do I actually make more? Fertilizer seems to be impossible to make?

Yeah realistically, and yes I know mass is still a factor. Also you can carry stacks of things on your back, pretty sure that's not intended. I can carry a stack of those 1 ton UKS Anchor hubs around and drop em one at a time, which saves time, but is somewhat against the laws of physics I think. Btw is there a keybind to open the inventory of your current kerbal? If not I suggest I, I keep hitting it. XD

I've been using KAS and KIS for a long time now and while I really like it and use it a lot there are some aspects of it I find perplexing, primarily in orbit, the 1 ton weight limit per kerbal makes some sense on kerbin but imo should scale with gravitational forces experienced, ie can lift more than 1 ton on minmus and perhaps a whole lot more in orbit, and in orbit it's a bit... weird moving parts around, since the majority of parts now don't actually fit into kerbal's inventory and doesn't have the back attachment system therefore you can't really transport large parts in orbit except by detaching them and bumping them with your kerbal (I don't recommend this, tends to fly away in random directions) or you can do something pretty weird, you can line up your kerbal to go from where the part is to where it's going, grab the part while you pass it, then attach it to where it's going when you get there, effectively teleporting the part, sometimes really far if you line up your kerbal right (can't use RCS controls while placing the part) That's pretty wonky imo. On the ground I assume you're meant to move parts along the ground by repeatedly picking them up and placing them, which works since you have some ground to use, in orbit you don't have anything to gradually shift it with like that, and keeping kerbals near parts in orbit is a real pain (perhaps extend the distance some in orbit?). Reason I use KIS for orbital construction is that OKS parts are so large that it's hard to get em all into orbit at once, and adding senior docking ports between all parts triples the partcount of a station and makes it really floppy. Not sure how to improve the orbital construction, one idea I got that I'm not sure is possible to implement is to have 2 or more kerbals grab onto large parts in orbit and basically work like RCS thrusters for the part, maneuver the part until it's chosen attachment point (surface, nodes) is close enough to another part and have it attach after you push a button to confirm the placement.

B9 IVA glass have simulated imperfections like dirt and specs on it, it's by design to make it look like glass, an object that's completely transparent doesn't look like glass, it looks like air, glass in reality has all those imperfections and reflections to it which we're good at ignoring out of hand. KSP can't really do reflections as far as I know and it would be really expensive computationally to do so, but imperfections it can simulate using a texture. I made that texture and I tried to layer some white, black and browns in there to simulate a window exposed to high heat (blacks are baked debris), high speed (tried to layer in streaks into the texture to make it look like water and air has pushed along the window in the direction it would go at speed) and some brown specs in places that are very low opacity, middle effect bellow the streaks of a swirling motion to simulate someone cleaning the windows with a rag or similar in a circular motion. I tried to balance the opacity to make it visible enough but not obtrusive. I really wish the windows had different effects based on situation though, would be awesome if they frosted up in space, got gradually more dirty as the plane flew, much more so during re-entry etc.

Ah, whops. XD 0.90.1 soon kthx squad.

bac9: #kspmodders mentioned that stock tweakables leak as well: http://i.imgur.com/e8qPKXA.gif https://i.4cdn.org/vg/1420196534801.webm Also terrain is leaking: http://forum.kerbalspaceprogram.com/threads/105514-BUG-Memory-Leak-Flying-Near-Ground Pretty safe to assume at this point it's a problem with the game, not your mod.

First launch with ATM can take a really long time, on the order of 30mins or more, but it's faster after that, install ATM, launch KSP, minimize/alt-tab/whatever and do something else until it chews through the textures, it's making a cache of compressed variants of the textures to load instead of the actual textures, this takes time, but when it's done it's done and doesn't need to be done again.

Unity/KSP limitation, basically colliders only interact when they intersect each other's surfaces, basically they're hollow shells, if you're going fast enough the wheel's collider will clear the surface of the ground between frames/physics ticks, the game sees the collider one one side then on the other, doesn't cause an interaction (some more sophisticated physics engines can assume they intersected based on that information but ancient physx doesn't) way to get around it is to give the engine as much time as possible to register the collision, ie touch down gently (you should anyway).

Playing around with em atm, really like em, has features I begged DYJ for ages to implement like edge variants (control surfaces vanish into the trailing edge of large pWings), heat-shielding on the bottom etc. Might I suggest some changes to the text labels of the tweakables menu? "Height root/tip" would make more sense labeled "thickness" I think, more descriptive at least imo. "offset" might work better labeled "sweep" (https://en.wikipedia.org/wiki/Swept_wing - https://en.wikipedia.org/wiki/Forward-swept_wing)

Yeah stock editor UI only lets you filter based on manufacturer or function, not both. It's really annoying, I can either see all pods, or all B9 parts, not all B9 pods.

@bac9: Sorry wasn't in earlier, I leave my IRC client + PC on 24/7 nothing much to report, working on getting my setup working again post HDD calamity. @karamazovnew: Heh, I actually forgot to try the engine igniter integration, oops. I'd like the buttons on the bottom to control it but I can't actually figure out how to map those buttons to plugin functions, I'll have to read up on that, I'd like to label the buttons on the sides instead but the plugin text goes edge to edge so I can't do that either. If I can't figure out the bottom buttons mapping I'll label the side buttons in the Utilities menu (screen you go to before the engine igniter one) like I have with the cameras. I've come up with a pretty wonky fix for now: PAGE { name = pluginEngineIgnitor text = Engine Ignitor plugin not installed textureInterlayURL = B9_Aerospace/Props/B9_MFD/images/bg03 //textOverlay = B9_Aerospace/Props/B9_MFD/pages/menuOverlay.txt disableSwitchingTo = btn1, btn2, btn3, btn4, btn5, btn6, btn7, btn8, btn9, btn10, up, down, enter, escape, home localMargins = 0,1,0,0 PAGEHANDLER { name = EngineIgnitorRPM method = ShowMenu pageActiveMethod = PageActive buttonClickMethod = ClickProcessor buttonUp = 0 buttonDown = 1 buttonEnter = 2 //buttonEsc = 3 //buttonHome = 4 button6 = 5 button7 = 6 button8 = 7 button9 = 3 button10 = 4 } } That works but none of it is labeled correctly, here is how it works: up, down, enter works as you'd expect back = unselect home = information left = off right = on next = toggle All those other pages/buttons you mention are intentional, allows you to go between the 3 versions of the APFD either by hitting the bottom button again or using next/prev.

Allows you to crossfeed fuel on radially attached parts, you need to fool around with a lot of fuel lines otherwise. Well it breaks all IVAs to remove it, not sure if it's broken or not actually. No it's used to close the air intakes when you get to space and similar animation features. Generators are ResGen and cargo doors are FireSpitter We're only still using it on the VTOL engines, stock's gimbal code doesn't have the engine turning feature the VTOL engines use. That's hotrockets for better engine effects. It's used for the compressed air nozzles. I think that's the mod we use to toggle nodes on the HX parts on/off to aid placement. Correct, some of then were updated by Taverious last time they broke .24/.25~

I can't see how that could be, B9 parts have unique names with a B9 prefix, look at the .cfg files, it's impossible for the game to confuse them, my best guess would be some plugin that comes with B9 isn't behaving (firespitter most likely). The B9 mk2 parts are just that, parts, they're textures models and a .cfg to glue those together, there is nothing magical about them that could cause editor mayhem. I can't say this enough: If you want to keep playing with B9 (or any mod for that matter) don't upgrade KSP day 1 (or install a clean new version of the latest KSP next to your old modded one), upgrade when B9 or it's included plugins have been updated/confirmed to work. The 3 of us made the assets and .cfgs (which can't really become incompatible) etc, but we also bundle some plugins for additional functionality, those aren't made by us and we can't do anything beyond bundling in the latest version when they get updated.

Firespitter has been hotfixed btw, look above. If you value playing with your mods always install a new KSP version in a different folder than your current install, keep playing the old version with your mods. Then move over when enough of the mods you like have been updated/confirmed working. Updating the mk2 shape is pretty labor intensive work sadly, I can't find a good workflow to edit the models in bulk and load them into Unity/KSP, it's tedious as a word I can't use here to do them one at a time and do all the steps from modo to unity to KSP for each part.

Porkjet's textures look like stock textures, that's what was he was going for and he succeeded, I'm not a fan of the stock look though.

There is no great mystery that HL and Mk3 are the same shape, PorkJet asked us to do that and asked for a reference model, we agreed and supplied it, we knew about the Mk2 shape change and agreed with it before release, as said B9 will be updated to have the new shape. Sadly both Bac9 and Tav haven't been around in quite a while (both vanish for days-months and come back, nothing new) and I've been busy with school as of late, done with that now for the year but I can't say how much time I'll have over the holidays to work on B9. Highest priority at this point is Mk2 shape conversion and I'd like to supply both a "full" package of all current B9 stuff and sub-packs for each hull shape (mk2, S2, HL, HX) and one pack with some structural stuff, and one with wings etc, idea is that if you want all of B9 you can just download the main pack, but if you only wants bits and pieces you can download the "sub packs" you want. A way to get around KSP's increasing ram restrictions. Inclusion of pWings and making the B9 gear adjustable using BahamutoD's plugin are also in the works. I got a bit mixed feelings about Porkjet's new stock parts (Mk2 and Mk3) they're pretty nice and all but they're bound to eat into B9's install-base quite a lot.

The small engines in the bottom right corner are BahamutoD's pop out engines.

I'm guessing this uses an epic amount of RAM? I'm near RAM cap already and assume I can't run this at all.

Nice spotlight, though worth mentioning the changes to the stock pods are from the bundled RPM/JSI, we made the MFDs in the B9 cockpits on top of RPM and for ease of distribution/compatibility we bundle all of RPM including it's patches to stock pods. Hence why they differ. Hint: hit home twice

Lowered tail? And yeah bomb-bay arrangements is an easy one, as would toggle-able heat-shielding be, both are due for the update that tweaks the mk2 outline to fit the new stock shape. (Symmetric cargo bay, toggle heat-shielding off, turn 180 degrees)

It's in outdated RPM versions, it's not in later versions, was for B9 v4 and earlier that didn't have it's own RPM configurations.

There are others in the thread that had the same problem, forgotten what the cause was but it's an installation issue or incompatible mod issue, like 99% of the posts in this thread.