aazz Posted December 13 Posted December 13 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 Author Posted December 13 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 Posted December 13 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 Author Posted December 13 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 Posted December 13 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
aazz Posted December 13 Posted December 13 4 hours ago, aazz said: 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 268.7 kB · 1 download Edit: I selected and ran the entire world and it worked perfectly. Thank you so much. I will attach the log. SSELODGen_log all world.7z
sheson Posted December 14 Author Posted December 14 10 hours ago, aazz said: Edit: I selected and ran the entire world and it worked perfectly. Thank you so much. I will attach the log. SSELODGen_log all world.7z 408.93 kB · 0 downloads Thanks for testing and letting us know.
captainlei1993 Posted December 15 Posted December 15 MarkarthWorld shouldn't appear in the worldspace list if mods like Markarth LOD Unlock is present.
sheson Posted December 15 Author Posted December 15 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.
captainlei1993 Posted December 15 Posted December 15 (edited) 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? Edited December 15 by captainlei1993
sheson Posted December 15 Author Posted December 15 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.
captainlei1993 Posted Sunday at 04:04 PM Posted Sunday at 04:04 PM 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.
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