Jump to content
  • 0
EssArrBee

FNV with OneHUD and UnifiedHUD

Question

I've been trying to put together a list of mods and install instructions for FNV for some time, but there is no real solution to using just one mod manager for FNV because of OneHUD and UnifiedHUD. The install scripts can only be used by NMM and I think FOMM which is a problem because neither of those seem to work through MO. NMM is 64-bit and FOMM crashes the second I try to install either mod.

 

Technically I can install OneHUD without the use of the installer, so that isn't my main problem, but UnifiedHUD is a different type of mod. I had heard about doing separate folder with the mods that UnifiedHUD needs to merge xml files then copying over, but that seems like a terrible thing for a guide to use if it is trying to simplify things for general users. The only thing I can think of is MO supporting 64-bit binaries so MO can start NMM.

 

What do you guys think, is there a better way to address these two mods or do I just wait for a plugin or 64-bit support?

Share this post


Link to post
Share on other sites

Recommended Posts

  • 0

I looked for a solution as well and I didn't find one, apart from using FOMM. There are a couple of other mods that are only available in that format. It's not very bad, just a time consuming, and each time you want to update the mod, you need to go through the whole process again.

 

The easiest (from user point of view) solution would be for Tannin to implement the functionality to install such mods directly from MO. Not sure how realistic that is though. Maybe we can get the answer on our new MO Support forums? :D

Share this post


Link to post
Share on other sites
  • 0

Mods like darnified UI, MCM, Unified Hud needs to see the XXX_menu.xml files installed by other mods to work properly. The fundamental concept of MO (Mod Organizer) is mod isolation. In the current situation with MO when installing those kind of mods with the fomod installer plugin (both internal and externall) the installer plugin can't find those xml files.

 

Solutions so far have been FOMM or NMM, you can set them up in such a way that they point to a fake Fallout New Vegas (FONV) install. You install the mods and then copy the contents back to MO.  This can indeed be cumbersome.

 

At this point there should be a another solution. MO RC8 has a much improved NMM importer. I know of someone who torture tested the importer for 2 days, Tannin used the feedback to improve the importer. After that it was tested again for 1.5 days and Tannin again used that feedback to make improvements. I haven't tested the NMM importer of MO RC8 myself at this point but I'm pretty confident it is pretty stable know.

 

Please try the following. Install the mods with NMM, then use the NMM importer to import them into MO. After that uninstall the mods in NMM. Please report back your findings.

Share this post


Link to post
Share on other sites
  • 0

Most interesting, Wolverine. If that works indeed, it would be much easier than using FOMM!

Share this post


Link to post
Share on other sites
  • 0

I'll play around with it this weekend after I finish up something else I'm doing. If can get it down to a solution where NMM importer works then I could probably write a guide properly with simple enough directions. Thanks for the explanation, wolverine.

Share this post


Link to post
Share on other sites
  • 0

this is just a shot in the dark here, but why not make a single mod package that contains all mods that have the XXX_menu.xml files needed to be seen, so that they will all be visible in a single folder and not isolated from one another, and then install the mods that need to see said files into the same folder. nothing will be isolated from one another.

 

I say this is a shot in the dark as I do not play fallout series currently and cannot physically experiment with their mods. I am assuming that there will be no serious overwrites or conflicts if the files from all of the aformentioned mods are placed in the same folder while the proper file structure is followed, and that MO would be able to read the file structure.

Share this post


Link to post
Share on other sites
  • 0

That would work if UnifiedHUD's installer could actually be run by MO, but it cannot. I think it is a .js file which would be java and there is not plugin for that.

Share this post


Link to post
Share on other sites
  • 0

so why not just open up the installer file with winrar or 7z and then copy/paste the files into the mod folder you make in MO? it takes a little knowledge of how the file structure is built for the mods, and which plugins you want, but if you can manually extract the necessary files and then place them into the self built mod folder then it should work.

Share this post


Link to post
Share on other sites
  • 0

As wolverine said already the only working way (that I am aware of) is simply creating a fake New Vegas directory placing inside the default_ini, the new vegas.exe, the new vegas launcher.exe and a Data folder containing the new vegas.esm and then change the settings in FOMM to point at that directory. You install in FOMM the hud mods you want or any other mod that cannot be installed with MO and then you just select all the files that will have been created inside that Data folder-except the new vegas.esm- and you add them in a winrar achive with a name of your choice. You then open that rar file in MO just like you install every other zip/rar mod file and voila. That way I have managed to install oneHud, DarnUI, Unified Hud and they all work just fine.

Share this post


Link to post
Share on other sites
  • 0

so "theoretically" my method would work as it works on the same principle as the method described by wolverine. cool.

 

only difference is that my method takes a little manual work instead of having to install and use FOMM to install the mods for me.

Share this post


Link to post
Share on other sites
  • 0

@EssArrBee and @rootsrat. Should you test it and find something which is not working and its related to the NMM importer please update 'bug report' ticket 435.

 

Files with extension .js indicate javascript files. Files with extension .java indicate java files. Javascript and Java are not related to each other, except for the names which can be confusing. MO's in-tool tutorials use Javascript.

 

Please create a feature request for javascript support for the fomod installers or a bug report for the UnifiedHUD's installer mod. Not sure which is most appropriate though.

Share this post


Link to post
Share on other sites
  • 0
As wolverine said already the only working way (that I am aware of) is simply creating a fake New Vegas directory placing inside the default_ini' date=' the new vegas.exe, the new vegas launcher.exe and a Data folder containing the new vegas.esm and then change the settings in FOMM to point at that directory. You install in FOMM the hud mods you want or any other mod that cannot be installed with MO and then you just select all the files that will have been created inside that Data folder-except the new vegas.esm- and you add them in a winrar achive with a name of your choice. You then open that rar file in MO just like you install every other zip/rar mod file and voila. That way I have managed to install oneHud, DarnUI, Unified Hud and they all work just fine.[/quote']

 

You don't have to make a zipfile and then install it manually. MO uses mod isolation and all 'mods' are just a directory in the /mods directory. On startup or after hitting the refresh button in the left pane MO reads that directory and then populates the left pane with mods. Hence instead of zipping 'all the contents' just put it in a directory in the /mods directory. This works fine and I have done this a few times. I only wish that I finally get around to updating the sandbox MO wiki so I can cut down on simplified explanations like this and just point to the correct place.

Share this post


Link to post
Share on other sites
  • 0

For those who want to try the NMM importer for the usage I suggested here is some information.

 

I've just retested the NMM importer for the third time, now with RC8. First impression: The NMM importer as in the last test has problems with files which are overwritten (when installed by NMM) and they are not copied (at least not all) when imported into MO. Not sure if that matters for xhud/MCM mods for Fallout 3 (FO3) and FallOut New Vegas (FONV). At this point I've only roughly checked a few things, amongst which are 'overwritten files'. A full interpretation of the import and a test report will likely take a day.

Share this post


Link to post
Share on other sites
  • 0

I'll keep this in mind later on when I test it out. I started doing something else this morning and before I knew it, it was already almost 4pm. I think the hud files might overwrite, but they are .xml files that are combined by UnifiedHUD. Maybe I'll take the vanilla ones out and put them in the fake directory and then import them back.

Share this post


Link to post
Share on other sites
  • 0

I checked the importer yesterday and I don't think it worked correctly. I'll need to do some more proper testing, but not sure if I'll find today, had a busy weekend and need to catch up on couple of things at home.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By Mkchief34
      I recently installed the latest Wyre Bash update, 310 Beta 1. I installed it because whenever I would try to save my Bashed Patch esp for Fallout: New Vegas, I would get this particular error message, and the patch itself does not save.
      "< not supported between instances of 'nonetype' and 'int'".
      It would also not register the masters for the patch in the screen section  beside the load order. I have reinstalled Wyre Bash, I have also deleted the previous patch (Which also had the same error), and I don't know what else to do in this case. U have some coding knowledge, but I think it won't help here.
      What should I do? I have attached a screenshot below of the error messsage itself and how no masters show up in the section for them in the GUI.

    • By sheson
      This is a beta of [FNV|FO3|FO4|FO4VR|TES5|SSE|TES5VR|ENDERAL|ENDERALSE]LODGen/Edit with terrain LOD meshes and textures generation.
      This is for experienced mod authors and users that know how to use xEdit, xLODGen or DynDOLOD already.
      Installation and Setup
      Download
      xLODGen beta 93 - based on 4.1.4b
      Unzip into a dedicated folder outside of any Steam, game or mod manager folders or special Windows folders like Program Files.
      Rename xLODGen.exe to [game mode]LODGen.exe (TES5LODGen.exe for example) or start with command line parameter -fnv, -fo3, -fo4, -fo4vr, -tes5, tes5vr, -sse, -enderal, -enderalse
      Use -o:"c:\OutputPath\" command line parameter to change where files are generated to, default is the game folder.
      Do not generate into any game or any mod manager folders.
      Requirements
      Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019 - Required by LODGen.exe/LODGenx64.exe and Texconv.exe/Texconvx64.exe. Get matching platform x86/x64 depending on which xLODGen.exe (x86) or xLODGenx64.exe (x64) is used.
      RTFM and Share Results
      See the included Skyrim-Occlusion-Readme.txt for a brief explanation of the Skyrim TVDT Occlusion data generation. Read the hints that are shown when the mouse pointer rests on a setting. Ask specific questions or give feedback in the dedicated Skyrim TVDT - Occlusion Data thread.
      See the included Terrain-LOD-Readme.txt for a brief explanation of the settings for terrain LOD generation. Read the hints that are shown when the mouse pointer rests on a setting. Ask specific questions about terrain LOD in this thread for a more in-depth explanation if required and share feedback (with screenshots) about results or problems.
      These tools generate LOD meshes and textures "exactly" like CK, but not like the meshes and textures which are shipping with the games (they are often manually edited).
      However, these tools provide more options and higher resolutions (use the x64 version if there are memory errors because you believe you require 4k or higher) and can be updated to add more useful features and options.
      I did some testing in the different games, but finding the best combinations of options and settings requires lots of testing and are a matter of personal opinion and which game is used, the load order, mods, even different worldspaces probably.
      That means, I am only able to give generic guidelines and hints to send you off to find and test for yourself and share your results. My main interested is that generations works correctly and without problems for now.
      Check out the thread xLODGen Terrain Settings Compare. Also refer to any modding guide which has a list of relevant mods close to your load order.
      The object and tree LOD generation is the same as the current versions of xEdit / xLODGen. Refer to their respective descriptions and explanations.
      Obviously, users of Skryim/Enderal/Skyrim SE/Skyrim VR/EnderalSE continue to use the easier and more comprehensive DynDOLOD for drastically improved object and tree LOD generation and only use xLODGen for terrain LOD (and maybe Occlusion) generation.
      First Time
      Here are suggestion to start without going crazy and that should be quick enough to generate:
      Set quality of meshes for LOD4 to 5 and then +5 for each next level. Or just set levels 8/16/32 to 10.
      Check protect cell borders (yes it fixes the ugly terrain drops at outer cell borders that still exist in Fallout 4).
      Use the max vertices setting only if you want to hard limit max file size.
      In Skyrim Special Edition or Skyrim VR, if you notice terrain briefly flickering when new areas are loading in, set [Display] bEnableLandFade=0 in Skyrim.INI
      Set Optimize Unseen to off for LOD4 for first generation. Start experimenting with a value of 550 with a quality setting of 10 or lower for LOD32 (used for map) and compare coastlines and file size to other settings.
      To quickly generate terrain LOD meshes just for the map, check only terrain LOD Meshes, check the Specific Chunk checkbox and set drop down to 32. Leave SW fields empty for complete map or set SW cell coordinates to same values as a *.btr filename to test a specific area with lots of water, river etc.
      Set texture sizes to 512 for a start. Larger sizes and large world spaces will take a considerable time (like 15 to 30 minutes or more easily). Each higher resolution means quadruple the work.
      Use DXT1 for diffuse and 565 (DXT1 if on Windows 7) for normal maps. If generating for Skyrim Special Edition use BC7. Uncheck mipmaps, raise steepness and Bake normal maps.
      For now, leave the Brightness, Contrast and Gamma at 0 and 1.0 respectively. It seems that only Skyrim CK and Skyrim SE CK are manipulating the intensity of the textures to adjust for the noise.dds and the god awful "improved" snow shader of Skyrim SE (just turn that thing off, really). If textures seem too dark in the game, brighten the noise.dds instead or vice versa. That way you can get perfectly matching LOD textures that look just like the textures in the loaded cells. For Skyrim a good average color of the noise texture seems to be around #C0. See below for a couple noise texture downloads.
      If you want to test larger texture sizes, use the chunk option to limit the number of textures that need to be generated. For example, check [x] Specific chunk, leave the drop down empty and set WS to the lower left cell coordinate of an 32x32 area, like 0, 0. It will then generate all textures up to 31,31. Not all worldspaces have their origin at 0,0 so you will have to check already generated meshes/texture filenames for their lower left coordinates.
      Questions and Feedback
      Obliviously anything related to terrain LOD should be posted in this thread.
      Posts related to Occlusion should be made here.
      Recommended Optionals
      TES5-Terrain-Tamriel.esm (Mega), SSE-Terrain-Tamriel.esm (Mega)
      TES5-Terrain-Tamriel-Extend.esm (Mega), SSE-Terrain-Tamriel-Extend.esm (Mega) - These extend the sea of ghost further to the north (see screenshots)
      SSE-Terrain-Tamriel-Full-Extend.esm (Mega) - Entire map from -96,-96 to 95,96 with northern ocean extension. Useful for mod authors.
      Put in game data folder obviously. Adds back terrain for Skyrim (Tamriel worldspace) at the outer edges so there is no missing terrain meshes/textures when generating terrain LOD for Skyrim.
      Load as early with lowest priority as possible, so that any other plugins overwriting or adding land records or cells with the same coordinates take precedence.
      Only required to be loaded when generating terrain LOD. No harm done when loaded in-game but typically the player can not get close to these areas. There are no effects outside the far away added cells.
      Noise
      Single color flat noise, Adjusted vanilla noise, HD Terrain Noise Texture SE
      Examples for Skyrim. Install to game folder like any other texture mod. The noise texture is applied in-game on top of terrain LOD textures, so no effect for LOD generation.
      Only the red channel is used in case the textures is not a grey channel format. MipMaps are ignored. The textures is tiled 3x3 per LOD quad, e.g. for LOD level 4, the noise texture is repeated 3 times to cover 4 cells, for LOD level 8, the noise texture is repeated 3 times to cover 8 cells and so on.
      Test-Terrain-Tamriel.7z
      For testing terrain LOD distances. Plain color terrain LOD textures for Tamriel with coordinates for every LOD quad. Green for LOD 4, yellow for LOD8, blue for LOD 16 and red for LOD 32.
    • By Majorman
      Discussion topic:
      iscontroller by onvil
      Wiki Link
      Patches all animations to work with custom meshes.
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.