DynDOLOD 3.00 Alpha 198

[Enhab]

2 hours ago, sheson said:

Read the first post which debug logs to also upload.

Check the task manager for background Texconv processes. See if terminating it makes the tool continue with an related error message.

Make a clean install of the latest driver release version only, do not install any of the crapware, clean out the log folder and remove old bugreport.txt and generate again. If problem persists upload new log, debug log and bugreport.txt if it exists.

Latest driver (AMD), no software. Cleaned the log folder, removed the bug report and tried generating again. I checked task manager when it froze, but TexConv wasn't there. Here are the smaller logs and here are the debug logs

Edit: That file sharing service turned it into an exe, which is sus as hell, so here's a Google Drive link.

Edited April 2, 2023 by Enhab

[sheson]

1 hour ago, Enhab said:

Latest driver (AMD), no software. Cleaned the log folder, removed the bug report and tried generating again. I checked task manager when it froze, but TexConv wasn't there. Here are the smaller logs and here are the debug logs

Edit: That file sharing service turned it into an exe, which is sus as hell, so here's a Google Drive link.

Edit ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini in notepad and add GLListDebug=1 and GLDebug=1 right under [DynDOLOD].
Remove old logs and bugreport.txt and run again. Upload new log, debug log and bugreport.txt if it exists.

[Enhab]

8 hours ago, sheson said:

Edit ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini in notepad and add GLListDebug=1 and GLDebug=1 right under [DynDOLOD].
Remove old logs and bugreport.txt and run again. Upload new log, debug log and bugreport.txt if it exists.

Here are the new logs after adding those lines: https://paste.ee/p/kcWwO https://drive.google.com/file/d/1eYxZL_Hqt-RH5m9PWhWMAUmzs5K2HZVY/view?usp=sharing

[sheson]

1 hour ago, Enhab said:

Here are the new logs after adding those lines: https://paste.ee/p/kcWwO https://drive.google.com/file/d/1eYxZL_Hqt-RH5m9PWhWMAUmzs5K2HZVY/view?usp=sharing

Remove old bugreport and logs and keep the changed INI settings, then see if there is anything different with this test version https://mega.nz/file/8dgERZDB#KmxMDvHOeToIPrWeE8e0aasvf1AeWJ3u6B2KJ3RRtOk, upload new bugreportr, log and debug log. Since the error only happens in DynDOLOD, no need to rerun or upload logs from TexGen.

[Enhab]

38 minutes ago, sheson said:

Remove old bugreport and logs and keep the changed INI settings, then see if there is anything different with this test version https://mega.nz/file/8dgERZDB#KmxMDvHOeToIPrWeE8e0aasvf1AeWJ3u6B2KJ3RRtOk, upload new bugreportr, log and debug log. Since the error only happens in DynDOLOD, no need to rerun or upload logs from TexGen.

It didn't stop this time, but eventually I got multiple "Please wait a moment" popups and then an error. Here are the logs: https://paste.ee/p/a1WH2 https://drive.google.com/file/d/1TFCATGHn1WSnCXNbzpnf5o9X3bMFypgc/view?usp=sharing

[sheson]

25 minutes ago, Enhab said:

It didn't stop this time, but eventually I got multiple "Please wait a moment" popups and then an error. Here are the logs: https://paste.ee/p/a1WH2 https://drive.google.com/file/d/1TFCATGHn1WSnCXNbzpnf5o9X3bMFypgc/view?usp=sharing

Add RenderSingle=1 under [DynDOLOD] in the ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini, delete old logs etc, run again, upload new logs.

[Enhab]

28 minutes ago, Enhab said:

It didn't stop this time, but eventually I got multiple "Please wait a moment" popups and then an error. Here are the logs: https://paste.ee/p/a1WH2 https://drive.google.com/file/d/1TFCATGHn1WSnCXNbzpnf5o9X3bMFypgc/view?usp=sharing

I ended up restarting my computer and running it again, and it froze again this time. Here are the logs: https://paste.ee/p/WrvJu https://drive.google.com/file/d/1qmpRikdEtieOhYESdT6Bqmdi9eKhT0gw/view?usp=sharing

Edit: Only just now saw your reply. I'll add the line and try again.

Edited April 2, 2023 by Enhab

[Enhab]

43 minutes ago, sheson said:

Add RenderSingle=1 under [DynDOLOD] in the ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini, delete old logs etc, run again, upload new logs.

I added the line and ran it again, and it finished! Here are the logs: https://paste.ee/p/qBLWx https://drive.google.com/file/d/1Eo6VysRNxVT373J1mcNq3Z01jis5e76i/view?usp=sharing

I ran it again just to be sure, and yep, looks like it's working fine now. Thanks for your help!

What was the issue? Just curious.

[ysrwho]

On 4/2/2023 at 1:11 AM, sheson said:

That means there must be a problem with DirectX (DirectCompute), which Texconv uses for BC7 compressions. BC1/BC3 are done with the CPU.

If you edit ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini and change to these values for the object and tree LOD atlas they will be done with the BC1/BC3 compression as well:
ObjectLODDiffuseFormat=200
ObjectLODAlphaDiffuseFormat=202
ObjectLODNormalFormat=200
TreeLODDiffuseFormat=202

See if you can update or repair DirectX or try a clean install of the latest release driver again.

I tried to repair my drivers, clean install etc. and nothing worked, still same issue. But i can generate textures in other formats and dyndolod is working too, so i don't think i will try to fix bc7 anymore. Now i can look at distant objects without my eyes bleeding. Thank you so much for your help! Have a wonderful day!

[Phlunder]

Just a short question regarding the DynDOLOD Resources 3 Alpha-32 for LE. The passthru LODs for vanilla trees don't use the generated trunk billboards, and don't create crown textures from the full ones. They still use the prepared atlas in Textures\DynDOLOD\lod\dyndolodtreelod.dds. The SE resources have the correct passthru meshes. No logs, just wanted to ask if its intended that the LE resources didn't get the latest passthru meshes.

[sheson]

50 minutes ago, Phlunder said:

Just a short question regarding the DynDOLOD Resources 3 Alpha-32 for LE. The passthru LODs for vanilla trees don't use the generated trunk billboards, and don't create crown textures from the full ones. They still use the prepared atlas in Textures\DynDOLOD\lod\dyndolodtreelod.dds. The SE resources have the correct passthru meshes. No logs, just wanted to ask if its intended that the LE resources didn't get the latest passthru meshes.

I am that lazy that I didn't update them with the new method.

[sheson]

7 hours ago, Enhab said:

I added the line and ran it again, and it finished! Here are the logs: https://paste.ee/p/qBLWx https://drive.google.com/file/d/1Eo6VysRNxVT373J1mcNq3Z01jis5e76i/view?usp=sharing

I ran it again just to be sure, and yep, looks like it's working fine now. Thanks for your help!

What was the issue? Just curious.

Something must be happening to the render context between making it current for the current thread and then immediately requesting a new texture ID when using shared contexts between threads. The workaround uses one context for rendering, models and textures instead of 3 shared ones.

The question is why it isn't a problem when running TexGen, which does what DynDOLOD does a hundreds times over.

[DudeGuy]

Hi there I'm new here. 

I've been having an issue with the LODgen portion of the DynDOLODD process. 

Either it hangs on certain parts and takes very long to do anything or it exits with the error: OpenGL: invalid operation.
Logs.7z
I've included a zipped file which I hope contains all the correct logs.  

Thanks for your time.

[sheson]

1 hour ago, DudeGuy said:

Hi there I'm new here. 

I've been having an issue with the LODgen portion of the DynDOLODD process. 

Either it hangs on certain parts and takes very long to do anything or it exits with the error: OpenGL: invalid operation.
Logs.7z
I've included a zipped file which I hope contains all the correct logs.  

Thanks for your time.

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

Get the test version from this post https://stepmodifications.org/forum/topic/17510-dyndolod-300-alpha-122/?do=findComment&comment=270483 and follow the instructions.

If the problem still happens follow the instructions from this post https://stepmodifications.org/forum/topic/17510-dyndolod-300-alpha-122/?do=findComment&comment=270485

[DudeGuy]

9 minutes ago, sheson said:

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

Get the test version from this post https://stepmodifications.org/forum/topic/17510-dyndolod-300-alpha-122/?do=findComment&comment=270483 and follow the instructions.

If the problem still happens follow the instructions from this post https://stepmodifications.org/forum/topic/17510-dyndolod-300-alpha-122/?do=findComment&comment=270485

Ah sorry about that I was assuming the debug log was only for issues with TextGen.

Here it is:
https://ufile.io/cb4gun3z

Thanks for the quick response.