Jump to content
  • 0
psycheval

MO FNV Load Order with esp flagged as esm

Question

Hi folks. Not finding any info on this particular subject so here goes.

 

I set up FNV following the Fear and Loathing Guide here on the Wiki. I am running:

MO 1.3.5,

LOOT 0.7.0.7,

FNV Edit 3.1,

Wrye-Flash Standalone 16.9.

Yes, I did add too the F&L Guide but it is minimal and I have not affected anything in the F&L Guide setup to this point. I was about to till I found this.

 

Simple expalantion to my issue is Project Nevada .esps that are flagged as masters are being sorted differently between MO with LOOT setting the load order and what FNVEdit and Wrye-Flash see as the load order. I do mean Right pane mod sorting not Left.

 

I am showing only the Masters in my order as the sorting issue is only happening in the masters not the plugins. Shorter list to eyeball too.

 

The load order as set by LOOT and seen in the right pane of MO:

 

 

FalloutNV.esm
DeadMoney.esm
HonestHearts.esm
OldWorldBlues.esm
LonesomeRoad.esm
GunRunnersArsenal.esm
ClassicPack.esm
MercenaryPack.esm
TribalPack.esm
CaravanPack.esm
YUP - Base Game + All DLC.esm
Sortomatic.esm
NVInteriors_Core.esm
Interior Lighting Overhaul - Core.esm
FreesideOpen.esm
New Vegas Redesigned 3.esm
ELECTRO-CITY - CompletedWorkorders.esm
NVInteriors_ComboEdition.esm
Tales from the Burning Sands.esm
SomeguySeries.esm
Detect Traps.esm
Advanced Recon Tech.esm
Ambient Temperature.esm
JIP Selective-Fire.esm
Inventory Access.esm
oHUD.esm
FINAL Seachlight Airport NCR.esm
Project Nevada - Core.esm
Project Nevada - Equipment.esm
Project Nevada - Rebalance.esp
ELECTRO-CITY - Highways and Byways.esm
domecity.esm
NVStripOpen.esm
The New Bison Steve Hotel.esm
NVInt_ARoomWithAView.esm
Project Nevada - Cyberware.esp
Project Nevada - Extra Options.esm
Interior Lighting Overhaul - L38PS.esm
FCOMaster.esm
Caliber.esm
Weapons.of.the.New.Millenia.esm
More Perks.esm
Afterschool Special.esm
D.E.I.M.O.S..esm
GRARG.esm
NevadaSkies.esm

 

How FNVEdit and Wrye-Flash show the load order:

 

 

FalloutNV.esm
01  DeadMoney.esm
02  HonestHearts.esm
03  OldWorldBlues.esm
04  LonesomeRoad.esm
05  GunRunnersArsenal.esm
06  ClassicPack.esm
07  MercenaryPack.esm
08  TribalPack.esm
09  CaravanPack.esm
0A  YUP - Base Game + All DLC.esm
0B  Sortomatic.esm
0C  NVInteriors_Core.esm
0D  Interior Lighting Overhaul - Core.esm  [Version 6.8]
0E  FreesideOpen.esm
0F  New Vegas Redesigned 3.esm
10  ELECTRO-CITY - CompletedWorkorders.esm
11  NVInteriors_ComboEdition.esm
12  Tales from the Burning Sands.esm  [Version 1.31b]
13  SomeguySeries.esm
14  Detect Traps.esm
15  Advanced Recon Tech.esm
16  Ambient Temperature.esm
17  JIP Selective-Fire.esm
18  Inventory Access.esm
19  FINAL Seachlight Airport NCR.esm
1A  Project Nevada - Core.esm
1B  Project Nevada - Equipment.esm
1C  oHUD.esm
1D  ELECTRO-CITY - Highways and Byways.esm
1E  domecity.esm
1F  NVStripOpen.esm
20  The New Bison Steve Hotel.esm
21  Project Nevada - Extra Options.esm
22  NVInt_ARoomWithAView.esm
23  Interior Lighting Overhaul - L38PS.esm  [Version 1.1]
24  FCOMaster.esm
25  Caliber.esm
26  Weapons.of.the.New.Millenia.esm
27  More Perks.esm
28  Afterschool Special.esm  [Version 2.01]
29  D.E.I.M.O.S..esm  [Version 1.05]
2A  GRARG.esm
2B  NevadaSkies.esm
2C  Project Nevada - Rebalance.esp
2D  Project Nevada - Cyberware.esp

FNVEdit and Wrye-Flash are pushing the esp flagged masters down below all other esm's. This, in my experience, is going to make a merged or bashed patch follow what FNVEdit and Wrye-Flash see as the load order and not what LOOT and MO see as load order. MO is then going to load the order in game as it is set in MO and all the patches are going to have incorrectly sorted masters. Not to mention all patches already associated with PN are already showing masters sorted incorrectly in Wrye. Making changes to an esp's masters order to match your load order in my experience is bad ju-ju. Makes things go nuts.

 

I deleted all the load order and modlist files in the MO profile and resorted all the mods after my initial install. Just in case something had gone wonky the first time through. Same result both times.

 

Hand sorting the mods makes no difference either. FNVEdit and Wrye still stick those master flagged esp's at the bottom.

 

I have only used LOOT to sort in MO also, not the sorter included in MO. I only use Wrye to check how the masters are loaded in relation to an esp's load order, set bash tags, and to make a bashed patch.

 

This is my first setup of MO on FNV. I typically install FO3/FNV mods in the Data directory. I've used MO on Skyrim exclusively for two years so it's not new to me. I got tired of Tamriel and needed some Wasteland.

 

What am I missing? I have a tingle in the back of my noggin' that tells me I've seen something on this before but I cannot seem to revisit that on Google for some reason. I more than likely slept quite a bit since then.

 

Thanks ahead of time, and be gentle if I'm having a stupid attack.

 

Share this post


Link to post
Share on other sites

2 answers to this question

Recommended Posts

  • 0

Although you have posted it in the MO forum, because you are using MO, I don't believe this is strictly a MO issue, or an issue in general.

 

MO, LOOT and Wrye Flash see these files as 'esms', you can tell that in Flash by the colouring applied to them. The 'issue' here is whether there is a reason for xEdit to list them in the editor selection window after esps, and if that will have an impact on any patches?

I have no idea why that is the case and there have been a number of different posts with similar questions regarding ESMified esps in xEdit being placed this way, in none of them do I recall an explicit answer or can I find them quickly now.

 

I will say this though, looking at the PN files in xEdit there doesn't seem to be any conflicts that arise from the positioning of them that way. I could be wrong, it was only a cursory look.

 

Perhaps this question needs to asked in the xEdit (FNVEdit) forum?

Share this post


Link to post
Share on other sites
  • 0

I didn't study the conflicts if any that might arise from the masters being out of order. I also don't think it is an MO problem specifically. I was looking for a short and sweet answer that I hadn't found myself after some fairly extensive digging. I will study on what I've got a little further. I don't expect to find a definitive answer. If there was such I think you or someone else that passes here would know it already.  I was about to do some merging in my load order and will do so now. I can get the kinks out I believe. This was just a new twist for me and I've been modding a good while.

 

Thanks much

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 Drak
      Hello There,
      I did a fresh install following STEP recommandations (FNV not in program files, modding directory neither, I started FNV after installing it).
      I can start the game with all mods from STEP except Step Patch - Conflict Resolution.

      I tryied to pinpoint my problem and as soon as I add the Step patch (then LOOT order dirladada) I get the following error in 
      nvac.log :
      23190643 _ NewVegasAntiCrash FalloutNV.exe
      23190643 _ 17E90000 07050000 nvac.dll
      23190643 i 008BFBC1 0441B60F FalloutNV.exe
      23190643 _ 17AE0000 06020050 nvse_1_4.dll
      23190643 _ 77170000 0A004A64 ntdll.dll
      23190646 a 0072607A 0048A1DF FalloutNV.exe
      23190647 h 181A42EB 8B48088B nvse_stewie_tweaks.dll (100342EB)
      23190647 ^ 0076E223 00000004 FalloutNV.exe
      23190647 h 181A42EE 8B01FF10 nvse_stewie_tweaks.dll (100342EE)
      23190647 ^ 0076E223 00000004 FalloutNV.exe
      23190647 h 181A42F0 FF1068F0 nvse_stewie_tweaks.dll (100342F0)
      23190647 ^ 0076E223 00000004 FalloutNV.exe
      23190647 m 000003EC 219C46E0
      23190647 r 10001432 00000009 d3dx9_38.dll (10001432)
      23190647 ^ 0045CEF5 0000000D FalloutNV.exe
      23190647 h 100034E0 834104FF d3dx9_38.dll (100034E0)
      23190647 ^ 0045CEF5 0000000D FalloutNV.exe
      23190647 h 100034E6 C7010000 d3dx9_38.dll (100034E6)
      23190647 ^ 0045CEF5 0000000D FalloutNV.exe
      23190647 u 00F0B4FA C0000409 FalloutNV.exe
      23190647 ! CRASHSAV E_FAIL_0 FalloutNV.exe
      23190648 q 00F0B4FA C0000409 FalloutNV.exe
      23190648 ! CRASHSAV E_FAIL_0 FalloutNV.exe
       
      I also tryed to use Cobb Crash Logger 
       
      Cobb Crash Logger Version 3.0.0, build 0.
      If this file is empty, then your game didn't crash! Probably!
      Exception C0000409 caught!
      Calltrace: 
      0x00F0B4FA ==> EntryPoint+0xFFFFFFFF in FalloutNV (0x0019F138) 
      0x771F88B4 ==> RtlInterlockedCompareExchange64+0x1B4 in ntdll (0x0019F204) 
      0x771E4EE6 ==> KiUserExceptionDispatcher+0x26 in ntdll (0x0019F208) 
      0x0019F21C ==> ¯\(°_o)/¯ (Corrupt stack or heap?)  (0x0019F20C)
      0x0019F26C ==> ¯\(°_o)/¯ (Corrupt stack or heap?)  (0x0019F21C)
      blablabla
      GAME CRASHED AT INSTRUCTION Base+0x00B0B4FA IN MODULE: C:\Steam\steamapps\common\Fallout New Vegas\FalloutNV.exe
      Please note that this does not automatically mean that that module is responsible. 
      It may have been supplied bad data or program state as the result of an issue in 
      the base game or a different DLL.
       
      Help welcome, I am at a loss..
    • 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.
  • 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.