Give Feedback
0 of 0
About this mod
An NVSE-powered plugin that is designed to manage and maintain all UI/HUD extensions added to the game by various mods. Once installed, UIO will ensure UI extensions are always properly installed and, when necessary, properly removed; it will automatically detect, resolve and prevent UI-related issues, and will help keep the game's UI intact.
- Requirements
- Permissions and credits
- Changelogs
User Interface Organizer, or UIO, is an NVSE-powered plugin that is designed to manage and maintain all UI/HUD extensions added to the game by various mods. Once installed, UIO will ensure UI extensions are always properly installed and, when necessary, properly removed; it will automatically detect, resolve and prevent UI-related issues, and will help keep the game's UI intact. You will be able to safely install/remove UI mods, at any time, without having to worry about it breaking other UI mods, or worse - the game.
Additionally, UIO refactors and optimizes several hotspots in the game's UI code and greatly increases menu loading speeds.
UIO enhances XML functionality:
UIO currently supports all UI mods that are known to me and require support (a full list can be found below). Adding support for unlisted/future mods is very simple, can be done by anyone, and does not require updating UIO, or involving me in any way. For instructions see below.
UIO also makes it possible to install any supported UI mod manually (i.e. by a simple files-to-folders extraction), without running any scripted installer (most UI mods use scripted installers in order to modify one or more of the game's UI files. These installers are known to fail on some machines, and may break other mods when uninstalled).
How does UIO work?
UIO operates at game launch, before any UI files are loaded in memory. It detects installed UI mods, makes sure every valid UI extension is properly registered, removes references to missing files and duplicate entries. All this is done without modifying any game files.
How do I use UIO?
Simply download and install it using NMM/FOMM, or manually extract (use 7-Zip) the 7z archive into the game's 'Data' folder. Please note that this is an NVSE plugin, not a standard mod - it doesn't include an ESP/ESM file and will therefore not show in your load-order.
UIO and Mod Organizer (MO)
Due to the way MO works, installing/removing/getting UI mods to work together in harmony, can be very tricky. This is no longer an issue when using UIO alongside MO - UI mods can be treated and handled exactly the same way as any "standard" mods.
Is there a Fallout 3 version?
Here.
Requirements
The New Vegas Script Extender (NVSE), version 5.1b4 minimum, installed and loaded with the game.
Currently supported mods
Advanced Recon Range Finder
Advanced Recon Thermal Nightvision
Arwen NV Realism Tweaks
Callahan Fullbore Autolock - Vera
CINEMATECH
Cyberian Dawn
Directors Chair - Total Visual Control Device
DYNAVISION 3 - Total Visual Enhancement
Flashlight NVSE
FPS Weapon Wheel
Grenade Hotkey
HUD Extended
IMCNNV - Imps More Complex Needs
Jetpack Mod
JIP Companions Command && Control
JIP Fast-Travel Anywhere
JIP Realistic Weapon Overheating
JIP Selective-Fire
Melee Hotkey
Neotropics Weapon Stats Display
nVamp - New Vegas Advanced Mod Project
One HUD - oHUD
Powered Power Armor
Primary Needs HUD
Project Nevada
Project Nevada - Extra Options
Quick Trade
Radar HUD
Radar Mod
Selective Fire (Pelinor)
Stimpak Counter NV
The Medical Injection System
The Mod Configuration Menu
The Weapon Mod Menu
Adding support for a mod
In order to make UIO recognize and support your mod, you need to create a text file containing your mod's details and place it in the appropriate folder:
1. Open the folder ..\data\uio\public\.
2. Create a plain text file (use your mod's name as the file name) and open it.
3. The file's structure should be as follows:
Line #1: Should be composed of the following parts, in successive order and with no spaces:
1. The path to your XML file, relative to ..\Data\Menus\Prefabs\
2. :: (double colon)
3. The target XML, which can be denoted in one of two ways:
a) A name of a valid game menu (ex: HUDMainMenu, ContainerMenu, etc.), or
b) A path to an XML file, prefixed by @ (ex: @globals.xml, @prefabs\text_box.xml, etc.).
4. :: (double colon)
5. The name of the UI component in the XML, to which your file should be injected.
Line #2: This line is used for conditions - when to/when not to install the extension. Complex conditions can be used, but will not be covered here (PM if you need to use conditions). In most cases, just leave it true.
Examples:
pnx\pnxhud.xml::HUDMainMenu::HUDMainMenu
true
pnx\pnxhud.xml::@main\hud_main_menu.xml::HUDMainMenu
true
WMM\WMM.xml::InventoryMenu::GLOW_BRANCH
true
jazzisparis\jip_glob.xml::@globals.xml::Strings
true
(Note: When required, you can include multiple entries in the same file, as long as the line structure is kept)
4. When done, save the file.
You can then include this file in your release (make sure it retains the same folder path as in step 1).
Source Code
Is available from here.
Additionally, UIO refactors and optimizes several hotspots in the game's UI code and greatly increases menu loading speeds.
UIO enhances XML functionality:
UIO currently supports all UI mods that are known to me and require support (a full list can be found below). Adding support for unlisted/future mods is very simple, can be done by anyone, and does not require updating UIO, or involving me in any way. For instructions see below.
UIO also makes it possible to install any supported UI mod manually (i.e. by a simple files-to-folders extraction), without running any scripted installer (most UI mods use scripted installers in order to modify one or more of the game's UI files. These installers are known to fail on some machines, and may break other mods when uninstalled).
How does UIO work?
UIO operates at game launch, before any UI files are loaded in memory. It detects installed UI mods, makes sure every valid UI extension is properly registered, removes references to missing files and duplicate entries. All this is done without modifying any game files.
How do I use UIO?
Simply download and install it using NMM/FOMM, or manually extract (use 7-Zip) the 7z archive into the game's 'Data' folder. Please note that this is an NVSE plugin, not a standard mod - it doesn't include an ESP/ESM file and will therefore not show in your load-order.
UIO and Mod Organizer (MO)
Due to the way MO works, installing/removing/getting UI mods to work together in harmony, can be very tricky. This is no longer an issue when using UIO alongside MO - UI mods can be treated and handled exactly the same way as any "standard" mods.
Is there a Fallout 3 version?
Here.
Requirements
The New Vegas Script Extender (NVSE), version 5.1b4 minimum, installed and loaded with the game.
Currently supported mods
Advanced Recon Range Finder
Advanced Recon Thermal Nightvision
Arwen NV Realism Tweaks
Callahan Fullbore Autolock - Vera
CINEMATECH
Cyberian Dawn
Directors Chair - Total Visual Control Device
DYNAVISION 3 - Total Visual Enhancement
Flashlight NVSE
FPS Weapon Wheel
Grenade Hotkey
HUD Extended
IMCNNV - Imps More Complex Needs
Jetpack Mod
JIP Companions Command && Control
JIP Fast-Travel Anywhere
JIP Realistic Weapon Overheating
JIP Selective-Fire
Melee Hotkey
Neotropics Weapon Stats Display
nVamp - New Vegas Advanced Mod Project
One HUD - oHUD
Powered Power Armor
Primary Needs HUD
Project Nevada
Project Nevada - Extra Options
Quick Trade
Radar HUD
Radar Mod
Selective Fire (Pelinor)
Stimpak Counter NV
The Medical Injection System
The Mod Configuration Menu
The Weapon Mod Menu
Adding support for a mod
In order to make UIO recognize and support your mod, you need to create a text file containing your mod's details and place it in the appropriate folder:
1. Open the folder ..\data\uio\public\.
2. Create a plain text file (use your mod's name as the file name) and open it.
3. The file's structure should be as follows:
Line #1: Should be composed of the following parts, in successive order and with no spaces:
1. The path to your XML file, relative to ..\Data\Menus\Prefabs\
2. :: (double colon)
3. The target XML, which can be denoted in one of two ways:
a) A name of a valid game menu (ex: HUDMainMenu, ContainerMenu, etc.), or
b) A path to an XML file, prefixed by @ (ex: @globals.xml, @prefabs\text_box.xml, etc.).
4. :: (double colon)
5. The name of the UI component in the XML, to which your file should be injected.
Line #2: This line is used for conditions - when to/when not to install the extension. Complex conditions can be used, but will not be covered here (PM if you need to use conditions). In most cases, just leave it true.
Examples:
pnx\pnxhud.xml::HUDMainMenu::HUDMainMenu
true
pnx\pnxhud.xml::@main\hud_main_menu.xml::HUDMainMenu
true
WMM\WMM.xml::InventoryMenu::GLOW_BRANCH
true
jazzisparis\jip_glob.xml::@globals.xml::Strings
true
(Note: When required, you can include multiple entries in the same file, as long as the line structure is kept)
4. When done, save the file.
You can then include this file in your release (make sure it retains the same folder path as in step 1).
Source Code
Is available from here.