Jump to content

DynDOLOD 3.00 Alpha 182


sheson

Recommended Posts

On 4/4/2023 at 1:12 AM, sheson said:

The load order of mods, especially when they do not contain textures used by TexGen, should have any effect on TexGen being terminated by the OS / exceptions with nvoglv64.dll without OPenGL reporting back the problem as "invalid operation" for example and TexGens own exception handler being executed. If anything it is indirectly. Check if the last mentioned full textures that are loaded in the log are from a different mod now.

I admit I've reached the end of my limited knowledge (and I'm a decade removed from Skyrim modding, getting back into it now) so I apologize in advance for that. By last mentioned full textures, do you mean the textures from the last line that has a "Loading..." statement like:

[02:58] [TwbRender.LoadTexture] <Debug: Loading textures\dlc01\dungeons\castle\CastleWallStone05.dds>

Should I be looking in my Vortex staging area to determine from which mod that file exists? Because I think the last texture that had that loading statement in my prior logfile was SERuinsBronzeInlay01_n.dds, which I don't see in my staging folder currently. I suppose that makes sense - I must have removed another mod in my fumbling that had the problem texture and that ""fixed"" the issue. (not really because it just avoided it without me understanding why)

I ran again with the test executable you provided and attached the log from that run. If I'm understanding correctly, this time the CastleWallStone05.dds file exists in Skyrim 202X 9.0.1 - Other. Is there anything else I can do to give you more info?

TexGen_SSE_realtime_log.zip

Edited by Onyx
Link to comment
Share on other sites

11 hours ago, Onyx said:

I admit I've reached the end of my limited knowledge (and I'm a decade removed from Skyrim modding, getting back into it now) so I apologize in advance for that. By last mentioned full textures, do you mean the textures from the last line that has a "Loading..." statement like:

[02:58] [TwbRender.LoadTexture] <Debug: Loading textures\dlc01\dungeons\castle\CastleWallStone05.dds>

Should I be looking in my Vortex staging area to determine from which mod that file exists? Because I think the last texture that had that loading statement in my prior logfile was SERuinsBronzeInlay01_n.dds, which I don't see in my staging folder currently. I suppose that makes sense - I must have removed another mod in my fumbling that had the problem texture and that ""fixed"" the issue. (not really because it just avoided it without me understanding why)

I ran again with the test executable you provided and attached the log from that run. If I'm understanding correctly, this time the CastleWallStone05.dds file exists in Skyrim 202X 9.0.1 - Other. Is there anything else I can do to give you more info?

TexGen_SSE_realtime_log.zip 289.83 kB · 0 downloads

Yes any texture in the last 2 or so seconds that has [TwbRender.LoadTexture] <Debug: Loading ... Not necessarily the last one, as things are multi-threaded and all parallel processes write to the log at the same. In this case textures\architecture\solitude\SStoneBase01.dds is also of interest. 
Edit ..\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.INI in notepad and add RenderTexturesSingleThread=1 under [TexGen] might help to have a clearer log - but might also make it so that the problem does not occur. See what happens if you do that.

If a file does not exist as loose file but only in BSAs, you can use the xEdit Asset Browser that is started with CTRL+F3 after loading the entire load order into xEdit. After enterting part of a filename into the filter field, the first mentioned container (BSA) for a file is the winning one. Data means loose file.

Link to comment
Share on other sites

4 hours ago, sheson said:

Yes any texture in the last 2 or so seconds that has [TwbRender.LoadTexture] <Debug: Loading ... Not necessarily the last one, as things are multi-threaded and all parallel processes write to the log at the same. In this case textures\architecture\solitude\SStoneBase01.dds is also of interest. 
Edit ..\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.INI in notepad and add RenderTexturesSingleThread=1 under [TexGen] might help to have a clearer log - but might also make it so that the problem does not occur. See what happens if you do that.

If a file does not exist as loose file but only in BSAs, you can use the xEdit Asset Browser that is started with CTRL+F3 after loading the entire load order into xEdit. After enterting part of a filename into the filter field, the first mentioned container (BSA) for a file is the winning one. Data means loose file.

This should be the log from a single threaded run. For better or worse, no change with only single threaded, it's still exiting early with no other logs being generated. I don't really have a good understanding of where to go next from here.

Whoops, I had run with only having RenderThreads=1, not actually RenderTexturesSingleThread=1. With that additional flag, it looks like it's going to succeed (still running but it's already gotten past the prior error point). I'll upload the logs from this run once they finish and I wake up.

Also that is a really cool feature, thanks for the tip! I see that the textures\architecture\solitude\sstonebase01.dds winner is from loose files. It has, in order: Data, Enhanced Solitude SSE.bsa, Skyrim - Textures1.bsa.

Edited by Onyx
Link to comment
Share on other sites

Hello, Sheson! Thanks for your constant updates.

Recently I was investigating issue with color mismatch on distant snow objects compared to distant land, and it turns out that textures \textures\terrain\tamriel\tamriel.x.x.x.dds are vanilla, so using brighter modded snow texture causes notable mismatch on distant land. Any advises?

Link to comment
Share on other sites

45 minutes ago, adelinadragonborn said:

Hello, Sheson! Thanks for your constant updates.

Recently I was investigating issue with color mismatch on distant snow objects compared to distant land, and it turns out that textures \textures\terrain\tamriel\tamriel.x.x.x.dds are vanilla, so using brighter modded snow texture causes notable mismatch on distant land. Any advises?

https://dyndolod.info/Generation-Instructions#Prerequisites
Typically generate terrain LOD meshes and textures with xLODGen before generating the LOD mod with DynDOLOD ...

https://dyndolod.info/Help/xLODGen

Link to comment
Share on other sites

1 hour ago, sheson said:

https://dyndolod.info/Generation-Instructions#Prerequisites
Typically generate terrain LOD meshes and textures with xLODGen before generating the LOD mod with DynDOLOD ...

https://dyndolod.info/Help/xLODGen

Is it OK that terrain in world map looks like this?

My quality settings for terrain LOD meshes: LOD4 = 3, LOD8 = 5, LOD16 = 8, LOD32 = 10, Max vert = 32767

The Elder Scrolls V  Skyrim Special Edition Screenshot 2023.04.09 - 17.04.25.35.png

Link to comment
Share on other sites

11 hours ago, sheson said:

Yes any texture in the last 2 or so seconds that has [TwbRender.LoadTexture] <Debug: Loading ... Not necessarily the last one, as things are multi-threaded and all parallel processes write to the log at the same. In this case textures\architecture\solitude\SStoneBase01.dds is also of interest. 
Edit ..\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.INI in notepad and add RenderTexturesSingleThread=1 under [TexGen] might help to have a clearer log - but might also make it so that the problem does not occur. See what happens if you do that.

If a file does not exist as loose file but only in BSAs, you can use the xEdit Asset Browser that is started with CTRL+F3 after loading the entire load order into xEdit. After enterting part of a filename into the filter field, the first mentioned container (BSA) for a file is the winning one. Data means loose file.

OK, with RenderTexturesSingleThread=1 the run succeeded. I've attached all 3 logs that came from this run. Should I just keep that flag in my config and consider this issue solved? DynDOLOD was also able to complete successfully (albeit not free of warnings or errors).

TexGen_SSE_singlethreaded_logs.7z

Link to comment
Share on other sites

1 hour ago, Onyx said:

OK, with RenderTexturesSingleThread=1 the run succeeded. I've attached all 3 logs that came from this run. Should I just keep that flag in my config and consider this issue solved? DynDOLOD was also able to complete successfully (albeit not free of warnings or errors).

TexGen_SSE_singlethreaded_logs.7z 522.79 kB · 0 downloads

Thanks for the logs. Yes, it is OK, since we now know that none of the textures are cause of the exception in the nvoglv64.dll that can be avoided by not using multiple render contexts, which is a workable option for now.

Link to comment
Share on other sites

39 minutes ago, backwords said:

Hello im new to Dyndolod lod generating. While generating lod it showed some errors. ill post them here. I don't know if i sohould be concerned.

https://paste.ee/p/3bxCO Large Reference Bugs

https://paste.ee/p/5a5MS Outdated Billboards

https://paste.ee/p/jnkxq Textures Do Not Match

Moved to the DynDOLOD 3 alpha thread. Read the first post which log and debug log to upload when making posts. https://dyndolod.info/Official-DynDOLOD-Support-Forum

Read the explanations for messages https://dyndolod.info/Messages, what they mean, their severity and if/what to do about them.

https://dyndolod.info/Messages/Large-Reference-Bugs and https://dyndolod.info/Help/Large-References
https://dyndolod.info/Messages/Billboard-For-Model-Has-Different-CRC32. Really follow the generation instruction https://dyndolod.info/Generation-Instructions
https://dyndolod.info/Messages/Textures-Do-Not-Match

If further explanations for a particular log message is required, provide the logs and ask a specific question.

Link to comment
Share on other sites

8 hours ago, MrXCh1k1X said:

I have a problem, I tried to install this mod with a tutorial video, however my game still looks like this: 

image.thumb.png.5e751083d5994c097398959fe144b900.png My textgen went without problems but my Dyndolod show a lot of warnings, Here is the full log:

DyndologLog.rar 149.84 kB · 1 download

Read the first post with entire log from the last LOD generation sesssion(s) and debug log to upload when making posts. https://dyndolod.info/Official-DynDOLOD-Support-Forum

What does "this" mean in particular? The screenshot seems to show vanilla object and terrain LOD and maybe pre-generated tree LOD from another mod.

If you have problems with third party guides ask their author for help.

See https://dyndolod.info/Generation-Instructions how to generate and to install the output - in particular how the generated output need to overwrite everything. Pay attention to the Prerequisites and how to use xLODGen to generate terrain LOD. https://dyndolod.info/Help/xLODGen

Warning and error messages, there severity and if/what to do about them are explained at https://dyndolod.info/Messages and in the https://dyndolod.info/Help/Summary-Of-Messages.

If you have a questions about a particular message, ask a specific question.

Link to comment
Share on other sites

13 minutes ago, FinalCraneFall said:

I just switched to SR Exterior Cities. Is this the correct line? Without "x" this line works perfectly and detected my SREX, but with the "x" it did not disable Objects and Trees and the result is so bad.
 
WarnModFileName=xSR Exterior Cities;SR-Exterior-Cities
 

Correct. ATM for SR Exterior Cities you have to manually make sure object and tree LOD are not checked when doing the second run for dynamic LOD only.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.