DynDOLOD 3.00 Alpha 182

[sheson]

10 hours ago, mooit said:

I was trying to edit my post over, the Blubbos link I posted is for the latest version. I made a mistake and forgot to put a link to the older version that I am using, that is still archived on nexumods.

Blubbos Trees in Whiterun - DELETED at Skyrim Special Edition Nexus - Mods and Community (nexusmods.com)

I don't like the new version, it's been changed, has a different look/trees...

The form id is just a tree, which should not cause any problems with references placing glow meshes. 

Seem the broken plugin was removed for a reason. See if "fixing" the HITMEs as already suggest makes a difference. https://dyndolod.info/Messages/Internal-File-FormID-Is-A-HITME
If not, generate LOD from scratch with the fixed plugin to see if that helps.

If that does not change anything, it is possible it selects a tree instead of the reference with the glow mesh when clicking with console open. Install More Informative Console to help finding the correct form id for the glow mesh. We would expect the NIF to have a name containing "glow" or "fx" for example.

If the glow can be seen when outside of Whiterun, use tcl in console to get near it to select it via console to get its form ID.

Test generating with "Fake lights child worlds" unchecked. If that help, then it means disabling dynamic LOD objects just takes longer than usual and increasing the time to fade-in from black would be the option to use in case you want to have LOD with those fake lights.

[ElCapitan8866]

On 5/5/2022 at 7:52 AM, sheson said:

If the process stops with a proper message that explains the cause of the error, then it is not crashing.

If the message has a link "Click on this link for additional explanations and help for this message", then click it to open further explanations and help as explained on the first post.
Unresolved form ids will cause CTD in the game (the game closes without telling you what the problem is)

Do not "delete" base records. To remove objects like trees, "delete" the references, clean the plugin with xEdit afterwards.
Alternatively define a different model on the base record or replace the model NIF. Could be an "empty" dummy NIF with just the BSFadeNode.

If further help is required with a message, use the "Copy this message to clipboard" to copy and paste the text when making reports as explained in the first post.
Also upload the log and debug log as explained in the first post.

Hi Sheson, thank you for the info. I used SSEEdit to create a copy of that tree into a new .esp (so I can move it down my load order) and simply replaced the ugly tree model with one that works with Happy Little Trees (DLC2TreePineShortHeavySnow01.niff instead of DLC2TreePineShortHeavySnow.niff). That did it, ugly tree is gone from the game and LODs generate without a problem. Thanks again!

[DarthVitrial]

In alpha 89, what does “Added principle support for Base Object Swapper transformation and location” mean? Since base object swapper was already supported for stuff like seasons. Is this for stuff like that Dynamic Things Alternative message I was getting, or is this something else?

[sheson]

36 minutes ago, DarthVitrial said:

In alpha 89, what does “Added principle support for Base Object Swapper transformation and location” mean? Since base object swapper was already supported for stuff like seasons. Is this for stuff like that Dynamic Things Alternative message I was getting, or is this something else?

I just opened the edit function to update the page on the website. Check it back in a while. https://dyndolod.info/Mods/Base-Object-Swapper

It means, DynDOLOD now supports the Pos[A|R], Rot[A|R], Scale setting as well as the [Form|Location/Cell_FormID|Location/Cell_EditorID].

If any of the tranforms is random, the reference is ignored for LOD.

"Principle support" means it needs testing with real mods utilizing the features and there might be bugs.

[z929669]

Hey sheson, could you provide a bit of background as to what prompted you to add apparent support for Grass Cache Fixes? What's the scenario this resolves?

GrassGID=gid
GrassGID=cgid

I also see mention of reading GID from BSA and some LODGen support as well for this stuff. I want to keep our guides properly updated with respect to the new version.

[sheson]

28 minutes ago, z929669 said:

Hey sheson, could you provide a bit of background as to what prompted you to add apparent support for Grass Cache Fixes? What's the scenario this resolves?

GrassGID=gid
GrassGID=cgid

I also see mention of reading GID from BSA and some LODGen support as well for this stuff. I want to keep our guides properly updated with respect to the new version.

Just added this to https://dyndolod.info/Help/Grass-LOD
In case the grass cache is used with runtime version 1.6.x and the *.CGID files have been renamed to *.GID, set GrassGID=gid in the ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini. This requires all *.GID to be of the valid data format, otherwise there will be Error reading grass [worldspace] [x,y] / Error processing grass data *.CGID Unable to read beyond the end of the stream as explained below.

This is to avoid having to keep both the same CGID and GID files in the load order or having to rename them back and forth.

Note that NGIO can not read CGID from BSA. This only works with the engine natively loading GID. DynDOLOD/LODGen read anything from BSA.

[Mertz]

Thanks for the .NET 6 LODGen version @sheson

[Mirari]

On 5/3/2022 at 2:07 PM, sheson said:

What DynDOLOD Alpha version are you using? If that happens with the latest Alpha, then upload the log and debug for the generation of the problematic results as requested.

A threshold of one is/should not a problem with the current version. There should be no need to manually edit anything.

I was using Alpha 88 (Download Name: DynDOLOD 3.00-32382-Alpha-88-1649940503.7z).

Here are the logs. I had attached them in my 2nd post. Figured out how to share them and had edited the post a few minutes after after posting it:

 

On 4/29/2022 at 8:08 AM, z929669 said:

Sorry, first time on this forum, getting the hang of what info to include.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Requested Logs :

DynDOLOD_SSE_Debug_log.txt

https://ufile.io/lmx580r2

DynDOLOD_SSE_log

https://ufile.io/mr94fb12

LODGen_SSE_Tamriel_log

https://ufile.io/ti0l6cvu

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 

[sheson]

10 hours ago, Mirari said:

I was using Alpha 88 (Download Name: DynDOLOD 3.00-32382-Alpha-88-1649940503.7z).
Here are the logs. I had attached them in my 2nd post. Figured out how to share them and had edited the post a few minutes after after posting it:

Ah right, the problem was that the debug log was already replaced and doesn't contain the generation anymore.
Please upload ..\DynDOLOD\Logs\DynDOLOD_SSE_Tree_Report.txt and DynDOLOD_SSE_Object_Report.txt

If you have the time, check if there is any difference with DynDOLOD 3 Alpha-89. In case it still happens, upload that debug log.

[tachibana907]

I have just installed DynDOLOD Resources SE 3.00 Alpha 25 and DynDOLOD 3.00 Alpha 89,

 created a TexGen Output and run the DynDOLODx64.exe

Then it show an error message "Do not install DynDOLOD Resources intended for other game versions. Do not modify any of the files. Verify the archive downloaded completely and all core files were installed."

Is there any solution for this case?

Thanks!

 

[sheson]

41 minutes ago, tachibana907 said:

I have just installed DynDOLOD Resources SE 3.00 Alpha 25 and DynDOLOD 3.00 Alpha 89,

 created a TexGen Output and run the DynDOLODx64.exe

Then it show an error message "Do not install DynDOLOD Resources intended for other game versions. Do not modify any of the files. Verify the archive downloaded completely and all core files were installed."

Is there any solution for this case?

Thanks!

Read the first post which log and debug log to upload when making posts.
Use "Copy this message to clipboard" and paste the entire message as explained on the first post.

Click on "Click on this link for additional explanations and help for this message" which should open https://dyndolod.info/Help/DynDOLOD-Resources, check its Troubleshooting section.

Really follow the installation instructions. https://dyndolod.info/Installation-Instructions, especially this:
Use 7-Zip to unpack the DynDOLOD Standalone archive into a new and empty 'DynDOLOD' directory that is outside of special OS folders like 'Programs Files' or 'Program Files (x86)', User, Documents, Desktop, Download and also not in SteamApps, game, Data or any mod manager folders. For example C:\Modding\DynDOLOD\.

The log will most likely show an older DynDOLOD Standalone version is being used.

[tachibana907]

[Window Title]
DynDOLOD

[Main Instruction]
DynDOLOD Resources SE issue.

[Content]
Do not install DynDOLOD Resources intended for other game versions.

Do not modify any of the files.

Verify the archive downloaded completely and all core files were installed.

Click on this link for additional explanations and help for this message

[Exit DynDOLOD]

[Footer]
Online Help | Support Forum | Copy message to clipboard

DynDOLOD_SSE_Debug_log.txt DynDOLOD_SSE_log.txt

[sheson]

36 minutes ago, tachibana907 said:

[Window Title]
DynDOLOD

[Main Instruction]
DynDOLOD Resources SE issue.

[Content]
Do not install DynDOLOD Resources intended for other game versions.

Do not modify any of the files.

Verify the archive downloaded completely and all core files were installed.

Click on this link for additional explanations and help for this message

[Exit DynDOLOD]

[Footer]
Online Help | Support Forum | Copy message to clipboard

DynDOLOD_SSE_Debug_log.txt 63.79 kB · 1 download DynDOLOD_SSE_log.txt 317.11 kB · 0 downloads

As expected, the first line of the log shows an older DynDOLOD Standalone version is being used:
DynDOLOD 3.0 Alpha-88 x64 - Skyrim Special Edition (SSE) (C973144D) starting session 2022-05-07 16:50:43

As explained, always use the latest version of DynDOLOD Standalone 3 Alpha with the latest version of DynDOLOD Resources SE Alpha.

Really follow the installation instructions. https://dyndolod.info/Installation-Instructions, especially this:
Use 7-Zip to unpack the DynDOLOD Standalone archive into a new and empty 'DynDOLOD' directory that is outside of special OS folders like 'Programs Files' or 'Program Files (x86)', User, Documents, Desktop, Download and also not in SteamApps, game, Data or any mod manager folders. For example C:\Modding\DynDOLOD\.

Remove old version first, do not unpack over old version. Always unpack into new and empty folder.

[tachibana907]

28 minutes ago, sheson said:

As expected, the first line of the log shows an older DynDOLOD Standalone version is being used:
DynDOLOD 3.0 Alpha-88 x64 - Skyrim Special Edition (SSE) (C973144D) starting session 2022-05-07 16:50:43

As explained, always use the latest version of DynDOLOD Standalone 3 Alpha with the latest version of DynDOLOD Resources SE Alpha.

Really follow the installation instructions. https://dyndolod.info/Installation-Instructions, especially this:
Use 7-Zip to unpack the DynDOLOD Standalone archive into a new and empty 'DynDOLOD' directory that is outside of special OS folders like 'Programs Files' or 'Program Files (x86)', User, Documents, Desktop, Download and also not in SteamApps, game, Data or any mod manager folders. For example C:\Modding\DynDOLOD\.

Remove old version first, do not unpack over old version. Always unpack into new and empty folder.

I delect all files of DynDOLOD and reinstall the new version, the problem have been solved.

Thanks for help!

[Gamma_Metroid]

Hi sheson, I've got another problem. This one might be related to xlodgen since I had the same problem when I was using that, so I included the lodgen log file as well.

The issue is that some generated lod meshes are losing their vertex colors at lod8 and above. I have included examples. Both levels use the same nifs for these objects so it's not that. And you can see in the lodgen log that vertex colors are enabled for each level. https://ufile.io/f/rlvdr

I noticed I am now one version behind on DynDOLOD but I didn't see anything in the changelog that looks related to this issue. Let me know if you think trying again with alpha 89 may help.