EverChosen97 Posted July 27, 2017 Share Posted July 27, 2017 (edited) Title pretty much says it all. Using TTW, WMX, WRP, and PN and pretty much all textures for scopes that can be added to weapons are messed up and i'm fairly sure I have all the required patches. LO: https://pastebin.com/namnvZeU I will try reinstalling WMX just to make sure I turned AI on/off when I installed it. Are there any other reasons as to why this might be happening? Edited July 30, 2017 by EverChosen97 Link to comment Share on other sites More sharing options...
dubiousintent Posted July 27, 2017 Share Posted July 27, 2017 I'm not familiar with TTW itself, but you should start by reading their FAQ page carefully. There are a number of patches needed for common mods like NMC, WMX, and PN listed there. This question would be better addressed on the TTW Support forum. While the members of that team do show up here on occasion, you will get a quicker response there. You might want to clarify a bit on what you mean by "messed up". There can be several possible causes. -Dubious- Link to comment Share on other sites More sharing options...
EverChosen97 Posted July 30, 2017 Author Share Posted July 30, 2017 Thanks for the reply but according to them it has nothing to do with TTW, so I came here to see if it was something to do with the other mods. I'm fairly sure by now I have all of the required patches, I cant think of any I might be missing Link to comment Share on other sites More sharing options...
dubiousintent Posted July 30, 2017 Share Posted July 30, 2017 Then I reiterate: just what do you mean by "messed up"? -Dubious- Link to comment Share on other sites More sharing options...
EverChosen97 Posted July 30, 2017 Author Share Posted July 30, 2017 (edited) Forgive me for being an idiot but I thought I clarified that in the OP. Will change that now. Broken textures, simple as that, for the majority of scopes that are able to be added to weapons Edited July 30, 2017 by EverChosen97 Link to comment Share on other sites More sharing options...
dubiousintent Posted July 31, 2017 Share Posted July 31, 2017 (edited) "Broken" as in you get the "white ! on a red background" (which indicates a mesh problem) or a solid color (which indicates a texture problem)? If so, please see the 'Solutions to Mesh (Red "!" icon) or Texture (solid color) problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide. Or "broken" as in you cannot add the scope mod to a weapon as expected, or as in you are getting the wrong reticule? I see you have a manually created "MergePatch" file near the bottom of the load order. Assuming your problem isn't solved by toggling "ArchiveInvalidation", this is what I would first suspect is in need of updating. Identify a particular scope having issues, determine it's Mod Index, then load both that plugin and your "MergePatch" file in FNVEdit and see which is winning the conflict. You might need to repeat having your entire load order in FNVEdit. See the 'Issue: Find the source mod-index of an object in-game' entry in the above mentioned section. Also, "merge patch" files need to be last in the load order. I know nearly every mod says that, but the only instance where that is not true for a "merge patch" is if the later loading plugins do not touch on ANY of the same records as the patch file. Typically that only applies to files required by "post-processors" such as ENB or SweetFX presets. "Wasteland Lighting" doesn't fall into that category. Move it above your "Merge Patch" file. Please see the 'Third Rule: The Rule of One' and 'Merge Patch file' sections of the wiki "FNV General Mod Use Advice" article.-Dubious- Edited July 31, 2017 by dubiousintent Link to comment Share on other sites More sharing options...
EverChosen97 Posted July 31, 2017 Author Share Posted July 31, 2017 (edited) The mod page for wasteland lighting specifically states however that it should go at the very bottom of the LO, even below the merged patch. And to elaborate further, no missing mesh, and no solid color. They appear to simply be using the wrong texture.I will provide screenshots if need be. This has been a long running problem of mine even before I downloaded 3/4 of the mods I have installed right now. No conflicts as far as I can tell. EDIT: Misinterpreted the instructions for RWL, now in proper LO spot Edited July 31, 2017 by EverChosen97 Link to comment Share on other sites More sharing options...
dubiousintent Posted July 31, 2017 Share Posted July 31, 2017 A "wrong texture" would mean some mod placed a different texture in the same location using the same filename. It's certainly possible and known to happen. The texture is linked as a filename and path in the mesh file. Not something you can fix in the "load order". The only solution is to determine which mod overwrote which file. (This is what "install order" is all about: when files overwrite each other, the last to overwrite "wins".) Another possibility is to install yet another mod later which replaces with a "more correct" texture, like "Immersive Scopes" or "Scope Replacer Pack". First thing is to determine what texture you want to "win". Then change your install order so it is installed last. -Dubious- Link to comment Share on other sites More sharing options...
EverChosen97 Posted July 31, 2017 Author Share Posted July 31, 2017 I'll give these textures a try, Thanks for the help! Link to comment Share on other sites More sharing options...
Recommended Posts