Jump to content

Install Order File?


Krytern

Recommended Posts

The install order randomly changes, making some NPCs faces black. I can't find what mod I need to load before Bijin's. If I uninstall Bijin's, then reinstall them the NPCs will look fine until the order changes again so their faces go black again. Since I can't just drag Bijin's under everything making it last in the install order to fix it instantly (which would be the most convenient, mod managers are for convenience whether you like how people use the feature or not) is there a file stored somewhere which lists the install order of the mods? Then I could just move Bijin's to the bottom in that.

Link to comment
Share on other sites

If there is a conflict with another mod it will alert you (red lightning bolt) so you can set a rule for which mod should win. If it's not conflicting with another mod then the install order is meaningless. The install order listed on the Mods page will change when you do something like update/reinstall a mod setting it to the last mod installed. This is why rules are better as it means you don't need to worry about install order, you deal with conflicts at install and never have to worry about it if you change anything with the mods.

 

If you are having issues with plugins moving from sort to sort, create rules with priorities. Use global priorities to create groups you can sort and local priority to sort within the group. I had the same issue and after grouping with priorities it doesn't happen anymore.

 

While dragging and dropping was easier the new rule based method is far better. It just has a steep learning curve with a lack of documentation.

Link to comment
Share on other sites

If there is a conflict with another mod it will alert you (red lightning bolt) so you can set a rule for which mod should win. If it's not conflicting with another mod then the install order is meaningless. The install order listed on the Mods page will change when you do something like update/reinstall a mod setting it to the last mod installed. This is why rules are better as it means you don't need to worry about install order, you deal with conflicts at install and never have to worry about it if you change anything with the mods.

 

If you are having issues with plugins moving from sort to sort, create rules with priorities. Use global priorities to create groups you can sort and local priority to sort within the group. I had the same issue and after grouping with priorities it doesn't happen anymore.

 

While dragging and dropping was easier the new rule based method is far better. It just has a steep learning curve with a lack of documentation.

I know about Dependencies. There is no conflict according to Vortex's dependencies. The install order clearly isn't meaningless because if I uninstall the mods, reinstall them then it fixes the issue. In Mod Organiser I always fixed the issue by making them last in the install order. Kept it fixed all the time as it was always at the bottom. These rules are not better because this is very inconvenient, being able to move mods up and down to instantly change my install order exactly how I want it is better.

 

In short: Dependencies isn't fixing it and it is the install order I need to change to fix it, so is there a file with the install order in it?

Link to comment
Share on other sites

 

... so is there a file with the install order in it?

 

 

No.

 

Edit: I did a quick search and it looks like this is caused by a conflict in facegen data with another mod. I would suggest a patch that copies the facegen data from your mod and place it at the end of your plugin load order.

Link to comment
Share on other sites

 

 

... so is there a file with the install order in it?

 

 

No.

 

Do you know any other way I could fix this issue? I'm open to anything that works, I just don't want to keep uninstalling and reinstalling the mods.

Link to comment
Share on other sites

 

If there is a conflict with another mod it will alert you (red lightning bolt) so you can set a rule for which mod should win. If it's not conflicting with another mod then the install order is meaningless. The install order listed on the Mods page will change when you do something like update/reinstall a mod setting it to the last mod installed. This is why rules are better as it means you don't need to worry about install order, you deal with conflicts at install and never have to worry about it if you change anything with the mods.

 

If you are having issues with plugins moving from sort to sort, create rules with priorities. Use global priorities to create groups you can sort and local priority to sort within the group. I had the same issue and after grouping with priorities it doesn't happen anymore.

 

While dragging and dropping was easier the new rule based method is far better. It just has a steep learning curve with a lack of documentation.

I know about Dependencies. There is no conflict according to Vortex's dependencies. The install order clearly isn't meaningless because if I uninstall the mods, reinstall them then it fixes the issue. In Mod Organiser I always fixed the issue by making them last in the install order. Kept it fixed all the time as it was always at the bottom. These rules are not better because this is very inconvenient, being able to move mods up and down to instantly change my install order exactly how I want it is better.

 

In short: Dependencies isn't fixing it and it is the install order I need to change to fix it, so is there a file with the install order in it?

 

If you double click on the Bijin esps in your PLUGINS page and change the Global priority to 75 and resort. It should fix your load order. As others have said it's your plugin order that is likely the cause and should be tried first. Vortex won't show all conflicts between plugins. It only shows those that authors have registered in LOOT. You have to use xEdit to view the conflicts within your PLUGINS. There is no other way. (I"m secretly hoping this is one of the things that might get integrated, to somehow show conflicting plugins, but it's a costly thing to add.)

Link to comment
Share on other sites

 

 

If there is a conflict with another mod it will alert you (red lightning bolt) so you can set a rule for which mod should win. If it's not conflicting with another mod then the install order is meaningless. The install order listed on the Mods page will change when you do something like update/reinstall a mod setting it to the last mod installed. This is why rules are better as it means you don't need to worry about install order, you deal with conflicts at install and never have to worry about it if you change anything with the mods.

 

If you are having issues with plugins moving from sort to sort, create rules with priorities. Use global priorities to create groups you can sort and local priority to sort within the group. I had the same issue and after grouping with priorities it doesn't happen anymore.

 

While dragging and dropping was easier the new rule based method is far better. It just has a steep learning curve with a lack of documentation.

I know about Dependencies. There is no conflict according to Vortex's dependencies. The install order clearly isn't meaningless because if I uninstall the mods, reinstall them then it fixes the issue. In Mod Organiser I always fixed the issue by making them last in the install order. Kept it fixed all the time as it was always at the bottom. These rules are not better because this is very inconvenient, being able to move mods up and down to instantly change my install order exactly how I want it is better.

 

In short: Dependencies isn't fixing it and it is the install order I need to change to fix it, so is there a file with the install order in it?

 

If you double click on the Bijin esps in your PLUGINS page and change the Global priority to 75 and resort. It should fix your load order. As others have said it's your plugin order that is likely the cause and should be tried first. Vortex won't show all conflicts between plugins. It only shows those that authors have registered in LOOT. You have to use xEdit to view the conflicts within your PLUGINS. There is no other way. (I"m secretly hoping this is one of the things that might get integrated, to somehow show conflicting plugins, but it's a costly thing to add.)

 

It has nothing to do with plugins. I infact already have the mod at the bottom of the plugin's load order. As I said earlier how I fixed it in MO is I had the mod at the bottom of the install order and that is what fixed it and kept it fixed.

I am going to try what SkunkMonkey mentioned after dinner it sounds like it would fix it since in the reddit posts he linked to it points out that putting the plugin at the bottom won't work.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...