FNV with OneHUD and UnifiedHUD
Posted 28 October 2013 - 07:38 AM
Posted 28 October 2013 - 07:49 AM
Posted 16 November 2013 - 09:40 PM
Posted 02 March 2014 - 04:10 AM
I hope this doesn't just reanimate a dead thread, because for me this is highly current. I have tried to get the more obvious and important HUD mods to play together well in my new FNV play through. Of course I use Mod Organizer as much as possible, keeping a clean install directory is as important as having clean underwear!
I use MO for everything other then the annoying HUD mods that need to play together to work well or even at all. For those I use FOMM and leave all the FOMM files in the Overwrite part of MO.
In somewhat alphabetical order the HUD mods are:
- CASM with MCM
- Flashlight NVSE
- JIP Selective-Fire
- Project Nevada
- Project Nevada - Extra Option
- Project Nevada - Extra Option - MCM fix
- Shilohs Clean Pipboy Screen
- Shilohs Colour Maps and Icons
- The Mod Configuration Menu - MCM
- MCM bug fix
- The Weapon Mod Menu
- Unified HUD Project
I followed the instruction for activation (FOMM uses Activate/Deactivate as wording for installation) of the mods on the oHUD page as follows:
Recommended Installation Order
[color=rgb(255,255,255);font-family:'Trebuchet MS', Helvetica, sans-serif;font-size:12.800000190734863px;background-color:rgb(64,64,64);]It is important to install One HUD after Darns UI and any mods the require iHUDification:[/color]
[color=rgb(255,255,255);font-family:'Trebuchet MS', Helvetica, sans-serif;font-size:12.800000190734863px;background-color:rgb(64,64,64);]1. Deactivate Unified HUD (if used).[/color]
[color=rgb(255,255,255);font-family:'Trebuchet MS', Helvetica, sans-serif;font-size:12.800000190734863px;background-color:rgb(64,64,64);]2. Activate Darnified UI.[/color]
[color=rgb(255,255,255);font-family:'Trebuchet MS', Helvetica, sans-serif;font-size:12.800000190734863px;background-color:rgb(64,64,64);]3. Activate Project Nevada[/color]
[color=rgb(255,255,255);font-family:'Trebuchet MS', Helvetica, sans-serif;font-size:12.800000190734863px;background-color:rgb(64,64,64);]4. Activate Mod Configuration Menu (MCM)[/color]
[color=rgb(255,255,255);font-family:'Trebuchet MS', Helvetica, sans-serif;font-size:12.800000190734863px;background-color:rgb(64,64,64);]5. Activate all other HUD altering mods (see above list).[/color]
[color=rgb(255,255,255);font-family:'Trebuchet MS', Helvetica, sans-serif;font-size:12.800000190734863px;background-color:rgb(64,64,64);]6. Activate One HUD (oHUD) *.[/color]
[color=rgb(255,255,255);font-family:'Trebuchet MS', Helvetica, sans-serif;font-size:12.800000190734863px;background-color:rgb(64,64,64);]7. Activate Unified HUD *.[/color]
[color=rgb(255,255,255);font-family:'Trebuchet MS', Helvetica, sans-serif;font-size:12.800000190734863px;background-color:rgb(64,64,64);]*Always install oHUD and uHUD last. And if you install any mod affecting the HUD after these, reinstall them both.[/color]
For some reason, probably or most definitely 'cause of my own mistakes, I can't get some of the functionality of the mods to work. CASM won't save apart from the set autosave timer (e.g every 5 minutes) and I can't for the life of me get my compass to show, under any circumstances! I think there are other parts that won't work as well, but those are the obvious ones for now. I suspect that Immersive HUD (included in the oHUD package) might be at fault, or something not playing well between it and something else.
Posted 02 March 2014 - 10:46 AM
Posted 02 March 2014 - 11:00 AM
@Ivanish, don’t worry about reviving an old thread. If this is the best fit for your question instead of a new thread, then so be it. It is better to have the information in one place than scattered all over.
Remember that files in the overwrite folder will always win any conflict. If you want to use a texture replacer and there are textures files in mods in the overwrite folder then the overwrite folder will win. This may make some things look odd.
Keeping the overwrite folder clean is recommended, but there is also the possibility of FOMM having problems if these files are moved to a mod the next time it is run. This is sort of a catch-22 situation and there is not a simple answer for it. I rend to keep the files in the overwrite folder in NV until I am satisfied I will not need to I will not need to update the FOMM files.
I am reviving an old FNV load order for a new FNV game and will install your choice of mods. Just some notes from my previous install:
CASM can be installed in MO, there is not anything in the mod that requires the FOMM installer. Just double click the installer and deselect the FOMOD folder and text file.
I downloaded both Shiloh DS - Colored Map and Icons and Shiloh DS - Clean Pipboy Screen mods and took a look at them. Both have a nice install interface and options selections and you can install Shiloh DS - Colored Map and Icons in MO if you use some caution.
For Shiloh DS - Colored Map and Icons will install with either the internal or external FOMOD installer, but I got two folders when it finished. One had the game files in it and the other one was empty. I just deleted the empty folder. Looking through the archive I did not see any xml files so this can be installed by MO if needed.
For Shiloh DS - Clean Pipboy Screen with either the internal or external FOMOD installer I got two Folders, but it is best to install in FOMM as it has a menu.xml file in it.
For all the other mods you listed, I use those and installed them in FOMM.
In the past I haven’t had any problems like you mention, give me a few days to get my load order in check. I have decided to give the beta version of BOSS a go on this setup and will need time to work through any issues.
Posted 02 March 2014 - 01:46 PM
I should mention that the idea of using FOMM and keeping the files in the Overwrite was taken from a guide post in the old STEP forums. I can't find the post now, but it was about installing mods that needed to "see" each other, most of those being HUD/UI mods. Not all of the mods I mentioned in my initial post have a menu.xml file, some of them I put in my somewhat experimental Overwrite-mod because they have to do with my HUD, UI or because they caused issues (possibly from bad scripts on the authors behalf) when I installed them in MO.
Most of the mods I use are either the common texture packs, the HUD/UI mods mentioned, Nevada Skies or the FOOK-Project Nevada Convergence thingy. The only issues I have seem to be with the HUD and how most of it don't want to show itself! Shy bastards!
I have used Mod Organizer extensively with Skyrim and gotten totally spoiled with how easy and smooth it was, so I'm not totally new with MO.
Thanks for the answers guys, looking forward to your experiences with your new load order, Thane.
Edited by Ivanish, 02 March 2014 - 01:55 PM.
Posted 02 March 2014 - 01:59 PM
You can't install the HUD stuff with MO. You have to use NMM and then import the stuff with the NMM import feature in MO, under the puzzle piece icon. Also, you have to manually move the MTUI compatible files for PN. Install PN, then go into the PN archive and go into the optional folder and then extract the contents of MTUI into the Data folder. Then continue installing the HUD mods.
Edit: You also can't have any other mods install when you start since the NMM import for MO doesn't work 100% yet.
Posted 05 March 2014 - 07:15 AM
Ok, time for an update. Using FOMM or NMM has no impact what so ever on my issues. FOMM might be old, but some of the HUD and UI mods most of us use are 3 or 4 years old now.
Load order seem to have a very minimal, I dare say negligible, effect on the previously mentioned problems. What will have immediate and critical impact is the order of which I overwrite/install/activate (call it what you will) the mods I use. My missing compass mentioned previously seem to be quite common with Project Nevada, DARN UI and oHUD (and it's previous three parts) which is obvious by simply making a Google search for e.g "Fallout New Vegas missing compass" or similar. Some users have stated that disabling and enabling the compass in the DUINVSettings.xml have solved their issues. It did not fix mine though.
What I did was desperately throwing the files from the DarnUI folder in the Project Nevada optional-folder, overwriting the files created in the whole Unified HUD process. This made my compass come back, but in turn made it impossible for me to use Adjustable HUD to move the objects on my HUD. Depending on what mod(s) overwrites what other mod(s) I can use different parts of the settings in the MCM and I will get different aspects of the HUD elements I want to show to actually be shown. Unified HUD seem to be a rather glorified mod if you ask me, and I'd rather have some help from you guys in tracking down which order I should actually install the mods. I'm even willing to learn a bit about editing the xml-files first hand, since it seems conflicts will be present, no matter what.
The order I got so far from reading up on the mods on either their Nexus page or their readmes are:
- Project Nevada (with the DarnUI files)
- Project Nevada - Extra Options
- MCM (Is this really the right spot for this? oHUD seem to think so, I have no idea)
- Shilos Pipboy mods (hardly a part of any of my issues IMHO)
- Selective Fire (this mod seem impervious to issues so far)
- Flashlight NVSE (activated after oHUD on recommendations from the author of Flashlight)
- The Weapon Mod Menu (this mod, like FlashlightNVSE, tells me it wants to be installed late and tells me if I messed up)
- Unified HUD
This order might be wrong, it might be right or it might be a good start. Simply put there doesn't seem to be enough information to go by to get these mods to work well together.
I can get my compass back, but at the cost of the usability of Adjustable HUD. I still cant get CASM with MCM to work properly, most of the MCM settings are useless. The Primary Needs part of oHUD doesn't work at all, even though the menu do show.
Several MCM-settings and my HUD (or rather the mxl-files I guess) seem affected by poor integration between these mods, this much is obvious.
Thanks again for reading, guys!
Posted 05 March 2014 - 11:02 AM
Posted 07 March 2014 - 01:35 AM
EssArrBee, your post made me try a HUD/UI setup without oHUD. Well, that was the root of all my issues. I'd rather have a working HUD than an Immersible and Adjustable one I guess. As to what part of which mod created this mess, I think you guys above have more knowledge. I am surprised that a few of the most common and popular mods could behave this poorly together though. Then again, some of them are 4 years old...
Thanks again for your time, guys. I'd love to see someone able to get all the mods I mentioned to work together, maybe GSDFan can do it with his new setup?
Posted 09 March 2014 - 04:29 PM
OK, I have what I believe is a working order for the problem presented here, at least on my system. Please note that I have just these mods installed as I had a game launch crash while I was building my new load order. I thought it was a mod problem, but somewhere along the line my fallout.ini got corrupted. I wasted a lot of time hunting it down and in the process I reinstalled the game files and deleted most of the installed mods. I decided to concentrate on these for now. I tested this in game for a few hours and the adjustable hud and other mods appear to be working.
Mods were installed with Fallout Mod Manager - FOMM - Fork and they went into the overwrite folder. In FOMM I used the package manager to install all of the mods, but I did not activate them until all of the were in the list.
In an interesting twist I found an alternate way to do this. Not sure how useful it is, nut it works. Read the spolier.
Posted 09 March 2014 - 07:09 PM
Posted 26 August 2014 - 08:49 PM
Sorry to bring this up again, but couldn't MO run the external installers (like fomod) inside the virtual filesystem (like with other utility programs)? That way the installer could see all the other mods and files that are currently active.
Posted 26 August 2014 - 09:08 PM
The external installer cannot "see" what mods are installed, only the internal installer can do that and it does not handle all the mods yet.
Gopher has switched to MO and is probably looking for a way to install the mods with MO.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users