Jump to content

v2.3 - Feedback & Bug Reports


Recommended Posts

2 minutes ago, z929669 said:

Did you install the LFfGM Arthmoor Town Patches with the Oakwood patch? That is no longer used (see instructions for that one).

Nope. Only the CRF and AsLAL patches.

Link to comment
Share on other sites

4 minutes ago, Mercury71 said:

Nope. Only the CRF and AsLAL patches.

Strange. I just checked, and mine is all above water, so you must have some other mod modifying the area. Check Moon and Star conflicts in xEdit.

Link to comment
Share on other sites

Just now, z929669 said:

Strange. I just checked, and mine is all above water, so you must have some other mod modifying the area. Check Moon and Star conflicts in xEdit.

Just found it!

Forgot to ...

2. Install the Patch for Moon and Star optional file as a separate mod for independent version tracking.

  • Like 1
Link to comment
Share on other sites

Snowy Landscapes in Snowy Regions remains in STEP 2.3. The mod is dropped from STEP per its dropped tag and the mod page mentions it has been fully incorporated into Vanilla Landscape Corrections. Users will need to regenerate LOD with xLODGen and DynDOLOD.

Link to comment
Share on other sites

1 hour ago, D1Z4STR said:

Snowy Landscapes in Snowy Regions remains in STEP 2.3. The mod is dropped from STEP per its dropped tag and the mod page mentions it has been fully incorporated into Vanilla Landscape Corrections. Users will need to regenerate LOD with xLODGen and DynDOLOD.

We're actually not dropping it until TechAngel updates the Smooth Shorelines Patch for VLC. I'll fix the tag on SLfSR

Link to comment
Share on other sites

8 hours ago, trackho said:

So other than having some landscape seams in the meantime, it'll be okay to drop SLfSR until VLC updates to the desired state?

The guide does not drop SLSR so that we can still use the Smooth Shores patch.

Link to comment
Share on other sites

Maybe not a bug report or it could be intentional, but I wanted to post here.

In the STEP - lighting and weather patch I noticed for worldscape record 0000BCB5 - FaldarsToothExterior02 that RiverWaterFlow (default) was used instead of RWT's RWT_LakeWater

Link to comment
Share on other sites

  • 2 weeks later...
On 8/30/2024 at 6:26 AM, d2eRX52 said:

SSE26.thumb.jpg.9eeb33c1fe0599d6ff7e3c31b8786d1e.jpgSSE28.thumb.jpg.751d21375680b54cb793e4bdb68ce8d9.jpg

is this seam vanilla and "just was there always? does anybody else have it? possible cause?

SSE29.thumb.jpg.ed0da2f2d895977514525b73f04a059d.jpgSSE30.thumb.jpg.594f86b9b2bfcd5ff23ca36abbd1cd6f.jpg

 

On 8/30/2024 at 6:39 AM, z929669 said:

This is a location yet to be addressed by VLC, which @TechAngel85 is the lead.

It's probably exacerbated by CL and/or MM.

I just stumbled across a fix for this issue by loading VLC after MM:

image.png

VLC at lower priority (position 126) than MM (position 145):

SkyrimSE 2024-10-25 21-35-10-37.jpg

VLC at higher priority (position 145) than MM (position 144):

SkyrimSE 2024-10-25 21-23-49-97.jpg

... but this may open up other issues, depending on how it's done. We could also move MM just above VLC, but I think that will cause more issues with CRF, FaECF, possibly RBB and some others sandwiched in between these.

@TechAngel85 We should verify LO of VLC with respect to MM and the cascade of LOOT sorting related to MM. Maybe it's a simple edit to the LOOT ML, but I want to be sure of the 'best' position of all these plugins in relation to one another. Fe, CRF probably needs to load after VLC.

Likewise, SLSR may also need to load after MM.


UPDATE: Vanilla Landscape Corrections.esp has no conflicts with MajesticMountains.esp.

The problem is actually due to Snowy Landscapes In Snowy Regions.esp overriding Vanilla Landscape Corrections.esp. Moving the former to one lower priority (126) than the latter (127) also fixes this issue.

I'm now rethinking that SLSR should be dropped regardless of the Smooth Shores Patches being lost without it. SLSR does have a good number of CRF patches that are lacking in VLC where SLSR and VLC conflict. Likewise, VLC has a small number of CRF patching that SLSR lacks.

I'm going to run the game for a wile without SLSR and the SmoothShores - SLSR Patch.esp to see if there are any issues without them.

Link to comment
Share on other sites

On 10/25/2024 at 9:38 PM, z929669 said:

... but this may open up other issues, depending on how it's done. We could also move MM just above VLC, but I think that will cause more issues with CRF, FaECF, possibly RBB and some others sandwiched in between these.

@TechAngel85 We should verify LO of VLC with respect to MM and the cascade of LOOT sorting related to MM. Maybe it's a simple edit to the LOOT ML, but I want to be sure of the 'best' position of all these plugins in relation to one another. Fe, CRF probably needs to load after VLC.

Likewise, SLSR may also need to load after MM.


UPDATE: Vanilla Landscape Corrections.esp has no conflicts with MajesticMountains.esp.

The problem is actually due to Snowy Landscapes In Snowy Regions.esp overriding Vanilla Landscape Corrections.esp. Moving the former to one lower priority (126) than the latter (127) also fixes this issue.

I'm now rethinking that SLSR should be dropped regardless of the Smooth Shores Patches being lost without it. SLSR does have a good number of CRF patches that are lacking in VLC where SLSR and VLC conflict. Likewise, VLC has a small number of CRF patching that SLSR lacks.

I'm going to run the game for a wile without SLSR and the SmoothShores - SLSR Patch.esp to see if there are any issues without them.

VLC - References.esm
This plugin holds all Object References that are changed in any way by VLC. Regardless if the objects are large references or not, all changes to Object References are placed within this master file to prevent any potential large reference bugs from occurring. Currently, the plugin houses mostly road and rock changes. The following are considerations for this master file:

  • USSEP changes to exterior Cell records should be forwarded. These are the ones with coordinates under Tamriel Worldspace.
  • USSEP changes to Object References is case by case. Unless you did the work on the mod, assume VLC should win all conflicts with Object References.
  • Load order does not matter in regards to Majestic Mountains ESM, since there are no conflicts and the MM ESP will always load after.
  • Load order only matters for other ESM plugins that contain conflicts with the included Object References; in which case, VLC should win said conflicts.
  • Conflicts with the included Object References with other ESL/ESP plugins will require a patch to allow VLC to win said conflicts.
  • Changes to this plugin will often require regenerating object LODs with DynDOLOD.

Vanilla Landscape Corrections.esp
This plugin holds all Landscape changes included in VLC. This includes changes to landscape shape, textures, and vertex colors. Though this plugin could be flagged as ESL, it currently isn't due to ongoing development. There should not be any Object References included in this file. The following are considerations for this plugin file:

  • USSEP changes to exterior Cell records should be forwarded.
  • VLC should lose conflicts with other mods in regards to the exterior Cell, or a patch created that forwards the other mod's Cell changes and VLC's Landscape changes.
  • Load order does not matter in regards to Majestic Mountains ESP, since there are no conflicts with and the MM ESM will always load before.
  • Load order only matters for other ESL/ESP plugins that contain conflicts with the included Landscape records. Choosing a "winner" in such cases is not always straightforward. If the conflict is with a mod that is included in VLC or VLC is designed to work with (LFfGM) then VLC should win. In all other cases, the mods may work with VLC winning or losing some or all conflicts. It really depends on the nature of the changes made, and will often require some sort of patching to make the mods harmonize.
  • Changes to this plugin will often require regenerating landscape LODs with xLODGen.

Hopefully that answers some questions. In regards to SLSR, I would allow VLC to win all conflicts with it. Frankly, it's not needed for the sake of VLC since it was entirely absorbed into VLC and reworked. It's only being kept for the Smooth Shores patch, which I, personally, would just forget about for now. I will eventually get around to redoing that patch for VLC.

Link to comment
Share on other sites

This might or might not be related to the last posts. At some point two years ago I mentioned a landscape visual bug in relation with the 'Fishing' CC, which is found here. Now apparently in CRF's latest version 'Frostbark Lumber Mill' and the wooden footbridge at that location has been removed by the author, which makes this 'Fishing' spot the only occurence at that riverbank just down the hill from Kynesgrove. The 'Fishing' spot is not only half flooded as before, but now also features a huge visible tear in the shoreline.

I am playing Step 2.3, but started my game without SLSR and the SmoothShores - SLSR Patch. This is so far the only visual bug I encountered.

FrostbarkLumberMill19.thumb.jpg.148fbefc326c77b2cb05d06888d193da.jpgFrostbarkLumberMill20.thumb.jpg.915cac30a543bde27291ae4f945c0a39.jpgFrostbarkLumberMill21.thumb.jpg.5d0b4ed5c686cd6ea021b20e66f8c614.jpgFrostbarkLumberMill22.thumb.jpg.dc465c35bbf48a2415c2f369234bb1aa.jpg

Link to comment
Share on other sites

8 hours ago, TechAngel85 said:

VLC - References.esm
This plugin holds all Object References that are changed in any way by VLC. Regardless if the objects are large references or not, all changes to Object References are placed within this master file to prevent any potential large reference bugs from occurring. Currently, the plugin houses mostly road and rock changes. The following are considerations for this master file:

  • USSEP changes to exterior Cell records should be forwarded. These are the ones with coordinates under Tamriel Worldspace.
  • USSEP changes to Object References is case by case. Unless you did the work on the mod, assume VLC should win all conflicts with Object References.
  • Load order does not matter in regards to Majestic Mountains ESM, since there are no conflicts and the MM ESP will always load after.
  • Load order only matters for other ESM plugins that contain conflicts with the included Object References; in which case, VLC should win said conflicts.
  • Conflicts with the included Object References with other ESL/ESP plugins will require a patch to allow VLC to win said conflicts.
  • Changes to this plugin will often require regenerating object LODs with DynDOLOD.

Vanilla Landscape Corrections.esp
This plugin holds all Landscape changes included in VLC. This includes changes to landscape shape, textures, and vertex colors. Though this plugin could be flagged as ESL, it currently isn't due to ongoing development. There should not be any Object References included in this file. The following are considerations for this plugin file:

  • USSEP changes to exterior Cell records should be forwarded.
  • VLC should lose conflicts with other mods in regards to the exterior Cell, or a patch created that forwards the other mod's Cell changes and VLC's Landscape changes.
  • Load order does not matter in regards to Majestic Mountains ESP, since there are no conflicts with and the MM ESM will always load before.
  • Load order only matters for other ESL/ESP plugins that contain conflicts with the included Landscape records. Choosing a "winner" in such cases is not always straightforward. If the conflict is with a mod that is included in VLC or VLC is designed to work with (LFfGM) then VLC should win. In all other cases, the mods may work with VLC winning or losing some or all conflicts. It really depends on the nature of the changes made, and will often require some sort of patching to make the mods harmonize.
  • Changes to this plugin will often require regenerating landscape LODs with xLODGen.

Hopefully that answers some questions. In regards to SLSR, I would allow VLC to win all conflicts with it. Frankly, it's not needed for the sake of VLC since it was entirely absorbed into VLC and reworked. It's only being kept for the Smooth Shores patch, which I, personally, would just forget about for now. I will eventually get around to redoing that patch for VLC.

This is helpful. Thank you.

1 hour ago, CorneliusC said:

This might or might not be related to the last posts. At some point two years ago I mentioned a landscape visual bug in relation with the 'Fishing' CC, which is found here. Now apparently in CRF's latest version 'Frostbark Lumber Mill' and the wooden footbridge at that location has been removed by the author, which makes this 'Fishing' spot the only occurence at that riverbank just down the hill from Kynesgrove. The 'Fishing' spot is not only half flooded as before, but now also features a huge visible tear in the shoreline.

I am playing Step 2.3, but started my game without SLSR and the SmoothShores - SLSR Patch. This is so far the only visual bug I encountered.

FrostbarkLumberMill19.thumb.jpg.148fbefc326c77b2cb05d06888d193da.jpgFrostbarkLumberMill20.thumb.jpg.915cac30a543bde27291ae4f945c0a39.jpgFrostbarkLumberMill21.thumb.jpg.5d0b4ed5c686cd6ea021b20e66f8c614.jpgFrostbarkLumberMill22.thumb.jpg.dc465c35bbf48a2415c2f369234bb1aa.jpg

Good to know. Tech's post may help me to address this and the other rocks issue mentioned.

Link to comment
Share on other sites

  • 2 weeks later...

Hi,
 

I've just started going through your STEP 2.3 guide in setting up Skyrim and figured I would point out what I think is an ambiguity that will lead to unnecessary confusion for some users going through it.

This section here says to "Repeat these steps to add the remaining executables as indicated in the table following."

S4X5cjY.png

With the following table then listing the tools to repeat (some of) these steps with.
RXuGg27.png

Now I think from what's being said here, you're essentially wanting a user to only follow the steps that are required to add a tool to MO (and ignore xEdit specific steps) and then only follow the additional steps that apply to the Arguments & Special Instructions part of the table for each tool.

I think some people might get confused on what steps to repeat and what should be ignored for each application simply by the way this is structured and worded.

Suffice to say I believe I understand what's being said here, but I can imagine some users very early on getting to this point and think "Well am I supposed to do all the steps, some of the steps or just what is only mentioned in the table?". I think this could perhaps be conveyed a little more clearly.

I appreciate all the work your team has done here and maybe you'll feel this is a little too neurotic, but figured I'd give you some feedback from someone who's going into this guide blind for the first time.

Edited by Jazmac
Link to comment
Share on other sites

For the section "Sorting Plugins With LOOT", this instruction when using LOOT from what I can tell might not be applicable if the plugin order doesn't change after sorting (which was at least the case for myself when using LOOT for the first time).

"4. Click [Apply Sorted Load Order]."

HvdEBws.png

Also

In the section "Cleaning Vanilla Master Plugins". It states in step 3:

KjyuECo.png

"3. This mod should appear at priority 78 in the MO left pane if all instructions were followed correctly."

Perhaps I've done something wrong, but following this guide will at least result in it being positioned at priority 79 because the guide instructs to create empty mod folders for "xEdit Output" and possibly 80 if the user decided to create an "SKSE Output" folder in advance of that tool being installed later.

Edited by Jazmac
Link to comment
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
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.