Darnified UI Problem

[Ciliate]

Long story short, the changes to the ini files are not taking affect. I have succesfully installed this mod before but for some reason, while I can get the mod to display as installed, the text is still to large. Yet I have made the font changes to all three of the ini files. Furthermore, if I uninstall D UI but leave the ini files be, the text in game is normal, again, like no changes have be made.
I am at a complete loss, I have removed all other mods, reinstalled, reavaluated, started a new save etc. The game just seems to refuse to read the changes I made to the ini files.
Does anyone else have a solution, otherwise I can not use this mod?

[talgaby]

Check all three INI files for write protection, plus the security tab in their properties to see if your user account (or the Everyone account) has full permission to write them. Sometimes the INI files get locked by the launcher permanently and you have to make them writeable manually.

[Ciliate]

Ok, I have made sure "read only" is unchecked for all three and double checked thier permissions, which are all set to allow everything from everyone. Still no changes but thank you for the advice.

[talgaby]

Strange. Editing the [Fonts] tab in Fallout_default.ini should make the change permanent…
Do you have any other mods for the UI? For example aHUD/oHUD needs to be installed after it.

[Ladez]

Is your archive invalidation enabled?

[Ciliate]

I am using oHUD but of course I have removed all mods and done a fresh install. Ladez, I am not famililer with that term, and google wasn't too helpful. Could you explain what you mean?

[Ladez]

By default the game loads assets (models, textures, sounds, menus) from the .bsa archives, so if you have any loose files replacing those in the archives, you will need to tell the game to load the loose files instead. Your mod manager should provide an option to toggle this on and off (archive invalidation). Make sure it's on, and retoggle it everytime you install a mod with loose files.

When you're using several interface mods that edit some of the same XML menu files, whatever mod you install last will override changes from the previous ones. The files must be merged together to preserve all their features, and luckily a mod has been put together to automate that process. It's called Unified HUD Project (uHUD.)

Follow this installation order:
- DarNified UI
- Other interface mods
- oHUD
- uHUD

Answer yes to all overrides. Whenever you add or remove an interface mod, deactivate uHUD and reactivate it.

Hello, Google search user! If you're reading this post in 2016, things have changed somewhat. First off, we don't use Unified HUD Project anymore, we use UIO. Secondly, do not overwrite any of Darnified's files when installing mods after it unless you're installing a patch for it.

[ρоѕιтяои_]

Did you extract the files on the page to your Fallout data folder and then make the ini changes? http://forums.bethsoft.com/topic/1131897-wipzbeta-darnified-ui-nv/

Downloads:
DUINV Test version 2 - Extract to "FONV\Data\".

If you have my bad but just an idea as I had this problem myself some time ago but can't remember what resolved the issue?

[baddude1337]

You definitely have the files and ESP activated? Only thing I can think off if the INI changes have been made.

[Ciliate]

Guys, I have managed to find the solution! I am using Mod orginizor to mod my game, and turns out to edit ini files I must do it through MO for those changes to take effect. Well I did those changes, and have fixed the problem.
I hope my issue helps others down the line!

[TakeThisL]

Originally posted by Ciliate:

Ok, I have made sure "read only" is unchecked for all three and double checked thier permissions, which are all set to allow everything from everyone. Still no changes but thank you for the advice.

im having the same problem could u pls help me?

[Ciliate]

I no longer play FONV. How you made sure to read through all these comments?

[institutesynth]

I had the EXACT problem. Turns out NMM never installed the fonts or textures, so I had to put them into the directory manually. Hope that helps anyone else.

[Danny.Boon]

If anyone still has an issue this may sound stupid but it literally just happened to me. . . Mine was a super simple fix if you follow the steps given on the forum post exactly you most likely will run into this issue. I took the directions way to literal and just C/P the whole file into my data folder when in reality you only need the contents INSIDE the folder (minus the read me file). Super simple thought nothing of it until I was on my way to work today.

[NaterDaWired]

I also had this issue with the text and some parts of the UI being really big. I had the INI edit for the fonts in all three inis with my MO2 profile, also had Automatic Archive Invalidation active.

I finally figured out why it still was broken, I had tried using BethINI to tweak the inis, but it was just messing things up, so I reverted my ini to the good one I had before.

Turns out BethINI put its changes not only in fallout.ini and falloutprefs.ini, but also in custom.ini and falloutcustom.ini that MO2 has. No wonder my ini edits were not working! I was wondering why the low res ugly LOD textures were still showing up even though I extended those out really far.