|
|
 Home  Forums Forum Index Neverwinter Nights NWN 1: Custom Content How Is The Parent Node Position And Orientation Applied To The Child Node?
NWN 1: Custom Content
Script Wrecked
Game Owner
 NWN
NWN: SoU
NWN: HotU
NWN 2
NWN 2: MotB
NWN 2: SoZ
Joined: 19 Oct 2002
From: The first plane of scripting hell. |
 Posted: Sunday, 01 November 2009 10:14AM |
For the child node of a model, how are the parent node's position and orientation values applied to the child node vertices to create/generate/produce the actual position of the child node vertices (remembering that the child node has its own position and orientation values as well)?
_________________
Script Wrecked
When all else fails, read the instructions. Get it here. | 
|
B_Harrison
Game Owner
NWN
NWN: SoU
NWN: HotU
Joined: 06 Mar 2004
From: England |
Posted: Thursday, 05 November 2009 01:41PM |
I'm not sure I understand your question entirely (it might've gone over my head, I'm certainly no expert), but a node's parent(s) only affect its position/orientation at the top selection level (ie, not sub-selections of vertices, edges, etc). So you can rotate a parent object and all child nodes will rotate as well, but moving vertices in the parent won't affect vertices (or modifiers, etc AFAIK) in child nodes.
Moving a child node will affect its position/orientation in relation to a parent node "globally," ie, any change in the parent node's position will affect the global positions of any child nodes.
Apologies if I've just misunderstood though.
_________________
~Ben
Mods | Blog | |
|
Script Wrecked
Game Owner
NWN
NWN: SoU
NWN: HotU
NWN 2
NWN 2: MotB
NWN 2: SoZ
Joined: 19 Oct 2002
From: The first plane of scripting hell. |
Posted: Friday, 06 November 2009 11:28AM |
Quote: Posted 11/05/09 13:41 (GMT) by B_Harrison
I'm not sure I understand your question entirely (it might've gone over my head, I'm certainly no expert), but a node's parent(s) only affect its position/orientation at the top selection level (ie, not sub-selections of vertices, edges, etc). So you can rotate a parent object and all child nodes will rotate as well, but moving vertices in the parent won't affect vertices (or modifiers, etc AFAIK) in child nodes.
Moving a child node will affect its position/orientation in relation to a parent node "globally," ie, any change in the parent node's position will affect the global positions of any child nodes.
Apologies if I've just misunderstood though.
The position and orientation directives are offsets and rotations applied to the individual vertices. The position and orientation directives of the parent node affect the child node. Therefore the parent node position and orientation directives are (somehow) applied to the child node vertices. | |
|
Script Wrecked
Game Owner
NWN
NWN: SoU
NWN: HotU
NWN 2
NWN 2: MotB
NWN 2: SoZ
Joined: 19 Oct 2002
From: The first plane of scripting hell. |
Posted: Thursday, 12 November 2009 08:51AM |
The nature of the problem is with the release of cloaks in NWN 1.68, some robes were broken, with various parts sticking out at odd angles (notably the backpack robes in Rosietreats Adventure Gear Volume I).
It turns out, this is due to the robe model no longer applying the orientation directive for the nodes of the model. For most robes, this is not a problem, because they have a "zero" orientation, viz there is no rotation applied to the verts of the node.
However, this breaks nodes which are expecting a non-zero orientation to be applied to get the verts into the correct placement.
However, if the orientation directive is manually applied to the actual vert values (generating a new vert value), low-and-behold, the verts are correctly placed.
The orientation is an axis-angle, which is applied to the verts using a rotation matrix.
This works admirably for flat hierarchy nodes, or more specifically, where there is only one non-zero orientation in the node hierarchy.
However, when there is multiple non-zero orientations in the node hierarchy, then... I have been unable to work out how to apply the parent node's orientation adjustment to the child node.
That's what I'm trying to do.  Edited By Script Wrecked on 11/12/09 08:53 | |
|
|
Search Forums |
Forums FAQ |
Forum Archives
|
