DynDOLOD 3.00 Alpha 180

[jimmywon34]

On 7/2/2022 at 2:30 PM, sheson said:

There seems to be an issue with usvfs_x64.dll from MO2. That's related to the virtual file system.

Update MO2 to the recent version.

thanks for the troubleshoot. i've ran it again once so far so good it's working. 

[maramsp]

I'm installing seasons of skyrim togewther with turn of the seasons now.

As we speak im running xlodgen.

But next up is dyndolod.

Should i regenerate the occlusion as well here?

I havent added any mods other then the seasons of skyrim and turn of the seasons.

So, i think i dont have to regenerate occlusion, but better to be safe then sorry to ask here, to know it for certain.

Thanks in advance!

[Vadnais]

https://ufile.io/g7d47aod

I got it working! Thanks a ton for your help. Using the Recalc Bounds function is what did it.

[maramsp]

18 hours ago, sheson said:

BTO files are NIF files and can be opened with NifSkope.

If you tell TexGen to generate textures in the BC7 format, then you need to use a DDS plugin that can read BC7 format. Otherwise set TexGen to use DXT1 for 3 channel and DXT5 for 4 channel (if just for a test).

The most important thing to check is if the base records have large enough object bounds so that all (most) grasses have billboards generated.

If you check the TexGen debug yourself, you will see a lot of lines like
Ignoring Meshes\landscape\grass\*.nif bounds volume 0, height 0 Seasonal Landscapes.esp ...

Those should be fixed with the CK recalc bounds function, so that billboards are generated for them automatically.

For this, there is the perferct paint program called paint.net

You can get it at getpaint dot net.

It automatically can open all sorts of dds, bc7, bc5, etc, etc.

This is for me the program to go, as i find it much more easier and lightweight compared to gimp

[bigbogdan98]

Decided to try out DynDOLOD 3 after a fresh reinstall of the game and got this error ? What should i do ?

[blyad]

12 hours ago, sheson said:

What makes a computer turn off is a hardware, BIOS setting or OS/driver problem.

This happens after I updated to newest version of 3.0. Before everything went smoothly without any BS.
`Texconv error C0000005` isn't listed in any index of yours about errors. Any information I found online relates to VCRedists not being updated, but that unfortunately isn't the case.
There was also something about MO2, but even after removing it nothing changes.
I'm rendering LOD on my new SSD with way more free space than it should take, so it also isn't a problem.

[sheson]

9 hours ago, maramsp said:

I'm installing seasons of skyrim togewther with turn of the seasons now.

As we speak im running xlodgen.

But next up is dyndolod.

Should i regenerate the occlusion as well here?

I havent added any mods other then the seasons of skyrim and turn of the seasons.

So, i think i dont have to regenerate occlusion, but better to be safe then sorry to ask here, to know it for certain.

Thanks in advance!

https://dyndolod.info/Help/Occlusion-Data

LOD Occlusion data hide LOD that is hidden behind terrain LOD. If object LOD changes, occlusion may need to be updated.
The occlusion plugin (like the DynDOLOD plugins) is created by copying worldspace and cell records from the plugins in the load order. If any of those records changes it may be necessary to update.

If the change is just season swap data, then worldspace and cell records do not change and we can assume the object LOD height is about the same, so most lily occlusion does not need to be updated.

7 hours ago, Vadnais said:

https://ufile.io/g7d47aod

I got it working! Thanks a ton for your help. Using the Recalc Bounds function is what did it.

Great. Enjoy.

4 hours ago, bigbogdan98 said:

Decided to try out DynDOLOD 3 after a fresh reinstall of the game and got this error ? What should i do ?

Read the first post which log and debug log to upload.

Do not post screenshots of text or message. Use the link "Copy message to clipboard" and paste the text instead as explained in the first post.

Remove special characters from the installation path, for example the #.

[sheson]

3 hours ago, blyad said:

This happens after I updated to newest version of 3.0. Before everything went smoothly without any BS.
`Texconv error C0000005` isn't listed in any index of yours about errors. Any information I found online relates to VCRedists not being updated, but that unfortunately isn't the case.
There was also something about MO2, but even after removing it nothing changes.
I'm rendering LOD on my new SSD with way more free space than it should take, so it also isn't a problem.

If a computer turns off, reboots, has a BSOD etc., then there is a hardware, BIOS setting, OS or driver problem.

If there is a log, debug log, bugreport.txt then upload them as explained at the first post. If there is an error message, event log entry copy and paste its text.

[maramsp]

27 minutes ago, sheson said:

https://dyndolod.info/Help/Occlusion-Data

LOD Occlusion data hide LOD that is hidden behind terrain LOD. If object LOD changes, occlusion may need to be updated.
The occlusion plugin (like the DynDOLOD plugins) is created by copying worldspace and cell records from the plugins in the load order. If any of those records changes it may be necessary to update.

If the change is just season swap data, then worldspace and cell records do not change and we can assume the object LOD height is about the same, so most lily occlusion does not need to be updated.

Thank you sheson!

But i find it quite strange that for running xlodgen, texgen and dyndolod now with seasons, that xlodgen by far takes the longest to run.
Xlodgen ran for 3 hours before completing, and while selecting only spr, aut, sum and wtr in dyndolod, even with occlusion enabled, just only took 54 minutes.

So, can you verify that this is normal, cause normally it was dyndolod which takes the longest.

Thanks in advance again!

[sheson]

31 minutes ago, maramsp said:

Thank you sheson!

But i find it quite strange that for running xlodgen, texgen and dyndolod now with seasons, that xlodgen by far takes the longest to run.
Xlodgen ran for 3 hours before completing, and while selecting only spr, aut, sum and wtr in dyndolod, even with occlusion enabled, just only took 54 minutes.

So, can you verify that this is normal, cause normally it was dyndolod which takes the longest.

Thanks in advance again!

The tools need the time they need based on user settings and load order.  Use BC7 quick instead of BC7 max.

[blyad]

3 hours ago, sheson said:

If a computer turns off, reboots, has a BSOD etc., then there is a hardware, BIOS setting, OS or driver problem.

If there is a log, debug log, bugreport.txt then upload them as explained at the first post. If there is an error message, event log entry copy and paste its text.

Turns out your software is really great way to stress test CPU, It was because of temps.
I left it for some time alone, without watching YT or anything, and it passed.

pic while rendering LOD

I also think it damaged my RAM

[Kryptkeeperss]

I'm sorta desperate for answers - nothing I've read has been able to help me on this matter so my last option was to create an account here. The title of this thread is self explanatory, I've done everything exactly as stated in a video tutorial, so I'm not sure why I was hit with this once I ran dyndolod. Is there version incompatibilities or something deeper than that? I'm not too sharp when it comes to things like this - if possible, keep the explanations a bit beginner friendly. Thank you.

- I've provided some pictures, I can provide a bit more if possible.

(I forgot to add - when I begin to install the resources, the dyndolod resources "core files" box is checked off and faded out - I'm unable to click on it.)

[sheson]

6 hours ago, blyad said:

Turns out your software is really great way to stress test CPU, It was because of temps.
I left it for some time alone, without watching YT or anything, and it passed.

pic while rendering LOD

I also think it damaged my RAM

Simple Windows programs like xEdit/DynDOLOD or LODGen using standard OS functions can not damage RAM any more than any other program by simply using it.

[sheson]

On 7/8/2022 at 6:18 AM, Kryptkeeperss said:

I'm sorta desperate for answers - nothing I've read has been able to help me on this matter so my last option was to create an account here. The title of this thread is self explanatory, I've done everything exactly as stated in a video tutorial, so I'm not sure why I was hit with this once I ran dyndolod. Is there version incompatibilities or something deeper than that? I'm not too sharp when it comes to things like this - if possible, keep the explanations a bit beginner friendly. Thank you.

- I've provided some pictures, I can provide a bit more if possible.

(I forgot to add - when I begin to install the resources, the dyndolod resources "core files" box is checked off and faded out - I'm unable to click on it.)

Moved the post to the DynDOLOD 3 Alpha thread.

Upload the log and debug log when making posts as explained on the first post.
Use the "Copy message to clipboard" link and paste the text instead of posting screenshots as explained on the first post.
Click the "Click on this link for additional explanations and help for this message" to open https://dyndolod.info/Help/DynDOLOD-Resources. Check the Troubleshooting section.

Do not install the game into special Windows folders like Program Files x86 to avoid issues with access permissions, UAC, antivir etc.

Yes, the error message is self explanatory. A required file that is installed with DynDOLOD Resources SE Core Files is not found in the used data folder of the game.
The FOMOD installer always has the Core Files checked. The checkbox can not be unchecked.

[blyad]

8 hours ago, sheson said:

Simple Windows programs like xEdit/DynDOLOD or LODGen using standard OS functions can not damage RAM any more than any other program by simply using it.

I've got BSOD with error code about ram, but thats probably not true, it's all about temps.

I will change thermal paste and all should return to normal. Didn't suspected that since I changed it like 5 months ago, but thats apparently it.