Fnv Ncr Trooper Overhaul
You've seen this already, presumably? Since DarnUI is in there, it might be of interest:I did see it. Thanks for reminding me about it.I think today I'm going to have quite a bit of time that I thought I was supposed to have last week. That means today or tomorrow I should do a bunch of updates, DDSopt preliminary support for vanilla BSAs, extra page of info for troubleshooting 4gb loader problems, redoing the first section on UI to use FOMM instead of NMM and the import thingy, mods always more mods, and conflict resolution. That is a ton of stuff to get to, so if I only get to three of them then I will call it a success.
Also, want to do some screens and get to some texture comparisons. My least favorite thing to do. I saw a little bits of discussion about NVSE flashlight being used. Are any of you using this mod? Its the most popular flashlight mod out there and I feel like it should be included to the guide because Nevada Skies can be quite dark. That being said, when I installed it, I did it after the whole NMM part of the guide and I keep on getting this error message that I must unistall MCM then reinstall the flashlight mod but I am not sure how to do that now that I have finished the guide and finished the part where you import your NMM mods to MO. Can anyone shed any light on this?
Double click NCR Trooper Overhaul in the left pane of MO and click the Template:Ui tab. Move the 'NCRTrooperOverhaul.esp' to the Optional ESPs box. NCR Trooper Overhaul - Distributed ( FNV ) Template:Indicator.
Fnv Ncr Trooper Overhaul Kit
(no pun intended)Sorry if this has been touched on in the last few pages. The best order on install for any HUD altering mods is found at the bottom of the one HUD page. Your best bet is to get the FOMM fork, uninstall uHUD and OneHUD, install flashlight nvse, then reinstall uHUD and OneHUD all with FOMM fork through MO. You have to install one mod at a time since the installed mod will end up in your overwrite folder. Just right click the overwrite and select create mod and name it. Then just do it for every mod I listed.If MCM has problems then reinstall it before the other mods I listed and flashlight nvse.Also, I can't officially support flashlight nvse since I can't get it to work with project Nevada.
Fallout New Vegas Ncr Trooper
If you get it working let me know how you did it. Yes, I support the FOMM change. I hate even using NMM for installing the UI mods because it crashes every second mod installation or so. It's ridiculous and really does waste my time.I'm starting work on it now.
The original FOMM was very unstable when used with MO, but the FOMM - Fork works really well unless one of the installers calls a specific FOSE function, but I haven't seen one yet. Also, I now have the added benefit of recombining the User Interface section into one big section instead of two.
Looks like Ewi has been busy. For your consideration and convenience;and of course the you already new about.Yeah, I like EWI's stuff overall, but to me it seems as if every rock textures is the same and the color is just being changed. When I finally have more time for it I am going to look over the rocks again. Hetrol's Manholes are still the best, but those sun rays may make it in pretty soon. Not sure about the desert pack either, I'm going to have to examine the desert area around Vegas because I've only ever been to the hotels and the airport, so I don't actually know what the landscape really looks like there. Alright, I have finally conquered the ins and outs of using MO and FOMM together without going completely insane. I know the possible problems that arise and how to solve them because I am amazing.I've updated the guide to now install the Interface mods that Unified HUD requires to show installation with MO and FOMM.
Glad to hear you're a fan of the NV Interiors.I notice that Improved Sound FX has several esp files, is there a trick to merging them such that Wrye Bash will import their data into the bashed patch?I can merge the majority of the sharing fixes with FNVEdit, but Wrye Bash only recognizes my originals not the merged file in the import sound tab when rebuilding the bashed patch.Use the directions on the guide and reduces the plugin count to two. The main plugin gets merged to bashed patch which leaves only my patch. Pardon my confusion, I'm using Wrye/Bain, the guide directions indicate a merge which I assume is a Mod Organizer function? Since I don't have MO functionality, would I then use FNVEdit & the merge script 1.6 to merge; 'Improved Sound FX - Weapon Sharing Fix.esp', 'Improved Sound FX - GRA.esp', 'Improved Sound FX - DM.esp', 'Improved Sound FX - HH Sharing Fix.esp', 'Improved Sound FX - HH.esp', 'Improved Sound FX - OWB Sharing Fix.esp', and 'Improved Sound FX - LR Sharing Fix.esp' as the MO users do?Please correct me if I've misunderstood. Currently only Improved Sound FX - OWB Sharing Fix.esp & Improved Sound FX - LR Sharing Fix.esp are merging into my bashed patch (by that I mean the checkmark turns to a '.'
In Wrye Flash), although I'm checking the boxes to include all available plugins during the build patch menu. That merge is different than the FNVEdit merge script. In MO you can merge multiple files from the same mod into one folder.For your problem just get rid of everything except the main plugin and the PN plugin. All the other plugins can be removed, in Wrye, you just untick the plugins on the right hand side of the installers tab. Each mod should it's plugins listed. Pretty sure that is how it works, been a while since I used Wrye for installation.After that just get the very next mod on the guide, my Improved Sound - WMX patch.
That includes the weapon sharing fixes and the DLC patches, plus WMX compatibility.