Search the Community

There is of course one scientific tidbit that bugs me, or rather how often people say it's impossible, and that's Warp Drives. More Specifically the Alcubierre Drive. I could go nuts and spew my thoughts on the matter all over this thread, but that would be awkward and would likely get people in trouble for replying Tl;Dr. Simply put, it's possible, we just need to generate this "exotic matter" that has negative mass(or something), which isn't even impossible according to at least two scientists. One of them is a bit of a nutball, honestly. His name is Michio Kaku and he believes in STRING THEORY! Well, okay, that's not that bad, actually, it's weird but I don't get it. According to the Youtube Comment Section however, he is INSANE! But that's the Youtube Comment Section, so it's not fair to them to pay attention to pretty much anything said there or take it at face value. Also there this guy called NASA seems to believe in this stuff. Wait. No, sorry, a Group called NASA. They're doing research on this stuff. Maybe you've heard of them? And yes, Clarke's first law is very important here. I mean, just 'cause one guy says that E=MC2 doesn't mean he knows EVERYTHING! Plus he didn't believe Quantum Physics was going to go anywhere(called it names to boot), and here we are talking about the Alcubierre Drive which needs Quantum Physics to talk about. Also Quantum Physics is a big deal these days. Go figure. I could post links to dozens of things to help my case, but basically, all people need to see me post is this youtube video: http://youtu.be/ctjbE_zcurg. Anyway, I'll give back the soapbox, guys. Cheers.

They might not respect the idea that information can be 'owned', much like the native americans didn't recognise land ownership. Hell I don't even respect the idea that information can be owned. If we make an offer like "you give us that fancy tachyon generator and we'll give you a record of everyone's phone calls." They might be offended and not accept the deal because we didn't offer them something substantial. On the other hand, they might accept information for information, like giving us the plans for that tachyon generator in exchange for our records. Actually upon reflection, we might have to give them billions of hours of telephone records just for them to figure out how to talk to us.

Since you talk about sat you must be using RT2. You need the dev version of MJ to fix that bug. Or disable delay in RT2 config.

I talk about the one after today ... which isn´t out yet. They already discovered balancing issues with the damage numbers from todays upodate and are planning another one which, as initially believed, would require another wipe (but now doesn´t)

I'm sure this has been asked before but the size of this thread.... I'm having trouble with landings. Normally without FAR I can land on a dime just using the landing marker from the MJ landing AP. But with FAR, I absolutlely suck at hitting a target. Is there any way for MJ to talk to FAR to at least ball park a landing trajectory? Barring that, have you considered adding a Estimated landing marker function? Barring that, any tips or tricks to landing with FAR in an atmosphere because I'm seriously not getting it. Any help at all would be greatly appreciated.

Having trouble with landings. Normally without FAR I can land on a dime just using the landing marker from the landing AP. But with FAR, I absolutlely suck at hitting a target. Is there any way for MJ to talk to FAR to at least ball park a landing trajectory? Barring that, any tips or tricks to landing with FAR? (wrong thread for that I know)

Alright, need to talk serious here. Working on this alone is getting harder and harder as I go on. This may be because this is too ambitious, or there is too much workload on me. I've been doing most of the program, while Norway174 has been helping in small bits when he can, as he is incredibly busy (You know, job stuff). Now, the only way for this project to continue is in my 2-tier plan: 1. Complete User Feedback, Designs and Suggestions - You heard us right. We want you to post right below this anything you want this program to be. It can be anything from small suggestions to completely detailed designs. All that matters is we don't want to make it our way, we want to make it your way. 2. HELP wanted - This one might be a little bit more needy, but important nonetheless. If you can print "Hello World" in a .NET programming language, you can help. No matter how much or how little work you provide, we will recognize you for your efforts. PM me if you want to help out. There may be a third tier, but only if it is plausible.

I think it is just the worry that Squad could turn into some awfull Employee-Abusing Development Company what drives these Threads. Without any Background-Knowledge, you cant even predict in which direction Squad is "developing"... but you know what? I am fairly happy that Squad does not talk about Employee-Matters. Imagine your boss would shout it from the rooftops what you did wrong and why they fired you. That does not mean that Nexis did anything wrong but it is a thing to discuss that falls clearly under the Privacy of Nexis and Squad even. My 5cents to this are: -Nexis, thank you what you have done for us by contributing to this Project -Squad, please keep in mind that huge fluctuation of employees brings a bad taste to your name.

Granted, unfortunately all they really want to talk about is Jersey Shore and the Kardashians. The ability to take other peoples super powers.

I hate dreams where your running from somebody or something, you feel like a drunk, keep falling over and stuff, then you try to close a door, your to weak to close it, they come rushing in, then you wake up. And then there are the dreams about snakes......there will be snakes everywhere you look. other dreams are just too naughty/weird/gross to talk about

Seems like there's two questions here: 1. How do I read part info 2. How do I read from the cfg itself, rather than what's loaded into the game. Every recognized line in a part.cfg file is loaded into the part object or its various modules or PartInfo object or whatever. The above code examples talk about how to get that. But if you actually want to read the cfg file you need to first find the confignode that is that part (i.e. find all PART confignodes, then find one with the value name where name == the part's id). Then you can getvalue for whatever property you want, and/or getnode if you want a subnode (like MODULE or INTERNAL or whatever).

Visitors to Julius Entering the Mun's SOI- I prepare for the burn Burning; It was a small burn due to the high periapsis Finished Travelling to the edge of the SOI of the Mun to meet Julius station A small correction burn; changed the ETA of docking to one orbit Whizzing round the Mun (Hooray for 500th screenshot!) The solitude of High orbits is unreal Raydon: Spotted the station! Mersy: Confirmed Raydon: Damn the Mun is far away Guston: Instruments OK, begin docking This docking had no RCS bar the stations and that was in effect, useless due to its size. It was the first time I'd ever needed to do or done anything like this but it demonstrates the craft's ease of use Nelrim: Hello there newcomers! Mersy: Hi there Nelrim, how are you Nelrim: Good but bloody bored- even the routinely-trained docking procedures are more interesting Mersy: Well we've got no RCS so this will be lively Nelrim: Best of luck chaps Mersy: Coming in now Nelrim: Right-o After some maneuvering, I the crew positioned it close enough for magnetism to take over Nelrim: Well done! Equalizing pressures, come on in when its ready! Unfolding the solar panels *** Milmon: Ok, when you're ready, come to us Raydon: Affirmative Guston: You're good to go Raydon Mersy: Opening the hatch interior Raydon: I'm out Guston: Right Mersy: Knock on their window, that'll be a good greeting Raydon: (Laughs) Affirmative, watch this Milmon: Crikey! Laughter Raydon: (Laughing) Still got your socks? Milmon: You guys... Raydon: Whats it like up here? Milmon: At the moment, routine. Since the comms module that we'll use to talk to the guys on the ground hasn't been launched yet, we're just staying alive Raydon: How long will it be till the next module of any kind comes? Milmon: I'm afraid I don't know Raydon: Shame... coming to the hatch now Milmon: Nelrim is at the hatch controls, standby Raydon: I'm on the ladder, prepare for my arrival, over Nelrim: Opening hatch now Raydon: (Stumbles through hatch) Closing hatch Nelrim: Yeah Click Raydon: Right, I'm getting this off for a bit, don't mind if I look around? Nelrim: Not at all Milmon: Nelrim, Guston is coming across now Nelrim: OK, I'll guide him in Nelrim: You there Guston? Guston: Aye, coming past now Nelrim: Grab the ladder and open the hatch manually, its locked Guston: Why so? Nelrim: Procedure Guston: ... Nelrim: You got the ladder Guston: Yea, unlocking the hatch now Nelrim: Glad you made- Raydon: Guston! You got here! Guston: Of course Nelrim: So... you ready to stay up here? Guston: Hope so Milmon: I'm coming to you now Nelrim: OK Guston: Have you got beds? Nelrim: Well, they are beds but more like strapped-down sleeping bags Guston: Small price to pay for the mission Milmon: (Opening the indoor hatch) Quite Raydon: Milmon! My dear fellow (Shakes hand) A pleasure to meet you Milmon: Likewise- I presume you've met Nelrim Raydon: Indeed (Shakes hands with Nelrim) What a view you've got Milmon: Magnificent isn't it Guston: I've got the camera from our ship, we will use that here if its ok Nelrim: Certainly, taking pictures for science is why we're here as well as research Mersy: I'll come over in an hour when I'm done with the MunShuttle- I've heard of your pictures and science at home, would be quite interested to see what you've got instore Nelrim: Well, I'd be much obliged! Milmon: One more thing chaps- we have decided to create a mission log, a book of some description, on the station's computer and written in the book- we'd be privileged if you could start it for future crews. We are the first and so we want to set almost a tradition for those that visit. Guston: Who came up with this?! Nelrim: (Raises his hand) I- Guston: My, its a good idea! I'll start it Milmon: I'll get it in a min, in the mean time, would you like to familiarize yourselves? Raydon: A tour? Milmon: Only the best (Laughter) Next, we shall land things! Stay tuned!

I blame social media. Once you've got twelve places to send out updates you forget that having a centralized place to talk about things is incredibly helpful, especially to those of us who think things like Twitter and Reddit are the most terrible things on the internet (aside from the obvious).

So, There are three possible destinies for your PC, the removal of your internet browser - death "Up to you then" - probable death Or making mods - VERY probable death And several near-stable loops such as the bored-RAM-break loop and for some people, the learn GIMP and Blender and Unity and C# - relearn GIMP and Blender and Unity and C# loop. The RAM loop tells you your PC died a long time ago. The C# loop is almost certain to make this happen: XKCD: Cautionary Point is, parents, talk to your kids about modding video games before someone else does.

Talk to JewelShizen, the maintainer of HL. He can help you.

Thanks! To answer your question about downloads, "yes and no." Yes, KSP TOT v0.10 is available for download. The version I'm showing off here, though, is still under heavy development and I haven't put it up anywhere yet. Stay tuned! And feel free to ask questions about the software if you have any. Thanks! Yes, the code requires the Optimization and Global Optimization toolboxes. If you don't have these available, it will not run. I have looked at the solver that you provided, but it's tuned for and heavily integrated with our current solar system, so it's easier to just keep using my own stuff that I have control over. If you're interested in testing, I may throw up a pre-release version later today or tomorrow at some point... Thanks! Keep in mind that KSPTOT v0.10 is available and will help do those Joolian moon tours. No need to wait for my "real time system" updates to start using KSPTOT! I have to apologize for not posting much over the past few days. I've been busy working on the back end of the code, which is mostly the architecture of the telemetry send/receive system. Most that involved getting KSPTOT to talk to KSPTOT Connect and KSP itself correctly, setting up the protocol for retrieving TM sent by the spacecraft, and so forth. Interesting challenges, but not really picture-worthy. Give me about an hour here and I'll have something neat to show, though.

CHAPTER 47 TYLO LANDING *** BERTY v.2.0.8b: SAS operational. RCS operational. Engines operational. Solar panel operational. Autopilot system online All systems nominal. Tylo Lander is fully operational and ready for landing. NED: It better be. BERTY v.2.0.8b: Initiating the Smart Eve Suit test. STEVE v.1.0.7: Smart Eve Suit test initiated. Synchronizing with on-board computer. Suit temperature – 20 °C. External pressure – 1 atm. Acceleration – zero g. Exoskeleton operational. Life support operational. AutoDoc operational. Recording equipment operational. Oxium level - 99,83%. BERTY v.2.0.8b: Smart Eve Suit test completed. All systems operational. NED: Huh. JOHNDON: What is it, N-Ned? NED: He's going to land on Tylo, so shouldn't we call the exosuit... STYLO? MALLOCK: :sigh: JEB: Are you feeling alright, professor? MALLOCK: Yes. I'm ready. BERTY v.2.0.8b: Double and triple-checking of all systems is advised before attempting landing. MALLOCK: Would it take long? BERTY v.2.0.8b: Less than completing one orbit, professor Mallock. JEB: We shouldn't take any risk. Let's do this. *** BERTY v.2.0.8b: Approaching the landing zone. Deorbit burn in 30 seconds. NED: This is it. Good luck professor. JOHNDON: Yes – k-kodspeed, Mal. JEB: Remember, if anything happens just press the abort button and Danrey will take care of the rest. DANREY: Exactly. MALLOCK: I, uhm, I will. BERTY v.2.0.8b: Don't worry, professor. Landing procedure is fully automated. MALLOCK: I really hope so. I have no idea how to operate such vessels. NED: That's why BERTY and STYLO will take care of everything. You're going down there as a geologist. JOHNDON: It'll be fine. I'm sure you'll pick up some great samples, professor! MALLOCK: Mhm. Well, I think- BERTY v.2.0.8b: Deorbit burn in progress. MALLOCK: Uh! STYLO v.1.0.7: Acceleration – 1.1g JEB: Are you okay? Doctor, is he okay? CAMBO: It seems so. Such big acceleration is a big stress for his body, but after EVAs on Vall and with the help of the suit there shouldn't be any problems. So far as he don't exceed 2-2.5g. STYLO v.1.0.7: Acceleration – 1.2g BERTY v.2.0.8b: Initiating final descent. 14353 meters above the surface. NED: How are you holding up? MALLOCK: I'm fine! CAMBO: Hmm. Try to calm your breath, professor, you're burning up oxium. You won't have much time on the surface anyways, so try to slow down. MALLOCK: Uh! Understood! BERTY v.2.0.8b: 10000 meters above the surface. STYLO v.1.0.7: Acceleration – 1.3g MALLOCK: I can see Jool and the Sun! Aren't we going too fast? BERTY v.2.0.8b: No, professor Mallock. The rate of the descent is well within projected limits. 6500 meters above the surface. MALLOCK: Are you sure?! STYLO v.1.0.7: Acceleration – 1.4g BERTY v.2.0.8b: Yes, professor Mallock. 3500 meters above the surface. MALLOCK: Uh! I'm pretty sure we're going too fast! CAMBO: Relax Mal, your heartbeat is skyrocketing. And you are burning up the oxium too fast. MALLOCK: Easy for you to say! BERTY v.2.0.8b: 850 meters above the surface. BERTY v.2.0.8b: 300 meters above the surface. 200 meters above the surface. MALLOCK: Oh crap! JEB: Listen to me, you must calm down! You're using too much oxium. BERTY v.2.0.8b: 100 meters above the surface. 50 meters above the surface. JEB: Professor? BERTY v.2.0.8b: 10 seconds to touchdown. MALLOCK: Oh crap, oh crap, oh crap! JEB: I said calm down! BERTY v.2.0.8b: Five seconds. Four. Three. Two. One. Touchdown. Tylo Lander has landed. STYLO v.1.0.7: Acceleration – 0.78g MALLOCK: Good Kod... JEB: BERTY? BERTY v.2.0.8b: 57% of fuel remaining. 55% percent of fuel required for a safe ascent. BERTY v.2.0.8b: Checking oxium level. STYLO v.1.0.7: Oxium level - 86,32%. BERTY v.2.0.8b: Oxium level within limit. Estimated time for surface exploration 4 hours and 20 minutes. Estimated time for ascent and waiting before the rendez-vous with LAMGML “Alfa†2 hours and 30 minutes. Total time required for scheduled activities 6 hours and 50 minutes. Total oxium reserves 7 hours and 38 minutes. JOHNDON: Uff. NED: I knew it! I just knew it everything will be okay this time. MALLOCK: This time? BERTY v.2.0.8b: Cease of communication will occur in 3 minutes. JEB: Do not, I repeat, do not attempt to leave the lander without our supervision. You still have reserves of oxium, so even if you wait 15-20 minutes until we complete the orbit you'll be fine. Do you copy? MALLOCK: Yes. I'm not going anywhere without you. *** MALLOCK: I'm at the end of the ladder. I'm stepping to the surface now. JEB: Doctor? CAMBO: He can go. JEB: Okay, you can do it professor. MALLOCK: Uh! JOHNDON: Any f-first words? MALLOCK: I'm just glad I'm here. NED: Hmm, not that bad. STYLO v.1.0.7: Oxium level – 80%. MALLOCK: Wow. The view is strangely familiar. It looks like some desert on Kerbin, but without the sky and trees and sand for that matter. Only crust. BERTY v.2.0.8b: Professor Mallock, there is a lot of work to be done. MALLOCK: Yes, of course. It's a shame the flag was too heavy to take it though. May I start now? I want to take a closer look at these rocks! BERTY v.2.0.8b: Please wait until the Smart Tylo Suit test is completed . STYLO v.1.0.7: Smart Tylo Suit test initiated. Suit temperature – 20 °C. External pressure – 0 atm. Acceleration – 0.78 g. Exoskeleton operational. Life support operational. AutoDoc operational. Recording equipment operational. Oxium level – 79,87%. BERTY v.2.0.8b: Smart Tylo Suit test completed. You may proceed. *** STYLO v.1.0.7: Sample 15 secured. You have space for – zero – more sample. Oxium level – 31,67% MALLOCK: I think I'm done here. How much time do I have? BERTY v.2.0.8b: Remaining time for surface activities 13 minutes. MALLOCK: Huh. Should I try and do something during these ten minutes? Or should I just get to the lander? JEB: Doctor? CAMBO: After four hours? The exosuit is the only thing that's moving him right now, apart from the adrenaline. If he can, he should go now. JEB: You've heard him, Mal. You should get to the lander and- BERTY v.2.0.8b: Negative. Vital data may still be gathered. Continuing the exploration is advised. MALLOCK: Oh. Okay than, I will- JEB: No Mal, you're exhausted and you're running low on oxium. Get to the lander. JOHNDON: J-Jeb? BERTY v.2.0.8b: Negative. This is unreasonable decision. Please proceed, professor Mallock. MALLOCK: Err... JEB: No! Get to the lander. NED: Am I not getting something or is Jeb arguing with BERTY? MALLOCK: I feel fine, you know. I can do it if- JEB: I said no. If exosuit malfunctions we will loose both you and the samples. We won't risk it, not after... Bob. BERTY v.2.0.8b: Jeb. Your assessment of the situation is heavily influenced by your emotions. It's advised that you take a stress pill and- JEB: No, BERTY. He's going back right now. This is a direct order from your commander. BERTY v.2.0.8b: ... STYLO v.1.0.7: Oxium level – 30% MALLOCK: Err, if you are- BERTY v.2.0.8b: Affirmative, commander. Executing direct order. Professor Mallock, please return to the Tylo Lander immediately. MALLOCK: Copy that. I can't wait to make some experiments with those samples! *** STYLO v.1.0.7: Oxium level – 28% BERTY v.2.0.8b: All systems nominal. Initiating ascent protocol in 10 seconds. MALLOCK: What about acceleration? BERTY v.2.0.8b: Peak acceleration is expected to be equal to 2.1g. Five seconds. MALLOCK: :sigh: I guess I don't have a choice. BERTY v.2.0.8b: Three. Two. One. Ignition. BERTY v.2.0.8b: Liftoff. Ascent protocol in progress. STYLO v.1.0.7: Acceleration – 1.6g MALLOCK: Uh! CAMBO: Try to breath normally please. JEB: It won't take long, professor. STYLO v.1.0.7: Acceleration – 1.7g MALLOCK: Uh! I really, really miss weightlessness, you know? STYLO v.1.0.7: Acceleration – 1.8g MALLOCK: And I would love to get off this suit. It stinks horribly after – uh! - after these several hours. CAMBO: This suit is the only thing preserving you from braking your spine right now, so you shouldn't be so harsh on it. STYLO v.1.0.7: Acceleration – 1.9g MALLOCK: Argh! How long, BERTY? BERTY v.2.0.8b: 30 seconds remaining. JEB: Just hold on a little longer. STYLO v.1.0.7: Acceleration – 2g CAMBO: Crap, I'm getting pretty bad readings! MALLOCK: What?! How bad? STYLO v.1.0.7: Acceleration – 2.1g BERTY v.2.0.8b: Warning. Crew member endangered. 15 seconds remaining. MALLOCK: How bad?! CAMBO: Don't talk, breathe! MALLOCK: Uh! BERTY v.2.0.8b: 10 seconds remaining. JEB: Come on Mal, don't give up! Just a little while longer! BERTY v.2.0.8b: 5 seconds remaining. MALLOCK: Uh! CAMBO: Breathe normally for Kod's sake, concentrate on breathing! MALLOCK: ...! JEB: Professor! BERTY v.2.0.8b: Ascent protocol completing. Orbit achieved. STYLO v.1.0.7: Acceleration – 0.1g MALLOCK: Argh! BERTY v.2.0.8b: Circularization in progress. JEB: It's over, Mal! You'll be alright! Right? CAMBO: Yes, he should be okay. MALLOCK: For Kod's sake! So what was it, doctor? CAMBO: It doesn't matter know. You- MALLOCK: It matters for me. Heart attack or what? CAMBO: Well, yes. Too much stress on your circulatory system. BERTY v.2.0.8b: Circularization completed. MALLOCK: Kod... STYLO v.1.0.7: Oxium level – 25% JEB: Try to relax now, professor. Danrey is on his way. MALLOCK: Copy that. I'll try at least... *** DANREY: Okay, matching orbital velocities. You should see me now, Mal. MALLOCK: Yes, I can see you! I can see the flames! DANREY: Repeat please? MALLOCK: Exhaust gases, I can see the exhaust gases from the engines. DANREY: Roger. And velocities matched. Are you ready for an EVA? MALLOCK: Yes I am. STYLO v.1.0.7: Oxium level – 6% DANREY: Copy that. I'll come closer to you. MALLOCK: Uhm, could you do this a little quicker? DANREY: I'm doing it as fast as I can safely do it, Mal. MALLOCK: Okay, okay. It's just, well, this whole thing really stressed me, you know? I guess I really was burning it much faster than I should. DANREY: You mean the oxium? Relax, I have more than enough for both of us. How about now? Can you see me? MALLOCK: With no problem. You know what? DANREY: Yeah? MALLOCK: There is one thing I want more than studying the samples. DANREY: Oh really? MALLOCK: Yes. Heck, even more than exploring Pol. DANREY: Just tell me what it is already. MALLOCK: I want to get out of this suit. It stinks terribly and I feel like I'm slowly suffocating being inside it. DANREY: Well, technically you are. MALLOCK: No, I mean like I am feeling very bad in it, you know? I don't know why though. DANREY: Mhm. Small discomfort after exploring one of Jool's muns. The little sacrifices we all make. *** MISSION STATUS ***

i get in the lift with an aggressive corgi, i talk to him while inquisitively daydreaming badass things

The facts were the same but the conclusion was oppositional. Also your rational/reasoning is lacking. The point of having set tank sizes is because it is easy to program. The size ratio comes from restrictions in the physics engine, as does the lack of n-body physics. Don`t fool yourself those restrictions are there because of game mechanics. The game mechanics are there because of the restrictions. You have things the wrong way round. Procedurals only go up to 5m at the moment so you simply cannot do the ridiculous thing you suggest as a reason to not have them. What is so great about having each engine on it`s own orange tank anyway? I can build anything and pretty much have. I`ve landed a 600T space station on a moon. I`ve planted a flag on *every* place it is possible, all stock with no mechjeb. You can talk to me about what is easy and what is not after you have done that. I`ll say it plainly. Procedurals do not make craft design easy. As has been said, are you making rockets or playing tetris? If the `challenge` is to use a restricted part set and still build what you want I take it you only use the smallest engine and the smallest tank size? As you say if you need a big tank you could just go "Herpaderp I`ll use the orange one and put a mainsail on it HERPADERP" so obviously you build your ships from ants and oscars leading to 3000 part craft that can barely fly? Ridiculous. EDIT : Apologies for the double post, should have edited the first post... I am in two minds about this. I can see how it would be pointless as you could just warp and your craft is built but also I can see how it could be good in career mode meaning you had to factor build time into your craft to get them to rendezvous or launch for a window. For time sensitive launches it would be an extra layer to consider. I would want it to be optional though, as in advanced mode or similar.

See, what I'd like is something in between the first two: something that makes those aesthetic or terrain changes to some of the more boring bodies (like your revamp of Laythe), but that adds some of your other concepts (Tylo, red Minmus) as entirely new bodies, a la the planet factory. But I think it's important that the stats of all existing bodies don't change significantly (except moving Eeloo to be a moon of a second gas giant, as has been talked about for a while) so I wouldn't use the third option; yes, the Joolian moons are bigger than any in our own solar system, as is Moho, but honestly I think that makes for a better game. The Galilean moons have surface gravities comparable to our own Moon, with no atmospheres, and that just isn't a challenge. You can land on Mun with very primitive designs, after all, so scaling down Jool's moons would mean the only challenge would be getting to Jool from Kerbin, and that's a non-issue once you get LV-Ns. KSP's smaller scale adds a sort of surreal quality to the gameplay, and the relative scales seem to reflect that well (unless you download the realistic solar system mod, of course). My main reason for liking the status quo for existing bodies is simply one of community. These boards are one of the things that really separates this game from the others I've played recently, and it'd be a shame to lose the commonality at the core of that. If we're having a conversation about designs that can reach Laythe from Kerbin, there's a big difference between accomplishing that in the core game, where they're halfway across the system from each other, versus in your proposal where they're adjacent moons of the same planet. Adding new planets and moons, or changing aesthetics, won't affect that. Minor gameplay changes are fine, like adding a very thin atmosphere to Moho (just enough to give it a haze, without really affecting takeoffs or landings), but I don't think you should do anything that'd require you to preface your accomplishments with "...but I'm using this mod" when describing them. So what I'd suggest is simply this: add a second gas giant using that nice blue coloration you've assigned to Jool, at Eeloo's current position. (Keep Jool green. As the wise man said, it's not easy being green.) While Saturn is a bit smaller than Jupiter, and Uranus/Neptune even more so, I'd like this one to be bigger than Jool to make it more visible from the inner planets. Give it four moons, in order from near to far: > Innermost is that small red Minmus, with a pretty severe orbital tilt. No atmosphere, no water, just a low-gravity rock in a painful orbit. (It's a captured Kuiper object, not a natural moon, so the usual patterns of orbits don't really apply.) > Next is a rocky Titan-type moon, smaller than Kerbin (~0.5g surface gravity) but with an Eve-thick atmosphere, containing just enough oxygen for jets to function at low altitudes. This'd be the best place to play with planes and the thick atmosphere would make it a significant challenge to take off from with rockets despite the lower gravity. It'd only have minimal oceans (<10%), with large mountains extending most of the way up through the atmosphere (a la Olympus Mons). > Then comes your Super Tylo, huge surface gravity and a thin atmosphere. > Finally, Eeloo as the outermost moon. Ideally this'd get cryovolcanoes and a very thin atmosphere (like that Moho suggestion above), but even as a naked almost-featureless ball it'd be nice as a convenient place for a mining base. If you could give this new gas giant rings (remembering to leave gaps where the moons are) and tilt its moons' plane relative to the ecliptic, even better. Regardless, the net result would be to add what is, in effect, a "hard mode" planetary system containing a bunch of very challenging, interesting bodies for people who've accomplished all the important feats in the stock game. That way, all accomplishments involving the existing bodies are unchanged. (Also, savegames wouldn't suddenly fail as objects orbiting each existing body crash due to changed gravities. Rovers and such on planets with changed terrains would have issues, of course, but I think the terrain changes are a bit more necessary.) If I talk about how I finally landed on Adlivun and Svarga, the first and third moons of Ghoti (or whatever you name them), people won't think I'm talking about Tylo, the second moon of Jool in their stock game; they might not get the particular reference I'm making, and would need to search the boards to find your mod, but there'd be no question of whether they'd accomplished the same feat already. Besides, more planets and moons gives us more stuff to do. Changing existing objects' stats only gives us DIFFERENT stuff to do.

Assigning a resource to a particular area would probably involve a plug-in and I'm not really all that good with code... (though I guess I could talk to Fractal...) I am developing a plugin regardless, to handle the future Data Storage functionality. The way I'm gonna handle xenon scoop balancing would be to have the scoop require a power supply- the more electricity you supply, the faster xenon would regenerate, up to a point. The end regeneration rate would be a set value, but the energy draw would still grow exponentially even after it has been reached (meaning you can't just leave it on without some huge passive EC generator). I am also toying with the idea of having the scoop detect when you're using an ION engine and automatically shut itself off. Right now I am however focusing on getting the Data Storage to work, but progress is slow as I have other obligations to attend to... Also, most of the textures are stock. The ION engines are literally upscaled models of the stock one. The texture used for the circular scoop belongs to Kerbtrek.

Thanks for the comments guys! thanks man. yeah soz about the length, got carried away. Next mission is way more complex but I'll try to make it's recount more concise! How else do you take off!? At leasts that's how the kerbals in this career think. Straight up, that's just crazy talk! I felt like those two 909's should be put in a museum after returning from this mission. They did all the work aside from ascent to LKO. Stalwart little engines! Yes gorram-it!! Damn why didn't I think of working that into the tale! The line in my sig is only a sentence or two apart from that line! But I'm always a bit afraid to proclaim that anyone is a leaf on the wind, incase that dooms them to getting a spike through the chest! Next mission is well under way so should have that up before long. It's a complex one so lots of pics to upload. btw was the res of the pics ok? I could only see them at low res cos I'm using my phone as a hot spot currently (which sucks). Should have proper net next week sometime, yay! Once I get connected again and can get to my dropbox I'm going to post all the craft files for this series, don't know why I didn't think of doing that before.

I understand a lot of work is being done to improve the wiki, which is a lot of work but at the same time desperately needed. I just picked up the mod and frankly, even with the "wiki" as it exists now on github i scarcely know where to begin. There is talk of upgrading things like the thermal generator, but how do I upgrade components? When i begin mining resources, must i physically connect craft to transfer the resources or make use of mods like KAS?

Originally Posted by vardicd, Would it be possible to put an explanation on the Dual Technique Magnetometer page as to how to read the Antimatter flux? It has two separate numbers, one that seems to range from 0 to 9-ish, and then a second number that changes as the 0 to 9 one rolls over, and I'm not sure if Higher numbers are better or lower numbers or one high and the other low? Uh, no, This just sent my brain screaming into a corner and its refusing to talk to me now. {Seriously, me and math have been enemies for a long time.} I need someone to explain this in a "this number high=good, this number low= bad" fashion or I will never get this.

i return to the lift to find Bladewolf, we talk a bit about our adventures while the lift continues to ascend to floor 21