Omeletter Posted October 25, 2012 Share Posted October 25, 2012 I searched every corner of the web for this, and found no answer. This is my last hope. Here we go. I made a simple cube in blender, applied a UV map to it, and applied a texture. Everything is fine, for now. I exported it as .obj I opened up the latest stable version of nifskope 1.1.1, which has recently updated, by the way. I opened a model of a vanilla Apple. Clicked the Nitrishape block, and imported my model over. I generated a collision mesh, and applied correct textures. The UV's are messed up. That's the only problem. Seriously, everything else is fine, I even managed to put it in game. The UV mapping looks like a messed up spiderweb in nifskopes UV editor. Why? Why the heck does it break? Why cant nifskope apply the correct UV? If you are going to blame it on blender doing something wrong, e.g. exporting it as obj in blender, believe me, its nifskope. I imported the obj back into blender and it looks fine. Once I import it into nifscope the UV goes crazy. Link to comment Share on other sites More sharing options...
Wasbunny Posted October 25, 2012 Share Posted October 25, 2012 Total wild guess but did you make sure under NiTriShapeData the Num UV Sets is set to 4097? Thanks for letting us know about the update to Nifskope btw. Link to comment Share on other sites More sharing options...
ghosu Posted October 25, 2012 Share Posted October 25, 2012 (edited) Sometimes the newer versions of NifSkope tend to "damage" the UV map (i had the problem with C4D myself and heard 'bout several problems in combination with Blender). Sometimes the UV map is disorted, sometimes it's not visible at all, sometimes you get error messages when you change NUM UV SET to 4097 and update - if NUM UV SET is set to 0 by default than there is something wrong for sure, normally it is 4097 (if directly exported from 3D editor using NIF plugin, if you just import the mesh as .obj it's normally set to 1). I'm still using rc04 since this version works for sure. Edited October 25, 2012 by ghosu Link to comment Share on other sites More sharing options...
LittleBaron Posted October 26, 2012 Share Posted October 26, 2012 All versions of Nifskope since RC-6 have been importing UV maps from object files incorrectly. I still keep a copy of RC-6 handy for this reason. Oddly, if you go to the NifTools website and look under reported issues, you'll see that this issue has been reported but has the statement 'works for me' next to it from a developer... and since they are now at Nifskope 1.0.1 I guess they don't consider it important enough to look into further. Link to comment Share on other sites More sharing options...
ghosu Posted October 26, 2012 Share Posted October 26, 2012 (edited) Haha, nice...Nifskope with not working UV map import. Well, who cares as long as it works for the developer :DBut i can't complain since this tool is for free, kinda funny though ;) Edited October 26, 2012 by ghosu Link to comment Share on other sites More sharing options...
Omeletter Posted October 29, 2012 Author Share Posted October 29, 2012 Thanks for all the replies, I fixed my issue! I downloaded Nifskope RC4, imported .obj there - the UV map is working correctly - and then exported the file as .obj again.I then opened the new Nifskope and imported the mesh back in. It works! The texture is displaying correctly. Link to comment Share on other sites More sharing options...
calyps Posted November 1, 2012 Share Posted November 1, 2012 Why were you exporting as an OBJ? Link to comment Share on other sites More sharing options...
LittleBaron Posted November 2, 2012 Share Posted November 2, 2012 @ calyps: Exporting from blender as an OBJ into Nifskope is far, far less tedious than converting the Nif back and forth into a format that Blender can import/export, and works great as long as your object needs no rigging. Link to comment Share on other sites More sharing options...
Recommended Posts