Has anyone else figured this out yet? Because after playing around I have a rough idea what's causing alot of the problems, and consequently, how to fix most of them. If anyone cares, I can probably make up a quickie tutorial.
What proplem? :huh:
Quote from: style on September 20, 2007, 11:25:36 AM
What proplem? :huh:
Certain Hexes done in nifskope for FF1 cause the nif-converter not to work... From what I can tell, usually it has to do with pieces that have been deleted and other pieces added. The mesh stores what nodes it has as it's "children", but if you delete a node in nifskope, that doesn't remove the data that says it's supposed to be there. Sometimes that's ok, the converter will just ignore them, but it causes problems just as eaisily.
Yeah I've been wondering how to convert skoped meshes as well. I assume you are using the exnifconverter?
If you can figure this out, you'll be my hero! It's a total pain having to do FF and FFv3R versions of every Skope.
It's in part because of this problem that I only work in FFvTTR. I'd like to see a solution if possible.
Well, unfortunately the ones I had problems converting (sans Tomato, but that's the FX rather then the hexing itself) have eithor been fixed or fixed+converted, not to mention the ones that just work with both that I don't bother converting. If someone would send me(mygreyhulk100@hotmail.com) a problematic mesh, I'll make a tutorial for fixing it.
I'll be honest though, my way might not be 100% perfect. I have a theory as to how to fix it, and it's worked with the few problem meshes I encounter, but not everything is as easy.
Edit: Scratch that, send it to tomatoisjp@gmail.com , I forgot how evil hotmail is with zips...
http://frworld.wikispaces.com/Converting+Skoped+Meshes
And it's done. Hope this helps.