DynDOLOD 3.00 Alpha 180

[heheloveer]

Not sure if this is worthy of a post here, but I just wrote another LOD generation guide in Chinese (link if someone here needs it for some reason). 40000 Chinese characters this time, which should translate to about 20000 English words. Probably one of the most thorough guides out there, excluding of course Sheson's own. I mean, theoretically there's no need for a 3rd party guide since no one can write it better than Sheson already did, but reading the official documents isn't easy for most Chinese players, not to mention they probably don't really know its existence. Well, my guide probably won't make much of a stir since it's still far too long to be an easy read, but every little bit counts, I guess. The majority of the content is information pulled from the official documents, though I did add some of my own findings and recommendations. Should be mostly accurate, though I could also be wrong.

Anyway, thanks Sheson for your constant efforts at improving Skyrim's LODs, for writing the best LOD guide the Skyrim modding community could ever hope for, and for answering every question thrown at you in the forum over the years. Consider this the submission of my firstborn.

Edited June 5, 2023 by heheloveer

[aJrenalin]

1 hour ago, z929669 said:

Are you on an AMD system? If so, see this post:

 

No, Nvidia

1 hour ago, sheson said:

See the first post or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which log and debug log to upload when making posts.
https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-Search

TexGen is probably waiting for a TexConv process to finish.

Add LockTexconv=1 under [TexGen] in B:\Mods\Skyrim\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.INI and see if that changes anything.
It helped users with the same problem a couple pages back.

Will try this now. Thank you

[Wulfga]

On 6/2/2023 at 12:03 PM, sheson said:

The log and debug log are both saved when the program is closed. Just send the signal to close once (e.g. clicking the X top right) and then wait a few seconds so the program can save the logs and shutdown properly.

As explained in the already linked page https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs, use the RealTimeLog=1 INI setting in case there are no logs or debug logs because the tool is being terminated prematurely.

If the screen goes black, then there is probably a hardware (including power supply), driver, overclocking, BIO setting, OS issue.

Thank you for squaring me away enough to get a bug report in. Was finally able to get far enough for one to generate on one of my attempts. In 40 or so runs this is the first time I've been able to generate a debug log. I PM'd you the bug report because honestly, it's got a decent amount of personal info in it, but I'd really like to not give up on this after all the time spent.

To anyone else who might know anything about this error, I absolutely can't get past this strange DLL error:

Faulting application name: TexGenx64.exe, version: 3.0.0.128, time stamp: 0x646a6e33
Faulting module name: nvoglv64.dll, version: 31.0.15.3598, time stamp: 0x646dfba9
Exception code: 0xc0000005
Fault offset: 0x0000000001550f2a
Faulting process id: 0x0xD40
Faulting application start time: 0x0x1D997D3012B155A
Faulting application path: H:\Modding\Tools\DynDOLOD\TexGenx64.exe
Faulting module path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_3c2bd4a1ec6d228e\nvoglv64.dll
Report Id: 31970090-ec36-4d74-b85b-fcaf1cfc50f9
Faulting package full name: 
Faulting package-relative application ID: 

I really don't want to give up on this, but no one has both the knowledge and the patience to get me past it.

Intel i9 13900k, RTX3070ti, completely fresh drivers, Alpha-128 Dyn from Nexus and the Alpha-36 Resources that the website links to. I'm sure this is somehow my fault but I've exhausted my ability to try more things. Ran SFC and DISM, both fine, I'm just at a loss.

Added the Realtime log (had to zip it, it's huge)

TexGen_SSE_realtime_log.7z

[sheson]

12 minutes ago, Wulfga said:

Thank you for squaring me away enough to get a bug report in. Was finally able to get far enough for one to generate on one of my attempts. In 40 or so runs this is the first time I've been able to generate a debug log. I PM'd you the bug report because honestly, it's got a decent amount of personal info in it, but I'd really like to not give up on this after all the time spent.

To anyone else who might know anything about this error, I absolutely can't get past this strange DLL error:

Faulting application name: TexGenx64.exe, version: 3.0.0.128, time stamp: 0x646a6e33
Faulting module name: nvoglv64.dll, version: 31.0.15.3598, time stamp: 0x646dfba9
Exception code: 0xc0000005
Fault offset: 0x0000000001550f2a
Faulting process id: 0x0xD40
Faulting application start time: 0x0x1D997D3012B155A
Faulting application path: H:\Modding\Tools\DynDOLOD\TexGenx64.exe
Faulting module path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_3c2bd4a1ec6d228e\nvoglv64.dll
Report Id: 31970090-ec36-4d74-b85b-fcaf1cfc50f9
Faulting package full name: 
Faulting package-relative application ID: 

I really don't want to give up on this, but no one has both the knowledge and the patience to get me past it.

Intel i9 13900k, RTX3070ti, completely fresh drivers, Alpha-128 Dyn from Nexus and the Alpha-36 Resources that the website links to. I'm sure this is somehow my fault but I've exhausted my ability to try more things. Ran SFC and DISM, both fine, I'm just at a loss.

Added the Realtime log (had to zip it, it's huge)

TexGen_SSE_realtime_log.7z 553.51 kB · 1 download

Do what I suggested in this post: https://stepmodifications.org/forum/topic/17510-dyndolod-300-alpha-128/?do=findComment&comment=271741

Add RenderSingle=1 under [TexGen] in H:\Modding\Tools\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.ini and check if it makes a difference. It helped other people one or two thread pages back that also had an exception in the NVIDIA driver nvoglv64.dll

The realtime log shows that it is not set to 1

[Wulfga]

52 minutes ago, sheson said:

Do what I suggested in this post: https://stepmodifications.org/forum/topic/17510-dyndolod-300-alpha-128/?do=findComment&comment=271741

Add RenderSingle=1 under [TexGen] in H:\Modding\Tools\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.ini and check if it makes a difference. It helped other people one or two thread pages back that also had an exception in the NVIDIA driver nvoglv64.dll

The realtime log shows that it is not set to 1

Ahh, that's fair. I had (I promise) set that to 1, but I did a fresh install of all DynDOLOD software and didn't set it back.

I DO THINK I FOUND PART OF THE PROBLEM.

When I completely uninstalled my Nvidia drivers rather than just doing fresh installs etc., it went WAAAY farther than I've ever seen it go before, and I finally got an "OpenGL version too low" error much farther in than normal. [02:52] Error: OpenGL: H:\Modding\Tools\DynDOLOD\TexGen_Output\Textures\dlc01\lod\dlc01dawnguardcastle01lod framebuffer objects unsupported.

I'm currently backing down through versions of the driver trying to find one that works. 531.41-desktop-win10-win11-64bit-international-dch-whql just failed, 531.61 failed previously. I'll add your "1" now for consistency. Thanks for catching that.

(attachments from no driver test where I let Windows 11 handle the GPU)

I'll test the RenderSingle=1 right now.

TexGen_SSE_log.txt bugreport.txt

[sheson]

8 minutes ago, Wulfga said:

Ahh, that's fair. I had (I promise) set that to 1, but I did a fresh install of all DynDOLOD software and didn't set it back.

I DO THINK I FOUND PART OF THE PROBLEM.

When I completely uninstalled my Nvidia drivers rather than just doing fresh installs etc., it went WAAAY farther than I've ever seen it go before, and I finally got an "OpenGL version too low" error much farther in than normal. [02:52] Error: OpenGL: H:\Modding\Tools\DynDOLOD\TexGen_Output\Textures\dlc01\lod\dlc01dawnguardcastle01lod framebuffer objects unsupported.

I'm currently backing down through versions of the driver trying to find one that works. 531.41-desktop-win10-win11-64bit-international-dch-whql just failed, 531.61 failed previously. I'll add your "1" now for consistency. Thanks for catching that.

(attachments from no driver test where I let Windows 11 handle the GPU)

I'll test the RenderSingle=1 right now.

TexGen_SSE_log.txt 156.58 kB · 1 download bugreport.txt 233.76 kB · 1 download

All I ask is this: Install latest driver only without any bloatware. Set RenderSingle=1. In case there is still a problem, upload new log, debug log or realtime log and bugreport.txt. Make sure you are not overclocking or have other hardware issues, like unstable CPU, memory etc.

[Wulfga]

9 minutes ago, sheson said:

All I ask is this: Install latest driver only without any bloatware. Set RenderSingle=1. In case there is still a problem, upload new log, debug log or realtime log and bugreport.txt. Make sure you are not overclocking or have other hardware issues, like unstable CPU, memory etc.

I've followed all your advice- that's what the couple-day pause was. I reviewed the BIOS line by line, removed all of the overclocking (broke my RAID array at 2am on accident) reinstalled everything fresh, and have consistently had the same issue.

With the rolled back driver to 531.41 and your INI edit, it's (veeerrrrrryyyy slowly) working. I owe you a beer.

For the record, I genuinely think there's something in the new Nvidia drivers that are breaking it. RenderSingle=1 on the current drivers did not work. If it were to ever come up again, RenderSingle=1 on nVidia driver version 531.41 worked fine for me. I do have an absolute mountain of other NVIDIA tools for CUDA, etc, so this might be unique to folks creating animations and doing complex AI work, can't say for sure, but it just finished with all overclocking in place and no changes except the single INI edit and the driver rollback. Cheers.

[20:33] Removing temporary files
[20:33] Waiting for Texconv to convert 2 textures
[20:34] TexGen completed successfully
[20:34] Exit TexGen, zip and exit, check log or restart?

Thanks for putting up with me.

[aJrenalin]

17 hours ago, sheson said:

See the first post or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which log and debug log to upload when making posts.
https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-Search

TexGen is probably waiting for a TexConv process to finish.

Add LockTexconv=1 under [TexGen] in B:\Mods\Skyrim\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.INI and see if that changes anything.
It helped users with the same problem a couple pages back.

This worked. thank you

[diesidepp]

hi, i opened dyndolodx64 and it said that my dyndolod resourses core files are outdated. what can i do? There is no newer version on nexus.

[sheson]

27 minutes ago, diesidepp said:

hi, i opened dyndolodx64 and it said that my dyndolod resourses core files are outdated. what can i do? There is no newer version on nexus.

Really read the message. The message states a fact.

The version of the DynDOLOD Resources Core files which are installed in the load order is older than the version required by the DynDOLOD Standalone version you are using.

The download archives available on the different DynDOLOD mods on Nexus are always the latest versions for their respective game and DynODLOD 2.x/3.x versions . So are the download links on the first post.

 No actual information was provided. If you require further help, upload the log.

[diesidepp]

1 hour ago, sheson said:

真的看了留言。該消息陳述了一個事實。

在加載順序中安裝的DynDOLOD資源核心文件 的版本比您正在使用的DynDOLOD獨立版本 所需的版本舊。

Nexus 上不同DynDOLOD模組 的下載檔案始終是其各自遊戲和 DynODLOD 2.x/3.x 版本的最新版本。第一篇文章中的下載鏈接也是如此。

 沒有提供實際信息。如果您需要進一步的幫助，請上傳日誌。

So how can i solve this problem, where can i download the same version of the dyndolod resources core files, thank you.

[sheson]

1 hour ago, diesidepp said:

So how can i solve this problem, where can i download the same version of the dyndolod resources core files, thank you.

Moved to the DynDOLOD 3 Alpha thread. Read the first post how not to post screenshots of messages and instead use the "Copy message to clipboard" link in order to paste text. https://dyndolod.info/Official-DynDOLOD-Support-Forum
DynDOLOD Resources SE core files are outdated

DynDOLOD 3 Alpha requires DynDOLOD Resources SE 3 Alpha. You have DynDOLOD Resources SE 2.x for DynDOLOD 2.x installed.

This is explained and linked in the first post of the DynDOLOD 3 Alpha thread.
The official online documentation that can be opened by clicking the "Online Help" or using the "Click on this link for additional explanations and help for this message" link from the message would lead you to https://dyndolod.info/Downloads, which has the links.

Pay attention to the requirements on Nexus when downloading DynDOLOD 3 Alpha. It also has the link:

Searching this forum for the message finds this thread https://stepmodifications.org/forum/topic/18692-dyndolod-resources-se-core-files-are-outdated/

[DefaultPIayer]

For some reason texgen will just stop generating textures around 7 minutes and 30 seconds not always that time but it's usually close don't know why though here's the Texgen Debug log and the sse log 

TexGen_SSE_log.txt

[sheson]

On 6/10/2023 at 8:00 PM, DefaultPIayer said:

For some reason texgen will just stop generating textures around 7 minutes and 30 seconds not always that time but it's usually close don't know why though here's the Texgen Debug log and the sse log 

TexGen_SSE_log.txt 522.31 kB · 1 download

Moved to the DynDOLOD 3 Alpha thread.

TexGen is probably waiting for a TexConv process to finish.

Add LockTexconv=1 under [TexGen] in B:\Mods\Skyrim\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.INI and see if that changes anything.
It helped users with the same problem a couple pages back where TexGen seems to be stuck or stopped.

[snazzpants]

Debug log

Hi, I'm having a similar issue as others here, when i attempt to use the TexGen one of two things happens:

1. the application closes shortly after beginning creating textures, this happens 99% of the time. I have the most current graphics drivers, up to date MO2, and have added "RenderSingle=1" to the INI file. the issue persists

2. the one time it didn't crash it gave me the OpenGL framebuffer error seen in my log files.

any help or advice would be appreciated, thanks!

TexGen_SSE_log.txt