DynDOLOD 3.00 Alpha 182

[Rozen]

1 hour ago, sheson said:

Let me know what happens with this test version https://mega.nz/file/ZABDXaRT#DfqjTPmgb_r0d4GkCwEw5dWYgd47VzVzQ9Pn2zLHeYU

Run 1: crashed and no logs besides the one in windows.

Faulting application name: DynDOLODx64.exe, version: 3.0.0.112, time stamp: 0x63dfe565
Faulting module name: ntdll.dll, version: 10.0.22621.900, time stamp: 0xa97a9ed6
Exception code: 0xc0000374
Fault offset: 0x000000000010c249
Faulting process id: 0x0x3238
Faulting application start time: 0x0x1D9398ACD3C7CE3
Faulting application path: C:\DynDOLOD 3.00-68518-Alpha-111-1673607327\DynDOLOD\DynDOLODx64.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: c650c480-37df-4000-9de6-c304a8bb562e
Faulting package full name: 
Faulting package-relative application ID: 

Run 2: Got through, logs> https://ufile.io/f/e41vo

Seems like it is getting better.

[sheson]

36 minutes ago, Rozen said:

Run 1: crashed and no logs besides the one in windows.

Faulting application name: DynDOLODx64.exe, version: 3.0.0.112, time stamp: 0x63dfe565
Faulting module name: ntdll.dll, version: 10.0.22621.900, time stamp: 0xa97a9ed6
Exception code: 0xc0000374
Fault offset: 0x000000000010c249
Faulting process id: 0x0x3238
Faulting application start time: 0x0x1D9398ACD3C7CE3
Faulting application path: C:\DynDOLOD 3.00-68518-Alpha-111-1673607327\DynDOLOD\DynDOLODx64.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: c650c480-37df-4000-9de6-c304a8bb562e
Faulting package full name: 
Faulting package-relative application ID: 

Run 2: Got through, logs> https://ufile.io/f/e41vo

Seems like it is getting better.

At this point, I suggest to test with default BIOS settings, or maybe even some settings turned off or lower.  Things like turning off PBO or use slower memory timings instead of XMP etc, siiar auto options the graphics card. I am not familiar with the platform you are using, so you would have to experiment/google a bit. In any case, the BIOS should hopefully offer different profiles, so you should save your current settings.

If you encounter exceptions that produce a bugreport.txt, upload it and debug of course.

[Rozen]

55 minutes ago, sheson said:

At this point, I suggest to test with default BIOS settings, or maybe even some settings turned off or lower.  Things like turning off PBO or use slower memory timings instead of XMP etc, siiar auto options the graphics card. I am not familiar with the platform you are using, so you would have to experiment/google a bit. In any case, the BIOS should hopefully offer different profiles, so you should save your current settings.

If you encounter exceptions that produce a bugreport.txt, upload it and debug of course.

I rather not touch my bios setting sense I have only been in there a few times and the few times I was in my bios was to turn on safe boot and a setting I needed on to update to windows 11 and on my video card I am using the gaming profile that it has.

I will keep testing when I can and report if I get a bug report log again.

Edited February 5, 2023 by Rozen

[lord_tusk]

Im having a weird issue that i couldn't find anything posted about before. In a few specific cells behind whiterun, mostly in 4,3, some tree lod billboards are oddly transparent and the sky line/ atmosphere line sorta "masks" out part of the tree lod; the "unmasked" portion glows really bright. I have them set as ultra tree lod but just using billboards. (i like the performance/consistency but also like them on map). The up close full models are completely normal, same tree references as all the other trees. I can't find the issue in any other areas so far. Issue also was persistent on new saves. Not sure if it has something to do with the occlusion.esp for this cell but my skyrim wouldn't load any saves or new save when i just disabled occlusion.esp. Disabling all of dyndolod output of course was a fix. Currently waiting on dyndolod to re run again now on the latest version (ran this back on 106) to see if this was recently fixed, but i wasn't really sure from the changelogs if it was. 

video of issue: https://drive.google.com/file/d/1SrSg8M3qFX8MdUrF024DD-4Rz1D_vMg6/view?usp=sharing

My dyndolod sse log and debug log:  https://ufile.io/f/smsi5

<3

[sheson]

6 hours ago, lord_tusk said:

Im having a weird issue that i couldn't find anything posted about before. In a few specific cells behind whiterun, mostly in 4,3, some tree lod billboards are oddly transparent and the sky line/ atmosphere line sorta "masks" out part of the tree lod; the "unmasked" portion glows really bright. I have them set as ultra tree lod but just using billboards. (i like the performance/consistency but also like them on map). The up close full models are completely normal, same tree references as all the other trees. I can't find the issue in any other areas so far. Issue also was persistent on new saves. Not sure if it has something to do with the occlusion.esp for this cell but my skyrim wouldn't load any saves or new save when i just disabled occlusion.esp. Disabling all of dyndolod output of course was a fix. Currently waiting on dyndolod to re run again now on the latest version (ran this back on 106) to see if this was recently fixed, but i wasn't really sure from the changelogs if it was. 

video of issue: https://drive.google.com/file/d/1SrSg8M3qFX8MdUrF024DD-4Rz1D_vMg6/view?usp=sharing

My dyndolod sse log and debug log:  https://ufile.io/f/smsi5

<3

Always use the latest alpha version. Do not waste time using older versions or reporting problems with older versions.

[bruhcubed]

20 hours ago, sheson said:

https://dyndolod.info/Generation-Instructions
Wait for all processes including all spawned LODGen command prompt windows to complete successfully. Pay attention to all log messages. It should end with the log message 'DynDOLOD plugins generated successfully' and lines like 'LODGen generated object LOD for [WORLDSPACE] successfully' for each selected worldspace. Do not use the output if there were errors that stopped the process prematurely.

The last error message window said "Error: OpenGL: Source framebuffer objects unsupported." You then clicked Exit. The output is not usable as explained in the documentation.
See if changing MaxTextureSize=8192 in ..\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini lets the process run through.

Also read https://dyndolod.info/Messages/Max-Tree-LOD-Billboard-Count-Of-256-On-Atlas-Exceeded

Hello again Sheson,

Your help was greatly appreciated! Trees are working now that I pushed it to be Ultra and it's not hitting that tree limit.

Once again though, the main issue being that pesky OpenGL error keeps showing up. I reran DynDOLOD with the changes in the ini file as directed by you but the error still showed up. I can post the log again if you wish. If it is pertinent to the issue, I have a GTX 1060 3gb with the latest Nvidia drivers.

It might be futile but is there any other options available to me to see if the process will run through?

Thanks again for your time!

[sheson]

1 hour ago, bruhcubed said:

Hello again Sheson,

Your help was greatly appreciated! Trees are working now that I pushed it to be Ultra and it's not hitting that tree limit.

Once again though, the main issue being that pesky OpenGL error keeps showing up. I reran DynDOLOD with the changes in the ini file as directed by you but the error still showed up. I can post the log again if you wish. If it is pertinent to the issue, I have a GTX 1060 3gb with the latest Nvidia drivers.

It might be futile but is there any other options available to me to see if the process will run through?

Thanks again for your time!

Watch VRAM usage while the tools are running. Add TextureCache=10 under [DynDOLOD] to ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini

Post the log, debug log and bugreport.txt if it exists.

[Damon]

Windmills are fully visible only from afar.

Up close they look like this:

Logs:

https://paste.ee/p/CF14d

Edited February 6, 2023 by Damon

[lord_tusk]

14 hours ago, sheson said:

Always use the latest alpha version. Do not waste time using older versions or reporting problems with older versions.

sorry about that, was re running on 111 while making the post, just got a little impatient. The problem persisted the exact same on the newest version as well.

[sheson]

13 hours ago, Damon said:

Windmills are fully visible only from afar.

Up close they look like this:

Logs:

https://paste.ee/p/CF14d

Moved to the DynDOLOD 3 Alpha thread. Read the first post with debug log to also upload.

As explained under https://dyndolod.info/Help/Large-Reference-Bugs-Workarounds#Testing, enable papyrus logging if anythign unforseen happens while testing the experimental workarounds and upload the papyrus log as well.

Explain how to reproduce the problem in a new game.

[sheson]

9 hours ago, lord_tusk said:

sorry about that, was re running on 111 while making the post, just got a little impatient. The problem persisted the exact same on the newest version as well.

Read the first post which TexGen/DynDOLOD logs and debug logs to upload when making posts.

Also upload DynDOLOD_SSE_Tree_LOD.txt, DynDOLOD_SSE_Tree_Report.txt, DynDOLOD_SSE_Object_Report.txt from ..\DynDOLOD\Logs\

Provide screenshots of LOD and full model as explained at https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots

https://dyndolod.info/Generation-Instructions
Do not install any 3rd party tree LOD billboards. Use TexGen to generate all desired LOD billboards.

Make sure all billboards are up-to-date.

[PRieST]

14 hours ago, Damon said:

Windmills are fully visible only from afar.

Up close they look like this:

Logs:

https://paste.ee/p/CF14d

Just a suggestion, are you maybe using a not up to date version of majestic mountains moss plug in?

I had a similar problem some months ago:

 

[bruhcubed]

Hi again Sheson,

Unfortunately I tried your fix and it hasn't worked. Some things of note which may be obvious but I'll say it anyways: the duration of the DynDOLOD generation is very long, running a little over 6 hours. It may be normal because I have Seasons enabled and many worldspaces but I'd thought I would mention it anyways. Another thing is the memory usage consistently hits above 14gb of use throughout the process. Lastly, I monitored the VRAM usage as directed by you, and saw that it would rarely, if ever, break past 5% total VRAM usage. I was sat next to the computer doing work while it ran DynDOLOD and throughout the entire generation, it did not put my GPU under load it seems.

Once again I have posted the logs at your request. But thank you for the help, it means a lot.

Logs: https://ufile.io/f/r5wzp

[sheson]

47 minutes ago, bruhcubed said:

Hi again Sheson,

Unfortunately I tried your fix and it hasn't worked. Some things of note which may be obvious but I'll say it anyways: the duration of the DynDOLOD generation is very long, running a little over 6 hours. It may be normal because I have Seasons enabled and many worldspaces but I'd thought I would mention it anyways. Another thing is the memory usage consistently hits above 14gb of use throughout the process. Lastly, I monitored the VRAM usage as directed by you, and saw that it would rarely, if ever, break past 5% total VRAM usage. I was sat next to the computer doing work while it ran DynDOLOD and throughout the entire generation, it did not put my GPU under load it seems.

Once again I have posted the logs at your request. But thank you for the help, it means a lot.

Logs: https://ufile.io/f/r5wzp

The logs you uploaded show that the LOD generation process completed successfully.

It seems the setting(s) I suggested fixed the issue with the OpenGL error and let the LOD generation process run through without error now. I.e. It seems to work now.

Am I to assume what you are referring as "not working" is that some season swapped objects do not have object LOD or wrong object LOD?

Provide actual information about the swapped objects you are missing LOD for or that have wrong LOD, for example make a screenshot with Mfg console open https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots
Then also upload ..\DynDOLOD\Logs\DynDOLOD_SSE_Object_Report.txt for that generation.

Maybe the objects / full models that are swapped require a LOD model or full model rules. 

[bruhcubed]

21 minutes ago, sheson said:

The logs you uploaded show that the LOD generation process completed successfully.

It seems the setting(s) I suggested fixed the issue with the OpenGL error and let the LOD generation process run through without error now. I.e. It seems to work now.

Am I to assume what you are referring as "not working" is that some season swapped objects do not have object LOD or wrong object LOD?

Provide actual information about the swapped objects you are missing LOD for or that have wrong LOD, for example make a screenshot with Mfg console open https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots
Then also upload ..\DynDOLOD\Logs\DynDOLOD_SSE_Object_Report.txt for that generation.

Maybe the objects / full models that are swapped require a LOD model or full model rules. 

Hello again, 

Thanks for the clarification. I've been combing the area with More Informative Console and have been taking screenshots of the issues. I think it's something to do with Seasonal Landscapes - Unfrozen? But I am completely unsure as to why the LODs for that mod would not be generated... 

I leave attached many files showing the effects of the disappearing LODs on some notable structures but its effect can be felt throughout the game world on things like rocks disappearing and reappearing into existence. Terrain works fine...

Thanks again for your time.

5 minutes ago, bruhcubed said:

Hello again, 

Thanks for the clarification. I've been combing the area with More Informative Console and have been taking screenshots of the issues. I think it's something to do with Seasonal Landscapes - Unfrozen? But I am completely unsure as to why the LODs for that mod would not be generated... 

I leave attached many files showing the effects of the disappearing LODs on some notable structures but its effect can be felt throughout the game world on things like rocks disappearing and reappearing into existence. Terrain works fine...

Thanks again for your time.

Forgot to post the object report, so here it is.

https://ufile.io/w1cpiv4q