[1.0.5] FASA 5.44

[MaverickSawyer]

In the Science tab there's a big white part with Big G in it. That goes beneath it. Put on thrusters and engines like the stock 24-77 and you're good to go.

Yeah, there's both a standard and a Rescue Big Gemini aft compartment. However, the part that you add below THAT, with the docking collar... It's not the usual SM. I'm confused as to where you add engines.

Also, during a LES test using the black Big Gemini, I snapped the rear crew compartment off upon parachute deployment... Don't know if that's normal when the parachute goes straight from stowed to full deployment at ~75 m/s, or if it was a one-off glitch.

Otherwise, the other parts (Agena, Atlas, Mercury, Mun lander) are all superb.

[jrandom]

Yeah, there's both a standard and a Rescue Big Gemini aft compartment. However, the part that you add below THAT, with the docking collar... It's not the usual SM. I'm confused as to where you add engines.

Also, during a LES test using the black Big Gemini, I snapped the rear crew compartment off upon parachute deployment... Don't know if that's normal when the parachute goes straight from stowed to full deployment at ~75 m/s, or if it was a one-off glitch.

Otherwise, the other parts (Agena, Atlas, Mercury, Mun lander) are all superb.

You mean the BigG just fell off? Put your parachute stage in its own stage and see if the problem goes away. (it might be specific to Realism Overhaul, but I found that staging the Gemini pod triggered a decoupler at the bottom -- I thought it was the g-force from parachute deployment that was snapping it off, too, but it was that darned decoupler.)

[frizzank]

With that much weight you need to use the drogue chute, I could strengthen the attachments but then it would be almost indestructible if you crashed.

Yes the Gemini cap is facing the wrong direction. but its just the texture. You can rotate it if it bugs you, not really a big enough deal to do a whole new update.

Edited December 23, 2013 by frizzank

[MaverickSawyer]

You mean the BigG just fell off?

No, the additional crew space, not the big white conical section you add after it. And yeah, the link failed under the opening shock.

With that much weight you need to use the drogue chute, I could strengthen the attachments but then it would be almost indestructible if you crashed.

Wait, we need to use the drogue?

*opens stock Gemini pod*

Son of a... *headdesk* That's what I missed.

That said, the Big Gemini stock craft seems to be busted. IDK why, it just says that some of the parts are locked or missing.

[ethan829]

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!

Loaded the included MIRV .craft and this is what I got:

[MKSheppard]

Any chance of a UA-1202 and UA-1203 SRM?

They were real proposals, as this August 1965 document I have from Scott Lowther details the potentialities for the "Titan IIID Standard Space Launch Vehicle".

The "Titan IIID" shown in this (2x2 5 Seg) is actually pretty interesting.

It's actually FOUR UA-1205 SRMs arranged in a cross pattern around the Titan III core.

At liftoff, only two UA-1205s actually ignite -- Motors 1 and 2.

They provide ALL the liftoff thrust until T+35 seconds, when Motors 3 and 4 ignite. At around T+75 seconds, Motors 1 and 2 burn out and are staged. At T+140 seconds, Motors 3 and 4 burn out and are staged, with the core igniting.

There's a bit more detail in the original document, including thrust/time curves for the SRBs; drawings showing the changes between Motor 1/2 and 3/4 to accomodate the differing thrust profiles.

Then there's this image that closes out the document, showing evolutionary paths open to the Titan family circa 1965:

Note 156" diameter (UA-156x family) SRBs -- these were later reused/recycled for Saturn V uprating efforts.

Also notice the proposed 156" diameter core for Titan as an evolutionary path.

Both paths (156" diameter core AND 156" diameter SRBs) were combined into the proposed Titan IIIG. Link.

[frizzank]

Loaded the included MIRV .craft and this is what I got:

http://i.imgur.com/RcAwMSg.png

That is a bug that was caused by me not checking part names when creating config files. The agena probe has the same part name as the ICBM. I copied the config as a base and did not change the name of the part. Oops!

Mirv probe core gets created, then the Agena with the same name and whala Mirv is now Agena.

you can fix it by changing the Agena_ProbeCore.cfg

At the top change

name = FASAICBMProbe

To

name = FASAAgenaProbe

Otherwise you can wait for an update if its not bothering you.

Edited December 23, 2013 by frizzank

[NathanKell]

Speaking of bugs.

LFE4X800Mini has no TechRequired line by advUnammned.

Mercury LES has a mesh line that doesn't point to its model. (should be mesh = Mercury_LES.mu right?)

[frizzank]

Speaking of bugs.

LFE4X800Mini has no TechRequired line by advUnammned.

Mercury LES has a mesh line that doesn't point to its model. (should be mesh = Mercury_LES.mu right?)

The LES is still using the legacy system of loading models and still works just fine.

mesh = model.mu
rescaleFactor = 1.0
scale = 1.0

The LFE4X800Mini, is missing its TechRequired code and is not currently showing up under the tech tree.

Thank you for your help....

[CaptRobau]

May I suggest adding this to the Radiometer:

	dataIsCollectable = True
	collectActionName = Collect Data
	interactionRange = 1.2

It'll allow the results to be taken from EVA, just like the stock Mystery Goo and other experiments. The Radiometer works great when put on the side of an Agena Target Vehicle, btw. IRL the Agena had a micrometeorite experiment there, which had to be retrieved with an EVA.

[Guest]

New SRMs would be really nice. Maybe go "all-out" and make boosters from 2 to 8 segments. 8 segments is what UA-1207s really looked like, because of the additional avionics segment. Dunno what 2-segments would be useful for, but I believe people would find use for this.

[Chebalu]

I have a problem because in the carrier mode I have only the white gemini pod (I have not tried in the sandbox mode). What went wrong?

Edited December 23, 2013 by Chebalu

[CaptRobau]

Probably your download or installation went wrong. Try it again.

[Cdodders]

No white nose cone or nose cone cap?!?!?!?!?!

[Chebalu]

Problem solved. The white pod is unlocked in advanced flight control, the normal one is unlocked in specializedControl. I don't know why?

But thanks CaptRobau!

[NathanKell]

The LES is still using the legacy system of loading models and still works just fine.

mesh = model.mu
rescaleFactor = 1.0
scale = 1.0

Weird, because there _is_ no model.mu in that folder. At some point you changed the mu file's name but didn't update the cfg. (the mu file *used* to be named model.mu.) Does it just grab any mu file then?

[frizzank]

Problem solved. The white pod is unlocked in advanced flight control, the normal one is unlocked in specializedControl. I don't know why?

But thanks CaptRobau!

I wanted to put it in a higher tech branch as an unlockable, didn't really have a better place to put it so suggestions are welcome.

Weird, because there _is_ no model.mu in that folder. At some point you changed the mu file's name but didn't update the cfg. (the mu file *used* to be named model.mu.) Does it just grab any mu file then?

Under the legacy system any model in that folder gets used, dose not matter the name.

dataIsCollectable = True

collectActionName = Collect Data

interactionRange = 1.2

Yes thats an awesome idea...

[NathanKell]

Huh, weird. Ok. Sorry 'bout that then.

[Cdodders]

the white nose cone for the rescue G is missing

[frizzank]

3.50 - Fixes

Rotated cone to correct direction

LES uses cfg points to model directly

4X800Mini is now in the tech tree

Agena probe is now named correctly and should not mess up the MIRV core. Crafts that had agena will have Mirv core instead of agena now.

MIRV Core is now wider so warheads can be placed without clipping.

Moved Gemini White pieces to there black counter parts location on the tech tree.

Radiometer is now transferable from EVA like the goo container.

http://www./download/3zgdg6ysh6tg0ow/FASA3.50.zip

http://kerbalspaceprogram.com/gemini-and-mercury-frizzank-aeronautical-space-administration-fasa/

[Deltac]

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.

Edited December 24, 2013 by Deltac

[frizzank]

Its meant to work with the other parts as a hole but it should have some in it anyways. At least everything else works....

I wanted to apologize to everyone for the buggy release. I was really rushing to get it out before Christmas break, and we all know what happens when we rush something. Thank you for sticking with me, and if you were having problems please download the latest, it should fix a lot of the problems.

Edited December 24, 2013 by frizzank

[sirkut]

Its meant to work with the other parts as a hole but it should have some in it anyways. At least everything else works....

I wanted to apologize to everyone for the buggy release. I was really rushing to get it out before Christmas break, and we all know what happens when we rush something. Thank you for sticking with me, and if you were having problems please download the latest, it should fix a lot of the problems.

Don't beat yourself up. I appreciate everything you are doing with this release.

[CaptRobau]

I'm just glad we got to play with it in the first place. Loving the Agena.

[Cdodders]

The white docking nose and cap arent there....