Editing Arcane University:Nifskope Weapons Setup

Jump to: navigation, search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 2: Line 2:
 
This guide will details all there is to know about setting up weapons models to be game-ready.
 
This guide will details all there is to know about setting up weapons models to be game-ready.
  
This is a workflow-agnostic tutorial, focused on NifSkope. As long as your workflow allows you to export a custom model to a NIF containing only the geometry, you can follow along to get your weapon game-ready.
+
This is a workflow-agnostic tutorial revolving around nifskope.<br>
 +
As long as your workflow allow you to export model into a bare NIF model containing only the geometry, you can follow along to get your weapon game-ready.
  
== General Considerations ==
+
__TOC__
There are a few things to know before getting started:
+
 
Skyrim only supports a limited number of weapons variations:
+
 
* One-Handed
+
= General Considerations =
** Dagger
+
 
** Sword
+
There is a few things to know before getting started:
** War Axe
+
Skyrim only support a limited number of weapons variations:
** Mace
+
* 1 Handed
* Two-Handed
+
** Daggers
 +
** Swords
 +
** Waraxes
 +
** Maces
 +
* 2 Handed
 
** Greatsword
 
** Greatsword
 
** Battleaxe
 
** Battleaxe
 
** Warhammer
 
** Warhammer
 
* Ranged
 
* Ranged
** Bow
+
** Bows
** Crossbow
+
** Crossbows
 
* Special
 
* Special
** Staff
+
** Staves
  
Anything you may see in mods are just models setup to look somewhat right (or not) as one of the above types.
+
Anything you may see in mods are just models setup to look somewhat right (or not) as one of the above type.
  
Aside the gameplay differences, the weapon type defines:  
+
Aside the gameplay-oriented differences, the weapon type define:  
 
* Where the weapon will go on the 3rd person model when sheathed
 
* Where the weapon will go on the 3rd person model when sheathed
* Where the player character will grip the model when holding it
 
 
* Which animation set it will be using
 
* Which animation set it will be using
 
* Which kind of impact it will create when hitting things (sounds and visuals)
 
* Which kind of impact it will create when hitting things (sounds and visuals)
 +
* Where the player character will grip the model when holding it
  
If the last point (impacts) don't matter much here, the other 3 set the limitation on how different your model can be from the target weapon type.
+
If the last point (impacts) don't matter much here, the other 3 set the limitation with how different your model can be from the target weapon type.<br>
 +
A handle to big will see the player's hand inside it, a blade too long will clip through the ground when sheathed, a bow to wide will obstruct the view of the player when aiming in 1st person, etc...
  
If the handle is too big, the player's hand will clip inside it. If the blade is too long, it may clip through the ground when sheathed. If a bow is too wide, it may obstruct player's view when aiming. As such, it is important to know in advance which weapon type your weapon will use. A good strategy is to use one of the vanilla weapons as a reference when modeling.
+
As such, it is important to know in advance which weapon type your weapon will target, and eventually to use one of the vanilla model as reference for the proportions when modelling.
  
Another thing to keep in mind is that Skyrim supports special first person models, which may be higher quality than their world model/third person model, as it won't be used for cluttering, or when worn by NPCs.
 
  
It is not mandatory to provide a different model for first person and third person, unless the first person model absolutely needs to have additional detail, but this is something to keep in mind when designing generic weapons that may be used in the hundreds by a level designer to clutter an armory. Unique weapons are safer to make with high detail, since they will only ever appear once in the game scene.
+
Another thing to keep in mind is that Skyrim supports special 1st person models, which may be higher quality than their worldmodel / 3rd person model counterpart as the model won't be used for cluttering, or worn by NPCs.<br>
 +
It is not mandatory to provide a different model for 1st person and 3rd person, unless the 1st person model absolutely need to be high poly and high-res, but this is something to keep in mind when designing generic weapons that may be used by the hundreds by a level designer to clutter an armory. On the other hand, unique weapons are probably best kept at high quality for both variants.
 +
 
 +
= Pre-requisites =
  
== Pre-requisites ==
 
 
To follow this tutorial, you will need:
 
To follow this tutorial, you will need:
* NifSkope
+
* Nifskope
 
* Skyrim Legendary Edition
 
* Skyrim Legendary Edition
 
* The Creation Kit
 
* The Creation Kit
 
* A way to export/convert a model's geometry from your modelling software to a NIF.
 
* A way to export/convert a model's geometry from your modelling software to a NIF.
  
== Anatomy of a weapon NIF ==
+
= Anatomy of a weapon NIF =
=== Inventory Position - BSInvMarker ===
+
 
 +
== Root - BSFadeNode ==
 +
 
 +
== Inventory Position - BSInvMarker ==
 +
 
 
In your inventory, your item will always be viewed from the positive y-axis. In order to change how it is viewed in the inventory, insert a BSInvMarker into the BSFadeNode, within the 'Extra Data List':
 
In your inventory, your item will always be viewed from the positive y-axis. In order to change how it is viewed in the inventory, insert a BSInvMarker into the BSFadeNode, within the 'Extra Data List':
 
*First, create the BSInvMarker by right-clicking onto the BSFadeNode and using <code>Block > Insert > Bethesda > BSInvMarker</code>.
 
*First, create the BSInvMarker by right-clicking onto the BSFadeNode and using <code>Block > Insert > Bethesda > BSInvMarker</code>.
Line 63: Line 74:
 
You cannot enter negative values in the fields, so make sure to start from negative values in Blender, since they will be made positive via the formula. If you do not have negative values to begin with, subtract 360 degrees again and again until you do.
 
You cannot enter negative values in the fields, so make sure to start from negative values in Blender, since they will be made positive via the formula. If you do not have negative values to begin with, subtract 360 degrees again and again until you do.
  
=== Metadata - BSXFlags ===
+
== Metadata - BSXFlags ==
  
=== Weapon Type - NiStringExtraData (Prn) ===
+
== Weapon Type - NiStringExtraData (Prn) ==
In order to make sure your weapon is sheathed in the correct position, you need to add a NiStringExtraData block to the BSFadeNode. This needs to have <code>Prn</code> as its name, and one of the values in the table below as its string data. This (in part) lets the game know where the weapon is sheathed and what kind of animations are used. If this block is not present in your nif, the weapon will likely show up at your feet. The following table shows which values are used in vanilla Skyrim, and by which kind of weapons.
+
 
 +
In order to make sure your weapon is sheathed in the correct position, you need to add a NiStringExtraData block to the BSFadeNode. This needs to have <code>Prn</code> as its name, and one of the values in the table below as its string data. This (in part) lets the game know where the weapon is sheathed and what kind of animations are used. If this block is not present in your nif, the weapon will likely show up at your feet. The following table shows which values are used by the vanilla Skyrim game, and by which kind of weapons.
  
 
{| class="wikitable sortable"
 
{| class="wikitable sortable"
Line 75: Line 87:
 
| QUIVER || Arrows
 
| QUIVER || Arrows
 
|-
 
|-
| SHIELD || Shields, some staves, torches
+
| SHIELD || Shields, some staffs, torches
 
|-
 
|-
 
| WeaponAxe || (War/Hand)Axes
 
| WeaponAxe || (War/Hand)Axes
Line 87: Line 99:
 
| WeaponMace || Mace
 
| WeaponMace || Mace
 
|-
 
|-
| WeaponStaff || Most staves
+
| WeaponStaff || Most staffs
 
|-
 
|-
 
| WeaponSword || (One-handed) Swords
 
| WeaponSword || (One-handed) Swords
 +
|-
 +
| WeaponAxe || (War/Hand)Axes
 
|}
 
|}
  
=== Collision - bhkCollisionObject ===
+
== Collision - bhkCollisionObject ==
 
+
=== Scabbard Model (Scb) - NiTriShape ===
+
  
The NiTriShape that is used for the scabbard needs to be called "<code>Scb</code>" in order for it to remain at the correct place, instead of moving with the weapon.
+
== Scabbard Model (Scb) - NiTriShape ==
  
=== Blood Lighting - NiTriShape ===
+
== Blood Lighting - NiTriShape ==
  
=== Blood Effects - NiTriShape ===
+
== Blood Effects - NiTriShape ==
  
=== Weapon Model - NiTriShape(s) ===
+
== Weapon Model - NiTriShape(s) ==
  
=== Example ===
+
= Example =

Please note that all contributions to Beyond Skyrim are considered to be released under the Creative Commons Attribution-ShareAlike (see Beyond Skyrim Wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel | Editing help (opens in new window)

Template used on this page: