Jump to content


Photo

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


  • Please log in to reply
680 replies to this topic

#676 sheson

sheson

    Dragon King

  • Mod Authors
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 4,680 posts

Posted 10 October 2019 - 11:28 AM

I have an issue with the xLODGen step during Lexy's LOTD Guide (was referred here via their discord). It takes far longer than 2h, closer to 12h as far as i can tell (leave it running overnight). The version of xLODGen used is the one from the guide, downloaded via WJ.

 

The issue is reproducible on my set up. On the 2nd attempt I triple checked to make sure only terrain LOD was checked, sse-terrain-tamriel.esm checked, each LOD# set up according to screenshots, etc; same outcome. I have no issues elsewhere in Lexy's guide, and once everything is done modded SSE runs perfectly.

 

PC specs; Ryzen 5 2600X, GTX 1080 8GB, 16GB DDR4 3200mhz RAM, 500GB NVMe SSD, Windows 10. I can also add that when the computer is running xLODGen only, there is barely any CPU utilization in taskmanager/performance. Program is completely responsive though. No errors in the log. The only unusual thing I noticed was that xLODGen takes a long time to switch to the next worldspace (e.g. tamriel -> markarth). 

 

Any help is appreciated.

I do not support 3rd party guides (that means I have no idea what settings or what screenshots you are referring to or what mods are involved).

 

In case the suggestions mentioned below do not help, be specific about the settings, which worldspace the problem happens, maybe the load order and if it is terrain LOD meshes or terrain LOD textures that seem to take a long time. By all accounts it could be normal or not.

 

Obviously use the latest version from the first post. Use the x64 version or vice versa the x86 version.

Make sure the OS settings for its page file are default.

Generate the worldspace that takes a long time separately. The generated output can be merged. It is just meshes and textures in separate folders for each worldspace.


Edited by sheson, 10 October 2019 - 11:30 AM.

  • 0

#677 Disannul

Disannul

    Prisoner

  • Members
  • 4 posts

Posted 10 October 2019 - 01:34 PM

I do not support 3rd party guides (that means I have no idea what settings or what screenshots you are referring to or what mods are involved).

 

In case the suggestions mentioned below do not help, be specific about the settings, which worldspace the problem happens, maybe the load order and if it is terrain LOD meshes or terrain LOD textures that seem to take a long time. By all accounts it could be normal or not.

 

Obviously use the latest version from the first post. Use the x64 version or vice versa the x86 version.

Make sure the OS settings for its page file are default.

Generate the worldspace that takes a long time separately. The generated output can be merged. It is just meshes and textures in separate folders for each worldspace.

Thanks for the rapid response and clarification, ill try to respond to your points.

 

1. Regarding the guide, i think its well known and popular, thus the length of time xLODGen needs in the guide is well known. I mentioned the guide more to state that there may be an issue for me because xLODGen is taking far longer than it is known to do with the modlist. I dont know how to ask your help without the modlist coming up. If you prefer not to help since no support for 3rd party guides (i understand and respect that), ill drop the issue. If not, ive added further details below.

 

2. There is no specfic error in any worldspace during the process according to the log. I belive it is the textures that are the issue; during texture processing it takes about 3h+ to go from Tamriel "skyrim" worldspace to Sovengarde "sovengarde" worldspace. At this point the entire xLODGen process should already be done according to the guide. CPU utilization was very low (around 1 - 5%) during the entire process.

 

Here is an excerpt from the SSELODGen log, which may be of interest. As far as i can tell it states the operation for tamriel worldspace took 36:59 minutes. However the preceeding line shows 45:56 minutes for start of 32.32.32_n.dds. I was watching this step, the 36:59 is referencing the next hour, not cumulative time i believe. Going from start of 32.32.32_n.dds processing to finishing took around 45m, so tamriel processing was around 1h35m. Not sure if this is relevant to the issue though.

 

[45:39] f:\lexy lotd\mods\xlodgen output\textures\terrain\tamriel\tamriel.4.40.60_n.dds
[45:45] f:\lexy lotd\mods\xlodgen output\textures\terrain\tamriel\tamriel.8.40.56_n.dds
[45:51] f:\lexy lotd\mods\xlodgen output\textures\terrain\tamriel\tamriel.16.32.48_n.dds
[45:56] f:\lexy lotd\mods\xlodgen output\textures\terrain\tamriel\tamriel.32.32.32_n.dds
[37:38] Building terrain LOD textures elapsed time: 36:59

[37:39] [MarkarthWorld] Generating Terrain LOD

 

3. Settings are as follows; xLODGen opened via MO2 with the argument "-sse -o:"F:\Lexy LOTD\mods\xLODGen Output"", all worldspaces selected from the guide, Terrian LOD generation only option checked. Within terrain LOD, for the following LODs (4,8,16,32)

 

x-LODSettings.jpg

  • mesh quality 5,10,10,15 respectively
  • diffuse size 512,256,256,256 respectively
  • protect borders for LOD4
  • Optimize unseen for LOD32 at 550, on for LOD8,16
  • all other settings seen in screenshot are consistent across the LODs

4. This issue was reproduced on version v Beta 51 the 1st time, and Beta 55 the 2nd time, 3rd partial attempt was again made on beta 55 but i canceled it since same issue. All versions were x64, my windows is x64

 

5. OS settings are majority default except for disabling of permission like location, camera, etc. Page file is 4GB on OS SSD.

 

I hope this helps clarify the issue!


Edited by Disannul, 10 October 2019 - 01:40 PM.

  • 0

#678 sheson

sheson

    Dragon King

  • Mod Authors
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 4,680 posts

Posted 10 October 2019 - 04:08 PM

Thanks for the rapid response and clarification, ill try to respond to your points.

 

1. Regarding the guide, i think its well known and popular, thus the length of time xLODGen needs in the guide is well known. I mentioned the guide more to state that there may be an issue for me because xLODGen is taking far longer than it is known to do with the modlist. I dont know how to ask your help without the modlist coming up. If you prefer not to help since no support for 3rd party guides (i understand and respect that), ill drop the issue. If not, ive added further details below.

 

2. There is no specfic error in any worldspace during the process according to the log. I belive it is the textures that are the issue; during texture processing it takes about 3h+ to go from Tamriel "skyrim" worldspace to Sovengarde "sovengarde" worldspace. At this point the entire xLODGen process should already be done according to the guide. CPU utilization was very low (around 1 - 5%) during the entire process.

 

Here is an excerpt from the SSELODGen log, which may be of interest. As far as i can tell it states the operation for tamriel worldspace took 36:59 minutes. However the preceeding line shows 45:56 minutes for start of 32.32.32_n.dds. I was watching this step, the 36:59 is referencing the next hour, not cumulative time i believe. Going from start of 32.32.32_n.dds processing to finishing took around 45m, so tamriel processing was around 1h35m. Not sure if this is relevant to the issue though.

 

[45:39] f:\lexy lotd\mods\xlodgen output\textures\terrain\tamriel\tamriel.4.40.60_n.dds
[45:45] f:\lexy lotd\mods\xlodgen output\textures\terrain\tamriel\tamriel.8.40.56_n.dds
[45:51] f:\lexy lotd\mods\xlodgen output\textures\terrain\tamriel\tamriel.16.32.48_n.dds
[45:56] f:\lexy lotd\mods\xlodgen output\textures\terrain\tamriel\tamriel.32.32.32_n.dds
[37:38] Building terrain LOD textures elapsed time: 36:59

[37:39] [MarkarthWorld] Generating Terrain LOD

 

3. Settings are as follows; xLODGen opened via MO2 with the argument "-sse -o:"F:\Lexy LOTD\mods\xLODGen Output"", all worldspaces selected from the guide, Terrian LOD generation only option checked. Within terrain LOD, for the following LODs (4,8,16,32)

 

x-LODSettings.jpg

  • mesh quality 5,10,10,15 respectively
  • diffuse size 512,256,256,256 respectively
  • protect borders for LOD4
  • Optimize unseen for LOD32 at 550, on for LOD8,16
  • all other settings seen in screenshot are consistent across the LODs

4. This issue was reproduced on version v Beta 51 the 1st time, and Beta 55 the 2nd time, 3rd partial attempt was again made on beta 55 but i canceled it since same issue. All versions were x64, my windows is x64

 

5. OS settings are majority default except for disabling of permission like location, camera, etc. Page file is 4GB on OS SSD.

 

I hope this helps clarify the issue!

Running time is not an indicator of anything really. The log will tell you if there are errors and completion messages tell what parts have been completed.

 

xLODGen is multithreaded. Building LOD texures done on the CPU, conversion to the final textures format is done in the background with TexConv which uses the GPU. So it is normal that at times CPU usage is low while the saving and TexConv thread is still working. There is total timer and a job timer.

 

Generate large worldspaces separately. Solstheim is the biggest, then Tamriel. Then you can probably do the remaining in one go.

The generated output can be merged. It is just meshes and textures in separate folders for each worldspace.

 

Test with the x86 version.


  • 1

#679 Disannul

Disannul

    Prisoner

  • Members
  • 4 posts

Posted 10 October 2019 - 05:05 PM

Running time is not an indicator of anything really. The log will tell you if there are errors and completion messages tell what parts have been completed.

 

xLODGen is multithreaded. Building LOD texures done on the CPU, conversion to the final textures format is done in the background with TexConv which uses the GPU. So it is normal that at times CPU usage is low while the saving and TexConv thread is still working. There is total timer and a job timer.

 

Generate large worldspaces separately. Solstheim is the biggest, then Tamriel. Then you can probably do the remaining in one go.

The generated output can be merged. It is just meshes and textures in separate folders for each worldspace.

 

Test with the x86 version.

Thanks, will test by generating and merging the worldspaces, and x86.


  • 0

#680 Disannul

Disannul

    Prisoner

  • Members
  • 4 posts

Posted Today, 06:11 AM

With further testing (same settings as previously);
 
x64 version; same result with inidvidual worldspace generation. Both tamriel and solstheim take around 2-3h individually. No errors, just very slow
 
x86 version; both tamriel and solstheim generation produces memory errors

Tamriel Log

 
Solstheim Error


Edited by Disannul, Today, 06:14 AM.

  • 0

#681 sheson

sheson

    Dragon King

  • Mod Authors
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 4,680 posts

Posted Today, 06:42 AM

With further testing (same settings as previously);
 
x64 version; same result with inidvidual worldspace generation. Both tamriel and solstheim take around 2-3h individually. No errors, just very slow


While it seems long, it could be totally normal for your hardware, OS settings and selected options. You could try to manually change (raise) priority in the task manager.


Edited by sheson, Today, 06:44 AM.

  • 0


3 user(s) are reading this topic

0 members, 2 guests, 0 anonymous users


    Google (1)