xLODGen - Terrain LOD beta 130 for FNV, FO3, FO4, FO4VR, TES5, SSE, TES5VR, ENDERAL, ENDERALSE

[DarkladyLexy]

hey Sheson I have recently installed the A Clear Map of Skyrim and Other Worlds mod I have set Level32=1 in the DynDOLOD_SSE.ini. generation was successful however whenever i go in game I CTD .Netframework crash log indicates the the like problem is "Textures\Terrain\Tamriel\Tamriel.8.-16.-48.DDS", When i look that the winning assets is SEELODGEN_Output. Any advice on how to fix what be helpful.

[sheson]

  On 1/31/2022 at 11:24 AM, DarkladyLexy said:

hey Sheson I have recently installed the A Clear Map of Skyrim and Other Worlds mod I have set Level32=1 in the DynDOLOD_SSE.ini. generation was successful however whenever i go in game I CTD .Netframework crash log indicates the the like problem is "Textures\Terrain\Tamriel\Tamriel.8.-16.-48.DDS", When i look that the winning assets is SEELODGEN_Output. Any advice on how to fix what be helpful.

Expand  

Check the xLODGen log if there were any error or warnings, especially for that particular texture.

Delete it. Generate it again.

The DynDOLOD INI settings are irrelevant when generating anything with xLODGen.

[DarkladyLexy]

  On 1/31/2022 at 12:58 PM, sheson said:

Check the xLODGen log if there were any error or warnings, especially for that particular texture.

Delete it. Generate it again.

The DynDOLOD INI settings are irrelevant when generating anything with xLODGen.

Expand  

Log shows no warnings.

 

I crashes when  I open the map so i wonder if there latest update of A Clear Map of Skyrim and Other Worlds broke something I will inform DoubleYou. I wasn't crashing with v2.0 of that mod so logical say something funky is going on with v2.1

[sheson]

  On 1/31/2022 at 1:19 PM, DarkladyLexy said:

Log shows no warnings.

 

I crashes when  I open the map so i wonder if there latest update of A Clear Map of Skyrim and Other Worlds broke something I will inform DoubleYou. I wasn't crashing with v2.0 of that mod so logical say something funky is going on with v2.1

Expand  

Check if the texture is actually causing the problem. If it is, then there is noting else to do than to delete it and generate it anew.

If the texture is corrupt or invalid and there is no message in the log, then it happened afterwards. For example generating into game or mod manager folders instead of a dedicated output folder outside of game/mod manager folders.

Unless you set texture compression 565 and use Windows 7, there is not really anything in xLODGen/TexConv that can generate an invalid texture without some kind of warning/error.

The texture or its generation with xLODGen has not really anything to do directly with the clear map mod.

[DarkladyLexy]

  On 1/31/2022 at 1:33 PM, sheson said:

Check if the texture is actually causing the problem. If it is, then there is noting else to do than to delete it and generate it anew.

If the texture is corrupt or invalid and there is no message in the log, then it happened afterwards. For example generating into game or mod manager folders instead of a dedicated output folder outside of game/mod manager folders.

Unless you set texture compression 565 and use Windows 7, there is not really anything in xLODGen/TexConv that can generate an invalid texture without some kind of warning/error.

The texture or its generation with xLODGen has not really anything to do directly with the clear map mod.

Expand  

I disable xLODGEN output and was able to open the map no crashing.

I reactived xLODGEN Output and crashed.

I reactived xLODGEN bu removed Tamriel.8.-16.-48.DDS from xLODGEN output and didn't crash.

[sheson]

  On 1/31/2022 at 1:47 PM, DarkladyLexy said:

I disable xLODGEN output and was able to open the map no crashing.

I reactived xLODGEN Output and crashed.

I reactived xLODGEN bu removed Tamriel.8.-16.-48.DDS from xLODGEN output and didn't crash.

Expand  

Just generate the texture anew again by using the specific chunk options.

[DarkladyLexy]

regeneration seems to have fixed it.

[ButchDiavolo]

Hi Sheson,

I have an odd issue which started today. I ran xlodgen 86 which suddenly started throwing out errors in the screen log. This started when it was generating dlc1hunterhqworld and intermittently for all the following worlds.

Example:

  Reveal hidden contents

FAILED (80070003: Het systeem kan het opgegeven pad niet vinden.) [translation: the system can't find the provided path]
[14:21] Error: Executing Texconv failure 80070003: "C:\Games\Skyrim SE AE\Tools\xLODGen 87\Edit Scripts\Texconvx64.exe" -nologo -y -aw 256 -sepalpha  -f BC7_UNORM -bc x -o "c:\games\steam\steamapps\common\skyrim special edition\data\textures\terrain\dlc2apocryphaworld" -flist "C:\Users\Wim\AppData\Local\Temp\SSEEdit\Texconv_DLC2ApocryphaWorld_22_0.txt"

So I checked here and saw there was an update to version 87. Installed that, changed the MO2 path to correctly find xlodgen64.exe and retried. But again it is throwing out these errors. When I check the logs, there is no mention of it. These errors only show up in the screen log as the lodgen is being generated... I had xlodgen terrain extended and xlodgen for Cathedral landscapes activated while generating. To be sure, I redownloaded those files and generated again, but the errors keep occurring. Needless to say, I have no idea what is causing this.

Attached are the logs. I copied the screen log from dlc1hunterhqworld onwards, since before that there were no errors.

Generating screen log.txtFetching info... LODGen_log.txtFetching info...

EDIT: Yeah, so I am a moron. Always fun when you post something and then get an idea that sorts it out. Turns out I had my bashed patch activated as well. Turning that off made the problem disappear *sigh and eyeroll*

Sorry.

Edited February 6, 2022 by ButchDiavolo
Cos I am a moron...

[sheson]

  On 2/6/2022 at 1:46 AM, ButchDiavolo said:

Hi Sheson,

I have an odd issue which started today. I ran xlodgen 86 which suddenly started throwing out errors in the screen log. This started when it was generating dlc1hunterhqworld and intermittently for all the following worlds.

Example:

  Reveal hidden contents

FAILED (80070003: Het systeem kan het opgegeven pad niet vinden.) [translation: the system can't find the provided path]
[14:21] Error: Executing Texconv failure 80070003: "C:\Games\Skyrim SE AE\Tools\xLODGen 87\Edit Scripts\Texconvx64.exe" -nologo -y -aw 256 -sepalpha  -f BC7_UNORM -bc x -o "c:\games\steam\steamapps\common\skyrim special edition\data\textures\terrain\dlc2apocryphaworld" -flist "C:\Users\Wim\AppData\Local\Temp\SSEEdit\Texconv_DLC2ApocryphaWorld_22_0.txt"

So I checked here and saw there was an update to version 87. Installed that, changed the MO2 path to correctly find xlodgen64.exe and retried. But again it is throwing out these errors. When I check the logs, there is no mention of it. These errors only show up in the screen log as the lodgen is being generated... I had xlodgen terrain extended and xlodgen for Cathedral landscapes activated while generating. To be sure, I redownloaded those files and generated again, but the errors keep occurring. Needless to say, I have no idea what is causing this.

Attached are the logs. I copied the screen log from dlc1hunterhqworld onwards, since before that there were no errors.

Generating screen log.txt 1.7 MB · 0 downloads LODGen_log.txt 348.88 kB · 0 downloads

EDIT: Yeah, so I am a moron. Always fun when you post something and then get an idea that sorts it out. Turns out I had my bashed patch activated as well. Turning that off made the problem disappear *sigh and eyeroll*

Sorry.

Expand  

The English version of the error message from the OS is "The system cannot find the path specified". If you search for it you will find that, the OS, Antivirus or some other third party program is preventing write access. 

If disabling a plugin actually has an effect on antivirus it must mean the generated texture is different - e.g. the content of the file is actually different and that is what triggers the anti virus.

As the first post explains, use the -o command line parameter to generate into a dedicated output folder that is not inside game or mod manager folders.

[hanzabu]

hi @sheson and thx for all your amazing tools.
I'm having CTDs with xlodgen 87, can u please post a mirror for the older versions (86)

bugreport.txtFetching info... LODGen_log.txtFetching info...

Edited February 7, 2022 by hanzabu

[sheson]

  On 2/7/2022 at 12:45 PM, hanzabu said:

hi @sheson and thx for all your amazing tools.
I'm having CTDs with xlodgen 87, can u please post a mirror for the older versions (86)

bugreport.txt 71.4 kB · 1 download LODGen_log.txt 97.44 kB · 0 downloads

Expand  

Upload the SSELODGen log.

[hanzabu]

  On 2/7/2022 at 1:07 PM, sheson said:

Upload the SSELODGen log.

Expand  

I'm having a pop up that says waiting, and then lodgen closes to desktop.

log.txtFetching info...

[sheson]

  On 2/7/2022 at 1:18 PM, hanzabu said:

I'm having a pop up that says waiting, and then lodgen closes to desktop.

log.txt 832.65 kB · 3 downloads

Expand  

Run this test version, which should print the LOD Level and coordinates for the error message.

Check if this is a repeatable error happening at the same part of the process.

[hanzabu]

  On 2/7/2022 at 1:41 PM, sheson said:

Run this test version, which should print the LOD Level and coordinates for the error message.

Check if this is a repeatable error happening at the same part of the process.

Expand  

added full logs

log.txtFetching info...

Edited February 7, 2022 by hanzabu

[sheson]

  On 2/7/2022 at 1:52 PM, hanzabu said:

added full logs

log.txt 972.01 kB · 0 downloads

Expand  

Upload bugreport.txt and  answer the question if the error happens at the same part of the process, e.g. check the if the error message "Error saving textures" is for the same LOD level and coordinates / same filename.

If it is make sure the output folder is empty, best delete it so it is create anew and that OS anti virus do not interfere with writing files.