Deltac

Take a look at my post above this, and you'll see that the Juno I was the one that launched Explorer 1. By what I'm looking at, there were no IRBM's developed from the Redstone family. Just one short range surface-to-surface ballistic missile, unless IRBM means SRBM, which it doesn't.

I don't understand what you just said, but I'll try to answer your question: The Juno I rocket was built on the Redstone rocket. The "Juno upper-stage" Frizzank is referring to is better known as the MGM-29 Sergeant cluster. They took that cluster, and put it on top of a Redstone (stretched). The Redstone itself was stage 1, then stage 2 was 11 solid rockets in that cluster, then stage 3 was 3 solid rockets, and then fourth and final stage was just 1 solid rocket. What you're looking at in that picture are 3 stages in 1, not 1 upper-stage The Redstone was already conceived by the time Juno was conceived. Atlas was developed on it's own by General Dynamics' Convair (the ICBM and Mercury Atlas), while the Redstone family was designed by the Air Force and manufactured by Chrysler. There was also a Juno II which was developed from the Jupiter Medium Range Ballistic Missile, which was an evolution of the Redstone family, but not a Redstone Rocket. There were other Jupiter rockets in the Redstone family, but they were used for testing components for the Jupiter Missile. Sources: http://en.wikipedia.org/wiki/Redstone_%28rocket_family%29 http://en.wikipedia.org/wiki/PGM-19_Jupiter http://en.wikipedia.org/wiki/Atlas_rocket http://en.wikipedia.org/wiki/Juno_I http://en.wikipedia.org/wiki/MGM-29_Sergeant And to answer your first post (DOUBLE POSTING IS BAD), the Kerbolar system is 64% of the Solar System's scale. The Mun is indeed closer to Kerbin than the Moon is to Earth. Kerbin is indeed smaller than Earth. In fact, Jool is said to be the size Earth is (source?). So yeah, Kerbal Space Program is Space on easy mode. There are mods to scale everything up if you want hard mode. Got ninja'd on the next page. It's the next page for me cause lookatmysig.

You are kind of new here, so I'll dance while typing this. Bobcat does not give out ETA. The only ETA you will be given is Soon or Not Soon. Soon means not a lot of work left to do (perhaps just balancing). Not Soon means either some issues came up with the item in question, or there's still more to add. Please take into account real life problems cropping up. My legs are tired.

Oh hello there, BoulderCo Aggressive memory reducer. That might be at fault here. Have you updated to the latest version? If so, can I get you to try unistalling that (and whatever else so you can actually play the game) and checking the parts that were previously affected? Wait a second, you don't have KW, Novapunch, or B9? The madness!

Yep. Spaceport Forum posts

That's what happens when you play the campaign mode, and either the parts are not researched yet, or are not in the research tree. If they are supposed to be in the tree, go back to the research center, find the parts, and "buy" them. Yep, you gotta do that when you add stuff to the tree.

List of other mods, please. And probably give us an output_log.txt while you're at it.

Welcome to the forums, noobie! Firstly, yes, the Agena and Gemini in this pack dock with each other. It's up to you to not crash them together... or to do just that, it's up to you. Secondly, the current VAB is actually bigger than the previous VAB, and can indeed allow for a Saturn V to be built. Look for Novapunch for custom building the Saturn V, and go here for a Saturn V replica. You will have to make your own LEM and CEM as no one has made a nicely detailed version of either.

"Installed the Aggressive version as is" That means I didn't add the folder to the config. The strange thing is when I loaded up KSP with the Aggressive version, some textures that were broken before were now fixed. Mostly parts with .png textures are affected, but a few .png textures are not affected. .tga parts appear to be unaffected, if I remember correctly.

Not sure if this is a bug, or just side affect from the memory reduction, but here goes! Installed the Aggressive version as is, worked like a charm in memory reduction. Looked at some of my parts, and the textures look like they lost more than just size. The textures in question are from the FASA pack. Everything else seems fine, but Novapunch parts might be affected, too. Pictures it illustrate the problem: Before aggressive After aggressive These two were taken at the same time of day: Before aggressive After aggressive The shading seems to be affected adversely.

Welcome to the KSP Bobcat Thread! Firstly, the spoiler system has been broken since early 2012 due to someone using it to hack the site, or some bs. That's been on the to-do list for a long time. Probably need to add "Find to-do list" onto a new to-do list. Secondly: Bobcat removed all the links to punish the people asking for updates (which obviously horribly backfired). Just go to spaceport, and search for bobcat.

Never had this issue. Do you have FAR installed? I had an issue with the Atlas Mercury not wanting to fly straight with FAR once.

Are you sure you're using the current version of Realchute? Everything works fine for me. Realchute includes a Module Manager file for FASA.

Bug Report time! The Agena target vehicle in FASA has a bad reaction to undocking after you return to it from the tracking station. After undocking, most of the parts want to seperate from the main probe core. Here's the thing, they haven't actually disconnected. The fuel tanks and engines still bring up their little context menus when right clicked. After some tests, I ended up unistalling KJR, and the bug did not occur. I took the liberty of reinstalling KJR, turning on Debug mode, and getting a copy of the output_log.txt Dell_output_log.txt Vehicles used in test: Gemini Test and Agena Test. That should be the only flight in that output log.

I managed to recreate the bug. If you try undocking the Gemini from the Agena after you return to it from the tracking station, then the Agena does the splits. Environment: Built the Agena, sent it out for launch, hack gravity, flew it on RCS away from the launch pad, and landed nozzle first on the ground. Built Gemini, sent it out for launch, hack gravity still on, flew it on RCS over to Agena for successful docking. Tested undocking at this point, bug did not occur. Re-docked Agena and Gemini, landed on Agena nozzle, went to space center. Selected Tracking Station, and then Gemini Agena test. Tested undocking, and bug occurred this time. I took a look at the output log, and nothing in there said anything about the any of the FASA parts at the time of undocking. I will not these two lines that popped up: Part FASAGeminiNoseCone2 cannot load module #4. It only has 4 modules defined Part FASAGeminiSasRcs cannot load module #3. It only has 3 modules defined I'm doubtful that has anything to do with it, but you never know. What I think might be causing this issue is Mechjeb. Several errors kept popping up for mechjeb in the log, so I'll update to the latest version and see what happens. Until then, I'll just have to complete the Agena Gemini missions before getting bored. Update: Couldn't post anything last night due to the forum going down right when I hit submit reply. Since then, I unistalled mechjeb completely, and retried. Bug occurred again after returning to vessel from tracking station. My next option is to unistall KJR.

Found another bug, but I'm not sure what's causing it. No hoorah. I had the Gemini docked with the Agena, and everything seemed okay. It's when I undocked from the Agena that the laws of physics were canceled out on the Agena, and only the Agena. Basically, after undocking, the agena probe and docking port recede into the rest of the Agena, passing through matter as if it weren't there. Strangely enough, right clicking on the other parts of the Agena brought up the menus as if everything were still connected. I then turned on RCS, and tried maneuvering around, and that's when the fabric of space and time collapsed in on itself. Things broke apart, as you can see in the picture. But the menus still came up. I then said, "Screw it," and throttled the engine up, which worked. The engine, and only the engine, moved forward until it hit the Gemini nose, as if physics were turned back on. But the engine went through the fuel tanks to get there. After that, the menus stopped coming back up, and the Kerbalnauts GTFO'd before something else happened. To be honest, this isn't the first time this has happened. The first time was after I renamed the Agena core to it's proper name, and my already in orbit Agena's core turned into the ICBM core, as expected. I undocked the Gemini, and physics collapsed. I however wrote this off since there was a part there that shouldn't be, and things were already broken looking anyway. Now that this has happened again, I think it might be something else. However, seeing as no one else has said anything about the Agena being broken, I'm not sure what to do. I'll recreate the events just to make sure. Mods installed: KJR CrewManifest (Sarbian version comes with toolbar plugin) 6s Service thing by Nothke that comes with Firespitter plugin Mechjeb Module Manager RCS build aid Real Chute Procedural Fairings Sumghai Service module which comes with Fustek Plugin American Pack (just the LRV) AIES Aerospace, not all parts KSPX KW rocketry, not all parts Lionhead Aerospace Hermes, which I'll probably unistall anyway as it's laggy. NovaPunch2, not all parts.

1) The Gemini Docking cone has two docking modules for size 0 and size 1 ports (clamp-O-tron and clamp-O-tron jr.) It does not matter which "control from here" you click. For action groups with the dual "decouple node", just add both. Might as well say that if anyone thinks it up 2) Without scrolling up, I think it's been mentioned, but it's up to Friz to write it down in his to-do list (if he has one! bum bum buuuuum!)

Don't worry about it friz. I like finding bugs Or making them! (:<

I found another bug! HOOORAAAH! So, even with the name change for the Agena probe, I still could not get Module Manager to add Mechjeb to it. The problem: You added Mono propellant to the part in the config, but you forgot the RESOURCE tag. I thought it was odd that the torque system ran on mono propellant, but there was no on board fuel for it to use original config: PART { name = FASAAgenaProbe module = Part author = Frizzank MODEL { model = FASA/Gemini2/FASA_Agena/Agena_ProbeCore } rescaleFactor = 1.0 scale = 1.0 node_stack_bottom = 0.0, -0.5, 0.0, 0.0, 1.0, 0.0, 0 node_stack_top = 0.0, 0.75, 0.0, 0.0, 1.0, 0.0, 0 //node_stack_connect1 = 0.624, 0.75, 0.0, 0.0, 1.0, 0.0, 0 //node_stack_connect2 = -0.624, 0.75, 0.0, 0.0, 1.0, 0.0, 0 TechRequired = unmannedTech entryCost = 5000 cost = 650 category = Pods subcategory = 0 title = Agena Probe Core manufacturer = FASA description = The Agena Probe core barely has enough computing power to run a modern calculator, but you just need it to sit there while you dock with it. // attachment rules: stack, srfAttach, allowStack, allowSrfAttach, allowCollision attachRules = 1,0,1,1,0 mass = 0.25 dragModelType = default maximum_drag = 0.2 minimum_drag = 0.15 angularDrag = 1.5 crashTolerance = 12 maxTemp = 3100 explosionPotential = 0.25 vesselType = Probe CrewCapacity = 0 MODULE { name = ModuleCommand minimumCrew = 0 RESOURCE { name = ElectricCharge rate = 0.005 } } MODULE { name = ModuleSAS } MODULE { name = ModuleReactionWheel PitchTorque = 0.01 YawTorque = 0.01 RollTorque = 0.1 RESOURCE { name = MonoPropellant rate = 0.005 } } MODULE { name = ModuleRCS thrusterTransformName = thrustTransformRCS thrusterPower = .5 resourceName = MonoPropellant fxOffset = 0, 0, 0.0 atmosphereCurve { key = 0 390 key = 1 175 } } RESOURCE { name = ElectricCharge amount = 100 maxAmount = 100 } //Where for art thow, Resource? { name = MonoPropellant amount = 20 maxAmount = 20 } } Found another bug! Yippee! The Gemini Docking Nosecone is no longer listed under utility. It's under propulsion. Reason why: The category node in the config is missing.

Welcome to the forums! ... Stupid Chris, you removed mentionings of FASA MM files being included in the pack on the first post. The changelog doesn't count as most people are just going to pass over it if they're new here. Anyway, Charles, there is a Module Manager config included in the pack. You just need to download Module Manager, put the Module Manager plugin into Gamedata, and then drag and drop the FASA files in Real Chute into Gamedata.

Sorry admins, but it must be done. This comment bears a bear picture: Happy bear approves

I think I found a bug! Hoorah! In the Agena probe Config, it has the same exact name as the ICBM probe config. name = FASAICBMProbe I think this might cause some bugs, such as the bug I have where trying to add mechjeb to all command parts won't work for the Agena probe via Module Manager. I only noticed this because I wanted to add a separate line in my MM config file for the Agena core, and I needed it's name. Also, for the nosecone problem, it is upside down backwards. I was wondering why it looked so weird. Frizzank, you got some 'splainin to do!

Could you show us a pic of what you're talking about? If you're talking about the guide rod on the Gemini Nose, it's supposed to be on the same side as the hatches.

ninja me one more time frizz, and I'm taking your coffee away.

I agree.