Jump to content

Are there any 2 man, 1.25 meter capsules that look like stock?


MarcAlain

Recommended Posts

Yeah it looks good, but again it's not 1.25m.

I wonder how tweaking some of these steeper sloped 2 man capsules would work though...

Edited by MarcAlain
Link to comment
Share on other sites

How about a quick ghetto hack on a Mk1-2 pod ? :) The configuration file below, placed anywhere within the GameData subdirectory structure, uses the model for the stock 3-man Mk1-2 pod, resized to 1.25m and stretched a bit, configured for 2 kerbals with proportionally adjusted costs and capacities. The top will conveniently fit a junior docking port or Mk-16 parachute.

PART
{

// --- general parameters ---
name = Mark1-3APod
module = Part
author = Roxette // C. Jenkins

// --- asset parameters ---

MODEL
{
model = Squad/Parts/Command/Mk1-2Pod/model
texture = mk 1-2 external shell Variant-Hatch , Squad/Parts/Command/Mk1-2Pod/
scale = 0.5, 1.1, 0.5
}

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.48, 0.0, 0.0, 1.0, 0.0, 1
node_stack_top = 0.0, 1.3, 0.0, 0.0, 1.0, 0.0, 1

// --- editor parameters ---
TechRequired = specializedControl
entryCost = 6800
cost = 1800
category = Pods
subcategory = 0
title = Mk1-3A Command Pod
manufacturer = Kerlington Model Rockets and Paper Products Inc
description = This modern stretched cockpit is designed to be fully re-useable. Its semi-spacious cabin can hold a maximum of 2 crew.
// attachment rules: stack, srfAttach, allowStack, allowSrfAttach, allowCollision
attachRules = 1,0,1,1,0

// --- standard part parameters ---
mass = 2.1
dragModelType = default
maximum_drag = 0.20
minimum_drag = 0.15
angularDrag = 2
crashTolerance = 18
maxTemp = 3400

vesselType = Ship

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

INTERNAL
{
name = PodCockpit
}

MODULE
{
name = ModuleCommand
minimumCrew = 1
}

RESOURCE
{
name = ElectricCharge
amount = 100
maxAmount = 100
}

MODULE
{
name = ModuleReactionWheel

PitchTorque = 7
YawTorque = 7
RollTorque = 7

RESOURCE
{
name = ElectricCharge
rate = 0.8
}
}
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
}
MODULE
{
name = ModuleScienceContainer

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

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

MODULE
{
name = FlagDecal
textureQuadName = flagTransform
}
}

Link to comment
Share on other sites

How about a quick ghetto hack on a Mk1-2 pod ? :) The configuration file below, placed anywhere within the GameData subdirectory structure, uses the model for the stock 3-man Mk1-2 pod, resized to 1.25m and stretched a bit, configured for 2 kerbals with proportionally adjusted costs and capacities. The top will conveniently fit a junior docking port or Mk-16 parachute.

Looks great man! That's as good as I think I can find for now :D

wln1qSV.jpg

Link to comment
Share on other sites

Right, but which value affects this? I've changed a few and it doesn't seem to change where the heatshield attaches vertically.

in the config it's the "node_stack_bottom" line. You will have to adjust the =.48 down (I would try something on the order of .65 first)

Link to comment
Share on other sites

How about a quick ghetto hack on a Mk1-2 pod ? :) The configuration file below, placed anywhere within the GameData subdirectory structure, uses the model for the stock 3-man Mk1-2 pod, resized to 1.25m and stretched a bit, configured for 2 kerbals with proportionally adjusted costs and capacities. The top will conveniently fit a junior docking port or Mk-16 parachute.

PART
{

// --- general parameters ---
name = Mark1-3APod
module = Part
author = Roxette // C. Jenkins

// --- asset parameters ---

MODEL
{
model = Squad/Parts/Command/Mk1-2Pod/model
texture = mk 1-2 external shell Variant-Hatch , Squad/Parts/Command/Mk1-2Pod/
scale = 0.5, 1.1, 0.5
}

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.48, 0.0, 0.0, 1.0, 0.0, 1
node_stack_top = 0.0, 1.3, 0.0, 0.0, 1.0, 0.0, 1

// --- editor parameters ---
TechRequired = specializedControl
entryCost = 6800
cost = 1800
category = Pods
subcategory = 0
title = Mk1-3A Command Pod
manufacturer = Kerlington Model Rockets and Paper Products Inc
description = This modern stretched cockpit is designed to be fully re-useable. Its semi-spacious cabin can hold a maximum of 2 crew.
// attachment rules: stack, srfAttach, allowStack, allowSrfAttach, allowCollision
attachRules = 1,0,1,1,0

// --- standard part parameters ---
mass = 2.1
dragModelType = default
maximum_drag = 0.20
minimum_drag = 0.15
angularDrag = 2
crashTolerance = 18
maxTemp = 3400

vesselType = Ship

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

INTERNAL
{
name = PodCockpit
}

MODULE
{
name = ModuleCommand
minimumCrew = 1
}

RESOURCE
{
name = ElectricCharge
amount = 100
maxAmount = 100
}

MODULE
{
name = ModuleReactionWheel

PitchTorque = 7
YawTorque = 7
RollTorque = 7

RESOURCE
{
name = ElectricCharge
rate = 0.8
}
}
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
}
MODULE
{
name = ModuleScienceContainer

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

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

MODULE
{
name = FlagDecal
textureQuadName = flagTransform
}
}

Interesting, I want to give this a go but I am unsure of how to do it, do I just copy the Mk1-2 Command Pod folder and replace the .cfg with this?

EDIT- Nevermind, though the same thing as mentioned several posts up happens to me when the heatshield won't attach correctly, the top node does not connect but the bottom does which is not good. Any adjustments I can make to the .cfg to make it work properly?

Edited by Jumpyyoza
Link to comment
Share on other sites

  • 2 weeks later...
This thread is quite old. Please consider starting a new thread rather than reviving this one.

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...