NifSkope - Is there a glossary?

[Relativelybest]

I'm trying to learn how to use NifSkope again. My efforts are somewhat hampered by the fact that a lot of the terms used make no sense to me, and all tutorials I've found -even the basic ones- seem to expect me to already know what they mean.

 

Just wondering, is there a glossary for this stuff? I've looked around for one but have found nothing so far.

[necKros]

Have you looked in the wiki? o: What kind of terms don't make sense to you?

[Skree000]

string: a text entry

block: a line of data in the Tree

branch: a series of blocks that are nested in a hierarchy in the Tree

 

thats all for now :)

[Relativelybest]

Have you looked in the wiki? o:

 

Yeah, I tried searching it but it gave no results.

 

What kind of terms don't make sense to you?

 

All of them?

 

Like, what does "collision" mean? Or "havok", or "sanitize"? Etc, etc.

 

Frankly, it would be easier to list the words I do understand. Hence why I asked for a glossary, rather then definitions of specific terms.

 

string: a text entry

block: a line of data in the Tree

branch: a series of blocks that are nested in a hierarchy in the Tree

 

thats all for now :)

 

Thanks, though you might want to start with explaining what this Tree is. I'm assuming it's the same thing as the block list, but still.

[NaboeN]

Branches usually grow out of trees (this also applies in Real Life, in case you've never played it) making Tree a list of branches

[necKros]

Have you looked in the wiki? o:

 

Yeah, I tried searching it but it gave no results.

 

What kind of terms don't make sense to you?

 

All of them?

 

Like, what does "collision" mean? Or "havok", or "sanitize"? Etc, etc.

 

Frankly, it would be easier to list the words I do understand. Hence why I asked for a glossary, rather then definitions of specific terms.

 

string: a text entry

block: a line of data in the Tree

branch: a series of blocks that are nested in a hierarchy in the Tree

 

thats all for now :)

 

Thanks, though you might want to start with explaining what this Tree is. I'm assuming it's the same thing as the block list, but still.

Mmm... that probably won't appear in the wiki, since they are very generic terms.

 

So... collision (often col for short) is one of the basics in 2D and 3D interaction between objects. As you can imagine, two objects collide if they share at least one point in the plane (2D) or space (3D). What you will find about collision in the nifskope are basically those yellow boxes around weapons and statics in general. They are collision boxes. When you are in the game, you can see your full object, but to the laws of physics, only exist those yellow boxes exist. Collision boxes were made to simplify physics. It's easier to calculate how a box should bounce or fall that a complex mesh.

 

And Havok is an engine which runs under the Beth engine. This one manages all the physics, as well as some particle systems. In Nifskope, the option in the render menu enables or disables the collision boxes.

 

And the option sanitize... I'm not sure, but they wiki should have the answer.

 

*edit* Here's what the wiki has to say about the auto-sanitize option:

This option, when enabled will auto-fix many types of small chores you may have neglected when changing data. Checking links, updating arrays, etc. (Best left on.)

[Skree000]

sanitize means to Clean up

 

sanitize is a menu that has several options inside it dedicated to cleaning up / making-better your nif file.

 

SOMETIMES however Auto-Sanitize-Before-Save can cause VERY bad things. I sometimes disable this because often saving my nif will corrupt it.

My nif files often have corrupt tables with strings that are far too large and are invalid. I think thats a nifskope problem