[Solved] Docking port/Loading Config/Weird Lighting & offset FX issues

gooddog15 · May 24, 2015

This thread has been repurposed...again. I dont like wasting precious needed space
Currently, I've been having problems with making docking ports. I simply can't make the docking part work in game.
I'm pretty sure I have everything right, like the placement and orientation of dockingNode in Unity, and having the correct node transform name in the config.
It seems at first, It appears functional when initially right clicked on, however clicking on undock doesn't do anything and the only thing I can do is turn crossfeed on/off and control here, as seen below.
Before "undocking" in game:
After:
In Unity:
Config:

PART
{

name = APASAdvanced
module = Part
author = Gooddog15

MODEL
{
model = TantaresC/Parts/APASAdvanced/ApasD
scale = 1, 1, 1
}

node_stack_bottom = 0.0, -0.026, 0.0, 0.0, -1.0, 0.0, 1
node_stack_top = 0.0, 0.141, 0.0, 0.0, 1.0, 0.0, 1
bulkheadProfiles = size1, srf

TechRequired = generalRocketry
entryCost = 1200
cost = 600

category = Utility
subcategory = 0
title = APAS Advanced
manufacturer = Tantares C
description = A docking port with a extending thing. (please note that the extending thing does nothing)

attachRules = 1,0,1,1,0

mass = .5

dragModelType = default
maximum_drag = 1
minimum_drag = 0.8
angularDrag = 2
crashTolerance = 60
maxTemp = 3600
fuelCrossFeed = False

MODULE
{
name = ModuleAnimateGeneric
animationName = Extend
startEventGUIName = Extend
endEventGUIName = Retract
}

MODULE
{
name = ModuleDockingNode
nodeType = size1
nodeTransformName = dockingNode
controlTransformName = controlNode
}

}

*Both issues below in the OP have been solved
Hello again, I'm having config file problems and I really don't want to create yet another thread, so I'm reusing this thread.
Currently I have two problems:
1: one part wont load at all due to it apparently not existing
2: another part apparently is not in the correct format, even though I can't see any problems with it's config file. This causes the game to stall.
part 1's config:

{

name = APASAdvanced
module = Part
author = Gooddog15

mesh = APAS.mu
scale = 1

node_stack_bottom = 0.0, -0.026, 0.0, 0.0, -1.0, 0.0, 1
node_stack_top = 0.0, 0.141, 0.0, 0.0, 1.0, 0.0, 1
bulkheadProfiles = size1, srf

TechRequired = generalRocketry
entryCost = 1200
cost = 600

category = Utility
subcategory = 0
title = APAS Advanced
manufacturer = Tantares C
description = A docking port with a extending thing. (please note that the extending thing does nothing)

attachRules = 1,0,1,1,0

mass = .5

dragModelType = default
maximum_drag = 1
minimum_drag = 0.8
angularDrag = 2
crashTolerance = 60
maxTemp = 3600

MODULE
{
name = ModuleAnimateGeneric
animationName = Extend
startEventGUIName = Extend
endEventGUIName = Retract
}

MODULE
{
name = ModuleDockingNode
referenceAttachNode = top
nodeType = size1
}
}
PART
part 2's config:

{

name = COAS
module = Part
author = Gooddog15

mesh = COAS.mu
scale = 1

node_stack_bottom = 0.0, 0.0, 0.0, 0.0, -1.0, 0.0, 0.5
node_attach = 0.0, 0.0, 0.0, 0.0, 1.0, 0.0, 1
bulkheadProfiles = size0, srf

TechRequired = generalRocketry
entryCost = 75
cost = 50
category = Utility
subcategory = 0
title = Crew Optical Alignment Sight
manufacturer = Tantares C
description = Some pointy thing we found in the interns desk. Use it to help dock stuff together
attachRules = 1,1,0,0,1

mass = 0.02

dragModelType = default
maximum_drag = 0.3
minimum_drag = 0.0
angularDrag = 2
crashTolerance = 15
maxTemp = 3600

PhysicsSignificance = 1

}
PART

*Both issues below in the OP have been solved
So, after getting back into modding due to being on a forced hiatus (computer issues), I've finally got most stuff working in game as it should, however there are some issues...
one of these issues is a in game lighting bug, and I have no idea what could be causing it.
in VAB:
in Flight:
I also have a FX issue, where its offset on the X axis, even if it's not specified in the config:
config:

{

name = SR19
module = Part
author = Gooddog15

mesh = SR19.mu
scale = 1
rescale = 1

node_stack_bottom = 0.0, -1.229, 0.0, 0.0, -1.0, 0.0, 1
node_stack_top = 0.0, 0.70, 0.0, 0.0, 1.0, 0.0, 1
node_attach = 0.0, 0.0, -5, 0.0, 0.0, 1.0, 1

fx_exhaustFlame_yellow = 0.0, -1.229, 0.0, 0.0, 1.0, 0.0, running
fx_exhaustSparks_yellow = 0.0, -1.229, 0.0, 0.0, 1.0, 0.0, running
fx_smokeTrail_medium = 0.0, -11.2673, 0.0, 0.0, 1.0, 0.0, running

sound_vent_medium = engage
sound_rocket_hard = running
sound_vent_soft = disengage
sound_explosion_low = flameout
bulkheadProfiles = size1, srf

TechRequired = generalRocketry
entryCost = 1200
cost = 600

category = Engine
subcategory = 0
title = KR-19
manufacturer = Technical Dynamics
description = Test. Use at your own risk

attachRules = 1,1,1,1,0

mass = .5
dragModelType = default
maximum_drag = 1
minimum_drag = 0.8
angularDrag = 2
crashTolerance = 60
maxTemp = 3600

stagingIcon = SOLID_BOOSTER
bulkheadProfiles = size1, srf

MODULE
{
name = ModuleEngines
thrustVectorTransformName = thrustTransform
throttleLocked = True
exhaustDamage = True
ignitionThreshold = 0.1
minThrust = 0
maxThrust = 150
heatProduction = 30
useEngineResponseTime = True
engineAccelerationSpeed = 10.0
allowShutdown = True
fxOffset = 0, -2.279, 0

PROPELLANT
{
name = SolidFuel
DrawGauge = True
ratio = 0.9
}

atmosphereCurve
{
key = 0 162
key = 1 150
key = 6 0.001
}

}

MODULE
{
name = ModuleGimbal
gimbalTransformName = thrustTransform
gimbalRange = 3
}

RESOURCE
{
name = SolidFuel
amount = 700
maxAmount = 700
}

}
PART

Edited June 21, 2015 by gooddog15

CaptainKipard · May 24, 2015

Recalculate normals outisde.

Edge split sharp edges.

If you don't understand what that means just google it.

If that's not the problem then the only other thing I can think of is something went wrong with normal mapping.

gooddog15 · May 24, 2015

Recalculate normals outisde.
Edge split sharp edges.
If you don't understand what that means just google it.
If that's not the problem then the only other thing I can think of is something went wrong with normal mapping.

thanks, edge splitting solved the lighting problem.

CaptainKipard · May 25, 2015

is the thrust transform in the right place?

gooddog15 · May 25, 2015

Yes.

the problem was with fxoffset under module engines. Apparently it doesnt follow the same position convention as everything else

gooddog15 · June 20, 2015

Hello again, I'm having config file problems and I really don't want to create yet another thread, so I'm reusing this thread.

Currently I have two problems:

1: one part wont load at all due to it apparently not existing

2: another part apparently is not in the correct format, even though I can't see any problems with it's config file. This causes the game to stall.

part 1's config:

PART
{

	name = APASAdvanced
	module = Part
	author = Gooddog15

	mesh = APAS.mu
	scale = 1

	node_stack_bottom = 0.0, -0.026, 0.0, 0.0, -1.0, 0.0, 1
	node_stack_top    = 0.0,  0.141, 0.0, 0.0, 1.0, 0.0, 1
	bulkheadProfiles = size1, srf

	TechRequired = generalRocketry
	entryCost = 1200
	cost = 600

	category     = Utility
	subcategory  = 0
	title        = APAS Advanced
	manufacturer = Tantares C
	description  = A docking port with a extending thing. (please note that the extending thing does nothing)

	attachRules = 1,0,1,1,0

	mass = .5

	dragModelType  = default
	maximum_drag   = 1
	minimum_drag   = 0.8
	angularDrag    = 2
	crashTolerance = 60
	maxTemp        = 3600

MODULE
{
name = ModuleAnimateGeneric
animationName = Extend
startEventGUIName = Extend
endEventGUIName = Retract
}

MODULE
{
	name = ModuleDockingNode
	referenceAttachNode = top
	nodeType = size1
}
}

part 2's config:

PART
{

name = COAS
module = Part
author = Gooddog15

mesh = COAS.mu
scale = 1

node_stack_bottom = 0.0, 0.0, 0.0, 0.0, -1.0, 0.0, 0.5
node_attach = 0.0, 0.0, 0.0, 0.0, 1.0, 0.0, 1
bulkheadProfiles = size0, srf

TechRequired = generalRocketry
entryCost = 75
cost = 50
category     = Utility
subcategory  = 0
title        = Crew Optical Alignment Sight
manufacturer = Tantares C
description  = Some pointy thing we found in the interns desk. Use it to help dock stuff together
attachRules = 1,1,0,0,1

mass = 0.02

dragModelType  = default
maximum_drag   = 0.3
minimum_drag   = 0.0
angularDrag    = 2
crashTolerance = 15
maxTemp        = 3600

PhysicsSignificance = 1

}

Randazzo · June 20, 2015

In the first one, the game appears to be attempting to load the model from the wrong directory. I've never encountered that personally before, and I can only guess (and that guess is it's getting confused at the identical name being used repeatedly) at what might cause it. I would suggest using a MODEL node instead, but then I think you might have problems with your base directory having a space in it, IE "Tantares C" instead of "TantaresC". There's also an extra space in the node_stack_top line, but that probably doesn't matter for your issue.


MODEL
{

[INDENT]model = Tantares C/Parts/APAS/part/APASAdvanced/APAS
scale = 1, 1, 1[/INDENT]

}

For the second one, I believe the node size you're trying to call for the bottom node (0.5) is breaking it. As far as I know, the node size can only be 0 (actually refers to the smallest size, does not remove the nodes visual indicator), 1, or 2.


node_stack_bottom = 0.0, 0.0, 0.0, 0.0, -1.0, 0.0, 0.5

should be


node_stack_bottom = 0.0, 0.0, 0.0, 0.0, -1.0, 0.0, 0
or
node_stack_bottom = 0.0, 0.0, 0.0, 0.0, -1.0, 0.0, 1

Edited June 20, 2015 by Randazzo

NecroBones · June 20, 2015

For the second one, I believe the node size you're trying to call for the bottom node (0.5) is breaking it. As far as I know, the node size can only be 0 (actually refers to the smallest size, does not remove the nodes visual indicator), 1, or 2.

You can go bigger than 2, for instance 3 is appropriate for 3.75m nodes. But yes, it should be integers only.

gooddog15 · June 20, 2015

In the first one, the game appears to be attempting to load the model from the wrong directory. I've never encountered that personally before, and I can only guess (and that guess is it's getting confused at the identical name being used repeatedly) at what might cause it. I would suggest using a MODEL node instead, but then I think you might have problems with your base directory having a space in it, IE "Tantares C" instead of "TantaresC". There's also an extra space in the node_stack_top line, but that probably doesn't matter for your issue.
MODEL
{
[INDENT]model = Tantares C/Parts/APAS/part/APASAdvanced/APAS
scale = 1, 1, 1[/INDENT]

}
For the second one, I believe the node size you're trying to call for the bottom node (0.5) is breaking it. As far as I know, the node size can only be 0 (actually refers to the smallest size, does not remove the nodes visual indicator), 1, or 2.
node_stack_bottom = 0.0, 0.0, 0.0, 0.0, -1.0, 0.0, 0.5
should be
node_stack_bottom = 0.0, 0.0, 0.0, 0.0, -1.0, 0.0, 0
or
node_stack_bottom = 0.0, 0.0, 0.0, 0.0, -1.0, 0.0, 1

Thank you so much! It solved both problems.

Also, I found a bug with part tools that caused the second problem. Apparently you cannot reset the gamedata directory without deleting and reinstalling part tools. Without doing that, it will write the model and everything else to the new and old directories, however they have nothing in them.

Randazzo · June 21, 2015

This thread has been repurposed...again. I dont like wasting precious needed space
Currently, I've been having problems with making docking ports. I simply can't make the docking part work in game.
I'm pretty sure I have everything right, like the placement and orientation of dockingNode in Unity, and having the correct node transform name in the config.
It seems at first, It appears functional when initially right clicked on, however clicking on undock doesn't do anything and the only thing I can do is turn crossfeed on/off and control here, as seen below.
Before "undocking" in game:
http://i.imgur.com/soYSSeT.png
After:
http://i.imgur.com/oeAomrf.png
In Unity:
http://i.imgur.com/GnQ9I7l.png
Config:
PART
{

    name = APASAdvanced
    module = Part
    author = Gooddog15

    MODEL
    {
    model = TantaresC/Parts/APASAdvanced/ApasD
    scale = 1, 1, 1
    }

    node_stack_bottom = 0.0, -0.026, 0.0, 0.0, -1.0, 0.0, 1
    node_stack_top    = 0.0,  0.141, 0.0, 0.0, 1.0, 0.0, 1
    bulkheadProfiles = size1, srf

    TechRequired = generalRocketry
    entryCost = 1200
    cost = 600

    category     = Utility
    subcategory  = 0
    title        = APAS Advanced
    manufacturer = Tantares C
    description  = A docking port with a extending thing. (please note that the extending thing does nothing)

    attachRules = 1,0,1,1,0

    mass = .5

    dragModelType  = default
    maximum_drag   = 1
    minimum_drag   = 0.8
    angularDrag    = 2
    crashTolerance = 60
    maxTemp        = 3600
    fuelCrossFeed = False

MODULE
{
name = ModuleAnimateGeneric
animationName = Extend
startEventGUIName = Extend
endEventGUIName = Retract
}

MODULE
{
    name = ModuleDockingNode
    nodeType = size1    
    nodeTransformName = dockingNode
    controlTransformName = controlNode
}

}

Try swapping nodeTransformName with referenceAttachNode. This will be referencing of of your previously assigned attach nodes, not the name of the node in the model.


{
        name = ModuleDockingNode
        referenceAttachNode = top
        nodeType = size1
        controlTransformName = controlNode // Not entirely sure you need this unless your control from direction would be off from your center of mass or prograde facing.
}

Edited June 21, 2015 by Randazzo

sumghai · June 21, 2015

gooddog15, please don't repurpose your existing threads to ask different questions each time. Start a new topic for your new question instead.

The forums is not in danger of running out of server space to store post data, and besides, leaving your old topic(s) as-is allows other people experiencing the same problem to look at the entire history / process of your problem solving.

If you keep repurposing theads, these same people would get really confused with the constantly changing content.

gooddog15 · June 21, 2015

Try swapping nodeTransformName with referenceAttachNode. This will be referencing of of your previously assigned attach nodes, not the name of the node in the model.
{
        name = ModuleDockingNode
        referenceAttachNode = top
        nodeType = size1
        controlTransformName = controlNode // Not entirely sure you need this unless your control from direction would be off from your center of mass or prograde facing.
}

Thank you!

gooddog15, please don't repurpose your existing threads to ask different questions each time. Start a new topic for your new question instead.
The forums is not in danger of running out of server space to store post data, and besides, leaving your old topic(s) as-is allows other people experiencing the same problem to look at the entire history / process of your problem solving.
If you keep repurposing theads, these same people would get really confused with the constantly changing content.

Understood. I know that the forum isn't running out of space, but it feels sort of wasteful to make 2 new threads in a short period of time.

sumghai · June 21, 2015

Understood. I know that the forum isn't running out of space, but it feels sort of wasteful to make 2 new threads in a short period of time.

It is not wasteful, and as I've pointed out previously, keeping questions in separate topics makes it easier for other people looking back through old threads.

[Solved] Docking port/Loading Config/Weird Lighting & offset FX issues

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Join the conversation