Difference between revisions of "NifSkope Comprehensive Guide"

5,940 bytes added ,  10:02, 2 August 2007
Added physics section, some minor updates to the format and grammer
imported>Chuey
(Added: Sections 5.3, 5.4; Section 6 & 7; Updated Glossary; Minor updates to other sections; Added Wiki catagorys)
imported>Chuey
(Added physics section, some minor updates to the format and grammer)
Let’s start simple. A .nif file [example: dagger.nif] is created by the [http://www.emergent.net/index.php/homepage/products-and-services/gamebryo GameBryo Essentials Toolkit] when the developer saves their final version of a game object. This object can be anything from a rock to a human head to a stone wall. [http://en.wikipedia.org/wiki/Gamebryo GameBryo] is the [http://en.wikipedia.org/wiki/Game_engine Game Engine] that was used to create TES:Oblivion as well as [http://en.wikipedia.org/wiki/Morrowind TES:Morrowind] before it.
 
These files are then compressed into a .bsa file by our good friends at [http://en.wikipedia.org/wiki/Bethesda_Softworks Bethesda Softworks]. The core need by modders[http://en.wikipedia.org/wiki/Modding Modders] to make new meshes and textures or edit existing ones is to have the ability to edit these NIF files. That is where NifSkope comes in.
 
NifSkope is a .nif viewer/editor available free from the [http://niftools.sourceforge.net/wiki/NifTools NIFTools] team. They have created this program to enable us to view and edit Net Immerse Files (NIF).
Now that we know what a NIF file is lets go get the NifSkope program.
 
:*Click this link to find NifSkope: [http://sourceforge.net/project/showfiles.php?group_id=149157&package_id=170735 NifSkope 0.9.8]
 
:* Expand the 0.9.8 version using the + sign next to the version number.
:* Click on the link: ‘nifskope-0.9.8-windows.exe’
:* Save the file to your Desktop.
:* Now go to your desktop and double-click the icon ‘nifskope-0.9.8-windows’
:* Follow the prompts and install NifSkope to your computer’s hard drive.
 
== Opening NifSkope for the First Time ==
Okay, so now we have NifSkope installed. Lets open it and see what’s inside.
 
:* Start -> All Programs -> NifTools -> NifSkope, NifSkope
 
Okay now we are in. First thing we need to do is tell NifSkope where the files we want to mod are.
 
:* Click: Render menu -> Settings…
 
<br>
This window controls NifSkope’s render window. You'll most likely never use 90% of the controls in here. We'll go into more detail on these later, so for now, all we are concerned with is the '''Auto Detect''' and '''Custom''' groups.
 
:* Auto Detect: Click ‘Oblivion’
 
You should have seen a file path appear in the Custom group. This file path should point to where you installed your TES:Oblivion game and then the /Data directory. If it doesn’t, then follow the instructions below. Otherwise click the small ‘X’ in the upper right and continue on to the next topic.
If the auto detect did not follow the correct path double click on the path it did provide. If it did not provide a path click the ‘Folder’ button. Either way enter the following:
 
:* C:/Program Files/Bethesda Softworks/Oblivion/Data
 
<blockquote>'''NOTE:''' This assumes that you installed the game into your C Drive, Program Files directory. If you are unsure of where you installed the game go to: Start, All Programs, Bethesda Softworks, Oblivion and right click on the ‘Oblivion’ icon and select ‘Properties’. In the ‘Target’ field you will find the install directory.</blockquote>
== Menu Items ==
NifSkope contains five menu drop downs. Some are obvious (Save, About, ect.) and some not so obvious (Optimize, Sanitize, ect.). We will explore these in more detail below so first lets open a NIF file.
 
:* Click: File menu -> Load
:* Browse to your Oblivion install directory, then Data/meshes/weapons/iron
* Click to highlight: battleaxe.nif▼
:* Click to highlight: Openbattleaxe.nif
:* Click: Open
<br>
 
<br>
=== Render Window Settings ===
The render window settings control the search path, rendering, and lighting of the render window. These controls will make dramatic changes to the way your model is rendered and should be used sparingly. LetsLet's walk through each of the setting options available to you.
:'''Auto Detect'''
::* Pressing one of the buttons will cause NifSkope to seek out and find the directory your texture files are located in for the game named on the button; then adds the result to the list of search paths.
Below are links to great [http://www.wikipedia.org Wikipedia] articles on Polygonal Meshes and Texture Maps. It's highly recommended that you read these articles to get a better understanding of these two concepts. So get yourself a beverage of choice, click on the links, and read. Continue on with the guide when you're done.
 
:* [http://en.wikipedia.org/wiki/Polygon_mesh Polygonal Meshes - Wikipedia Article]
:* [http://en.wikipedia.org/wiki/Texture_mappingTexture Maps - Wikipedia Article]
 
=== Orientating the Model ===
:* Click: Render menu -> Save User View
Now the current orientation of the model in the render window has been saved.
:* Press the Z Axis View (Blue - View from above) toolbar button on the toolbar.
:* Now press the Restore User View (Lt Gray - Restore..) toolbar button on the toolbar.
The model is now re-orientated back to the view that you saved!
 
Our battleaxe is made up of two separate meshes: the handle and the blades. Place your mouse cursor over the render window and follow along.
 
:* Click on the blade portion of the battleaxe with your left mouse button.
 
Notice how the blades become outlined with white lines. The white lines are showing you the mesh beneath the texture map. Now look over to the Block List window and expand '0 NiNode Battleaxe'.
Notice how the 10 NiTriStrip Battleaxe:0 is highlighted. NifSkope has highlighted this section of the block list because you've selected its associated mesh in the Render Window. Now go back to the Render Window and select the handle. The highlight moves to 16 NiTriStrip Battleaxe:1 because block #16 contains the data pertaining to the handle mesh.
 
:* Right click on the blades portion of the battleaxe model.
 
Not only does the highlight move back to block #10 but a menu will appear. This is the 'Model Editing Menu'. For now, just remember how to open the menu. We'll get into more detail on this menu's options further in the guide.
The primary use of this mode is to give the perception of 'walking' near to the model in the render window. When this mode is active you will no longer have the ability to rotate the model. The view will be fixed parallel to the perceived ground plane that will be present in the game environment. Meaning if the Z axis is up, your view will be locked on the Y axis plane. Let's try this:
 
:* Click: Render menu -> Settings... -> Up Axis, set this to Z.
:* Close the Render Settings menu.
:* Press the 'Enable Walk Mode' (Dk Gray) toolbar button.
:* Hold your mouse over the Render Window.
:* Press and hold the center mouse button to 'walk' the model around the viewport.
:* Press and hold the left mouse button to move the model around the viewport.
 
Try this example:
:* Click: Open on the toolbar menu
:* Go to: Data\meshes\architecture\skingrad
:* Open: skhousemiddle01.nif
:* Click: Render menu -> Settings... -> Frontal, uncheck
:* Position -> Declination: -80, Planar Angle: 45
:* Click: Presents -> Dark Night
:* Close the Render Settings Window.
 
Now place your mouse cursor over the render window and walk left and right across the model. This will give the perception of walking past this Skingrad house at the dead of night with the moon overhead.
 
Now lets get our render setting back to default:
:* Click: Render menu -> Settings... -> Check: Frontal
:* Click: Presents -> Sunny Day
:* Close the Render Settings Window.
:* Reopen your iron battleaxe model. [Data\meshes\weapons\iron\battleaxe.nif]
 
== Scene Root Node ==
All NIF files start with a Scene Root Node (0 NiNode). This is the location of X0,Y0,Z0 in 3D space. Everything in the game environment is positioned based on the location of it's associated Scene Root Node. You cannot move the Scene Root Node, but can move the associated model in relation to it. This enables you to position the model to a specific location in reference to other objects in the game environment.
 
:* Click: Z Axis View button on the toolbar.
:* Expand the 0 NiNode Battleaxe block in the Block List Window.
 
In the render window look at the point where the three axis meet. Zoom in to get a good look at the blue 'X' with a yellow square in the middle. The yellow square is your Scene Root. It will appear when you select the 0 NiNode block.
 
:* Select block 1 BSX Flags in the Block List Window.
 
Notice how the scene root Node disappears but the blue 'X' remains to show you where the zero point is. It is very important to remember this when you are importing a mesh into an existing NIF file. Improper positioning of the mesh can cause many types of problems when loading a new NIF in the game environment. Especially those dealing with animations, examples: drawing a sword from a scabbard or pulling an arrow from a quiver.
 
In the Block List Window:
 
:* Click to highlight: 1 BSX Flags BSX
 
Now look at the Block Details Window -> Flags -> Value column
 
In the Block List Window:
 
:* Click to highlight: 2 NiStringExtraData Prn
 
Look at the Block Details window -> String Data -> Value column
 
== Extra String Data: UPB Block ==
The UPB block specifies the models physics in terms of several principal variables. Since this data applies to the fundamentals of physics it is implied that the game engine's physics processing is affected by these variables. UPB is not the primary section of the NIF that sets the models physics. Each mesh contained in the NIF files has specific physics defined. See the Physics section for more information. The variables are:
: '''Collision Groups '''
::* The effects of changing this value are unknown. ''Needs explanation. See Key2.nif''
 
Look at the Block List window:
:* Expand 0 NiNode Battleaxe
:* Expand 9 bhkCollisionObject
:* Expand 8 bhkRigidBody
:* Expand 7 bhkListShape
:* Expand 6 bhkConvexTransformShape
 
What these blocks tell the game engine is that this model contains a rigid body collision object. The collision objects are defined as various shapes: Capsule, Box, or Mesh (''Are there others?''). In this guide we will only be discussing capsule and box shapes. Creating and/or editing meshes are outside the scope of this guide.
Look in the render window; notice the orange lines surrounding the battleaxe's handle? That is the collision object 'capsule'. You can edit the collision object using the Block Details window. Let's try that now.
 
:* Click to highlight: 4 bhkCapsuleShape
:* Look at the Block Details List.
 
What you're seeing in the Block Details is a list of the data contained in this collision object. Since this object's base shape is a capsule you have the radius and locations of the capsule's beginning and end.
 
:* Double-Click: Block Details -> Radius -> Value (0.3000)
:* Highlight the value 0.3000
:* Type in: 1.5000
:* Hit Enter on the keyboard
 
Now look at the render window. The capsule radius has increased! Don't forget to change the values for Radius 1 and Radius 2 to 1.5000 also. Now we will change the location of the capsule's beginning and end.
 
:* Double-Click: Block Details -> First Point -> Value
:* Enter: X 1.0000 Y -5.0000 Z 0.0000
:* Hit Enter on the keyboard
:* Double-Click: Block Details -> Second Point -> Value
:* Enter: X -1.0000 Y 5.0000 Z 0.0000
:* Hit Enter on the keyboard
 
Now look at the render window. The capsule is on an angle and longer then before! Use this method to adjust the shape and location of a collision capsule to fit a new or edited mesh. Go ahead and play with the radius and point values. Then continue on with the guide when you're ready.
This type of collision object creates a box around your model or section of your model. Notice how the developer used a box shape around the blades and a capsule around the handle. Combinations of collision object shapes can produce a more life like experience for the player. Let's look at the box shape in more detail.
 
:* Click to highlight: 5 bhkBoxShape
:* Block Details window -> Dimensions
 
The X,Y,Z coordinates here adjust the overall size of the box shape. Each in relation to its length, width, and thickness.
 
:* Double-Click: Dimensions -> Value
:* Enter: X 5.0000 Y 5.0000 Z 2.0000
:* Press Enter on the keyboard
 
Notice how the box shape has grown in size! Use this method to fit a collision box around a new or edited mesh. Now let's adjust the location of our box shape.
 
:* In the Block List window:
:* Click to highlight: 6 bhkConvexTransformShape
:* In the Block Details window:
:* Right-Click: Transform row -> Transform, Edit
 
The '''Transform Editor''' window opens. This window allows you to adjust transform data for this collision object. There are three sections:
NifSkope defines NiTriStrips as, "A shape node that refers to data organized into strips of triangles.". The shape node being NiTriStripsData.
 
:* Expand 0 NiNode BattleAxe
:* Expand 10 NiTriStrips BattleAxe:0
 
In this block contains all the mesh, material, and texture map information necessary to render the model correctly in the game environment. Later we will break down each of these data nodes to better understand their purpose.
NifSkope defines NiTriShape as, “A shape node that refers to a singular triangle data.”. It is assumed that this is necessary to enable the mesh to conform to movements made by the associated actor. Meaning: NiTriShape data blocks are found on objects that are warn by an actor in the game environment. As the actor moves (i.e. swings a sword) the mesh around the actor must move along with him/her. And as such must conform to this movement; whereas an object such as a longsword does not need to conform to the actors movements.
 
:* Click: File menu -> New Window
:* Make the new window active on your desktop.
:* Click: Load on the toolbar.
:* Go to: /Data/meshes/armor/iron/m
:* Double-Click: boots.nif
:* Expand 0 NiNode Scene Root
:* Expand 10 NiTriShape Foot
 
Just as a NiTriStrips block, it contains all the mesh, material, and texture map information necessary to render the model correctly in the game environment. But notice the additional data node NiSkinInstance. This node is used to define what armature bones are associated with this object. For now, just remember where it’s located. We will get more into armature bones later in the guide.
 
:* Go ahead close the NifSkope window with the boots.nif file. But leave the battleaxe.nif window open as we will need it for the next section.
 
= '''Shape Block Details''' =
 
If you haven’t done so already:
:* Expand 0 NiNode BattleAxe
:* Expand 10 NiTriStrips BattleAxe:0
 
== ''' Tangent Space (binormal & tangent vectors)''' ==
The tangent space binormals and vectors must be updated anytime a new mesh is imported into NifSkope. Luckly the NifTools Team has provided a tangent space update script for you.
 
:* Right Mouse Click: 11 Tangent Space (binormal & tangent vectors)
:* Select: Block -> Remove
Block 11 has now been deleted from your Block List. That’s okay, we will now add it back.
:* Right Mouse Click: 10 NiTriStrips BattleAxe:0
:* Select: Mesh -> Update Tangent Space
 
Block 11 Tangent Space (binormal & tangent vectors) has been created for the NiTriStrips BattleAxe:0. When updating the tangent space it isn’t necessary to first delete the existing one but is recommended as a reminder.
Oblivion already contains several ‘pre-made’ material types for almost every type of material used in the game. Just copying and pasting material data from one NIF to another is a great time saver. But it’s important to know what each of the parameters contained in this block do to become a more skilled modder and tweak the setting to achieve custom look to your model.
 
:* Click to highlight: 12 NiMaterialProperty 6 – Default
:* Look at the Block Details window
 
: '''Name'''
 
==== '''Menu Method''' ====
:* Right Click: Ambient Color in the Block Details window
:* Select: Color
 
What you see in front of you is the NifSkope color chooser window. There is an outer ring which defines the color [http://en.wikipedia.org/wiki/Hue hue]. The triangle defines the shade. The shade can also produce black or white at the extremes. Let's give it a try:
 
:* Notice the white circle inside the outer ring. Select it with your Left Mouse Button and rotate it around the outer ring. This changes the hue.
:* Now select the white circle inside the triangle with your Left Mouse Button and drag it around inside the triangle. This changes the shade of the hue you selected in the previous step.
:* Click: ok
 
Now look at the Value column of the Ambient Color row. Notice how the cell is highlighted in the color you have chosen. Also look at your render window and notice how the model of the battleaxe has changed to show the ambient color you chose.
Look at the Value cell for the row Ambient Color and notice the #ffffff text that is there. This is the [http://en.wikipedia.org/wiki/HTML HTML Notation] for white. You can change this value by:
 
:* Double-Click: #ffffff in the Value cell of the Ambient Color row.
 
You now see three text boxes: Red, Green, and Blue specified by the first letter of each. The value 1 means that the associated color is at its minimum shade. The value of 0 means the associated color is at its maximum shade. Meaning, a primary color will become darker as the value approaches 0. For example, if you enter 0 for each of the primary colors you will end up with black. You can use variations of 0 - 1 in each of the primary colors to produce a specific hue and shade of your liking.
= '''Importing Meshes and Textures''' =
You now have a basic understanding of what is contained in a NIF file from the Blocks to Block data. Now we will focus our attention on how to edit a NIF file. In this section we will learn how to perform the following:
:* Import an existing mesh
:* Import a new mesh
:* Import an existing texture
:* Import a new texture
:* Import existing Material Properties
:* Renaming a NIF file
:* Saving a NIF File
:* Saving a New Texture File
 
Open your battleaxe.nif file if you haven't done so already.
One of the most fundamental tasks to modding any game is the ability to add new meshes. NifSkope makes this a very simple task.
 
:* Expand: 0 NiNode BattleAxe
:* Right-Click: 16 NiTriStrips BattleAxe:1
:* Select: Mesh -> Remove Branch
 
<blockquote>'''NOTE:''' You might have noticed a selection in the editing menu for Remove. This option will remove only the currently selected node and not all the children below it. Remove Branch, however, will remove both the currently selected node and any children below it. </blockquote>
You have successfully deleted 16 NiTriStrips BattleAxe:1 and you will notice that the battleaxe's handle is missing from the model in the render window. Now lets import a new mesh to replace it.
 
:* File menu -> New Window
:* Toolbar -> Click: Load
:* Open: Data\meshes\weapons\daedric\battleaxe.nif
:* Expand: 0 NiNode BattleAxe
:* Right-Click: 16 NiTriStrips BattleAxe:1
:* Select: Block -> Copy Branch
 
<blockquote>'''NOTE:''' Same applies for copy as with remove. Copy Branch will not only copy the selected node but also all of the children below it.</blockquote>
 
:* Now activate the NifSkope window with your handless iron battleaxe.
:* Right-Click: 0 NiNode BattleAxe
:* Select: Block -> Paste Branch
 
You've done it! The iron battleaxe has been modded to add the daedric handle. Now be very careful not to save this file over your existing iron battle axe or the change will be permanent. You can go ahead and close the other window with the daedric battleaxe, but leave this modded iron battleaxe open as we'll be using it in the next few sections.
If you already have Blender and have created a mesh, you are welcome to use it in place of the one provided.
 
:* Click here and download the new mesh NIF file I've created for you.
:* Save the NIF file to your desktop.
 
If you don't have the modded battleaxe.nif file from the previous section open go ahead and open it now.
 
:* File menu -> New Window
:* Toolbar -> Load
:* Open: Desktop\newmesh.nif
 
Now you are in the mesh file I created for you. One thing to point out is that Blender can only export NIF files to the 20.0.0.4 version. Oblivion, however, uses the 20.0.0.5 version of NIF files. The process explained in the next few steps is referred to as the Blender workaround or sometimes even the NifSkope dance.
Now activate your modded iron battleaxe NifSkope window. What we will do now is import the older 20.0.0.4 NiTriShape into our newer 20.0.0.5 NifSkope window. This will enable the Oblivion game engine to use the new mesh. First we need to remove the old battleaxe blades from our modded iron battleaxe. Activate that window now.
 
:* Right-Click: 10 NiTriStrips BattleAxe:0
:* Select: Block -> Remove Branch
 
We have successfully removed the old battleaxe blades and are ready to import the new ones. Go back and activate the newmesh.nif window.
 
:* Expand: 0 NiNode newmesh
:* Right-Click: 1 NiTriShape BattleAxe:0
:* Select: Block -> Copy Branch
 
Return to the modded iron battleaxe window.
 
:* Right-Click: 0 NiNode BattleAxe
:* Select: Block -> Paste Branch
:* At the warning prompt Select: Continue
 
Now you will notice that the new blades have been imported into 16 NiTriShape and the blades are visible in the render window. We must now convert the new mesh into a NiTriStrips Block for use as a weapon.
 
:* Right-Click: 16 NiTriShape BattleAxe:0
:* Select: Mesh -> Strippify
:* Expand: 16 NiTriStrips BattleAxe:0
 
Notice that the mesh data block as also converted from 17 NiTriShapeData to 17 NiTriStripsData (you can go back to the newmesh.nif file to see this). But we are still missing a very important data block: NiBinaryExtraData Tangent space (binormal & tangent vectors). We must now add that data block to our new NiTriStrips block.
 
:* Right-Click: 16 NiTriShape BattleAxe:0
:* Select: Mesh -> Update Tangent Space
 
Node 17 NiBinaryExtraData Tangent space (binormal & tangent vectors) has been added! But we are not finished yet. Because this was a new mesh created from Blender it is important that we ensure the normals are correctly faced and smoothed. Otherwise we could encounter problems with the way the texture map appears in the game environment. Lets do that now.
 
:* Right-Click: 16 NiTriShape BattleAxe:0
:* Select: Mesh -> Face Normals
:* Right-Click: 16 NiTriShape BattleAxe:0
:* Select: Mesh -> Smooth Normals -> Click, Smooth
 
You have now successfully imported a new mesh into this NIF file! If you haven't done so already, now is a good time to save your modded iron battleaxe. We will be using this modded iron battleaxe for the next few sections. You can go ahead and close the newmesh.nif window.
 
:* Toolbar -> Save
:* Save In: -> Desktop
:* Name: mybattleaxe.nif
 
== '''Importing An Existing Texture''' ==
Oblivion come stocked with countless pre-made textures from walls to human faces. All base textures will work on all meshes but the results might not appear as expected. We will try to add and existing texture to better explain why this is.
 
:* Expand: 0 NiNode BattleAxe
:* Expand: 10 NiTriStrips BattleAxe:1
:* Expand: 12 NiTexturingProperty
 
Notice the file path present in the value cell of 13 NiSourceTexture. It isn't necessary to use the Block Details window to change the base texture file path. You can edit the file path directly in the Block List window by double-clicking on it.
 
:* Double-Click: 13 NiSourceTexture -> Value Cell
:* Enter: textures\weapons\ironclaymore.dds
 
Now notice the handle in the render window and how it looks all scattered and broken up. The blade portion of the texture map is all split up across the handle and the grip is on the blade section of the battleaxe. The texture map didn't start with the claymore's handle on the bottom of the battleaxe and end with the claymore's blade tip at the top of the battleaxe. There's an important reason for this. It's called the UV Map. See The UV Map section for more detail.
So let's import the texture that is meant to be applied to this mesh.
 
:* Double-Click: 13 NiSourceTexture -> Value Cell
:* Enter: textures\weapons\DaedricBattleAxe.dds
 
Use this method to apply the correct texture map to an imported existing NiTriShape or NiTriStrips Block.
If you already have GIMP and have created a new texture, you are welcome to use it in place of the one provided.
 
:* Click here and download the new texture DDS file I've created for you.
:* Save the DDS file to: Oblivion\Data\textures\weapons
 
If you don't have the modded battleaxe.nif file from the previous section open go ahead and open it now.
The steps to importing a new texture are the same as importing an existing one except we will be applying it to our new mesh.
 
:* Double-Click: 20 NiSourceTexture -> Value Cell
:* Enter: textures\weapons\newtexture.dds
 
Now notice the battleaxe's blades in the render window. The new texture has been applied. Go ahead and save your file as mybattleaxe.nif.
 
The texture map doesn't properly conform to the model's geometry because the iron battleaxe's UV coordinates don't place the vertices in the correct location on the iron claymore's texture map. And so you end up with what you see. To correct this issue you would need to create a new UV Map for the battleaxe's handle that provides the proper UV coordinates for its vertices on ironclaymore.dds. Blender and GIMP are freeware programs that can help perform this function but are outside the scope of this guide.
 
= '''Physics''' =
Modern game engines have the ability to simulate various principles of [http://en.wikipedia.org/wiki/Physics Physics]. This is in effort to give a more life-like feel to the game environment. But this also complicates things in terms of both game development and [http://en.wikipedia.org/wiki/Modding Modding]. In this section we will walk through the physics data contained in the NIF file as well as explain the need for careful adjustment of the values.
 
<blockquote>'''NOTE:''' It is intended to keep this section as simple as possible. Physics is a very complex subject which cannot be explained in this guide. Links are provided on each of the physics properties for readers who want to find more information on the topic. But the intent of this guide is to give the reader a basic concept behind each of the variables contained in NifSkope and leave the physics lessen to a College Professor. </blockquote>
 
:* File menu -> Open: Data\meshes\weapons\iron\claymore.nif
:* Expand: 0 NiNode Claymore
:* Expand: 8 bhkCollisionObject
▲:* Click to highlight: battleaxe.nif7 bhkRigidBody
 
The iron claymore is a rigid body mass. To better understand why physics variables are required you should first understand what a [http://en.wikipedia.org/wiki/Rigid_body Rigid Body] is. The since the claymore model is a rigid body it is necessary for the bhkRigidBody block to tell the game engine how the claymore will react to its environment.
 
: ''' Layer '''
::* Set's the objects current layer. It's expected that this is used by the developers while working in GameBryo. Doesn't appear to serve much other purpose but it's recommended that the proper layer be specified.
: ''' Col Filter '''
::* Specifies if this object is linked to other objects and appears to combine the collision data.
: ''' Layer Copy '''
::* Likely used in GameBryo when coping collision objects to other layers. Not used otherwise. Set this to the same value as Layer.
: ''' Layer Copy '''
::* Likely a variable in GameBryo that determines if the Collision Filter was copied to the new layer along with the collision object. Not used otherwise.
: ''' Translation '''
::* Moves the collision object by the specified amount along the X, Y, or Z axis in relation to the mesh's scene root.
: ''' Rotation '''
::* Rotates the collision object by the specified amount along the Y, P, or R axis in relation to the mesh's scene root.
: ''' [http://en.wikipedia.org/wiki/Linear Linear] [http://en.wikipedia.org/wiki/Velocity Velocity] '''
::* The rate or change in rate at which this object is moving along a straight line when accelerated. This specifies a direction (the line) in X,Y, and Z of the object's Linear Velocity when accelerated. Default is zero which does not alter the direction of acceleration (i.e. you throw it straight, it goes straight). This is one of the two required properties in Linear Velocity, the other being speed.
: ''' [http://en.wikipedia.org/wiki/Angular_velocity Angular Velocity] '''
::* The direction and speed of which this object is rotating when accelerated. This specifies a direction (the direction) in X,Y, and Z of the object's Angular Velocity when accelerated. Default is zero which does not alter the direction of rotation (the Right Hand Rule). This is one of the two required properties in Angular Velocity, the other being speed.
: ''' [http://en.wikipedia.org/wiki/Inertia Inertia] '''
::* This list of variables defines how the objects mass is distributed across the model. It appears to specify 12 points equally distributed locations along the models centerline from top to center to bottom. Applying all the inertia to one section can make the object react top or bottom heavy.
: ''' Center '''
::* NifSkope: …used to relocated the object's center of mass.
: ''' [http://en.wikipedia.org/wiki/Mass Mass] '''
::* A numerical value of the object's mass. It is assumed that this has some relationship to weight but how or in what way is unknown. It's advised to find an object of similar cubic size and apply that objects mass value to your object.
: ''' Linear Damping '''
::* Reduces the amount of linear motion when an object is accelerated. It is noted by NifSkope that a value too low will cause the object to be set in a fixed (non-moving) state.
: ''' Angular Damping '''
::* Reduces the amount of angular motion when an object is accelerated.
: ''' [http://en.wikipedia.org/wiki/Friction Friction] '''
::* Specifies the objects friction in a numerical value. It's assumed that this numerical value has some relationship to an object's coefficient of static friction. But how or if is unknown. It's advised to find an object with similar friction characteristics and copy the value into your objects friction value. For example, you wouldn't assign the friction value of a shield made of bone with the friction value of a shield made of glass.
: ''' Restitution '''
::* This variable sets the object's coefficient of restitution in a numerical value. It is unknown how the value affects the resulting coefficient of restitution in applying elasticity or inelasticity. For example a tennis ball has a coefficient value of 0.71 while a steel ball bearing has a value of 0.60. It is advised to use a value found on a similar object.
::<blockquote>'''NOTE:''' Do not confuse Restitution with Elasticity; they are two completely separate principles. It's understood that restitution is the measure of how an object gives back what was gained during an impact whereas elasticity is a measure of how an object deforms while under strain. '''
 
 
This section will explain what the [http://en.wikipedia.org/wiki/Scabbard scabbard] (Scb) NiNode is and the basic concept of creating one.
 
:* Click: Load on the toolbar.
:* Open: Data\meshes\weapons\iron\dagger.nif
:* Expand: 0 NiNode Dagger
:* Expand: 9 NiNode Scb
:* Expand: 11 NiTriStrips Scb:0
 
Here you will notice that the main difference between the battleaxe.nif and dagger.nif is the addition of a second NiNode called Scb. This NiNode contains the scabbard data including a UPB Block and its own complete NiTriStrips Block. Now look at the render window and notice the textured mesh covering the blade. Click on this mesh to select it. Notice how 11 NiTriStrips becomes highlighted. You've selected the dagger's scabbard.
Because the scabbard is a separate object you can make it anything you want. Make it a human head or maybe a tree. Doesn't seem very realistic but it's all possible. So the steps to create a scabbard are:
 
:* Import a NiTriStrips block with the mesh you want to use.
:* Parent it to its own NiNode
:* Add the necessary UPB data block. TIP: It's best to copy and paste it from the location you got the NiTriStrips block.
:* Then parent the NiNode Scb you created to the weapon's 0 NiNode
 
== '''Scabbards Are Only the Beginning''' ==
Anonymous user