amokrun1 Posted April 9, 2022 Share Posted April 9, 2022 I'm getting the red triangle on a weapon when it has two mods applied to it. Equip first and third person are fine, it's just when I drop it to the ground. Other modifications or no modifications are also fine. I suspect it must be wrong pathing but looking at the weapon record I cannot see what it is. Where is the path for the world model for a weapon that has modifications applied to it? Link to comment Share on other sites More sharing options...
M48A5 Posted April 9, 2022 Share Posted April 9, 2022 (edited) Look for a mesh that is "weapon name" _go.nif and remove the _go. Edited April 9, 2022 by M48A5 Link to comment Share on other sites More sharing options...
amokrun1 Posted April 9, 2022 Author Share Posted April 9, 2022 Thanks for the reply! Couldn't find a _go affix anywhere though. I looked in the meshes folder and the path entries in the weapon record, is there somewhere else I might want to try? Link to comment Share on other sites More sharing options...
M48A5 Posted April 9, 2022 Share Posted April 9, 2022 The only other way I know to find the offending mesh is to use XEdit. Have you tried using the left mouse button to click on the area of the error symbol? You could then get the ID number and using the console command "GBO" you can get the the base object number, where the first two digits are the load order number of the object. You would then be able to tell which mods are conflicting and you could make the correction with XEdit. I had this problem with Fallout Remastered and Jingwei's Shock Sword. It showed correctly when equipped but you would get the missing mesh symbol when it was dropped or placed on display. Since weapons don't have a world model the _go.nif was causing the problem. When I removed the "_go" from the nif, the problem was corrected. Link to comment Share on other sites More sharing options...
amokrun1 Posted April 9, 2022 Author Share Posted April 9, 2022 (edited) I can see all mods affecting the weapon(Gauss Rifle in this case) but cannot see the conflict. Faulty mesh maybe? When you say you remove the _go, do you mean you just renamed the file? EDIT: Found the problem. Pathing mistake as I had thought. There was a typo, opening up Nifskope and renaming the nifs resolved it. Edited April 9, 2022 by amokrun1 Link to comment Share on other sites More sharing options...
Recommended Posts