sheson Posted November 25, 2024 Author Posted November 25, 2024 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. 1
Drugspirta Posted November 26, 2024 Posted November 26, 2024 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 Posted November 30, 2024 Posted November 30, 2024 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 Posted November 30, 2024 Author Posted November 30, 2024 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 Posted December 13, 2024 Posted December 13, 2024 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 Posted December 13, 2024 Author Posted December 13, 2024 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 Posted December 13, 2024 Posted December 13, 2024 (edited) 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, 2024 by aazz
sheson Posted December 13, 2024 Author Posted December 13, 2024 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 Posted December 13, 2024 Posted December 13, 2024 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 Posted December 13, 2024 Author Posted December 13, 2024 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?
aazz Posted December 13, 2024 Posted December 13, 2024 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.
sheson Posted December 13, 2024 Author Posted December 13, 2024 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.
aazz Posted December 13, 2024 Posted December 13, 2024 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
sheson Posted December 13, 2024 Author Posted December 13, 2024 37 minutes ago, aazz said: thank you This is a log that was executed with only tamriel and lod4 selected. SSELODGen_log.7z 253.57 kB · 1 download Test what happens with this test version https://mega.nz/file/tZxlxQBK#4DQJky2f3TwQzwcDjdlzZOjEVtS_TgZ7K0Q2zFn6CCc Upload new log also in case the issue does not happen anymore.
aazz Posted December 13, 2024 Posted December 13, 2024 1 hour ago, sheson said: Test what happens with this test version https://mega.nz/file/tZxlxQBK#4DQJky2f3TwQzwcDjdlzZOjEVtS_TgZ7K0Q2zFn6CCc Upload new log also in case the issue does not happen anymore. This is the log of running the newly uploaded test version with only tamriel selected. It worked normally without error. Thank you very much. Now let's select all worlds and run it. SSELODGen_log (2).7z
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now