FunkyGandalfCat Posted September 22, 2016 Share Posted September 22, 2016 (edited) So, I am working in this mod for a while now, After I finished the 3D and textures went to Nifskope.I followed step by step Malfazar Complete Weapon Tutorial.When I got to the part when you put the texture on the weapon, this happened:EVERYTHING IS ALWAYS EXPORTED AS OBJhttp://s16.postimg.org/7oz4orwyd/Texture_Problem.pngThen I realized that the damn NifSkope decided to f*#@ all my uv maps uptake a look what it does:http://s25.postimg.org/wrok5pku7/problem2.pngWhat it looks like on maya:http://s25.postimg.org/cycgd07gf/Problem3.png2 weeks working on it and then this happens, very frustranting.Please helpe me, why Nifskope destroys my uvs? Edited September 22, 2016 by FunkyGandalfCat Link to comment Share on other sites More sharing options...
LeVosgien Posted September 23, 2016 Share Posted September 23, 2016 (edited) UV messed up.... This is a well known issue with importing OBJ into Nifskope pre 2.0+ versions. Switch to a more recent release, no matter what other modders tell you. Or use the maya nif exporter, which is on nexus mod pages. Less trouble than importing obj anyway (in whichever version of nifskope you're using). As a side note: be careful not to go too overboard with the polycount. Nif files are in an old 16bits format, meaning a max of 65K vertices before things start to unravel. Though that might be per niTrishape rather than per file, I'm not sure which it was. You could easily bake a lot of those nice details into a lower poly version's normal map. Edited September 23, 2016 by LeVosgien Link to comment Share on other sites More sharing options...
FunkyGandalfCat Posted September 28, 2016 Author Share Posted September 28, 2016 UV messed up.... This is a well known issue with importing OBJ into Nifskope pre 2.0+ versions. Switch to a more recent release, no matter what other modders tell you. Or use the maya nif exporter, which is on nexus mod pages. Less trouble than importing obj anyway (in whichever version of nifskope you're using). As a side note: be careful not to go too overboard with the polycount. Nif files are in an old 16bits format, meaning a max of 65K vertices before things start to unravel. Though that might be per niTrishape rather than per file, I'm not sure which it was. You could easily bake a lot of those nice details into a lower poly version's normal map.Yep, thanks for the tipsI installed the nif exporter and worked perfectly. Link to comment Share on other sites More sharing options...
Recommended Posts