Jump to content

Flags, wrong order and Cyclic errors


Durete

Recommended Posts

Hello everyone.

 

 

When I installed a bunch of mods through Vortex (installing 1 by 1, test worked, later on when playing I got random CTD's)
I delved further into what causes issues.


====================================================

Programs I use:

Vortex: To install and manage mods and load order.
LOOT: To check for any errors that Vortex does not show
Xedit: To create merge plugin (Excluding the levelled lists)
Wrye bash: To find load order issues not found with the above programs and to make a bash patch (to include the levelled lists)

=======================================================



When I open Wrye Bash, it shows several "Orange Boxes", Indicating that Masters are not in the correct/expected order.

while nothing serious, it still will change gameplay, and sometimes cause Crashes or other unwanted behavior.

 

Here is my problem with a few of them: (Here is just one example) this is for the game Fallout 4 (I post it here as it is more an issue I have with Vortex than with the specific game.)

The Vivid weathers and True storms Patch
It expects to load Vivid weathers>True storms>The patch

However: True storms has a "Master" flag in Vortex, which causes it to load first.

When I make it so that True storms depends on VIvid weathers so it forces to load after, I get cyclic errors.

How do I do this properly, so that Vortex will load Vivid weathers before True storms, even while True storms has a "Master" Flag, and Vivid weathers does not?


Thank you.

Link to comment
Share on other sites

What Vivid Weather - True Storms patch?

I'd like to look at the patch and read the instructions,

Also, how OLD is the patch, because on the True storms page it says

 

NOTE: Mods with patches for True Storms will not work with version v1.4 unless they are updated! These are being updated and will happen very quickly so please be patient. Using old patches may cause unintended behavior and issues, so you're best running True Storms by itself if you cannot wait. There are always bumps when doing major updates, so your patience is appreciated.
Link to comment
Share on other sites

 

What Vivid Weather - True Storms patch?

 

I'd like to look at the patch and read the instructions,

 

Also, how OLD is the patch, because on the True storms page it says

 

 

NOTE: Mods with patches for True Storms will not work with version v1.4 unless they are updated! These are being updated and will happen very quickly so please be patient. Using old patches may cause unintended behavior and issues, so you're best running True Storms by itself if you cannot wait. There are always bumps when doing major updates, so your patience is appreciated.

 

Ahh must have read over that one.

This merge is last updated in 2018:

 

https://www.nexusmods.com/fallout4/mods/15908

 

 

Anyway this is just one of the examples, I have about 5 of these issues where wrye bash gives the orange Box.

 

BetterSettlersMortalSoldiersPack
LovingPiper
Cross_Corecrits_FarHarborPatch
Realistic Guns and Bullets Overhaul

 

Are other examples.

 

I just noticed some have some really weird "Expected masters order" As Realistic Guns and Bullets overhaul shows that "Armorkeywords.esm" loads before "DLCWorkshop02"

Cross Corecrits Far Habror patch expects "Cross Corecrits.esp to load before DLCCoast.esm

BetterSettlersMortalSoldiersPack expects BetterSettlers to load before DLCCoast

Link to comment
Share on other sites

OK looking at the mod page, where are you getting the idea that Vivid Weathers MUST go before True Storms?

All the mod page says is:

 


  1. Firs install both True Storms and Vivid Weathers if you didn't yet.
  2. Then with NMM/MO2 or manually choose merge patch type and Vivid Weathers season.

 

Then it's up to you to decide if you want to use the patches that use the Vivid Weather stuff and tosses out the True Storms stuff
Or use the patches that tosses out the Vivid Weather stuff and uses the true storms stuff.

There's nothing about Load order for those two, this is a MERGED Patch that removes conflicts, but sacrifices one mods stuff for the others

Did you read the description page of the Patch?

Link to comment
Share on other sites

Note that the Description page NEVER says to have Vivid Weathers above TrueStorms,



Darker Nights compatibility
Darker Nights mod support both True Storms and Vivid Weathers mods, however, it installation suggests that you have only one weather mod. So you need manually pull out of Darker Nights package patches for both mods and rename them. Load order here is important.
If you use True Storms Priority then your load order should look somewhat like this:
Fallout4.esm
...
TrueStormsFO4.esm
...
[Any True Storms esp extensions]
Vivid Weathers - FO4.esp
[Any Vivid Weathers esp extensions]
WeatherSynergy*.esp
DarkerNights - Vivid Weathers.esp
DarkerNights - TrueStorms.esp

If you use Vivid Weathers Priority then your load order should look somewhat like this:
Fallout4.esm
...
TrueStormsFO4.esm
...
[Any True Storms esp extensions]
Vivid Weathers - FO4.esp
[Any Vivid Weathers esp extensions]
WeatherSynergy*.esp
DarkerNights - TrueStorms.esp
DarkerNights - Vivid Weathers.esp

Link to comment
Share on other sites

OK looking at the mod page, where are you getting the idea that Vivid Weathers MUST go before True Storms?

 

All the mod page says is:

 

  1. Firs install both True Storms and Vivid Weathers if you didn't yet.
  2. Then with NMM/MO2 or manually choose merge patch type and Vivid Weathers season.

 

Then it's up to you to decide if you want to use the patches that use the Vivid Weather stuff and tosses out the True Storms stuff

Or use the patches that tosses out the Vivid Weather stuff and uses the true storms stuff.

 

There's nothing about Load order for those two, this is a MERGED Patch that removes conflicts, but sacrifices one mods stuff for the others

 

Did you read the description page of the Patch?

 

 

 

The order comes from the Wrye Bash Program, that gives an Orange box, indicating masters being in a different order than expected.

 

http://i63.tinypic.com/2wmjrl0.png

Link to comment
Share on other sites

 

OK looking at the mod page, where are you getting the idea that Vivid Weathers MUST go before True Storms?

 

All the mod page says is:

 

  1. Firs install both True Storms and Vivid Weathers if you didn't yet.
  2. Then with NMM/MO2 or manually choose merge patch type and Vivid Weathers season.

 

Then it's up to you to decide if you want to use the patches that use the Vivid Weather stuff and tosses out the True Storms stuff

Or use the patches that tosses out the Vivid Weather stuff and uses the true storms stuff.

 

There's nothing about Load order for those two, this is a MERGED Patch that removes conflicts, but sacrifices one mods stuff for the others

 

Did you read the description page of the Patch?

 

 

The order comes from the Wrye Bash Program, that gives an Orange box, indicating masters being in a different order than expected.

 

http://i63.tinypic.com/2wmjrl0.png

 

 

 

So, why are you using Wryebash and Vortex and having them fight each other.

 

When Wryebash does that, it's carrying over what the other person's load order was when they made the esp.

 

Stop chasing your tail by using both together.

There is NO EXAMPLE of Vivid Weathers, esp ever being pout above Truestorms.esm

 

You're going solely by the colored boxes in Wryebash and completely ignoring the description page for the patch.

Stop doing that, or you'll never get a working load order.

Link to comment
Share on other sites

 

 

OK looking at the mod page, where are you getting the idea that Vivid Weathers MUST go before True Storms?

 

All the mod page says is:

 

  1. Firs install both True Storms and Vivid Weathers if you didn't yet.
  2. Then with NMM/MO2 or manually choose merge patch type and Vivid Weathers season.

 

Then it's up to you to decide if you want to use the patches that use the Vivid Weather stuff and tosses out the True Storms stuff

Or use the patches that tosses out the Vivid Weather stuff and uses the true storms stuff.

 

There's nothing about Load order for those two, this is a MERGED Patch that removes conflicts, but sacrifices one mods stuff for the others

 

Did you read the description page of the Patch?

 

 

The order comes from the Wrye Bash Program, that gives an Orange box, indicating masters being in a different order than expected.

 

http://i63.tinypic.com/2wmjrl0.png

 

 

 

So, why are you using Wryebash and Vortex and having them fight each other.

 

When Wryebash does that, it's carrying over what the other person's load order was when they made the esp.

 

Stop chasing your tail by using both together.

There is NO EXAMPLE of Vivid Weathers, esp ever being pout above Truestorms.esm

 

You're going solely by the colored boxes in Wryebash and completely ignoring the description page for the patch.

Stop doing that, or you'll never get a working load order.

 

 

Hmm ok, thanks.

 

 

I had a lot of random CTD's with even just basic mods together.

So went to look on fixes on how to get a stable environment, I found a few posts/youtube video's that all say pretty much the same order when installing a mod:

 

1) Install mod through vortex

2) Enable & Sort mods in Vortex

3) Open LOOT check for any errors that vortex did not give, fix if needed.

4) Delete Bash Patch in Wrye Bash

5) Create new FO4Merged.esp merged patch in xEdit

6) Remove leveled lists from FO4Merged.esp in xEdit

7) Open Wrye Bash, fix the orange boxes

8) Create new batch Patch in Wrye Bash

 

So these were the steps that I took after every mod I installed. to prevent spending hours and hours enabling 1 mod, testing, enable next mod, testing, and when the tests seemed fine to go and play the game and still get random CTD's.

I spend already 400+ hours trying to just install mods that I want but still can't play for more than 5-10 minutes without random CTD's :(

Link to comment
Share on other sites

 

Hmm ok, thanks.

 

 

I had a lot of random CTD's with even just basic mods together.

So went to look on fixes on how to get a stable environment, I found a few posts/youtube video's that all say pretty much the same order when installing a mod:

 

1) Install mod through vortex

2) Enable & Sort mods in Vortex

3) Open LOOT check for any errors that vortex did not give, fix if needed.

4) Delete Bash Patch in Wrye Bash

5) Create new FO4Merged.esp merged patch in xEdit

6) Remove leveled lists from FO4Merged.esp in xEdit

7) Open Wrye Bash, fix the orange boxes

:cool: Create new batch Patch in Wrye Bash

 

So these were the steps that I took after every mod I installed. to prevent spending hours and hours enabling 1 mod, testing, enable next mod, testing, and when the tests seemed fine to go and play the game and still get random CTD's.

I spend already 400+ hours trying to just install mods that I want but still can't play for more than 5-10 minutes without random CTD's :sad:

 

 

 

 

1) Install mod through vortex

2) Enable & Sort mods in Vortex

3) Open LOOT check for any errors that vortex did not give, fix if needed. - NOT NECESSARY

4) Delete Bash Patch in Wrye Bash - WHY?

5) Create new FO4Merged.esp merged patch in xEdit

6) Remove leveled lists from FO4Merged.esp in xEdit

7) Open Wrye Bash, fix the orange boxes - NO!

:cool: Create new batch Patch in Wrye Bash - BY USING REBUILD PATCH

 

 

All you should be doing with Wryebash is making a Bashed Patch.

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...