Grate work :)
I started decoding the nif file format and found it easier than I thought, Till i decoded the Vector3 look like the following (Using hex editor and nifscope)
It's kinda hard to solve when you don't find anything useful in nif.xml
I believe the last byte is some sort of constant... but i don't see a pattern in it though :( (The first two bytes)
I get how you did it but now I'm stuck
I successfully made the init.py and it was pretty easy.
I have tried to analyze the nif files but its hard to get its structure if you get my point.(binary)
the header was easy to figure out look like this
Gamebryo File Format, Version 20.2.0.7
Then some binary data containing version, endian type, user version = 12, number of blocks, user version 2 = 83, and a lot of other information such as strings and creator
I know the "user version" cause else creation kit freaks out and crashes. Nifscope tells me this values as well, but only when i open a skyrim model
any tips on how to get the valuable information. And how did you do?
I will check the nif.xml that comes with nifscope
My bad with the duplication when i compared the two models the list just increased without clearing itself. So by opening the model and removing it will cause the list be become huge.
I let you know if i find any thing else.
off topic
I have another question how did you start building this plugin. Cause I want to make a plugin for Skyrim that can handle like animations add the most important the collision with is pretty hard to make in nifscope and the animations are an own file so its gonna get hard to make. but i think i can do it :D . But firs i make it simple, probably import.
I assume that you have taken a look at some other scrips and plugins.
Any tips would be appreciated.
Just tried out the export function and it worked...
Something in the script or the XML is wrong because i don't think it is supposed create a file that is 8x bigger than the normal file. The model i tested was colossi and the exported file is 4,3 MB big and original is 526 KB so... something is wrong :(
I tried to check the model data and it seams to add a lot of unnecessary data to the file cause of its size. And compared in blender the exported model is turned 90 deg right from the normal if you get my point. else it seams to wok. The animation menu get a lot of added unusable animations with the same name as the one that is working. This may be an issue.
It worked better with the latast download but i get two miss shaped "foot/leg" on the colossi, any ideas
I assume i only have to edit something in the structure.xml or is that a part in the py scripting
it is the left front "foot" and it is twisted 90 deg towards the center
and the right front that is just a little twisted towards the center lik 10-20 deg
what it told me to add and i did and the model was loaded....
just a bit screwed up look at pic
do i have to add a refTo to the Srib aswell??
if i have to what values do i add, cause it never complained and nothing interesting is showed up in the console
Btw i like the script and it was easy to modyfy the xml file so it would load the model
This error occour 2 more times with the values
offset 473776 tag=SRIB ver=0 rep=1 sectleng=272 unused=0 perentry=272.0
offset 474048 tag=IKJT ver=0 rep=4 sectleng=128 unused=0 perentry=32.0
script init.py line 860 in execute
m3import.importFile(self.properties.filepath)
script m3import.py line 1003 in importFile
importer.importFile(filename)
script m3import.py line 347 in importFile
self.model = m3.loadModel(filename)
script m3.py line 10598 in loadModel
sections = loadSections(filename)
script m3.py line 10588 in loadSections
raise Exception("There were %s unknown sections" % unknownSections)
Exception: There were 3 unknown sections
@println: Go
Grate work :)
I started decoding the nif file format and found it easier than I thought, Till i decoded the Vector3 look like the following (Using hex editor and nifscope)
hex - - - - - - - decoded (nifscope)
00 00 00 3E - - 0.1250
00 00 80 3E - - 0.2500
00 00 00 3F - - 0.5000
00 00 80 3F - - 1.0000
00 00 A0 3F - - 1.2500
00 00 C0 3F - - 1.5000
00 00 00 40 - - 2.0000
00 00 80 40 - - 4.0000
49 9D AE 40 - - 5.4567
It's kinda hard to solve when you don't find anything useful in nif.xml
I believe the last byte is some sort of constant... but i don't see a pattern in it though :( (The first two bytes)
YAY solved it :D
@println: Go
Ok I thank you for your help and i will search the net, check blender forum and so.
I get how you did it but now I'm stuck
I successfully made the init.py and it was pretty easy.
I have tried to analyze the nif files but its hard to get its structure if you get my point.(binary)
the header was easy to figure out look like this
Gamebryo File Format, Version 20.2.0.7
Then some binary data containing version, endian type, user version = 12, number of blocks, user version 2 = 83, and a lot of other information such as strings and creator
I know the "user version" cause else creation kit freaks out and crashes. Nifscope tells me this values as well, but only when i open a skyrim model
any tips on how to get the valuable information. And how did you do?
I will check the nif.xml that comes with nifscope
@println: Go
My bad with the duplication when i compared the two models the list just increased without clearing itself. So by opening the model and removing it will cause the list be become huge.
I let you know if i find any thing else.
off topic
I have another question how did you start building this plugin. Cause I want to make a plugin for Skyrim that can handle like animations add the most important the collision with is pretty hard to make in nifscope and the animations are an own file so its gonna get hard to make. but i think i can do it :D . But firs i make it simple, probably import.
I assume that you have taken a look at some other scrips and plugins.
Any tips would be appreciated.
Just tried out the export function and it worked...
Something in the script or the XML is wrong because i don't think it is supposed create a file that is 8x bigger than the normal file. The model i tested was colossi and the exported file is 4,3 MB big and original is 526 KB so... something is wrong :(
I tried to check the model data and it seams to add a lot of unnecessary data to the file cause of its size. And compared in blender the exported model is turned 90 deg right from the normal if you get my point. else it seams to wok. The animation menu get a lot of added unusable animations with the same name as the one that is working. This may be an issue.
used the latest plugin files.
It worked better with the latast download but i get two miss shaped "foot/leg" on the colossi, any ideas
I assume i only have to edit something in the structure.xml or is that a part in the py scripting
it is the left front "foot" and it is twisted 90 deg towards the center
and the right front that is just a little twisted towards the center lik 10-20 deg
Thx for the help but.
I added the SRIB and IKJT to Sections and it complained so i added
<field offset="528" name="ikjtData" type="Reference" refTo="IKJTV0"/>
what it told me to add and i did and the model was loaded....
just a bit screwed up look at pic
do i have to add a refTo to the Srib aswell??
if i have to what values do i add, cause it never complained and nothing interesting is showed up in the console
Btw i like the script and it was easy to modyfy the xml file so it would load the model
Downloadad the script and tried to import colossus.m3 but all i get is an error.
I was able to import the zergling anyway
ERROR Unknown section at offset 473024 wtih tag=RIB_ version=6 repetitions=1 sectionLengthInBytes=752 guessedUnusedSectionBytes=4 guessedBytesPerEntry=748.0
This error occour 2 more times with the values
offset 473776 tag=SRIB ver=0 rep=1 sectleng=272 unused=0 perentry=272.0
offset 474048 tag=IKJT ver=0 rep=4 sectleng=128 unused=0 perentry=32.0
script init.py line 860 in execute
m3import.importFile(self.properties.filepath)
script m3import.py line 1003 in importFile
importer.importFile(filename)
script m3import.py line 347 in importFile
self.model = m3.loadModel(filename)
script m3.py line 10598 in loadModel
sections = loadSections(filename)
script m3.py line 10588 in loadSections
raise Exception("There were %s unknown sections" % unknownSections)
Exception: There were 3 unknown sections