No HUD mods seem to work

[NoobNoob56]

Hello all! Thanks for the help in advance,

 

Trying to Jump back into FO4 (with a 5120x1440 display no less!), but hitting a weird issue when trying to use HUD mods of any kind.

 

to start, I'm using the most recent patched version of FO4 on Steam, Up-to-date Vortex and mods in question. F4SE installed.

 

Trying to use / problems

Full Dialogue interface / Dialogue works, but custom (Non-arrow based) menus don't work

Truby9 - Ultrawide interface acts like its not even installed

Def_UI - acting like its not even installed.

 

However, I have a ton of other mods installed that work fine, but they dont modify the HUD or and user interface.

 

I've double checked that archive invalidation by way of the .ini files (Custom and otherwise) are set up correctly with

[Archive]

bInvalidateOlderFiles=1

sResourceDataDirsFinal=

But still having no luck whatsoever. This appears to have happened after the most recent update.

Any ideas?

EDIT: HadToRegister - Thanks for reminding me. F4SE is installed in game as well

Edited December 28, 2019 by NoobNoob56

[HadToRegister]

I believe HUD mods require the F4SE script extender.

I could be wrong

[NoobNoob56]

Ah! i should have mentioned that I have F4SE installed as well, but still no dice.

Edited December 28, 2019 by NoobNoob56

[HadToRegister]

Ah! i should have mentioned that I have F4SE installed as well, but still no dice

 

You mentioned that that happened AFTER the recent update.

 

I believe, the recent update changed a few files in the Interface SWFs as well as an ESM or two, which might be the problem.

I know that people definitely weren't happy with the last update due to so many major files being changed

[StormWolf01]

Agreed, on all points.

Backing HTR up on this. If this is happening after the last update, and your other mods are working ok, there's most likely an incompatibility with the update.

 

However, it may also be something to do with your resolution settings, as these are all HUD related issues. However, I apologize, diagnosing resolution problems really is NOT my area of knowledge :(

 

Another thing to make sure of is that the mods are installed correctly. I would recommend trying to install the mods manually to make sure all their files are located in the proper folders.

This is going to have a side effect, too. Because if, while you are manually copying those files over, windows asks you if you want to over-write or replace any .swf files, there's a problem.

.swf files are compressed flash files. Two of them by the same name, aren't compatible with each in the data folder. One can't over-ride another. They have to be patched together with a swf editor so that a singular file contains the information for both. Or in this case, possibly all 3.

I REALLY apologize, the mods pages are very seriously lagging for me right now. I did manage to check Full Dialog interface, and it's Full of .swf files. I know that Def_UI depends on them as well. I'd recommend checking to see if there are any compatibility patches for some of the problem mods.

[NoobNoob56]

Thank you, to both of you. (ALL of the mod pages are lagging, its not just you)

 

I double checked, all of the relevant mod files appear to be where they should be, with no results.

I suppose that this could be related to the major changes, and I'll just have to wait for potential updated.

 

Thanks a bunch!

[StormWolf01]

Heya NoobNoob. Ugh. Well, that at least makes it so that we can check off an improper install off the list of potential causes.

And if you didn't get any replace files notifications, we can probly cross swf incompatibility 'tween the mods off the list too.

 

You might try going into your game settings and setting the game to run at a more standardized resolution, and see if that fixes it. I do know that some of these swf files have specific settings for where the items have to appear on screen. So with the huge resolution that you have (serious congrats on that! I'm very jealous! ) the swf files may not be able to place the screen items correctly.

If that doesn't cure it, you can always reset the game res setting back again :wink:

 

There's one other option that I can think of, which is manually updating the file headers for the mods to match the new game version. This however, will NOT fix the problem that HTR was talking about earlier, if the vanilla files are the cause of this.

But it will mean that you will have to download and install Xedit. https://www.nexusmods.com/fallout4/mods/2737/ or open the mods in the CK.

I don't use the CK, so I can only tell you how to do it in Xedit.

 

Before doing this, make backup copies of the esp/esm/esl files that you are going to edit, just in case!!

 

After installing Xedit (also I apologize, I almost always typo this as "exit". So I'll apologize in advance if I do, and miss it!)

it will bring up a list of ALL your installed mods. Press the CTRL key and tap the A key on your keyboard to highlight the entire list. Uncheck ONE mod in the list, and since they are all highlighted it will uncheck all of them. Now, single click one of the mods in the list, to undo the highlight all. Now, put check marks next to the mods that we need to update. Then click Okay, or Load (can't remember what the button says, atm.)

That will take a minute or two.

Once it loads all the files for the mods, you will see them listed in the left hand panel. They will have a + sign beside their name. Click on the + to expand the list for that mod. You will then see a file that says HEADER. Click on that, and it will open in the right hand side panel.

You're going to want to look for the version number. If the mod hasn't been updated, it will most likely read something close to

0.950000

You will want to right click that version number, choose edit, and type in

1.000000

I recommend using copy and paste. Especially since you will be doing this at least 3 times).

Once you have that mod edited, you will have to do the same thing with the next mod. Rinse and repeat until all three have been updated.

 

Also, a big popup is going to spring up, asking if you're sure that you want to make changes to the file. Don't freak out, that's just Xedit doing a double check, it's perfectly normal.

 

When you're finished updating the headers, press and hold your CTRL key, and tap the S key. That will have xedit save the changes to the files.

 

The reason why I'm recommending this, is because the new update to the game, updated the way that it reads mod headers. In Some cases, if that header version doesn't match what the game is looking for, it will completely SKIP over that mod, as if it doesn't exist.

Edited December 29, 2019 by StormWolf01

[HadToRegister]

One last question.
You use Vortex. did you remember to DEPLOY the mods after INSTALLING them?

[dark47]

@StormWolf - will this illiminante the "unrecognized version" message you get from Wrye Bash? How about Fallout4.esm. Wil making this change to this file mess anything up?

 

There's also some kind of patch you can make with Hud Framework when you use multiple files that edit the hud. I'm trying to figure that out now because I want to use "Full Dialog Interface " with "Transfer Settlements" but the widgit from TS isn't showing up. I thinik there's a little tutorial on the "Transfer Settlements" mod page, but I'm having a little trouble with that.

 

Sorry, the tutorial is on the Hud Framework page.

[StormWolf01]

Heya Dark47! I am afraid that I haven't used WryeBash, So I'm afraid that I'm not familiar with the error message that you're talking about.

Basically, the fix that I posted, is to make the new version .163 read the mod headers correctly for older mods, instead of (in some cases) just outright skipping them.

 

I guess, if a person was to make backups of their files, and then give it a try to see if it works. Or if anybody can give me a link to an official repository for older versions of wryebash, I'd give it a shot.