Nintendude1236 Posted March 16, 2018 Share Posted March 16, 2018 I realise this question has likely been posed before, but I saw no clear responses to it so... I have recently begun switching from NMM to MO, and for the most part things seem to be going cleanly. However, I've run into a bit of an issue regarding nifskope and it's texture paths. Previously, whilst my Skyrim installation ran on NMM, I had made some manual edits using Nifskope to models from mods; namely, I swapped a vanilla texture (since the mesh being changed was a modified vanilla model) to one from a replacer mod. Seeing as MO uses a virtual data folder rather than the normal one, I must ask: what new texture paths need I set for modded models to render textures properly in Nifskope? Link to comment Share on other sites More sharing options...
Frankfranky Posted March 16, 2018 Share Posted March 16, 2018 open nifskope, go into options>resources and click autodetect game paths. I also added the Mod Organizer folder to the paths. I don't know if this is actually necessary, mb it is.Now go into MO and add nifskope as an exectutable. If you want to see the textures in Nifskope you have to run it from inside MO. 1 Link to comment Share on other sites More sharing options...
Nintendude1236 Posted March 17, 2018 Author Share Posted March 17, 2018 That seems to have done the trick! Thank you! Link to comment Share on other sites More sharing options...
pokkla Posted April 12, 2020 Share Posted April 12, 2020 I was having this problem too. Once I put Nifscope as an executable into MO2 and added the paths, it worked. I'll also add, even with the fix, it does not work if I'm opening a nif directly from MO2's 'data' tab. I like the folder view, like the data tab, so I find it easier to go into 'Explore Virtual Folder' and find the nif how many ever folders down from 'meshes'. Plus, it allows me to open multiple instances of nifscope so I can do side by side visual comparisons. Either way, opening a mesh from nifscope or the virtual folder, it's really nice to see the textures compared to the wireframe. Thanks. Link to comment Share on other sites More sharing options...
z929669 Posted September 11, 2020 Share Posted September 11, 2020 You can open NIF files in NifScope from the MO file tree/conflicts if you associate NIF files with NifScope in Windows. You don't even need to set up as a MO executable, I don't think. Link to comment Share on other sites More sharing options...
101jojo92 Posted October 25, 2020 Share Posted October 25, 2020 (edited) I was having this problem too. Once I put Nifscope as an executable into MO2 and added the paths, it worked. I'll also add, even with the fix, it does not work if I'm opening a nif directly from MO2's 'data' tab. I like the folder view, like the data tab, so I find it easier to go into 'Explore Virtual Folder' and find the nif how many ever folders down from 'meshes'. Plus, it allows me to open multiple instances of nifscope so I can do side by side visual comparisons. Either way, opening a mesh from nifscope or the virtual folder, it's really nice to see the textures compared to the wireframe. Thanks. 2020 NifSkope can definitively read .dds files now. To anyone getting here through google nowadays, check your NifSkope version, you might have downloaded a older version linked by a tutorial or some like that. (that's me) Edited October 25, 2020 by 101jojo92 Link to comment Share on other sites More sharing options...
Dovah164 Posted March 19, 2021 Share Posted March 19, 2021 THANKYOUUUUUUUUUUUUUUU Link to comment Share on other sites More sharing options...
Recommended Posts