DynDOLOD 3.00 Alpha 182

[sheson]

5 minutes ago, rileymil said:

Awesome gonna try that setting and run it without the Bruma worldspace as well. In the meantime here are my logs if that would help or interest you pertaining to this issue. Also restarted my computer before that second attempt, the same thing happened so I assume its not any leftover TexGen or other processes. 

Debug Log https://paste.ee/p/qiO4L

Log https://paste.ee/p/3FjAp

Upload the entire log and the entire debug log.

[rileymil]

4 minutes ago, sheson said:

Upload the entire log and the entire debug log.

https://ufile.io/43rghcdx

https://ufile.io/dp7vn940

Here are the full logs, sorry figured it would be easier for you to not have a few thousand lines to go through! 

[Phlunder]

I ran into an issue with Alpha-101 using TexGen for Enderal LE. The process seems to run out of memory with a vanilla texture. Another issue I had with earlier versions as well is that for a few tree types (as statics) that I flagged with Has Tree LOD and given proper bounds, TexGen doesn't generate normals (just flat ones). One example for that would be 000880FA;_00E_TropicalTree_Trunk01. 

Here are the logs.

 

 

[sheson]

17 minutes ago, Phlunder said:

I ran into an issue with Alpha-101 using TexGen for Enderal LE. The process seems to run out of memory with a vanilla texture. Another issue I had with earlier versions as well is that for a few tree types (as statics) that I flagged with Has Tree LOD and given proper bounds, TexGen doesn't generate normals (just flat ones). One example for that would be 000880FA;_00E_TropicalTree_Trunk01. 

Here are the logs.

I have no problem with generating the stitched object LOD texture tropicalfloor which had the error in your log.

If it always the same texture, check if it is valid / upload it.

If it is not always the same texture, see if setting RenderThreads=1 helps.

Do not install the game into special Windows folders like Program Files x86 to avoid issues with OS file permissions, UAC, anti vir etc.

[Phlunder]

6 minutes ago, sheson said:

I have no problem with generating the stitched object LOD texture tropicalfloor which had the error in your log.

If it always the same texture, check if it is valid / upload it.

If it is not always the same texture, see if setting RenderThreads=1 helps.

It is always a different texture, ridgedstonewall and now cavebasewall05. I also set the RenderThreads to 1 in the TexGen_ENDERAL.ini but I get the same error. I'll see if a reboot fixes it, but I never seen that problem before on my system/setup either.

[sheson]

11 minutes ago, Phlunder said:

It is always a different texture, ridgedstonewall and now cavebasewall05. I also set the RenderThreads to 1 in the TexGen_ENDERAL.ini but I get the same error. I'll see if a reboot fixes it, but I never seen that problem before on my system/setup either.

Use the x64 version.

If that does not help add TextureCache=10 to ..\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_ENDERAL.ini

The trunks seemingly having flat normal map seems to be another issue I am looking into.

[Phlunder]

9 minutes ago, sheson said:

Use the x64 version.

If that does not help add TextureCache=10 to ..\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_ENDERAL.ini

The trunks seemingly having flat normal map seems to be another issue I am looking into.

Oh my, I seemed to never have updated my paths in MO2 for DynDOLOD/TexGen for my Enderal setup. Sorry for that. Works fine with x64 version!

[sheson]

10 minutes ago, Phlunder said:

Oh my, I seemed to never have updated my paths in MO2 for DynDOLOD/TexGen for my Enderal setup. Sorry for that. Works fine with x64 version!

Great!

Regarding the flat normalmaps, IIRC this came up before.

For example the Enderal\landscape\Tropical\Vegetation\Trunk01.nif has 0 0 0  tangents/bitangents.
You can also see in NifSkope, that it does not react to direct light, only ambient.

Fix those with NifSkope and they should have nice normal maps generated.

[Phlunder]

13 minutes ago, sheson said:

Great!

Regarding the flat normalmaps, IIRC this came up before.

For example the Enderal\landscape\Tropical\Vegetation\Trunk01.nif has 0 0 0  tangnents/bitangents.
You can also see in NifSkope, that it also does not react to direct light, only ambient.

Fix those with NifSkope and they should have nice normal maps generated.

That indeed fixed it! I just updated tangent space for all of them, not sure if something else is necessary, but looks fine now! Thanks a lot.

[rileymil]

1 hour ago, sheson said:

Try to close the program normally (not kill it) so the log and debug log files are created and upload them.
For next run add RealTimeLog=1 under [DynDOLOD] in ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini

Check if the program still uses CPU.  Check with task manager if there are any LODGen/Texconv processes still running in the background it might be waiting for.

Check if it runs through without enabling the worldspace BSHeartland.

So after an hour and a half (lol) generation was successful with 1. no BSheartland worldspace checked, 2. RealTimeLogs=1 (checked periodically) and 3. an update to Microsoft Visual Studio! 

With that successful, can I now just run DynDOLOD again with only BSHeardland checked, change the name of the necessary output files (heartland esps, and then add the textures/meshes/skse folder to my Tamriel DynDOLOD folder)? Or do I now need to run it with everything checked at once for everywhere to work? I can leave it overnight and see how it does in a few hours if that is the case, but I would prefer the former option if that is a thing. Hope I'm making sense, been a few more hours at this than I was expecting.

[sheson]

1 hour ago, rileymil said:

So after an hour and a half (lol) generation was successful with 1. no BSheartland worldspace checked, 2. RealTimeLogs=1 (checked periodically) and 3. an update to Microsoft Visual Studio! 

With that successful, can I now just run DynDOLOD again with only BSHeardland checked, change the name of the necessary output files (heartland esps, and then add the textures/meshes/skse folder to my Tamriel DynDOLOD folder)? Or do I now need to run it with everything checked at once for everywhere to work? I can leave it overnight and see how it does in a few hours if that is the case, but I would prefer the former option if that is a thing. Hope I'm making sense, been a few more hours at this than I was expecting.

Updating existing DynDOLOD output is always possible. https://dyndolod.info/Updating Do not rename any output files / do not invent instructions.

However, I suggest to let me first investigate and probably fix the problem for the next version as there is no reason for that delay when it generates on-demand textures / it should not try to generate any if source textures are missing.

Edit: Use Alpha-102 for that.

[Francis]

2 hours ago, sheson said:

Moved to the DynDOLOD 3 alpha thread.

The cause is explained in the message. "Broken Tamriel terrain LOD meshes detected." and "Some terrain LOD meshes generated by Oscape have bugs resulting in severe visual issues" - You have installed a mod that contains broken terrain LOD meshes.

How to resolve it is explained in the message. "Permamently remove the broken terrain LOD meshes or use xLODGen to generate terrain LOD meshes to overwrite the broken terrain LOD meshes" - Remove the broken terran LOD meshes or generate valid ones with xLODGen.

As explained in the first post, click the link "Click on this link for additional explanations and help for this message" to open additional help.

https://dyndolod.info/Generation-Instructions#Prerequisites
Typically generate 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.

Thanks, I'm still learning about LODs and these tools. I assumed I had broken some meshes somehow, but really I just had't come across xLODGen in the third party guides I was reading/watching. 

[xcal68]

5 hours ago, sheson said:

Read the first post which entire log and debug log (in this case from TexGen and DynDOLOD) to upload when making posts.

Read the first post which log and debug log to upload when making posts. 

TexGen fixed in 102 - trunks are back.  Thanks.

[Iams]

Hello,

I have just downloaded the latest version of DynDOLOD Alpha 102.

I use MO2, skse 2.2.3, AE 1.6.640 and I linked TexGen and DynDOLOD.

I launched TexGen after having done xLODGen without any problem.

But it gives me "Item not found".

On the help, they recommend to tell it on the support, which I do now

 

TexGen_SSE_Debug_log.txt

[sheson]

10 minutes ago, Iams said:

Hello,

I have just downloaded the latest version of DynDOLOD Alpha 102.

I use MO2, skse 2.2.3, AE 1.6.640 and I linked TexGen and DynDOLOD.

I launched TexGen after having done xLODGen without any problem.

But it gives me "Item not found".

On the help, they recommend to tell it on the support, which I do now

 

TexGen_SSE_Debug_log.txt 520.74 kB · 0 downloads

Read the first post which log and bugreport.txt to also upload when making posts.