Jump to content

Recommended Posts

Posted
15 minutes ago, sheson said:

I asked to run the test version and in case it still has a problem to test if there also is an error saving the texture with xEdit.
You only need to do what I actually ask and report the results properly, so there is no confusion. You made it sound like there was an error saving the texture with xEdit.

In that case upload the new SSELODGen_log.txt from the test version.

What mod(s) are the reported textures from?
Are the game/mods installed on a spinning disk?

Sorry for any confusion I caused.
Those textures are
atheuzz landscape
vanaheimr - snow
atheuzz mountains
imveterate imperium
rally's solstheim landscape
praedy's soul acirrn
These are things that came from .
However, even when I just deleted all modes and ran it, the same timeout error was displayed.

I'm running it again with the test version now, and it takes 2 hours. Once completed, we will upload the log again.

Posted
9 minutes ago, aazz said:

Sorry for any confusion I caused.
Those textures are
atheuzz landscape
vanaheimr - snow
atheuzz mountains
imveterate imperium
rally's solstheim landscape
praedy's soul acirrn
These are things that came from .
However, even when I just deleted all modes and ran it, the same timeout error was displayed.

I'm running it again with the test version now, and it takes 2 hours. Once completed, we will upload the log again.

Since the problem is with textures, you can uncheck terrain LOD meshes generation.
It is enough to select Tamriel, since the error already happed in that worldspace.
You can also save time by setting lower resolution for LOD level 32 or just generating LOD Level 4 by checking specific chunk and changing the drop down to 4.
You can click the X top right once to close xLODGen once the error occured, it should still save the log message so far.
Make sure the output folder is empty.

Posted
31 minutes ago, sheson said:

Since the problem is with textures, you can uncheck terrain LOD meshes generation.
It is enough to select Tamriel, since the error already happed in that worldspace.
You can also save time by setting lower resolution for LOD level 32 or just generating LOD Level 4 by checking specific chunk and changing the drop down to 4.
You can click the X top right once to close xLODGen once the error occured, it should still save the log message so far.
Make sure the output folder is empty.

thank you
This is a log that was executed with only tamriel and lod4 selected.

SSELODGen_log.7z

Posted
30 minutes ago, captainlei1993 said:

arkarthWorld shouldn't appear in the worldspace list if mods like Markarth LOD Unlock is present.

As explained in the text at the bottom of the xLODGen window, every worldspace for which a matching lodsettings *.lod file is found is listed.

If you do not want the tool to generate LOD files for a specific worldspace, then do not select that worldspace.
If the game does not use LOD files, it does not matter what tool was used to generate them.

Posted
44 minutes ago, captainlei1993 said:

So in order to fix the Cidhna Mine Terrain Issue, the best practice would be running xlodgen twice, the first time generate all worldspaces except for markarth world then generate only markarth world for the second time, right?

No logs or any explanations have been provided.

I assume this problem happens while using a mod that sets to use the Tamriel LOD meshes inside Markarth. That means the Markarth LOD meshes are not used. Generating LOD meshes for Markarth is irrelevant no matter if/how/when they are generated.

If the Tamriel terrain LOD meshes are used inside Markarth, check the "Hide Quads" checkbox while generating terrain LOD meshes.
Whatever mod is changing to use Tamriel LOD inside Markarth also needs to actually set hide quad flags for the corresponding cells in the Tamriel worldspace or do matching edits to the terrain height itself.

Posted
33 minutes ago, sheson said:

No logs or any explanations have been provided.

I assume this problem happens while using a mod that sets to use the Tamriel LOD meshes inside Markarth. That means the Markarth LOD meshes are not used. Generating LOD meshes for Markarth is irrelevant no matter if/how/when they are generated.

If the Tamriel terrain LOD meshes are used inside Markarth, check the "Hide Quads" checkbox while generating terrain LOD meshes.
Whatever mod is changing to use Tamriel LOD inside Markarth also needs to actually set hide quad flags for the corresponding cells in the Tamriel worldspace or do matching edits to the terrain height itself.

I mean you can overwrite the Tameriel LOD meshes from the first time generation with renamed markarth terrain meshes(with Markarth LOD unlocked disabled) from the second time generation. This method is just a workaround so I will try the method you mentioned here and see if the issue still persist. Thanks for your reply.

  • sheson changed the title to xLODGen - Terrain LOD beta 129 for FNV, FO3, FO4, FO4VR, TES5, SSE, TES5VR, ENDERAL, ENDERALSE

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.