Difficulty Getting UI/HUD Mods to Work Together

[VintageRawr]

So I'm trying to run a few UI/HUD editing mods together, and because not all of them are covered under Unified HUD, they aren't cooperating.

 

Mods Used:

User Interface Organizer

NVSE

Mod Configuration Menu

JIP LN NVSE Plugin

One HUD

Project Nevada/DLC/Extra Options

Solid Project (Companion Wheel and Quick Equip Wheel)

Weapons Name Display

The Weapon Mod Menu

 

The HUDs from Project Nevada and Solid Project are working as intended. The adjustable and immersive HUDs from one HUD, as well as the weapons name display, are not. I can't even interact with them in MCM. Most of the check marks do nothing when I click on them, and the adjustable parts do nothing when I try to move them around. I'm flexible if some of them have to be removed because they absolutely won't work together, I'm just frustrated because I'm not sure where the problem is. I've also tried to make a patch in FNVedit and none of them are interested in it.

[JustChill]

I encountered that issue either from time to time, but mostly oMODs parts don't want to work as intended.

Yet, it helped restarting the game and taking care of my load order.

 

I use a combo of this:

- oHUD

- Radar Mod

- FPS Weapon Wheel

- HUD Extended

- JIP Companions Command and Control

- JIP Realistic Weapon Overheating

- JIP Selective Fire

- Stimpak Counter (even though that one is redundant as of FPS Weapon Wheel).

 

I had no problem running these together with UIO.

However, I've yet not heard from "Solid Project". Thanks for pointing that one out, looks gorgeous.

 

 

 

I only can recommend trying to reload the save or even completely reinstalling.

For myself, I also couldn't figure the exact issue of when this happens. But as I said it's mostly happening with adjustable HUD in my case.

[dubiousintent]

Please see the wiki "HUD-UI-Menu issues" article.

All the HUD-UI elements of those mods use XML scripts. Usually they add a line to an existing vanilla script to include their script as part of some particular menu (forgot which off the top of my head but detailed in that article). They use MCM to provide "in-game customization" of their script parameters. If a particular mod's configuration isn't working, it's usually because of errors implementing the MCM. But nothing has changed in the MCM interface that I am aware of. (I track it.)

UIO dynamically stitches together the various modifications such mods make to the UI-HUD when the game loads. It is important to "re-install" the specific mods indicated in that article if you change the install order of other UI-HUD mods at any time so UIO picks up the changes.

Re: OP's list, I have been using all of those except:

* Solid Project (Companion Wheel and Quick Equip Wheel)

* Weapons Name Display

without problems from day one after I wrote the above article. You could try installing the separate, older component HUD plugins (such as aHUD) instead of the oHUD plugin, but I doubt that would make much difference.

 

I would suspect a potential conflict between "Solid Project" and "Project Nevada", and that both make changes to similar areas of the UI-HUD.

 

The "XML Schema" is implemented in the game engine. As such it is unlikely to be affected by any of Windows system updates. A conflict between XML script files is more likely. Carefully check which are in each package and examine in any plaintext editor.

 

-Dubious-