DynDOLOD 3.00 Alpha 180

[sheson]

3 hours ago, kn1ghtradiant said:

That was it, thanks! I updated the drivers which didn't help but the new .exe worked perfectly.

Great. Can you also test this version if it still works? https://mega.nz/file/5BgHGbKT#LRe05xEQEpV4uXpZSEv6LuJaUK-g9fEvBvsnZJFYcfU

[MITSUYOMI]

hey just a quick question, upon checking the log file when running dyndolod.exe, there is a warning that indicates that a file does not adhere to file naming conventions. Does this affect the output LOD? 

[z929669]

56 minutes ago, MITSUYOMI said:

hey just a quick question, upon checking the log file when running dyndolod.exe, there is a warning that indicates that a file does not adhere to file naming conventions. Does this affect the output LOD? 

An example of this is Veydogolt Trees, and I haven't found any problems affecting the DynDOLOD outcome other than the log warnings; however, I suspect this could preclude such mods benefiting from certain DynDOLOD features now or added in the future (in addition to being bad practice in general).

That mod has bark normals named like treepineforestbarkcomp_pine_9N.dds and branch textures named like Spruce05_Normal.dds

[sheson]

1 hour ago, MITSUYOMI said:

hey just a quick question, upon checking the log file when running dyndolod.exe, there is a warning that indicates that a file does not adhere to file naming conventions. Does this affect the output LOD? 

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

Read the explanations for the message https://dyndolod.info/Messages/Filename-Does-Not-Adhere-To-File-Naming-Conventions

If this affects visuals depends if the normal map texture file name is a typo or if in fact a non normal map texture has been assigned to a texture slot meant for normal map textures. If there are visuals issues, they can range from not being noticeable to being very noticeable.

Processes expect normal map textures to end in *_n.dds or vice versa filenames ending in *_n.dds to be a normal map texture.

[ysrwho]

hello, can i have some help please? Texgen suddenly stops working when creating textures. No error, no freezing, no crashing, it just stops generating. I waited for hours but it didn't continue. When it starts generating "brick012lod.dds" it just stops. I tried deleting the file from Dyndolod Resources but no solution, "brick012lod.dds" showed up and it stopped again. I'm putting texgen log below. What should i do?

TexGen 3.0 Alpha-122 x64 - Skyrim S.txt

[sheson]

2 hours ago, ysrwho said:

hello, can i have some help please? Texgen suddenly stops working when creating textures. No error, no freezing, no crashing, it just stops generating. I waited for hours but it didn't continue. When it starts generating "brick012lod.dds" it just stops. I tried deleting the file from Dyndolod Resources but no solution, "brick012lod.dds" showed up and it stopped again. I'm putting texgen log below. What should i do?

Read the first post which debug log to also upload.

Check the task manager if TexGen is waiting for any background Texconv processes.

Make a clean install of the latest graphics drivers only without any crapware or terminate it before running TexGen.

[ysrwho]

12 hours ago, sheson said:

Read the first post which debug log to also upload.

Check the task manager if TexGen is waiting for any background Texconv processes.

Make a clean install of the latest graphics drivers only without any crapware or terminate it before running TexGen.

I reinstalled my graphics drivers, it didn't work. Checked the task manager, texconv is running but doesn't do anything. But i tried DynDOLOD 2.98 and it's texgen worked perfectly, no stopping or error or anything. DynDOLOD 3 is the problem. Debug log is bigger than 3mb, its 13,5mb. How do i put my debug log here?

[sheson]

45 minutes ago, ysrwho said:

I reinstalled my graphics drivers, it didn't work. Checked the task manager, texconv is running but doesn't do anything. But i tried DynDOLOD 2.98 and it's texgen worked perfectly, no stopping or error or anything. DynDOLOD 3 is the problem. Debug log is bigger than 3mb, its 13,5mb. How do i put my debug log here?

 Read the first post how to zip and use a file service to upload the log and debug log files.

Obviously there is an issue with Texconv, which is not able to do its thing may be because of OS, UAC, anti vir preventing file access or some trouble with the graphics card/driver or 3rd party crapware  preventing it from compressing textures. Maybe the best/real graphics card is not the first one reported by the OS. If you kill the texconv process the TexGen/DynDOLOD will most likely continue with an error message.

[ysrwho]

3 hours ago, sheson said:

 Read the first post how to zip and use a file service to upload the log and debug log files.

Obviously there is an issue with Texconv, which is not able to do its thing may be because of OS, UAC, anti vir preventing file access or some trouble with the graphics card/driver or 3rd party crapware  preventing it from compressing textures. Maybe the best/real graphics card is not the first one reported by the OS. If you kill the texconv process the TexGen/DynDOLOD will most likely continue with an error message.

I turned off windows firewall and i ran texgen again. Now it stops generating when it comes to "falmerhutlod" or something, which is different than the previous one. I don't know if it's related to the os because this problem only happened in my new modlist, i was using dyndolod without any problem three months ago with my old modlist. Also tried to kill texconv process and texgen sent an error message like you said. Debug log uploaded.

TexGen_SSE_Debug_log.rar

Edited March 31, 2023 by ysrwho

[WizardPie]

So, I was trying to run TexGen, and got the following error: framebuffer objects unsupported. Here is the debug log for one of these attempts: [ https://paste.ee/p/2HlXe ] I tried this multiple times, and it was not always ridgedstone08patternlod that it failed on, it was seemingly random as to when it would fail.

So, after searching this forum for a while, I figured I would update my graphics driver, as you seemed to have suggested that to others, however, instead of fixing the problem, this only made things worse. Now when I try to run TexGen,  as soon as it starts on the 'creating textures' section, it immediately crashes without even creating a debug log. Please help.

Edit: I was able to fix the crashing issue, which happened to be due to a setting in the geforce control panel. However, the 'framebuffer objects unsupported' problem is still present.

(p.s. I couldn't figure out how to edit the original post, sorry)

[sheson]

8 hours ago, ysrwho said:

I turned off windows firewall and i ran texgen again. Now it stops generating when it comes to "falmerhutlod" or something, which is different than the previous one. I don't know if it's related to the os because this problem only happened in my new modlist, i was using dyndolod without any problem three months ago with my old modlist. Also tried to kill texconv process and texgen sent an error message like you said. Debug log uploaded.

TexGen_SSE_Debug_log.rar 637.6 kB · 1 download

Replace Texconvx64.exe in the ..\DynDOLOD\Edit Scripts\ folder with this version https://mega.nz/file/QERUxLaB#wr0QIq9BKLqVAhxIwRlINoVBkUkiY_vxH9fJCytA_cU and let us know what happens. Delete all files in the log folder in order to have clean logs. If problem persists upload new log and debug log.

[sheson]

6 hours ago, WizardPie said:

So, I was trying to run TexGen, and got the following error: framebuffer objects unsupported. Here is the debug log for one of these attempts: [ https://paste.ee/p/2HlXe ] I tried this multiple times, and it was not always ridgedstone08patternlod that it failed on, it was seemingly random as to when it would fail.

So, after searching this forum for a while, I figured I would update my graphics driver, as you seemed to have suggested that to others, however, instead of fixing the problem, this only made things worse. Now when I try to run TexGen as soon as it starts on the 'creating textures' section, it immediately crashes without even creating a debug log. Please help.

Edit: I was able to fix the crashing issue, which happened to be due to a setting in the geforce control panel. However, the 'framebuffer objects unsupported' problem is still present.

(p.s. I couldn't figure out how to edit the original post, sorry)

Upload the new log and debug log and bugreport.txt (if it exists) for the updated driver.

Let us know what setting you changed in the Geforce control panel.

Edit ..\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.INI in Notepad and add GLListDebug=1 and GLDebug=1 under [TexGen]. Delete old logs and bugreport.txt and then run again. Upload that log and debug and bugreport.txt if it exists as well.

[WizardPie]

Well, the setting was: Allow access to the GPU performance counters to all users

However, that seems to have been a temporary fix, because now it went back to crashing(which results in no logs whatsoever for some reason). So now I rolled back the driver, which stops the crashing but still gives the error. Here are the fresh logs after adding

GLListDebug=1

GLDebug=1

to TexGen_SSE.ini, there is no bugreport.txt though

Logs.7z

[sheson]

1 hour ago, WizardPie said:

Well, the setting was: Allow access to the GPU performance counters to all users

However, that seems to have been a temporary fix, because now it went back to crashing(which results in no logs whatsoever for some reason). So now I rolled back the driver, which stops the crashing but still gives the error. Here are the fresh logs after adding

GLListDebug=1

GLDebug=1

to TexGen_SSE.ini, there is no bugreport.txt though

Logs.7z 220.61 kB · 0 downloads

Check the Windows event log for related messages to crashes without log. It typically means the tool is being terminated. In that case also add RealTimeLog=1 to the INI.

In any case, run this test version of TexGenx64.exe https://mega.nz/file/xBATGDxT#09spFHG99r0lPVz9DRrQ_UBuzheFe1pWgeZkeezS7wk with GLListDebug=1 and GLDebug=1. Clear out the log folder first. Upload the new log, debug log and bugreport.txt if it exists.

[ysrwho]

9 hours ago, sheson said:

Replace Texconvx64.exe in the ..\DynDOLOD\Edit Scripts\ folder with this version https://mega.nz/file/QERUxLaB#wr0QIq9BKLqVAhxIwRlINoVBkUkiY_vxH9fJCytA_cU and let us know what happens. Delete all files in the log folder in order to have clean logs. If problem persists upload new log and debug log.

This time it stopped at "icefrozen03lod.dds", different texture again. I tried moving dyndolod resources in my load order (highest priority) but it didn't work too. Log and debug log uploaded.

Logs.rar