Install Order is Suddenly Messed Up

[Tannin42]

Glad it's solved but I'd like to clarify something:

 

The "Install Order" displayed in Vortex is a preview of how the mods are going to be deployed (might have been better to call it "Deploy Order"), it is not the order in which you installed the mods.

 

So your expectation that Majestic Mountain shouldn't be in spot 0 if it loads after other (enabled!) mods is correct, that install order should reflect your rules.

 

The only explanation I have for why its wrong is that either its "outdated" (as in: the "preview" was generated before Vortex was done loading all rules so it ended up being out of sync) or there was a problem sorting the mods (e.g. a cycle in the rules) for which you would have gotten a notification you might have forgotten to tell us about.

 

But again, this is all about mods, the rules on the mods tab do not affect the order of plugins in the plugins tab.

[Poorman65]

Tannin42

 

Wouldn't the deploy order matter in this case, since meshes and textures are being modified by multiple Mods? Not all of the Mods are represented by Plugins. In this case, the Bijin Mod provides the All-in-one Plugin, but there is a Bijin Customizer Mod that replaces some of those contents.

 

If the Customizer gets deployed first, won't the main Bijin Mod mess up these same files?

 

Also, is there a way to get the Mods to sort properly now? I know I can sort the Plugins, but that doesn't seem to have any impact on the Mods.

[Poorman65]

 

 

Even though the Blackface issue is gone, the wrong Texture is showing up in the game.

 

In the attached pic you can see that the main Bijin Mod is loading after the associated Customizers, but it is configured to Load Before.

 

I even re-installed the Customizer so that it would possibly do a re-sort, but it stayed as loading first.

 

It looks like Sorting has just stopped running.

[Poorman65]

Comparing the Vortex Mods contents with the Skyrim Data, it looks like the correct stuff is ending up in the Bijin textures. So, maybe it is a UI issue and the actual deployment is happening correctly.

[HadToRegister]

I would think that a "Customizer" mod, would LOAD AFTER the mod it's Customizing.
Considering the Customizer Mods CHANGE what's in the Bijins MOd, which would mean in order for their changes to take effect, they'd need to be BELOW Bijins in the load order.

Have you tried to load the two Customizer mods AFTER Bijins War-maidens?

[Tannin42]

Well, you're right that the deploy order is relevant to which textures/modules get loaded, what I meant is just that the deploy order is not affected by plugin rules and plugin order is not affected my deployment rules.

 

But most of the time the mod order is only a matter of taste, which texture you pick is up to your preference and won't have any impact on the game.

If it's important that the plugin order and the asset order is synchronized (usually with scripts), mod authors should be using .bsa files anyway. .bsa files get loaded in the same order as their corresponding plugin and since assets from bsas don't conflict on a file-system level, their deploy order is irrelevant.

 

> Comparing the Vortex Mods contents with the Skyrim Data, it looks like the correct stuff is ending up in the Bijin textures. So, maybe it is a UI issue and the actual deployment is happening correctly.

 

That would support my first theory: Vortex generates its "deploy order" preview before it has loaded all rules. This would indeed only affect what it displays in the UI, all rules are re-evaluated at the time you deploy mods and at that time everything should be loaded.

[Poorman65]

  On 10/27/2019 at 5:14 AM, HadToRegister said:

I would think that a "Customizer" mod, would LOAD AFTER the mod it's Customizing.

Considering the Customizer Mods CHANGE what's in the Bijins MOd, which would mean in order for their changes to take effect, they'd need to be BELOW Bijins in the load order.

 

Have you tried to load the two Customizer mods AFTER Bijins War-maidens?

It is configured for the Customizer to load After. The problem we are discussing is that the UI is showing the Customizer Before.

[HadToRegister]

  On 10/27/2019 at 6:01 PM, Poorman65 said:

 

  On 10/27/2019 at 5:14 AM, HadToRegister said:

I would think that a "Customizer" mod, would LOAD AFTER the mod it's Customizing.

Considering the Customizer Mods CHANGE what's in the Bijins MOd, which would mean in order for their changes to take effect, they'd need to be BELOW Bijins in the load order.

 

Have you tried to load the two Customizer mods AFTER Bijins War-maidens?

It is configured for the Customizer to load After. The problem we are discussing is that the UI is showing the Customizer Before.

 

 

 

That doesn't matter, what actually matters is that it's set to LOAD AFTER.

THAT is what determines which Textures, Meshes, BSAs etc get loaded before or after.

[Poorman65]

  On 10/27/2019 at 6:15 PM, HadToRegister said:

 

  On 10/27/2019 at 6:01 PM, Poorman65 said:

 

  On 10/27/2019 at 5:14 AM, HadToRegister said:

I would think that a "Customizer" mod, would LOAD AFTER the mod it's Customizing.

Considering the Customizer Mods CHANGE what's in the Bijins MOd, which would mean in order for their changes to take effect, they'd need to be BELOW Bijins in the load order.

 

Have you tried to load the two Customizer mods AFTER Bijins War-maidens?

It is configured for the Customizer to load After. The problem we are discussing is that the UI is showing the Customizer Before.

 

 

 

That doesn't matter, what actually matters is that it's set to LOAD AFTER.

THAT is what determines which Textures, Meshes, BSAs etc get loaded before or after.

 

The Customizer isn't a Plugin, so there is nothing done with it at Load time. Install order "Does" matter, since files are overwritten on the file system during Deploy. The file conflicts that have to get resolved in the Mods panel determine which gets deployed first, with the last to be deployed winning.

 

At load time, the game has no knowledge that the Customizer even exists. It just loads the Bijin plugin with the files that have been overwritten by the Customizer.

[rmm200]

"since files are overwritten on the file system during Deploy". This is true of NMM but not Mod Organizer and Vortex. You can't back off a NMM mod - the previous files no longer exist.

​MO, using a Virtual File System, and Vortex using Hard Links, give you mods that can be reversed just by disabling them.