Kemini + FASA Gemini + RasterProp? (done)

[Wesreidau]

Hello, and boundless apologies to the add-on makers I'll be slighting with this.

I love the FASA Gemini IVA model, and in particular, go crazy with Raster Prop Monitor's add-on that's filled with gorgeous switches and MFDs. However, the Gemini capsule's exterior isn't stockalike in the slightest, requiring two or three parts just to get to a standard rocket body radius. On the other hand, Kemini has a cute-if-cramped two man stockalike capsule that fits neatly on standard nodes, but the IVA... well nothing is going to compare to the Gemini IVA.

I took a look at the config files and so forth, and think with a little direction I could hammer this out myself. So the first question is how do you associate an IVA to a part, and would these be compatible, IE windows etc. There are a number of little features on the Gemini that obviously can't work like the docking camera, but just the ability to look around the cabin and press buttons without excessive clipping is all I'm asking for.

The second thing; if I bundled these add-ons together and repackaged them with credit to the authors, would I be immediately lynched, bifurcated or merely beaten? My life insurance policy pays double if I'm bifurcated.

Addon threads for reference.

The IVA: http://forum.kerbalspaceprogram.com/threads/24867-1-0-FASA-Apr-29th-1-0-Release-v5-31

The Exterior: http://forum.kerbalspaceprogram.com/threads/104925-1-0-2-K2-Command-Pod-Two-Kerbal-stock-alike-pod

The MFDs: http://forum.kerbalspaceprogram.com/threads/66824-0-23-5-FASA-Gemini-IVA-Modernization-2-0-%28RasterPropMonitor%29

Edited May 3, 2015 by Wesreidau

[Mecripp]

In the cfg you see on FASA

INTERNAL
{
  name = FASAGeminiInt2
}

EDIT- You would make the one look like if your wanting to use FASA internal on K2 Command Pod

PART
{
// this is a sample config file, for determining a good file format for defining part parameters
// comment line - ignored by cfg parser
// empty lines, or lines without a '=' sign are also ignored
// all other lines are split at the '=' sign, and the left operand is used to know what parameter we are setting
// diferent parameters require data in different formats (see docs), and each module has it's own parameters (again, see docs)
// each assignment must be in a single line. Lines without assignments will be ignored. (You CAN turn on word wrap, though)
// each keyword here relates to an existing variable in the assigned module. If the keyword isn't found, it is ignored.
// conversely, if a keyword is left unassigned (as in not in the file), it will be initialized with it's default value
// This is done automatically, so any public variable defined in the loaded module can be accessed this way (provided it's value can be parsed)


// --- general parameters ---
name = K2Pod
module = Part
author = JFJohnny5

// --- asset parameters ---
mesh = K2Pod.mu
scale = 1
rescaleFactor = 1

// --- node definitions ---
// definition format is Position X, Position Y, Position Z, Up X, Up Y, Up Z
node_stack_bottom = 0.0, -0.44, 0.0, 0.0, -1.0, 0.0, 1
node_stack_top = 0.0, 1.43, 0.0, 0.0, 1.0, 0.0, 0
bulkheadProfiles = size1, size0
CoPOffset = 0.0, 0.5, 0.0
CoLOffset = 0.0, -0.35, 0.0


// --- editor parameters ---
TechRequired = advFlightControl
entryCost = 4400
cost = 2200
category = Pods
subcategory = 0
title = K2 Command Pod
manufacturer = Castor-Pollux Industries
description = Through the use of some "creative engineering" and a technique which apparently makes it "bigger on the inside" the design team at CPI has managed to squeeze two Kerbals into a pod originally designed for just one! What a breakthrough! Just don't try to move around too much...

// attachment rules: stack, srfAttach, allowStack, allowSrfAttach, allowCollision
attachRules = 1,0,1,1,0

// --- standard part parameters ---
mass = 1.7
dragModelType = default
maximum_drag = 0.2
minimum_drag = 0.15
angularDrag = 2
crashTolerance = 14
maxTemp = 2400 // 3400

vesselType = Ship

// --- internal setup ---
CrewCapacity = 2

INTERNAL
{
  name = FASAGeminiInt2
}

MODULE
{
	name = ModuleCommand
	minimumCrew = 1	
}
RESOURCE
{
	name = ElectricCharge
	amount = 75
	maxAmount = 75
}

MODULE
{
	name = ModuleReactionWheel

	PitchTorque = 8
	YawTorque = 8
	RollTorque = 8

	RESOURCE
	{
		name = ElectricCharge
		rate = 0.4
	}
}

MODULE
{
	name = ModuleScienceExperiment	

	experimentID = crewReport

	experimentActionName = Crew Report
	resetActionName = Discard Crew Report
	reviewActionName = Review Report

	useStaging = False	
	useActionGroups = True
	hideUIwhenUnavailable = True	
	rerunnable = True

	xmitDataScalar = 1.0

	usageReqMaskInternal = 5
	usageReqMaskExternal = -1
}
MODULE
{
	name = ModuleScienceContainer

	reviewActionName = Review Stored Data
	storeActionName = Store Experiments
	evaOnlyStorage = True
	storageRange = 1.5
}

RESOURCE
{
	name = MonoPropellant
	amount = 15
	maxAmount = 15
}

MODULE
{
      name = FlagDecal
      textureQuadName = flagTransform
}

}

EDIT- You would have to have FASA installed or pull out a couple of files

EDIT- You could use them for your self but FASA is License/EULA All Rights Reserved

EDIT- You might keep a eye on http://forum.kerbalspaceprogram.com/threads/118037-WIP-GEMINI-by-OLDD

Edited May 3, 2015 by Mecripp2

[Wesreidau]

All right, I've managed it and chopped most of the unused FASA materials out. Shame I can't share it though.

[frizzank]

If you want to put together a separate add-on for fasa that you can install on top of a fasa install I will put link on the fasa page to it. Send me a PM if your interested in putting it together.