Fantasy Frontier Online (Aura Kingdom) New Nifs

[Nonstop]

Something seems to have changed with the recent nifs from this game.They have no game version in the header, although still has the shortened header like 20.3.1.2 files have but obviously something is different within the files.



Included a few of the new nifs, I really have no idea about this stuff so any help that can be provided would be great.

https://www.mediafire.com/file/sainp8k8 ... s.zip/file

[moonpaladin]

Hello, sorry for invading your post! but here I have more examples of models that cannot be opened with noesis , I was trying to modify the file so that noesis can open it but it keeps giving me errors, I hope someone can update it, thank you very much

http://www.mediafire.com/file/uom0z2rfg ... 9.nif/file

http://www.mediafire.com/file/ouot1dl8b ... 9.nif/file

example3.png

[shakotay2]

Google is your friend, don't you know that?

06-03-18 (!) the user jiejie12351 posted at ragezone forums "Hey guys. I found that nifskope can read nif 20.3.1.2 directly with the latest release." (http://forum.ragezone.com/f939/read-nif ... a-1146052/)

So what was the latest release then? Guess the exe as of 23rd of Febr. 2018 - works for this 20.3.1.2 nif:
.

r289-nif skope.png

[shakotay2]

For problematic nifs hex2obj usually does a good job (if it's for the meshes only):
(first sub mesh only)
.

r7049-nif.png

[moonpaladin]

Thanks Shakotay! Yeah I used the latest NifSkope (NifSkope_2_0_2020-07-09-x64) and it didnt work , I'm gonna take the 2017 version! thanks again Shakotay!

[wansf]

are you going to update the noesis script?

[moonpaladin]

For problematic nifs hex2obj usually does a good job (if it's for the meshes only):
(first sub mesh only)
.
r7049-nif.png

eyy! Shakotay what should be the values for the UVs? I'm using 1F67E for star address but it fails, gonna be checking how to get those values for uvs, I'm not much familiar with those but if you can share your values for uvs will be cool and helpfull. thanks

[shakotay2]

I'm using 1F67E for star address but it fails,

Didn't care for uvs but what is the logic behind using (0x)1F67E?
Scrolling down in the file after that FF.. block there's only ONE possible address for me. Much to learn you have... use the source!
.

r7049-nif-uvs.png

[moonpaladin]

I'm using 1F67E for star address but it fails,

Didn't care for uvs but what is the logic behind using (0x)1F67E?
Scrolling down in the file after that FF.. block there's only ONE possible address for me. Much to learn you have... use the source!
.
r7049-nif-uvs.png

hahaha Yeah I'm still learning! thanks Shakotay

[moonpaladin]

Scrolling down in the file after that FF.. block there's only ONE possible address for me. Much to learn you have... use the source!

Hello Shakotay! I was practicing with the other version of the nif and I have been able to get the mesh values, but it is still difficult for me to find the exact values of the UV block, what would be the value of the FVF size of the nif 289? . I tried with 1E168 and 40F09 values but both are incorrect :/.

nif289test.png

[shakotay2]

but it is still difficult for me to find the exact values of the UV block, what would be the value of the FVF size of the nif 289?

dunno what you mean, it's 12, as used by you. Or speaking of "size UVB" (size of UV block)?

I tried with 1E168

there's floats, not half floats, you won't get far as long as you don't get the difference

Also learn to find blocks, it's a little bit nasty here because they inserted a zero bytes, or 3 bytes at 0x42AFA, 0x4EB44 for example.
blocks:
0x40f0a, 596 vertices
0x42afd - 446ed normals
0x446fe - 462ee whatever

0x46c4b some FI block

(That's very time consuming and I don't have the time to check for uvs here, sry.)

update:
.

r289-nif-uvs.png

[moonpaladin]

Also learn to find blocks, it's a little bit nasty here because they inserted a zero bytes, or 3 bytes at 0x42AFA, 0x4EB44 for example.
blocks:
0x40f0a, 596 vertices
0x42afd - 446ed normals
0x446fe - 462ee whatever

0x46c4b some FI block

(That's very time consuming and I don't have the time to check for uvs here, sry.)

xD! Yeah I identified those but still trying to figure how to identify which block correspond to the uv. thanks

[moonpaladin]

r7049-nif-uvs.png

Shakotay I was able to find the UVB start of another .nif similar to the "alpaca mount", how can I save the mesh with its UVs? I don't know why I am getting an error when I try to open the exported .obj. And now I have tried with the .nif 7049 and the same thing happens. I am practicing to identify blocks as you said, but I have a doubt about the value "8" and "4", how is it calculated or how do I know what value has to go there? I know the 99 is because the UVB is separate from the mesh block, but the other two values are still not quite clear to me. Thank you!
https://www.mediafire.com/file/sxqq2ryi ... 7.nif/file

test18.png

FVF SIZE SHOULD BE 6!

[moonpaladin]

Lol, what a retard xD, is not 8, should be 6! well but how to calculate those values

[shakotay2]

r7037-nif-uvs.png

.
0x5F2E is the start of a new block/a signature part, whatever - simple to see with some experience (0x5F3B: start of face index block).

4 is length of two half float uvs, so start address of uvs' block is
0x5F2E - 1735x4 (hex.)= 0x4412

(This calculation is different for nif r289, see my updated previous post above.)

btw: you should change the FVFsize from 8 to 6 in your previous picture to not confuse people.
And toggle the "seq" button to "VB".

Seems you're gaining experience! Cool.