Jump to content

AWSO compatibility with WMX


EverChosen97

Recommended Posts

So I want to download the All weapon sounds overhaul mod from here: http://www.nexusmods.com/newvegas/mods/62870/?tab=4&&navtag=http%3A%2F%2Fwww.nexusmods.com%2Fnewvegas%2Fajax%2Fcomments%2F%3Fmod_id%3D62870%26page%3D2%26sort%3DDESC%26pid%3D0%26thread_id%3D5363295&pUp=1 but it sadly doesn't work properly with the TTW version of WMX. There is however a patch for the regular WMX but it requires the WMX-DLCmerged.esp and WMX-POPmerged.esp plugins active to work. Now thats where the problem arises, as the TTW version has merged those together, thus removing the plugins from the LO. Is there a way I can remove those masters from the patch using the GECK or FNVEdit and still expect it to work? (preferably FNVedit, I have no experience with the GECK)

 

Also before anyone asks, yes I've commented on the mod page and posted on the TTW forums but with no replies. I've just sent a PM to the mod author to see if I can possibly get a response but that of course takes time so this is pretty much my last resort. Thanks to anyone who bothers to help me in advance!

Edited by EverChosen97
Link to comment
Share on other sites

Just removing masters from a mod will break it. Speaking in general terms, you should make your own TTW patch for WMX and that Sound overhaul using the TTW version of the WMX file. (Easier said than done.) Loading all the files involved (including both WMX merged plugins and the TTW merge), adding all as "masters" to your new patch file, and then using the "clean masters" command which will safely remove the unneeded masters IF all references to them have been removed from the new patch. You need to be injecting and renumbering the "TTW merged" content into the new patch instead of the content from the "WMX merged" patches.

 

There is an incomplete article that describes 95-98% of the basic process (including links to other tutorials) in "Multiple file Merge-Up Procedure". The last "incomplete" 2-5% is because I haven't figured out how to properly give the resulting plugin a different filename in FNVEdit. It can probably just be renamed in Windows Explorer, but I consider that a "workaround" instead of a solution. But everything else has been tested to work correctly. You will need to adapt it to your specific situation.

 

-Dubious-

Edited by dubiousintent
Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...