DynDOLOD Beta for Skyrim Special Edition, Skyrim VR and Enderal SE 2.98

[sam_dmitry]

As suggested, check the logs for errors. Checking logs can immediately tell you what is wrong.

 

The DynDOLOD_SSE_log.txt shows: 

<Error: LODGenx64.exe check the logfile for errors D:\\Games\\TES V - Skyrim SE\\DynDOLOD\\Logs\\LODGen_SSE_Tamriel_log.txt>

There were errors in one or more LODGen logs (see report above) resulting in incomplete static object LOD.
Check the LODGen logs and fix cause of errors.

The LODGen_SSE_Tamriel_log.txt shows:

Error reading meshes\\terrain\\Tamriel\\Tamriel.4.44.0.btr from BSA/BA2 The lz4 assembly requires the Microsoft Visual C++ 2015 runtime installedlz4.AnyCPU.loader

The Requirements in the manual list:

 

Microsoft Visual C++ 2017 Redistributable - Required by LODGen.exe. Get matching platform x86/x64 depending on which DynDOLOD.exe (x86) or DynDOLODx64.exe (x64) is used. LODGen.exe will print an explanatory message in case it is missing.

 

The 2015/2017 Redistributes are compatible. 

 

Use a legal copy of the game.

 

Holy cow. sheson Thank you so much!

 

I could not understand the error, because I had already installed all versions of Microsoft Visual C ++.

But I have already had both versions for x64 and x86 installed at the same time. This is very strange, but all my programs and games worked correctly, so I did not betray this value.

 

I deleted all x86, reinstalled 2015 and 2017 versions for x64 and Dindolod finally earned!

 

 

 

 

Use a legal copy of the game.

My conscience is clear, I have a license in Steam. But then I downloaded the game with a mod collection, on which one person worked for a long time, in terms of performance and optimization.

I just improve it.

 

It can be easily associated with legal Steam, but I am too lazy to do this)

 

 

 

Thank you for your work! Skyrim no longer looks bald and clumsy from afar)

Edited April 16, 2019 by sam_dmitry

[kranazoli]

Hi Sheson,

 

I've been using Winterhold Restored, for months, and now with the 2.58 DynDOLOD I got an instant CTD when I try to fast travel, or approach Winterhold.

When I disable DynDOLOD the issue has gone away.

 

I noticed that issue at the mod topic, as well.

 

Exactly, that is my issue:

 

 

"Hi,

 

I've been using your mod, for months...

 

Now, I saw that version:

 

1.)

 

" Winterhold Restored (Loose Version)

 

This update requires a new game.

Please read the pinned comments for more details before downloading.

Temporarily disable the BSA version and enable this version if you need to regenerate LODs for DynDOLOD."

 

I also used for months DynDOLOD, as well.

 

BUT!

 

Tried twice, that version and generate the whole DynDOLOD process.

 

coc riverwood

(waiting everything is loaded, ...)

 

tmm 1

 

And, if I try to fast travel to Winterhold, every single time I got a sudden CTD. Every time.

 

2.)

 

After that, I deactivated DynDOLOD (Resources and Texgen + DynDOLOD)

So, load order is the same.

 

Load, that save without DynDOLOD, and works fine. (Fast Travel from Riverwood to Winterhold)

 

I followed your rules, and while I generated DynDOLOD disabled the BSA version, enabled the Loose Version.

After finish, the process deactivated loose one, and let the BSA version.

 

Before, I never ever had to issue something like that.

 

It is obviously related to DynDOLOD or your Loose version, and the rest...

 

3.)

 

ATM:

 

I re-run DynDOLOD again, BUT with the BSA version.

I used for months, and of course the newest DynDOLOD for SSE, 2.58.

 

Very odd!

 

1.) It can't because of load order issue, cause without DynDOLOD (just disabled at MO2) it works fine. So, the load order does not change.

2.) It can't bemod issue, cause in that case without DynDOLOD I also should get CTD, but not.

 

After I finish with the new process, I will give feedback...

 

But:

Do you have any idea, what could be wrong?!

 

Thanks!

 

PS:

I also didn't notice at all with LOD with the BSA version.

 

- So, I do not really understand why the Loose version exists?

- Nobody, told issue like that?

 

Edited:

 

Sadly, the same issue with the BSA version, as well.

I moved your mod at the very button of my load order.

 

coc riverwood

coc whiterun

 

When I want to fast travel, sudden CTD.

 

Hmmmm.... I have no idea...

 

The same CTD, just when I am just trying to approach at Winterhold. For instance, from The Shrine Of Azura, and down the path to Winterhold...

I didn't have any issue with the previous one. Which is sadly don't have. :/"

 

 

I accept any idea, how can I solve that issue.

 

Thanks!

Hi Sheson,

 

It looks like, I also have almost the exact same issue with Winterhold Restored after generated DynDOLOD. :/

That issue in the meantime solved, cause mod author updated Winterhold Restored to 2.1, and found out the issue was cause Majestic Mountain also updated to 2.2

 

After that, that CTD issue has gone away totally.

 

In the meantime, we had a new issue with DynDOLOD, when Dragonsreach top was missing.

And you fixed it, with the 2.58 version of DynDOLOD.

 

ATM, with DynDOLOD 2.59 I have that issue:

 

1.) I can fast travel to Winterhold, but not to the College of Winterhold. (CTD)

2.) % to another part of Winterhold Restored (stable, or the part of the valley (near the ocean), or to the church, and I can step to the inn at Winterhold.

3.) When I go out from the Inn, and starting to move, approach where Faralda is stand, I got a sudden CTD again. :/

 

Rumble!

 

BUT!

Without DynDOLOD, just use Winterhold Restored 2.1 (BSA or Loose version) does not matter no issue at all.

So, the mos is fine. And also I have such mod, which releated to that issue. (for instance a broken NIF file, or something like that)

 

The issue is 99% again with DynDOLOD.

 

I will generate DynDOLOD again, but just for Tamriel Worldspace, and I guess I again will ask yoursupoort what's going on.

(bugreport, log files, etc...)

 

Thank You in advance!

 

I really hope, you can find out what's going on...

[sheson]

Hi Sheson,

 

It looks like, I also have almost the exact same issue with Winterhold Restored after generated DynDOLOD. :/

That issue in the meantime solved, cause mod author updated Winterhold Restored to 2.1, and found out the issue was cause Majestic Mountain also updated to 2.2

 

After that, that CTD issue has gone away totally.

 

In the meantime, we had a new issue with DynDOLOD, when Dragonsreach top was missing.

And you fixed it, with the 2.58 version of DynDOLOD.

 

ATM, with DynDOLOD 2.59 I have that issue:

 

1.) I can fast travel to Winterhold, but not to the College of Winterhold. (CTD)

2.) % to another part of Winterhold Restored (stable, or the part of the valley (near the ocean), or to the church, and I can step to the inn at Winterhold.

3.) When I go out from the Inn, and starting to move, approach where Faralda is stand, I got a sudden CTD again. :/

 

Rumble!

 

BUT!

Without DynDOLOD, just use Winterhold Restored 2.1 (BSA or Loose version) does not matter no issue at all.

So, the mos is fine. And also I have such mod, which releated to that issue. (for instance a broken NIF file, or something like that)

 

The issue is 99% again with DynDOLOD.

 

I will generate DynDOLOD again, but just for Tamriel Worldspace, and I guess I again will ask yoursupoort what's going on.

(bugreport, log files, etc...)

 

Thank You in advance!

 

I really hope, you can find out what's going on...

There is to post all that superfluous information about unrelated problems from the past you had with mods. Stick to the problem and information at hand.

 

It seems there is a problem with the load order. That issue might cause CTD. Read the DynDOLOD FAQ entry about CTD. It points to the readme with hints how to troubleshoot missing or invalid NIFs.

Edited April 17, 2019 by sheson

[kranazoli]

sheson, on 17 Apr 2019 - 3:56 PM, said:

There is to post all that superfluous information about unrelated problems from the past you had with mods. Stick to the problem and information at hand.
It seems there is a problem with the load order. That issue might cause CTD. Read the DynDOLOD FAQ entry about CTD. It points to the readme with hints how to troubleshoot missing or invalid NIFs.

 

Sheson,

It can't be! Before that also got something like that info, and found out the issue is with MM, and later DynDOLOD (missing Dragonreach top)

Again:

It can't be load order issue, cause without DynDOLOD everything works fine. Load order does not change, after I generate DynDOLOD. (just the DynDOLOD files)

Everything else works fine, I can fast travel anywhere, no CTD at all. Nothing.

I can run for hours at Winterhold Restored installed, BUT just without DynDOLOD.

Beleive me, I know, what could cause CTD. ATM, 99% sure it is DnyDOLOD.

(before that also DynDOLOD waas the guilty one, not load order, or anything else.)

It is also can't be NIF issue. Got it Sheson:

Without DynDOLOD no issue at all. The NIF files are there!

I generated a new DynDOLOD, but just for Tamriel, without xLODGEN, just TexGen and DynDOLOD. Nothing else.

Please, answer that question:
 

1.     How could it be, that without DynDOLOD I have no issue at all?
2.     No CTD; No Load order issue; NIF files is there (and SSE AssestOptimized), etc...

How could it be, that without DynDOLOD I have zero issue?!

Something logic answer?

I read the manual.

So, I do not post anything, at all?!

For me it is obvious my CTD is because of DynDOLOD.

I thought this is the DynDOLOD support topic.

I have some idea, that maybe No Snow Under The Roof.

 

 

 

DynDOLOD_SSE_log

 

http://pasted.co/85e5e848

 

TexGen_SSE_log

 

http://pasted.co/2bc311f5

 

 

LODGen_SSE_Tamriel_log

 

http://pasted.co/259cf3be

 

 

Again, the only thing I can say, and repeat myself:

MEA CULPA; MEA CULPA; MEA CULPA

Edited April 17, 2019 by kranazoli

[kranazoli]

I am a real GENIUS, I thought it right.

The CTD is releated to NSUTR + DynDOLOD together.

 

100%

 

I can solve it.

 

Thank you for your cooperation.
(No sense to live without sarcasm and neurons)

 

Watch the (our) video at my signature! (...from love...)

[sheson]

sheson, on 17 Apr 2019 - 3:56 PM, said:

 

There is to post all that superfluous information about unrelated problems from the past you had with mods. Stick to the problem and information at hand.

It seems there is a problem with the load order. That issue might cause CTD. Read the DynDOLOD FAQ entry about CTD. It points to the readme with hints how to troubleshoot missing or invalid NIFs.

 

Sheson,

 

It can't be! Before that also got something like that info, and found out the issue is with MM, and later DynDOLOD (missing Dragonreach top)

 

Again:

 

It can't be load order issue, cause without DynDOLOD everything works fine. Load order does not change, after I generate DynDOLOD. (just the DynDOLOD files)

 

Everything else works fine, I can fast travel anywhere, no CTD at all. Nothing.

 

I can run for hours at Winterhold Restored installed, BUT just without DynDOLOD.

 

Beleive me, I know, what could cause CTD. ATM, 99% sure it is DnyDOLOD.

 

(before that also DynDOLOD waas the guilty one, not load order, or anything else.)

 

It is also can't be NIF issue. Got it Sheson:

 

Without DynDOLOD no issue at all. The NIF files are there!

 

I generated a new DynDOLOD, but just for Tamriel, without xLODGEN, just TexGen and DynDOLOD. Nothing else.

 

Please, answer that question:

 

1.     How could it be, that without DynDOLOD I have no issue at all?
2.     No CTD; No Load order issue; NIF files is there (and SSE AssestOptimized), etc...

How could it be, that without DynDOLOD I have zero issue?!

 

Something logic answer?

 

I read the manual.

 

So, I do not post anything, at all?!

 

For me it is obvious my CTD is because of DynDOLOD.

 

I thought this is the DynDOLOD support topic.

 

I have some idea, that maybe No Snow Under The Roof.

 

 

 

DynDOLOD_SSE_log

 

http://pasted.co/85e5e848

 

TexGen_SSE_log

 

http://pasted.co/2bc311f5

 

 

LODGen_SSE_Tamriel_log

 

http://pasted.co/259cf3be

 

 

Again, the only thing I can say, and repeat myself:

MEA CULPA; MEA CULPA; MEA CULPA

 

DynDOLOD does not cause CTD. The DynDOLOD Resources do not cause CTD. In case of principle bugs and problems that sometimes sneak in there are always plenty of users reporting the same issues.

 

CTDs are often caused by missing or corrupted NIFs. The way DynDOLOD uses them for LOD makes a difference - they can work fine when used "normally". We have troubleshooted this plenty of times in the past years.

That is why there is a FAQ entry and the readme explaining how to troubleshoot for that specific issue.

 

Other then that, the DynDOLOD plugins are build by copying records from other plugins in the load order.

If the CTD is caused by records in the plugins, it is also very easy to troubleshooting with a binary search removing all records that do not contribute to CTDs.

 

 

FAQ: Game: ILS or CTD

 

A: More LOD uses more memory and this can cause infinite loading screen (ILS) or crash to desktop (CTD) if the game is not setup correctly. This should generally not be a problem with Skyrim Special Edition or Skyrim VR, but for Skyrim double check heap memory usage (block 1) with Memory Blocks Log from https://www.nexusmods.com/skyrim/mods/50471/ and adjust SKSE or SSME memory settings. Or use the alternative OSAllocator from crash fixes with pre-loader. Remove satefy-load if it is used to verify it doesn't cause CTD. Set ExpandSystemMemoryX64=false in enblocal.ini 

 

A: Do not use the experimental TreeFullFallBack setting without understanding what it does and what it is for. 

 

A: If heap memory is not the cause of CTD see ..DynDOLOD\Docs\DynDOLOD-README.txt for checking if a missing or invalid nif model used for dynamic LOD is the cause. 

Edited April 17, 2019 by sheson

[steveowashere]

Hello Sheson!

 

I am trying to get DynDOLOD to run via Steam Play (wine) on Linux. I have an otherwise stable setup and everything is working great.

 

I'm encountering error when tree billboards are being generated with Texconv.exe / Texconvx64.exe

 

It gives the following errors:

Invalid value specified with -m (0)

Error: [Tamriel] Trees LOD generation error: Executing TexConv returned error: "Z:\home\steven\.steam\steam\steamapps\common\Skyrim Special Edition\DynDOLOD\Edit Scripts\Texconv.exe" -nologo -y -sepalpha -m 0 -f BC7_UNORM -bcquick -o "Z:\home\steven\Documents\Backups\Textures\Terrain\Tamriel\Trees" "Z:\home\steven\Documents\Backups\Textures\Terrain\Tamriel\Trees\TamrielTreeLod.dds"

Running Texconv.exe / Texconvx64.exe via command line shows that the program will run just fine and displays my correct GPU.

 

Installed and using latest 2.59 standalone and resources. It's a fresh install, so no chance of leftovers.

 

I've tried multiple output directories, permissions are not an issue.

 

I've tried setting textures back to BC1 & BC3.

 

Tried both 32 and 64 versions of DynDOLOD.

 

Attached are bugreport.txt & DynDOLOD_SSE_log.txt

 

Thanks for any help

 

bugreport.txt

DynDOLOD_SSE_log.txt

[sheson]

Hello Sheson!

 

I am trying to get DynDOLOD to run via Steam Play (wine) on Linux. I have an otherwise stable setup and everything is working great.

 

I'm encountering error when tree billboards are being generated with Texconv.exe / Texconvx64.exe

 

It gives the following errors:

Invalid value specified with -m (0)

Error: [Tamriel] Trees LOD generation error: Executing TexConv returned error: "Z:\home\steven\.steam\steam\steamapps\common\Skyrim Special Edition\DynDOLOD\Edit Scripts\Texconv.exe" -nologo -y -sepalpha -m 0 -f BC7_UNORM -bcquick -o "Z:\home\steven\Documents\Backups\Textures\Terrain\Tamriel\Trees" "Z:\home\steven\Documents\Backups\Textures\Terrain\Tamriel\Trees\TamrielTreeLod.dds"

Running Texconv.exe / Texconvx64.exe via command line shows that the program will run just fine and displays my correct GPU.

 

Installed and using latest 2.59 standalone and resources. It's a fresh install, so no chance of leftovers.

 

I've tried multiple output directories, permissions are not an issue.

 

I've tried setting textures back to BC1 & BC3.

 

Tried both 32 and 64 versions of DynDOLOD.

 

Attached are bugreport.txt & DynDOLOD_SSE_log.txt

 

Thanks for any help

It doesn't seem to makes much sense for TexConv to return "Invalid value specified with -m (0)" but accept the exact same command line when running it manually. Something in the environment must be different between executing the command manually and running DynDOLOD.

 

Have a look at this https://github.com/Microsoft/DirectXTex/issues/128. The mipmap levels also uses swscanf_s to check the value. 

 

You could test with the official version from https://github.com/Microsoft/DirectXTex/releases, renaming it to Texconvx64.exe should work.

 

Do not install DynDOLOD into Steam or Game folders. Is it normal for to have a hidden ".steam" folder in the path?

 

If all else fails, set the textures to use R8G8B8 and R8G8B8A8 in DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini so that TexConv is not executed.

 

For example:

 

ObjectLODDiffuseFormat=87

ObjectLODAlphaDiffuseFormat=88

ObjectLODNormalFormat=87

TreeLODDiffuseFormat=88

 

Then manually convert them once they have been created. You can also set ObjectLODDiffuseFormat=88 if you prefer to have a single object LOD texture.

Edited April 21, 2019 by sheson

[steveowashere]

 

Have a look at this https://github.com/M...XTex/issues/128. The mipmap levels also uses swscanf_s to check the value. 

Yes, this seems to be a wine issue then. I'll try to see if there are any workarounds. Otherwise i'll report it as a bug with wine.

 

 

 

Is it normal for to have a hidden ".steam" folder in the path?

Yes, that's Steam's doing. It puts everything there by default.

 

 

If all else fails, set the textures to use R8G8B8 and R8G8B8A8 in DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini so that TexConv is not executed.

I've tried this, but still the same error. It seems that texconv is still trying to do something. My DynDOLOD_SSE.ini settings for texture format is as follows:

ObjectLODDiffuseFormat=87
ObjectLODAlphaDiffuseFormat=88
ObjectLODNormalFormat=87
TreeLODDiffuseFormat=88

bugreport.txt

DynDOLOD_SSE_log.txt

DynDOLOD_SSE.ini

[sheson]

 

Yes, this seems to be a wine issue then. I'll try to see if there are any workarounds. Otherwise i'll report it as a bug with wine.

 

 

Yes, that's Steam's doing. It puts everything there by default.

 

I've tried this, but still the same error. It seems that texconv is still trying to do something. My DynDOLOD_SSE.ini settings for texture format is as follows:

ObjectLODDiffuseFormat=87
ObjectLODAlphaDiffuseFormat=88
ObjectLODNormalFormat=87
TreeLODDiffuseFormat=88

Ahh right I forgot. It is actually using TexConv to create mipmaps in the first place since that option is quicker than the build-on method. Sorry, looks like you are out of luck at the moment for tree LOD (Object LOD atlas should work because the mipmaps are generated internally). I might add a setting to control that in the next version.

Edited April 21, 2019 by sheson

[steveowashere]

Thanks for the help regardless! That option might be nice to have, but I don't know who else would need it besides crazy people trying to run modded Skyrim under wine.

 

I'll try to figure out if texconv can be fixed under wine in the meantime.

 

Otherwise I have a VM I can just run DynDOLOD there, not ideal, but still possible.

[sheson]

Thanks for the help regardless! That option might be nice to have, but I don't know who else would need it besides crazy people trying to run modded Skyrim under wine.

 

I'll try to figure out if texconv can be fixed under wine in the meantime.

 

Otherwise I have a VM I can just run DynDOLOD there, not ideal, but still possible.

Actually... I can just compile a version of TexConv that defaults to use 0 in case the number of the -m command line can not be determined. Maybe that works out for you.

 

Just replace them both TexConv.exe and TexConvx64.exe in the Edit Scripts folder with this version and see if it works, 

[steveowashere]

 That's a really good idea, but sadly it still is giving the same error. Thanks for the effort.

[sheson]

 That's a really good idea, but sadly it still is giving the same error. Thanks for the effort.

Try this version https://mega.nz/#!9FZBjSqK!v2ksMIYsDyepgQXVLKOz3GGGIYxciuNq47WGG8rnYjk

[steveowashere]

This didn't work either. But, a different error now

FAILED [mipmaps] (80070057)

[Log attached]

 

 

DynDOLOD_SSE_log.txt