Jump to content
  • 0
Sign in to follow this  
Enshara

Mod Organizer not creating a Virtual file System

Question

I was following Essarrbee's guide on installing mods for fallout new vegas and when i reached the part were it told me to start the game, i noticed that none of the mods were working. I then checked on google to see if anyone else had the problem and came accross the post by GSDFan, so I did the get NVSE version thing and got version 4. Then i downloaded free commander, installed it, set it up as a executable in MO and ran it from inside MO navigated to my FNV data directory and did not see any of the ESP's from the installed and activated mods.

 

Any help would be most appreciated

Share this post


Link to post
Share on other sites

13 answers to this question

Recommended Posts

  • 0

Just what exactly are you trying to do? If you were following that guide you would have seen the need, and the instructions, to install NVSE and have it working properly.

 

There is no need to install FreeCommander if all you want to do is mod and play FNV using MO. Just follow the guide and it works.

 

Perhaps a viewing of the video tutorials for MO is in order? Follow the links from the wiki link above to the MO wiki and start there.

 

Modding isn't a hard task, but it does take a methodical mindset. So to with MO. It is very different to other mod managers but once you examine the way it works it is very effective.

Edited by GrantSP

Share this post


Link to post
Share on other sites
  • 0

I installed NVSE and have it working correctly(I think), when I typed into the console "GetNVSEVersion" I got version 4.

 

I did follow the guide and it did not work.

The only reason why I installed FreeCommander is to check why it was not working.

 

I have modded skyrim successfully with MO in the past.

 

What I am trying to do is play FNV with mods, but none of the mods actually run, if I understand the logic behind GSDFans response on the 6th of Jan when he mentioned FreeCommander, then you can use the program to check whether the virtual file system that MO creates is working.

Share this post


Link to post
Share on other sites
  • 0

Modding FNV in MO is the same as modding Skyrim with MO.

 

  1. Download mods
  2. install
  3. activate
  4. sort
  5. play

Instead of the generalised comment "VFS isn't working" perhaps try looking at what specifically isn't, or appearing to not be, working.

Which mod(s) are you expecting to see but aren't? How are you determining they aren't working?

Share this post


Link to post
Share on other sites
  • 0

I first noticed that none of the mods were working when I started up a new game and it did not stay "x mod has loaded" as it did about half a year ago when I installed the mods using FOMM. I then tested it by looking at my mod list and choosing a mod at random (i choose new vegas bounties) and going through the nexus page (and watching videos of others using the mod) and tried to find the start of the mod, In this case it should have been a item on trudy's bar making reference to becoming a bounty hunter, but that item was not there. I then closed down new vegas and reread the entirety of the guide checking just in case I had missed something out, having gone through the guide again and not finding anything that I didn't do I went to google and checked to see if anyone else had this problem and whether it had been sorted out. which is when I discovered the beta version of MO. I downloaded and installed that hoping that it would fix the problem, (it didn't) how ever that put my load order in alphabetical order so I ran LOOT through mod organizer, which is when LOOT told me that the only things that it could detect was the base game, all the DLC and the other things I got from buying the Ultimate edition. So I then hit a metaphorical brick wall. So I searched the forums again come across GSDFans responce and downloaded FreeCommander and checked my NVSE and posted my results from checking FreeCommander through MO

Share this post


Link to post
Share on other sites
  • 0

By 'beta' version you are referring to 1.3.1b? If so uninstall and install 1.2.18. The beta version should only be used to test the functionality of that beta, not as your working environment.

 

I'm a bit concerned by this comment:

I downloaded and installed that hoping that it would fix the problem, (it didn't) how ever that put my load order in alphabetical order so I ran LOOT through mod organizer, which is when LOOT told me that the only things that it could detect was the base game

 

To me this sounds like you have an already modded FNV setup, after which you then installed MO and expected to have it 'see' those installed mods.

 

This is not what MO does. ALL mods MUST be installed via MO and then those mods will be available to the game via MO's VFS.

Any mod that exists in the real, physical Data folder on your computer will need to be removed, that folder should be cleaned and verified by Steam and then all those mods installed using MO.

The reason why MO is showing you only the vanilla plugins is you ini plugin list used will be a default one that has no record of any added data, in the same way as you might have added mods using the FNV Launcher beforehand.

 

I'll remind you again of the video tutorials and wiki for MO that can be found in the 'Wiki' link at the top of the page.

Share this post


Link to post
Share on other sites
  • 0

When I said that I downloaded version 1.3.1b what I meant was that I already had version 1.2.18. I upgraded in order to try and fix the problem.

I did and do not expect MO to see previously installed mods (of which there are none) infact if it did see any mods that were installed previously then I would suspect that my new computer is not new at all.

I did install the mods in MO, I did exactly the same thing that I did when I played skyrim.

Share this post


Link to post
Share on other sites
  • 0

Like I said before, using MO for FNV is exactly the sama as for Skyrim.

 

Make a copy of you 'downloads', 'mods' & 'profiles' folders from under the Main MO install folder and completely remove that installation.

 

Run FNV from its launcher to ensure a clean set of default game ini files are generated.

Install MO again from the original 1.2.18 installer, or archive, and run it for the first time. You should get messages about which game you want to manage and whether you want tutorials etc. if you don't see those your existing ini files are still there.

Now move your 'downloads', 'mods' & 'profiles' folders back into this new install.

Start MO and if it recognises these installed mods they are displayed in the left-hand pane.

Ensure they are active in the left-hand pane, as you do with Skyrim and ensure any plugins are also active in the right-hand pane.

 

If all of this is good any mods shown there will be inside MO's VFS once the game is started. All that this entails is tricking the game engine to look at MO's installed folders, there should be minimal code running once the game is started.

Share this post


Link to post
Share on other sites
  • 0

Ok I have downgraded and all the mods that I installed in 1.3.1b are in 1.2.18 but none of the mods inside MO are inside the game when it is started. The mods are active in the left-hand pane and the plugin are active in the right-hand pane, but when I start up the game and start a new game none of the mods are active inside the game.

Edited by Enshara

Share this post


Link to post
Share on other sites
  • 0

I'm making the assumption you have LOOT and xEdit installed for Skyrim and know how they are installed for that game, install those and see if they can see these mods installed.

Share this post


Link to post
Share on other sites
  • 0

do you mean xEdit or FNVEdit?

 

If you do mean FNVEdit then I have installed FNVEdit and LOOT and neither of them can see the mods that are installed.

Edited by Enshara

Share this post


Link to post
Share on other sites
  • 0

Yeah, xEdit is the generic name for FNVEdit,FO3Edit,TES4Edit & TES5Edit.

 

If what you say is correct then there is something wrong with this specific install of MO.

 

Can you, either in spoiler tags or with a Pastebin link or similar, provide your modorganizer.ini and the actual paths to you installed mods folder?

Somehow the files that are showing in MO as installed aren't being provided to either the game or tools that view that.

 

Also can you provide the contents from the active profile's folder? There should be:

saves
archives.txt
fallout.ini
falloutprefs.ini
initweaks.ini
loadorder.txt
lockedorder.txt
modlist.txt
plugins.txt
 
Perhaps zip them into an archive and post a link.

Share this post


Link to post
Share on other sites
  • 0

what do you mean by actual paths to you installed mods folder, do you mean 

C:\Games\Steam\SteamApps\common\Fallout New Vegas


And now as if by magic its working :s all I did was copy modorganizer.ini and the active profile into a folder and upload it to a filesharing website and somehow mod organizer views that as a fix :s

 

sometimes, i sware i dont understand technology

Edited by Enshara

Share this post


Link to post
Share on other sites
  • 0

By the full path I mean the actual path that takes me to MO's 'mods' folder.

e.g. C:\Program Files (x86)\Steam\SteamApps\common\Fallout New Vegas\Mod Organizer\mods\

 

 

:O_o: I have no idea why that would help, possibly your system was processing those files and they weren't available to MO? I have no idea.

 

At any rate, I would do a general check of your system just to make sure everything is fine. Update any drivers etc. that Windows suggests and run any malware or virus checkers you have, just to be safe.

 

In the future, just remember all the settings that MO uses to generate the game environment are either ini files or folders. All the settings are stored in an easily accessible manner and the only 'magic' is the hook.dll that tricks the executables into believing the files are somewhere else.

 

I hope your gaming experience in the future is stress free. Have fun.

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
Sign in to follow this  

  • Similar Content

    • By z929669
      Step Fallout: New Vegas Guide 1.0.0 released!

      Guide Link | Changelog | Feedback & Bug Reports
      Nexus Link
      Many thanks to @Majorman for working on this guide for the past 6 weeks as our official FNV guide Curator!
    • 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 86 - 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 z929669
      Discussion topic:
      Step FalloutNV Guide (by Majorman)
      Resources: Nexus Mods
      Please submit feedback about the 1.0.0 guide to this topic.
  • 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.