Jump to content

DynDOLOD 3.00 Alpha 180


sheson

Recommended Posts

1 hour ago, sheson said:

Yes, comparing the not found billboard filenames from the LODGen log message with the created billboard filenames from the TexGen log it is apparent that they do not match.

Replace LODGenx64Win.exe with this test version https://mega.nz/file/5MAAgYrQ#ieDfR3kCL68ykFh9WNxA6rc7ERJcBxBcl8L4sqPQ0Ng and Execute LODGen in expert mode https://dyndolod.info/Help/Expert-Mode and check if it finds/uses the correct billboard filenames.

With this version the grass lods are indeed found in the meshes and the file size is more or less the same with my previous working output. I didn't enable verbose this time so the logs don't contain much information, but I imagine it's working alright. Thanks for the help!

Edit: just enabled verbose and generated a single LOD4 area. Sure enough there isn't any "grass mapping not found" message in the logs.

Edited by heheloveer
Link to comment
Share on other sites

10 minutes ago, star_death69 said:

I've disable the Last tow mods (with the circlets) and reran TexGen here are the logs: Logs_20230221_1306.7z

Unless I am checking the wrong Circlets mods on Nexus, they do not contains the texture at the path Textures\cubemaps\ShinyBright_e.dds bit at a different path.

What happens if you click "Preview" under the Rendered Object LOD Textures and look at DynDOLOD\Render\Skyrim\Objects\dlc01\lod\seruinswindowslod.nif ?

Link to comment
Share on other sites

19 minutes ago, heheloveer said:

With this version the grass lods are indeed found in the meshes and the file size is more or less the same with my previous working output. I didn't enable verbose this time so the logs don't contain much information, but I imagine it's working alright. Thanks for the help!

Edit: just enabled verbose and generated a single LOD4 area. Sure enough there isn't any "grass mapping not found" message in the logs.

Thanks for letting us know.

Link to comment
Share on other sites

9 minutes ago, sheson said:

Unless I am checking the wrong Circlets mods on Nexus, they do not contains the texture at the path Textures\cubemaps\ShinyBright_e.dds bit at a different path.

What happens if you click "Preview" under the Rendered Object LOD Textures and look at DynDOLOD\Render\Skyrim\Objects\dlc01\lod\seruinswindowslod.nif ?

That is true, they seem to be under a different path.
image.thumb.png.3ce4332309ffc3ad4dace8711601ee67.png

These are the logs if I disable all for mods: Logs_20230221_1318.7z

If I preview the seruinswindowslod.nif, they look like that:

image.thumb.png.ee99b9f031b0a85a0ebb32578c6f358d.pngimage.thumb.png.1805a46003ce6862acccb05ef6408fcf.png

On the first glance they do not look wrong to me.

Link to comment
Share on other sites

23 minutes ago, star_death69 said:

That is true, they seem to be under a different path.
image.thumb.png.3ce4332309ffc3ad4dace8711601ee67.png

These are the logs if I disable all for mods: Logs_20230221_1318.7z

If I preview the seruinswindowslod.nif, they look like that:

image.thumb.png.ee99b9f031b0a85a0ebb32578c6f358d.pngimage.thumb.png.1805a46003ce6862acccb05ef6408fcf.png

On the first glance they do not look wrong to me.

See what happens with this test version https://mega.nz/file/sQBEQYiA#4x0xGGPisn1rLJNaiHV005p9qWbGl2ZyuXIFSto-P_Q

Link to comment
Share on other sites

6 hours ago, CBSkyrimModding said:

Thank you, will do. One more quick question: I've cleaned, sorted, and resolved all issues reported by LOOT, but the Step guide recommends using the following LOD mods:

xLODGen Resource - SSE Terrain Tamriel_Extended
Far Object LOD Improvement Project SSE
DynDOLOD Bright Waterfall Fix for ENB
Aspens Ablaze Add-On - DynDOLOD 3
Glacier LOD Meshes

Just to be clear, in addition to your other instructions, you want me to disable all of these before running a clean pass of TexGen?

First, no, do not disable any LOD resource mods (like these) other than xLOSGen Resource, which is for terrain LOD only and should only be enabled when generating terrain LOD.

Second, some of those mods are not recommended in the Step SSE guides. Leave all LOD resource mods active, but disable anything with pre-generated billboards or LOD


Also, use the latest Alpha 115 now.

Link to comment
Share on other sites

15 hours ago, sheson said:

If you are following a third party guide, you need to ask qestions about it on its forum section.

https://dyndolod.info/Generation-Instructions
Finalize the load order as explained in the prerequisites above. Make sure all mods, plugins and patches (that affect affect trees, grasses or any textures) are enabled and their overwrite order is sorted. Ignore wrong 3rd party advice to temporarily disable plugins, mods, meshes or textures. Such advice is categorically wrong or outdated. In case of issues, solve the cause or use appropriate rules or settings for desired results. Disabling plugins, mods, meshes or textures is a troubleshooting step and not a fix. In case of problems or questions, use the official DynDOLOD support forum for qualified help and advice.

However:

https://dyndolod.info/Help/xLODGen#Requirements
Remove or disable the plugin after terrain LOD generation. No harm done if loaded in-game. Typically the player can not get close to these areas. There are no effects outside the far away added cells.

https://dyndolod.info/Mods/Waterfalls
Bright Waterfall Fix for ENB - do not install DynDOLOD Bright LOD Waterfall Fix

Thank you very much for all your help. It turns out the issue with DynDOLOD not recognizing my LODs and billboards was due to the fact that when I converted my TexGen_Output files with Texconv, the Texconv_Output files didn't include the associated .ini and .txt files. The solution was to copy everything in the TexGen_Output folder and paste it in the Texconv_Output folder WITHOUT replacing anything already there (just adding all of those missing .ini and .txt files to the converted .dds files). Everything works and is looking great.

Hope this info is useful to you and the people you help.

Link to comment
Share on other sites

Hi Sheson,

I ran Dyndolod a few more times here are two more bugreports that I encountered with the alpha 115. The problem is most likely with amd drivers, but want to give you some feedback I am using the driver only version of 23.2.1.

error: Assertion Failure

https://ufile.io/jdduc6g4

error: OpenGL invalid operation exception

https://ufile.io/jdduc6g4

Best,

LoooneyTunes

 

copied the wrong file here is the OpenGL exception

https://ufile.io/ub4rn1i8

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.