FCO - UIO Extension not detected

[ethox]

Hi there,

I recently got back into modding and I've been having no issues until installing FCO (Fallout Character Overhaul).

My issue is that after creating my character, an error shows up saying that the FCO Eyebrow UI extension has not been detected by UIO and that UIO either isn't installed correctly or with the newest version.

The thing is that UIO should be the latest version and seems to be installed correctly.

I attempted to look into this myself and tried editing the the FCOEyebrows text file in the UIO folder, it didn't appear correct to me so I have amended it according to the UIO description.

The File now reads as such;

FCO\FCOEyebrows.xml::tutorialmenu

true

#FCO\StyleSelect.xml::tutorialmenu

true

If this is still wrong and/or there is another problem/solution then I would greatly appreciate the help as I haven't been able to find any support for this issue.

I am open to any suggestions at this point.

Thanks guys :happy:

[dubiousintent]

As you are dealing with XML files, I suspect the reason you are getting the UIO error is a result of your "install order". Not having your "load order", this is only a surmise that you have other mods that affect XML files installed. Please see the wiki "HUD-UI-Menu issues" article.

 

-Dubious-

[ethox]

As you are dealing with XML files, I suspect the reason you are getting the UIO error is a result of your "install order". Not having your "load order", this is only a surmise that you have other mods that affect XML files installed. Please see the wiki "HUD-UI-Menu issues" article.

 

-Dubious-

 

Fairly sure I actually used this guide when installing the UI mods I have installed.

This is my current load order;

GameMode=FalloutNV

FalloutNV.esm=1

DeadMoney.esm=1

HonestHearts.esm=1

OldWorldBlues.esm=1

LonesomeRoad.esm=1

TribalPack.esm=1

MercenaryPack.esm=1

ClassicPack.esm=1

CaravanPack.esm=1

GunRunnersArsenal.esm=1

Project Nevada - Core.esm=1

Project Nevada - Cyberware.esp=1

Project Nevada - Equipment.esm=1

Project Nevada - Rebalance.esp=1

Project Nevada - Extra Options.esm=1

YUP - Base Game + All DLC.esm=1

Advanced Recon Tech.esm=1

Detect Traps.esm=1

PipboyRemover.esm=1

SomeguySeries.esm=1

NVWillow.esp=1

More Perks.esm=1

More Perks for Companions.esm=1

More Perks for Dead Money.esm=1

More Perks for Honest Hearts.esm=1

More Perks for Old World Blues.esm=1

More Traits.esm=1

Interior Lighting Overhaul - Core.esm=1

Interior Lighting Overhaul - L38PS.esm=1

FCOMaster.esm=1

NevadaSkies.esm=1

The Mod Configuration Menu.esp=1

Project Nevada - Cyberware Additions.esp=1

Project Nevada - Rebalance Complete.esp=1

Project Nevada - All DLC.esp=1

Project Nevada - Dead Money.esp=0

Project Nevada - Honest Hearts.esp=0

Project Nevada - Old World Blues.esp=0

Project Nevada - Lonesome Road.esp=0

Project Nevada - Gun Runners' Arsenal.esp=0

Delay DLC - DM + HH + OWB + LR + GRA.esp=1

YUP - NPC Fixes (Base Game + All DLC).esp=1

EVE FNV - ALL DLC.esp=1

Project Nevada - EVE All DLC.esp=1

FOVSlider.esp=1

christinecos.esp=1

FlashlightNVSE.esp=1

Light My Flare.esp=1

The Weapon Mod Menu.esp=1

Advanced Recon Tech.esp=1

Advanced Recon Gear.esp=1

Advanced Recon Gear - Project Nevada.esp=1

Advanced Recon Armor.esp=1

Advanced Recon Armor-Predator Mode.esp=1

Advanced Recon Riot Gear Helmet.esp=1

Advanced Recon Desert Ranger Helmet.esp=1

Detect Traps - Traponator 4000.esp=1

Detect Traps - Perk.esp=1

Detect Traps - DLC.esp=1

Advanced Recon Tech - Detect Traps.esp=1

GRA-WRP-Patch-Two_Unofficial.esp=1

pipboy2500_edisleado.esp=1

Roberts_NewVegas.esp=1

dD - Enhanced Blood Main NV.esp=1

FCO - PathFixing Vanilla.esp=1

FCO + YUP.esp=1

Russell.esp=1

NewVegasBounties.esp=1

NewVegasBountiesII.esp=1

NewVegasBountiesIII.esp=0

NewVegasKiller.esp=1

TheInheritance.esp=1

TheBetterAngels.esp=0

FCO - GlowingOne.esp=1

FCO - Roberts Patch.esp=1

FCO - OHSB NPC Edits.esp=1

FCO - Sweat.esp=1

FCO - Russell.esp=1

FCO - Willow.esp=1

FCO - Willow (Cazy).esp=0

FCO - NPC Changes.esp=1

FCO - The Last Few Edits + DLC.esp=1

FCO - New Vegas Bounties.esp=1

FCO - New Vegas Bounties II.esp=1

FCO - New Vegas Bounties III.esp=0

FCO - NewVegasKiller.esp=1

FCO - TheInheritance.esp=1

FCO - The Better Angels.esp=0

1nivVSLArmors.esp=1

1nivPNSLPatch.esp=1

1nivVSLArmors Cheat.esp=1

WeaponModsExpanded.esp=1

WMX-DLCMerged.esp=1

WMX-POPMerged.esp=1

WMX-EVE-AllDLCMerged.esp=1

WMX-ArenovalisTextures.esp=1

Project Nevada - WMX.esp=1

More Perks Update.esp=1

More Perks for Companions Update.esp=1

More Perks for Dead Money Update.esp=1

More Perks for Honest Hearts Update.esp=1

More Perks for Old World Blues Update.esp=1

More Traits Update.esp=1

MorePerksFixed.esp=1

UnlimitedTraits.esp=1

FCO - More Perks.esp=1

Tutorial Killer.esp=1

MoreBeardAndMoustacheStyles.esp=1

theHeroNV_1.1.esp=1

ME3 - MirandaRace.esp=1

Deus Ex HR - Adam Jensen Race by Tesvixen.esp=1

NevadaSkies - TTW Edition.esp=0

NevadaSkies - Basic Edition.esp=0

Interior Lighting Overhaul - Ultimate Edition.esp=1

ILO - GS Shack.esp=1

ILO - PipBoy Light.esp=1

ILO - New Vegas Bounties.esp=1

ILO - New Vegas Bounties II.esp=1

ILO - NVWillow.esp=1

ILO - Nevada Skies Patch.esp=1

ILO - YUP Patch.esp=1

NevadaSkies - Darker Nights.esp=1

NevadaSkies - Ultimate DLC Edition.esp=1

If you could try and tell me a proper order for installing FCO alongside these other Ui mods I would appreciate it.

[dubiousintent]

There are some problems with that LO. "GunRunnersArsenal" should come before the "Pre-order packs". The rest is suspiciously alphabetical. Run LOOT against it and see what changes it makes AFTER you go through the points listed below. If you believe LOOT is wrong, make your adjustment to the LO and then run it again. There are number of minor positional adjustments you can make without any problem. But if LOOT insists some plugin has to come before another, then it has a "master/dependency" relationship reason (perhaps only implicitly) for doing so. I don't argue unless I know exactly what is going on internally in all the plugins involved.

 

Please see the 'Third Rule: The Rule of One', 'Essentials for Getting Started', and 'Vanilla "Load Order"' entries in the 'First Timer Advice' section of the wiki "FNV General Mod Use Advice" article.

All of the following may not apply to your specific situation, but are worth repeating anyway.

* Be aware that one error may mask a number of other errors, which will not appear until those masking them have been resolved. Building a stable game consists of resolving each problem individually until none remain, and then realizing that every change you make thereafter (including updates to mods already installed) run the risk of introducing new problems. Be prepared to revert to a previous save if you do so.

* Did you install Steam to it's default location? If so, please see the wiki "Installing Games on Windows Vista+" article for why the original default Steam behavior of installing games to the "C:\Program Files" folder tree was bad (they learned better, and don't do that any more); and why "disabling UAC and running as Administrator" is NOT sufficient, with instructions how to move it. This is the single most important thing you can do to fix and protect yourself against problems in the future. As much of a PITA as that is, it's never going to be any easier than now. Please see the 'Restoring to "Vanilla"' section of the wiki "FNV General Mod Use Advice" article as well.

* Are you running Win10? Did you get the "Fall Creator's Update" (FCU aka "RedStone 3")? Do you have "New Vegas Stutter Remover" (NVSR) installed? If all three are "true", then please see the 'Issue: Recent (post-Win10 FCU) CTDs after 10-20 minutes of play' (and other "heap size") entries in the 'Solutions to Performance problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

The FCU update was released in mid-November 2017, so a "brand new" system probably did not come with it installed. However, the default configuration is usually to have OS updates automatically installed. (Those usually start being distributed on the second Tuesday of each month, but may take a week or more to get to everyone.) See the MS "Get the Windows 10 Fall Creators Update" article for how to check your version release and manually pull down the update if necessary. It is important to keep your OS always "up to date" to prevent malware infections.

* Are you using the 4GB Patcher? If not, please see the 'Maximizing use of memory' section of the wiki "FNV General Mod Use Advice" article.

* If you are using the full 4GB of memory, most likely your CTD problem (now or in the future) is the default "heap size" is too small. Please see the 'Solutions to "Crash To Desktop" (CTD) problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

* Move any "inactive" plugins out of the game "Data" folder. They count against the "plugin cap" because they get loaded by the game engine if found, and can cause "Missing Master" problems. Please see the wiki "Missing Masters" article if you get that error message.

* "Compatibility patches" to make one mod work with another need to be placed after (as in "physically lower, higher numbered") in the "load order" than both of the plugins they are designed to make compatible. ESMs should always be placed at the top (lowest numbered) positions in the "load order", followed by the related ESPs though they can be separated from their ESMs by other plugins. "LOOT" does a good job of determining those basic orders. Getting the "load order" incorrect will cause "Missing Master" errors as well.

* Don't install compatibility patches for mods you do not have installed/active (e.g. get rid of any "TTW" patches if you aren't running TTW).

* Don't install every optional file for a mod. Read the install instructions carefully. Optional files need to be selected on a "case by case" basis. For example: with any mod you usually only need one ESP (and possibly one ESM) "base" file depending upon whether you have all the DLCs active or not. Only if you don't have them all active do you need to install any specific DLC versions if there is an "Ultimate Edition/All/Merged DLC" version.

* Do not use an "Auto-purge" mod for game play. (That was old advice from before we knew better.) They are designed for debugging by mod creator's only, according to the author of the JIP extensions to NVSE. See the 'Issue: CTD without warning, "Out of Memory error", or stops responding after the Main Menu', "Cause-2", "Solution-3" entry in the wiki "Fallout NV Mod Conflict Troubleshooting" guide for the game settings that do the same job.

* Please see the paragraph about "auto-saves" under the 'Essentials for Getting Started' section of the wiki "FNV General Mod Use Advice" article. If you have been using the built-in "auto-save" feature and you get the endless "roulette wheel" when loading a save game, then your current save game file is corrupted and you will have to either go back to a save before the corruption occurred (hard to tell) or start over.

* You really need to use a "Merge Patch File" with that collection of mods. Please see the 'Third Rule: The Rule of One' and 'Merge Patch File' sections of the wiki "FNV General Mod Use Advice" article.

Please see the several 'Issue: Body Replacer - FCO ...' entires under the 'Solutions to Graphics problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

 

 

However, none of these are specific to any XML issues. Plugins which MAY contribute to the problem that I can see are:

* PipboyRemover.esm

* The Mod Configuration Menu.esp

* The various "Project Nevada" plugins all affect XML files

* FlashlightNVSE.esp

* The Weapon Mod Menu.esp

* pipboy2500_edisleado.esp

 

All except the two Pipboy mods are covered in the "HUD-UI-Menu" article. I would install both of those mods before any of the others in that list as you are swapping the Pipboy interface much like a "base UI".

-Dubious-

[ethox]

Wow that's actually a lot of help for me, I'll definitely try this when I reinstall my mods again to see if this rectifies the issue.

I didn't know that inactive plugins counted against the cap either so that will be useful in future also.

I am not really having any other issues aside from the UI extension at the moment but I don't have an actual save I've been playing either, so I'm not worried about saves and I can take as long as needed to get the game stable before playing.

Thanks again :happy:

[VaporWatch]

@ethox,

 

One issue I had on my most recent load in was having the loose files for UIO in the wrong load order. Are you using Mod Organizer? If not, I strongly recommend it as it gives you far more control over what mods take priority, and this includes the loose files and BSAs. You need to make sure the UIO loads after any other mods that affect anything to do with the UI, HUD, MCM, etc (since UIO doesn't have a plugin, I'm talking about the assets of the mod loading after everything). With Mod Organizer, it's super easy to manipulate the loading order of loose files by simply moving them up or down, just like anything else with plugins. With Nexus Mod Manager, you need to make sure UIO is the very last mod installed that affects the UI, HUD, MCM, etc.

 

Dunno if that will help you, but I was having the same issue and my problem was the loose files for UIO was loading in advance of the FCO files. Once I moved it below FCO, all was well.

 

Good luck!

[ethox]

@ethox,

 

One issue I had on my most recent load in was having the loose files for UIO in the wrong load order. Are you using Mod Organizer? If not, I strongly recommend it as it gives you far more control over what mods take priority, and this includes the loose files and BSAs. You need to make sure the UIO loads after any other mods that affect anything to do with the UI, HUD, MCM, etc (since UIO doesn't have a plugin, I'm talking about the assets of the mod loading after everything). With Mod Organizer, it's super easy to manipulate the loading order of loose files by simply moving them up or down, just like anything else with plugins. With Nexus Mod Manager, you need to make sure UIO is the very last mod installed that affects the UI, HUD, MCM, etc.

 

Dunno if that will help you, but I was having the same issue and my problem was the loose files for UIO was loading in advance of the FCO files. Once I moved it below FCO, all was well.

 

Good luck!

 

I'll try this before reinstaling if you think it might work, it's worth a try anyway I guess.

Already have Mod Organiser but haven't really used it so now is a good chance.

Thanks man

Edited February 22, 2018 by ethox