Jimbodiah Posted December 6, 2016 Share Posted December 6, 2016 Crew is irrelevant. Why needs space for 100+ kerbals? I think the main goal for large habs is extra living and storage space for the few kerbals on long missions. USI LS needs large habs to accommodate kerbals on long trips, maybe look into the calculation for this "hab space" and tune for the LS mods. 16-20 kerbals seems like plenty for the large torus to me, leaving the other space available for LS mods or maybe the storage container module. Quote Link to comment Share on other sites More sharing options...
tater Posted December 6, 2016 Share Posted December 6, 2016 20 for the D is way too few. 185 is more than it needs... it is huge, though. Quote Link to comment Share on other sites More sharing options...
JoseEduardo Posted December 6, 2016 Share Posted December 6, 2016 the CFG-D is around the same size as the Von Braun's wheel would be at 64% scale, and in his plans it would have 50 crew aboard maybe 60 kerbals cap? 50 like Von Braun's plan plus 10 for tourists or people waiting for the next "moon shuttle service" Quote Link to comment Share on other sites More sharing options...
tater Posted December 6, 2016 Share Posted December 6, 2016 Yeah, I was thinking something in that range as I recall. Even 100 is not implausible. Depends on how comfortable it is. I'd probably err on the side of more volume per kerbal with a goal of much longer term habitation. The D could possibly be 3 levels. Quote Link to comment Share on other sites More sharing options...
ShotgunNinja Posted December 6, 2016 Share Posted December 6, 2016 7 hours ago, Shadowmage said: Anyone have an idea on the m^3 (and mass) per crew needed for life-support equipment on the ISS (storage, recyclers, scrubbers, etc)? The ISS has about 900 m^3 of habitable volume, for a crew of 6 (up to 9). This is an eagle view of all the life support systems. Quote Link to comment Share on other sites More sharing options...
Jimbodiah Posted December 6, 2016 Share Posted December 6, 2016 Yeah, this is not meant to be a passenger liner that fits as many people in coach as they can. Most space would be allocated towards extra living space for long flights, storage space and equipment. And I don't see any point in having 100 kerbals on board either for game-play. Not sure on current versions, but older versions of KSP would come to a complete halt because of the IVA animation icons of 10+ kerbals, let alone 100. Quote Link to comment Share on other sites More sharing options...
tater Posted December 6, 2016 Share Posted December 6, 2016 1 hour ago, Jimbodiah said: Yeah, this is not meant to be a passenger liner that fits as many people in coach as they can. Most space would be allocated towards extra living space for long flights, storage space and equipment. And I don't see any point in having 100 kerbals on board either for game-play. Not sure on current versions, but older versions of KSP would come to a complete halt because of the IVA animation icons of 10+ kerbals, let alone 100. There is no IVA, so I don't see the total as really having any impact. USILS is sort of pegged to seats (base habitation is related to seats, anyway), so in that sense they represent room. Seats also give a sense of size, and the CFG-D is huge. Quote Link to comment Share on other sites More sharing options...
TopHeavy11 Posted December 6, 2016 Share Posted December 6, 2016 O.O Your mod pack is incredible! It's nice to find a low performance-murdering mod that has all you could ever want from the Ares boosters to Orion itself! This is gonna be added to my mod roster for sure! Also, like'd! Quote Link to comment Share on other sites More sharing options...
Shadowmage Posted December 6, 2016 Author Share Posted December 6, 2016 Going to spend a bit of time tonight working on the 'docking-port-fix' system. Initial code is written, fairly simple after I figured out what all needed to be done; less than a few hundred lines for the entire system, and completely event driven (so should not add any appreciable performance costs). The 'fixer' is a separate module that will be added in the flight scene to any part that contains a docking port (or multiple ports); every part in a vessel will be examined for docking ports, one 'fix' module will be added for each docking port present on the part. What it will do is add a 'Force Undock' button any time it detects that a docking port is 'stuck' (docking port is in docked state but 'undock' button is already deactivated); pressing the button will call a method to decouple the parts (using stock couple/decouple code). And.. that should be it. Nice and simple. Going to -try- and develop it as an external mod, independent of SSTU (so, like my rescue-pod-fix). Hopefully should be small and lightweight. Will keep you guys posted, and put out some links if/when I get it working. (Although it begs the question of why the stock docking port doesn't include code to check -itself- for undocking errors; why is it disabling the undock button if it is still docked?) Quote Link to comment Share on other sites More sharing options...
Jimbodiah Posted December 7, 2016 Share Posted December 7, 2016 Because, reasons. Quote Link to comment Share on other sites More sharing options...
tater Posted December 7, 2016 Share Posted December 7, 2016 Hehe. Reverse engineering stock design decisions is always fun, right? Quote Link to comment Share on other sites More sharing options...
Shadowmage Posted December 7, 2016 Author Share Posted December 7, 2016 On the plus side, I figured out how to hook directly into the ModuleDockingNode's own Update code. Heck, with the method they have used (FSM with delegate methods and callbacks), I can completely replace, in-line, most of the docking port code without breaking existing patches/etc. Basically the module merely calls these delegate methods for its update functionality, and the devs were kind enough to leave them public/unprotected -- so you can remove or replace any particular bit of the docking port code without having to touch the original source. Kind of a neat way of handling things -- it has not always been that way; previously all the functionality was built directly into the FixedUpdate, was truly 'hard-coded' and unalterable. This means that if I can figure out what the -root- of the problem is, I can merely insert code into the docking port itself that can fix the problem (haven't tried yet, but I think I can even set it up in an override-fashion, adding new code and still calling the original delgate as well). So.... if any of you guys run into an SSTU+stock craft that has stuck docking ports, please post up the persistence file to GitHub so that I can investigate the problem a bit more. Quote Link to comment Share on other sites More sharing options...
TopHeavy11 Posted December 7, 2016 Share Posted December 7, 2016 How do you change diameter? Quote Link to comment Share on other sites More sharing options...
tater Posted December 7, 2016 Share Posted December 7, 2016 6 minutes ago, TopHeavy11 said: How do you change diameter? I'm going to go out on a limb and say that you are in sandbox mode. In that case, you need to go into Settings from the KSC view, and at the very top is "Difficulty Settings." Select that. Under "Advanced" select All Part Upgrades Applied in Sandbox. Now the diameter is a right click in the VAB. Quote Link to comment Share on other sites More sharing options...
TopHeavy11 Posted December 7, 2016 Share Posted December 7, 2016 Thanks. Quote Link to comment Share on other sites More sharing options...
tater Posted December 8, 2016 Share Posted December 8, 2016 (edited) De nada. Now for @SQUAD to fix the absurd default in sandbox to NOT apply all upgrades. Edited December 8, 2016 by tater Quote Link to comment Share on other sites More sharing options...
Shadowmage Posted December 8, 2016 Author Share Posted December 8, 2016 (edited) 3 hours ago, tater said: De nada. Now for @SQUAD to fix the absurd default in sandbox to NOT apply all upgrades. Yeah, sadly, I saw no mention of that in the 1.2.2 patch notes =\ Is anyone aware of a bug/feedback ticket for this in the stock bug tracker? (If not, one of us should probably open one up; flagged as feedback) Speaking of 1.2.2 -- I have no idea if SSTU is compatible or not. Should be fine as long as they didn't do any API changes. I'll do a re-compile and put out an updated release this weekend. Probably won't have too many fixes or balance changes in it, but the SC-E will be back in and mostly functional. It flies and lands, but haven't tested re-entry recently. I did clean up the GUI a bit though so its not quite so outrageous. Will try and do some testing/updating to make sure it can at least re-enter in stock. Edited December 8, 2016 by Shadowmage Quote Link to comment Share on other sites More sharing options...
mechanicH Posted December 8, 2016 Share Posted December 8, 2016 (edited) 39 minutes ago, Shadowmage said: but haven't tested re-entry recently I have tested it many times and it re-enters and lands smooth like butter. Its a perfect shuttle. Edited December 8, 2016 by mechanicH Quote Link to comment Share on other sites More sharing options...
Qwarkk Posted December 8, 2016 Share Posted December 8, 2016 17 hours ago, Shadowmage said: *snip* SC-E will be back in and mostly functional. It flies and lands, but haven't tested re-entry recently. I did clean up the GUI a bit though so its not quite so outrageous. Will try and do some testing/updating to make sure it can at least re-enter in stock. Downloaded the SC-E stuff today to give it some testing. It reenters and lands really well. The only problem I've come across is that every time I load or launch my shuttle, the wheels will be deployed, even if it is saved/launched with them retracted. Quote Link to comment Share on other sites More sharing options...
Shadowmage Posted December 8, 2016 Author Share Posted December 8, 2016 1 hour ago, Qwarkk said: Downloaded the SC-E stuff today to give it some testing. It reenters and lands really well. The only problem I've come across is that every time I load or launch my shuttle, the wheels will be deployed, even if it is saved/launched with them retracted. Thanks for the testing The landing gear state not persisting is a known issue with the KSPWheels deployment/animation module. It has already been fixed in dev code (and dev4 branch on github), and will be available with the next KSPWheels release. Quote Link to comment Share on other sites More sharing options...
Andromeda_ Posted December 9, 2016 Share Posted December 9, 2016 Can anyone help me with the centrifuge? I see that it requires 30 tons to activate but no matter how many ships are docked it refuses to work. Quote Link to comment Share on other sites More sharing options...
tater Posted December 9, 2016 Share Posted December 9, 2016 1 hour ago, Andromeda_ said: Can anyone help me with the centrifuge? I see that it requires 30 tons to activate but no matter how many ships are docked it refuses to work. 30.52 tons of Rocket Parts. Have an SSTU tank, and "Configure Containers" in the right click, and add rocket parts. There is a large "fitting out" craft I made for a CFG-D. The orange tank is propellant, and everything forward is equipment to fit out (inflate) the -D. Quote Link to comment Share on other sites More sharing options...
Jimbodiah Posted December 9, 2016 Share Posted December 9, 2016 (edited) This is why I made my own SSTU ATV a while back Edited December 9, 2016 by Jimbodiah Quote Link to comment Share on other sites More sharing options...
Theysen Posted December 9, 2016 Share Posted December 9, 2016 51 minutes ago, Jimbodiah said: This is why I made my own SSTU ATV a while back 9/10 - wrong flag Quote Link to comment Share on other sites More sharing options...
Jimbodiah Posted December 9, 2016 Share Posted December 9, 2016 It's only one that looks good on anything Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.