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

[Parisienne]

Hi there. Has anyone come across this issue? I have been looking for a solution but have been unable to find one. 

https://imgur.com/a/Xjo6OKb

Thank you.

LODGen_log.txt

Edited November 8 by Parisienne

[sheson]

23 minutes ago, Parisienne said:

Hi there. Has anyone come across this issue? I have been looking for a solution but have been unable to find one. 

https://imgur.com/a/Xjo6OKb

Thank you.

LODGen_log.txt 617.32 kB · 0 downloads

You upload the LODGen_log.txt and not the SSELODGen_log.txt that would show the xLODGen log messages that includes the terrain LOD texture generation.
The screenshot probably shows mixing of terrain LOD textures that were made for different load orders.

Read the first post and the Readme.txt included in download archive how to always set a dedicated output folder outside of the the games data folder with the -o command line argument and install the generated output as mod.

[Parisienne]

Quote

The screenshot probably shows mixing of terrain LOD textures that were made for different load orders.

Thank you, It's a fresh set up for a new skyrim playthrough but even still, I've somehow managed to generate terrain texture files in the skyrim root directory. I was using MO2 "create files in mod instead of overwrite" but I'll switch to the -o command. Appreciate the quick help!

[SuzanoSho]

For usage with FO4, I keep getting "no modules found in data folder"

My Fallout 4 installation is here "E:\Fallout 4 GOTY\".
I've tried setting -d "E:\Fallout 4 GOTY\Data" as an arguement in both Vortex and on a desktop shortcut for the program, same result.
The log states the following (I've replaced the name of the user folder with asterisks):

 

FO4LODGen 4.1.5k EXTREMELY EXPERIMENTAL Terrain LOD Beta (826AB10F) starting session 2024-11-13 22:55:12

The Source Code Form of this program is subject to the terms of the Mozilla Public License, v. 2.0
If a copy of the MPL was not distributed with this file, You can obtain one at https://mozilla.org/MPL/2.0/.

The Source Code Form is available at https://github.com/TES5Edit/TES5Edit

Using Fallout4 Data Path: \
Using Scripts Path: E:\FO4LODGen\Edit Scripts\
Using ini: C:\Users\*****\Documents\My Games\Fallout4\Fallout4.ini
Using custom ini: C:\Users\****\Documents\My Games\Fallout4\Fallout4Custom.ini
Using save path: C:\Users\****\Documents\My Games\Fallout4\Saves\
Using plugin list: C:\Users\****\AppData\Local\Fallout4\Plugins.txt
Using settings file: C:\Users\****\AppData\Local\Fallout4\Plugins.fo4viewsettings
Using language: En
Using general string encoding: 1252  (ANSI - Latin I)
Using translatable string encoding: 1252  (ANSI - Latin I)
Using VMAD string encoding: 65001 (UTF-8)
Loading active plugin list: C:\Users\****\AppData\Local\Fallout4\Plugins.txt

EDIT: Nvm, I'm an idiot. Please disregard. I was just forgetting to include the colon (:) in the argument and was putting a space instead.

Edited November 14 by SuzanoSho

[Drugspirta]

Hi,

In my Skyrim AE 1.6.1170 after a successful XLODGen + TexGen + DynDOLOD outputs generation I see distanced terrain textures as black ones with crosses.

https://imgur.com/a/ZiURpNC

 

I'm using custom textures from Nexus, 

when I come closer - they are being rendered correctly.

LOD generation logs:

TexGen_SSE_log: https://ufile.io/7plviscy
DynDOLOD_SSE_log: https://ufile.io/a9ycjywh
TexGen_SSE_Debug_log: https://ufile.io/c166n9dg
DynDOLOD_SSE_Debug_log: https://ufile.io/qr04tgxu

I also have terrain LOD generated via XLODGen and a grass cache, 
XLODGen terrain generation log: https://ufile.io/n48kwy1c
My last mods load order are XLODGen output -> TexGen output -> DynDOLOD output.

 

Please help to understand how to fix it,

Thanks.

[sheson]

1 hour ago, Drugspirta said:

Hi,

In my Skyrim AE 1.6.1170 after a successful XLODGen + TexGen + DynDOLOD outputs generation I see distanced terrain textures as black ones with crosses.

https://imgur.com/a/ZiURpNC

 

I'm using custom textures from Nexus, 

when I come closer - they are being rendered correctly.

LOD generation logs:

TexGen_SSE_log: https://ufile.io/7plviscy
DynDOLOD_SSE_log: https://ufile.io/a9ycjywh
TexGen_SSE_Debug_log: https://ufile.io/c166n9dg
DynDOLOD_SSE_Debug_log: https://ufile.io/qr04tgxu

I also have terrain LOD generated via XLODGen and a grass cache, 
XLODGen terrain generation log: https://ufile.io/n48kwy1c
My last mods load order are XLODGen output -> TexGen output -> DynDOLOD output.

Please help to understand how to fix it,

Thanks.

TexGen and DynDOLOD are irrelevant for terrain LOD.

You only uploaded the LODGen_log.txt which shows terrain LOD meshes generation, which is already included in the xLODGen messages log that is saved as SSELODGen_log.txt. Upload that file to show all terrain LOD generation including the textures.

To take useful screenshots of LOD, use tfc to fly to the LOD area and higher. The map might show the same prpblem.

If the terrain LOD textures generated by xLODGen are dark, it is either because of the full terrain textures, modified brightness, contrast gamma settings or an issue with the terrain LOD normal map textures. Obviously load a terrain LOD diffuse and normal map texture in an image viewer to check their apprance .
If terrain LOD is only wrong in the game, then terrain LOD textures might be missing or there is an issue with the noise.dds texture.

[Drugspirta]

On 11/25/2024 at 8:03 AM, sheson said:

On 11/25/2024 at 8:03 AM, sheson said:

TexGen and DynDOLOD are irrelevant for terrain LOD.

You only uploaded the LODGen_log.txt which shows terrain LOD meshes generation, which is already included in the xLODGen messages log that is saved as SSELODGen_log.txt. Upload that file to show all terrain LOD generation including the textures.

To take useful screenshots of LOD, use tfc to fly to the LOD area and higher. The map might show the same prpblem.

If the terrain LOD textures generated by xLODGen are dark, it is either because of the full terrain textures, modified brightness, contrast gamma settings or an issue with the terrain LOD normal map textures. Obviously load a terrain LOD diffuse and normal map texture in an image viewer to check their apprance .
If terrain LOD is only wrong in the game, then terrain LOD textures might be missing or there is an issue with the noise.dds texture.

 

Thanks sheson, I fixed it by regenerating Terrain LOD  with default values. Thanks for tfc hint tho.

[ExquisiteLemon]

Just recently updated and reran my DynDOLOD, just curious on if I need to run it again based on the steps I took since it’s been a while.

 

1.  Ran xLODgen to generate LODS, ran fine and installed new output.  DID NOT update DynDOLOD scripts or resources files beforehand (because I didn’t think about it).

2.  Uninstalled old script and resources for DynDOLOD and downloaded and installed current versions as well as new version of DynDOLOD

3. Ran TexGen and DynDOLOD and installed each output respectfully.

 

Do the old resources and script versions for DynDOLOD matter in regard to having them be installed when running xLODgen?

[sheson]

43 minutes ago, ExquisiteLemon said:

Just recently updated and reran my DynDOLOD, just curious on if I need to run it again based on the steps I took since it’s been a while.

1.  Ran xLODgen to generate LODS, ran fine and installed new output.  DID NOT update DynDOLOD scripts or resources files beforehand (because I didn’t think about it).

2.  Uninstalled old script and resources for DynDOLOD and downloaded and installed current versions as well as new version of DynDOLOD

3. Ran TexGen and DynDOLOD and installed each output respectfully.

Do the old resources and script versions for DynDOLOD matter in regard to having them be installed when running xLODgen?

No.

The only connection between terrain LOD meshes generated by xLODGen and object LOD meshes generation by DynDOLOD is this:
https://dyndolod.info/Generation-Instructions#Prerequisites
Typically generate and install terrain LOD meshes and textures with xLODGen before generating the LOD mod with DynDOLOD, as the terrain LOD meshes are used to optimize object LOD meshes.

[aazz]

hello
Could you please help me with this problem??

If you look at the log 
[03:08] <Warning: Cache timeout loading texture Textures\Landscape\parallax\ReachMossyRocks01.dds>
[03:08] <Warning: Error loading texture Textures\Landscape\parallax\ReachMossyRocks01.dds>
An error occurs like this.
The problem is not that this error occurs only in one or two textures, but that this error occurs in almost all landscape textures.
If I ignore the error, run xlodgen all the way, run dyndolod, and then enter the game, the textures from the landscape mod won't apply on midload and look ugly.

I thought it might be a problem with the texture mod, so I tried changing to a different mod, but the same error occurred.
In addition, I added it to the exclusion list in the Windows antivirus settings and tried running it in Windows 8 in the compatibility section.
I also tried reinstalling Visual C++ and reinstalling the graphics card driver just in case.

Could you please help me with this issue??

SSELODGen_log.7z LODGen_log.txt

[sheson]

6 hours ago, aazz said:

hello
Could you please help me with this problem??

If you look at the log 
[03:08] <Warning: Cache timeout loading texture Textures\Landscape\parallax\ReachMossyRocks01.dds>
[03:08] <Warning: Error loading texture Textures\Landscape\parallax\ReachMossyRocks01.dds>
An error occurs like this.
The problem is not that this error occurs only in one or two textures, but that this error occurs in almost all landscape textures.
If I ignore the error, run xlodgen all the way, run dyndolod, and then enter the game, the textures from the landscape mod won't apply on midload and look ugly.

I thought it might be a problem with the texture mod, so I tried changing to a different mod, but the same error occurred.
In addition, I added it to the exclusion list in the Windows antivirus settings and tried running it in Windows 8 in the compatibility section.
I also tried reinstalling Visual C++ and reinstalling the graphics card driver just in case.

Could you please help me with this issue??

SSELODGen_log.7z 408.42 kB · 1 download LODGen_log.txt 821.26 kB · 1 download

Test if there is anything different with this test version https://mega.nz/file/QU5SCACC#GVBVfhDeNWjZZAyPpzx6thB879VtQuSNvs0ve0xKOWA

If not, test what happens if you start xEdit, start the Asset Browser with CTRL+F3, filter for a mentioned texture from the log, right click it in the list as select "Save As" from the first mentioned container.

[aazz]

42 minutes ago, sheson said:

Test if there is anything different with this test version https://mega.nz/file/QU5SCACC#GVBVfhDeNWjZZAyPpzx6thB879VtQuSNvs0ve0xKOWA

If not, test what happens if you start xEdit, start the Asset Browser with CTRL+F3, filter for a mentioned texture from the log, right click it in the list as select "Save As" from the first mentioned container.

I tried both methods, but the same error occurs.

Edited December 13 by aazz

[sheson]

15 minutes ago, aazz said:

I tried both methods, but the same error occurs.

Upload the xEdit log or at least the error message from xEdit.

If xEdit also has an error saving the texture, then there is a problem with the container (BSA) it is in or with accessing the BSA or the loose file itself (container = Data).

So either the BSA is invalid or corrupt or access to file is being interfered with by the OS, antivir or other 3rd party program. Try rebooting. If using MO2, enable its debug log and check it for related entries/messages.

[aazz]

1 hour ago, sheson said:

xEdit 로그나 적어도 xEdit의 오류 메시지를 업로드하세요.

xEdit에서 텍스처를 저장하는 동안 오류가 발생하면 컨테이너(BSA)에 문제가 있거나 BSA 또는 느슨한 파일 자체(컨테이너 = 데이터)에 액세스하는 데 문제가 있습니다.

따라서 BSA가 잘못되었거나 손상되었거나 OS, 바이러스 백신 또는 기타 타사 프로그램이 파일 액세스를 방해하고 있습니다. 재부팅을 시도하세요. MO2를 사용하는 경우 디버그 로그를 활성화하고 관련 항목/메시지를 확인하세요.

There is no error while saving the texture in xEdit. However, if you click “save as” to save the texture and run xlodgen, the same Cache timeout loading texture error occurs.
They said there may be a problem with the bsa file, so I reinstalled Skyrim, rebooted the computer, terminated all processes, ran only mo2, and ran xlodgen, but the same error message occurred.

[sheson]

19 minutes ago, aazz said:

There is no error while saving the texture in xEdit. However, if you click “save as” to save the texture and run xlodgen, the same Cache timeout loading texture error occurs.
They said there may be a problem with the bsa file, so I reinstalled Skyrim, rebooted the computer, terminated all processes, ran only mo2, and ran xlodgen, but the same error message occurred.

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?