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

[sheson]

  On 11/22/2018 at 12:09 PM, blo0dik said:

 

Sheson help me plz in version 2.50 almost always gives an error.  

Creating atlas textures E:\Games\MODS SSE\Utilities\DynDOLOD-Standalone.2.50\DynDOLOD\DynDOLOD_Output\Textures\DynDOLOD\LOD\DynDOLOD_Atlas_DeepwoodRedoubtWorld.dds from 23 textures

[00:15:00.203] [16:31]  

[00:15:00.203] [16:31] Exception in unit userscript line 331: System Error.  Code: 5.

Access denied

[00:15:00.203] [16:31]  

[00:15:00.203] [16:31] Check log lines above the exception for additional hints. Check the FAQ and search official forum http://forum.step-project.com/forum/101-shesons-dyndolod-support/ for those errors.

[00:15:00.203] [16:31]  

[00:15:00.203] [16:31] If problem persists, post error report with entire contents (not just the last couple lines) of ..\DynDOLOD\bugreport.txt and ..\DynDOLOD\logs\DynDOLOD_SSE_log.txt to official forum http://forum.step-project.com/forum/101-shesons-dyndolod-support/

[00:15:00.207] [16:31] Error during Applying script "DynDOLOD Worlds": System Error.  Code: 5.

Access denied

 

Bashad patch is disabled, all merged patches too. My windows 10 and i use Dindolod through MO2. what could be the reason for such an error?

 

You did not post error report with entire contents (not just the last couple lines) of ..\DynDOLOD\bugreport.txt and ..\DynDOLOD\logs\DynDOLOD_SSE_log.txt to official forum, so I am just guessing:

 

Creating atlas textures E:\Games\MODS SSE\Utilities\DynDOLOD-Standalone.2.50\DynDOLOD\DynDOLOD_Output\Textures\DynDOLOD\LOD\DynDOLOD_Atlas_DeepwoodRedoubtWorld.dds from 23 textures

 

System Error. Code: 5. Access denied

 

So either the OS/AntiVirus/other process does not let it write the atlas, or it prevents reading of one or more of the 23 textures (or their _n.dds version) listed in ..DynDOLOD\Edit Scripts\DynDOLOD\cache\DynDOLOD_SSE_DeepwoodRedoubtWorld_textures_used.txt

Edited November 22, 2018 by sheson

[gem2492]

I'm using DynDOLOD 2.50, but it isn't working for me. TexGen is fine and successful, but DynDOLOD keeps giving me FAILED (8000405).

I was using BC7 Quick.

 

Here are the logs:

https://www.mediafire.com/file/4cqrjsega4gj2u0/TexGen_SSE_log.txt/file

https://www.mediafire.com/file/4wrwakaozbe1jl2/DynDOLOD_SSE_log.txt/file

 

And here is my mod list (just in case): https://modwat.ch/u/gem2492/plugins

 

And by the way, 2.43 also works fine.

Edited November 22, 2018 by gem2492

[blo0dik]

  On 11/22/2018 at 12:20 PM, sheson said:

You did not post error report with entire contents (not just the last couple lines) of ..\DynDOLOD\bugreport.txt and ..\DynDOLOD\logs\DynDOLOD_SSE_log.txt to official forum, so I am just guessing:

 

Creating atlas textures E:\Games\MODS SSE\Utilities\DynDOLOD-Standalone.2.50\DynDOLOD\DynDOLOD_Output\Textures\DynDOLOD\LOD\DynDOLOD_Atlas_DeepwoodRedoubtWorld.dds from 23 textures

 

System Error. Code: 5. Access denied

 

So either the OS/AntiVirus/other process does not let it write the atlas, or it prevents reading of one or more of the 23 textures (or their _n.dds version) listed in ..DynDOLOD\Edit Scripts\DynDOLOD\cache\DynDOLOD_SSE_DeepwoodRedoubtWorld_textures_used.txt

Yes i am sorry In general, if you use Dindolod with admin rights, then such an error does not appear, and I have an antivirus from Windows native.

The following problem appeared, it is written in the dynodod window that the process is finished, you can save and exit, and the BAT window is still open, in which the lod are being generated (Finished LOD level 4 coord). And it continues somewhere 20 minutes already.  I need to wait for the completion in the bat file and it will close itself, or close the dindolod?

Edited November 22, 2018 by blo0dik

[sheson]

  On 11/22/2018 at 1:14 PM, blo0dik said:

Yes i am sorry In general, if you use Dindolod with admin rights, then such an error does not appear, and I have an antivirus from Windows native.

The following problem appeared, it is written in the dynodod window that the process is finished, you can save and exit, and the BAT window is still open, in which the lod are being generated (Finished LOD

level 4 coord). And it continues somewhere 20 minutes already.  I need to wait for the completion in the bat file and it will close itself, or close the dindolod?

The written synonym of the tools is DynDOLOD. People are easily confused enough already even when using clear and consistent language. Do not use wrong or made up names. There is no need for such pollution.

 

The last few lines of the log should say something like:

 

Gave up waiting for [...LODGen...] to become available.

Wait for [...LODGen...] to finish by itself before closing DynDOLOD.exe'

 

So that should have answered the question already.

 

 

 

FAQ: LODGen.exe: Runs a long time / The LOD files generated are several GB in size

 

A: The selected configuration options require a lot of work. Do not manually close LODGen.exe. Wait for all processes to complete before closing DynDOLOD.

 

A: If there are more objects with LOD, it takes longer and creates larger files. If there are more triangles in the models used for LOD, it takes longer and creates larger files. If there are more triangles in the terrain meshes, it takes longer. 

 

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

[blo0dik]

  On 11/22/2018 at 1:51 PM, sheson said:

 

The written synonym of the tools is DynDOLOD. People are easily confused enough already even when using clear and consistent language. Do not use wrong or made up names. There is no need for such pollution.

 

The last few lines of the log should say something like:

 

Gave up waiting for [...LODGen...] to become available.

Wait for [...LODGen...] to finish by itself before closing DynDOLOD.exe'

 

So that should have answered the question already.

 

 

 

FAQ: LODGen.exe: Runs a long time / The LOD files generated are several GB in size

 

A: The selected configuration options require a lot of work. Do not manually close LODGen.exe. Wait for all processes to complete before closing DynDOLOD.

 

A: If there are more objects with LOD, it takes longer and creates larger files. If there are more triangles in the models used for LOD, it takes longer and creates larger files. If there are more triangles in the terrain meshes, it takes longer. 

 

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

 

Yes, I understood everything, thanks. And yes, I decided to try an experimental TreeFullFallBack setting, simply because in version 2.49, I did get some wonderful trees lods , and in other versions they were ugly, and I do not know what it is connected with, the settings are the same, the bts7 format is both there and there, and the folders DynDOLOD_Output  differed in size by a lot.. so I decided to try something else. I apologize for the time you have spent, and for your English, all the best to you.

Edited November 22, 2018 by blo0dik

[sheson]

  On 11/22/2018 at 12:21 PM, gem2492 said:

I'm using DynDOLOD 2.50, but it isn't working for me. TexGen is fine and successful, but DynDOLOD keeps giving me FAILED (8000405).

I was using BC7 Quick.

 

Here are the logs:

https://www.mediafire.com/file/4cqrjsega4gj2u0/TexGen_SSE_log.txt/file

https://www.mediafire.com/file/4wrwakaozbe1jl2/DynDOLOD_SSE_log.txt/file

 

And here is my mod list (just in case): https://modwat.ch/u/gem2492/plugins

 

And by the way, 2.43 also works fine.

 

BC7 is a new option added in 2.48. See this post in case you want to use other texture compression like before, which is natively build into xEdit/DynDOLOD and does not rely on an external tool.

 

8000405 could mean there was a problem initializing the DirectX device. I would assume a general problem should have already happened when running TexGen and the BC7 compression selected. DynDOLOD.exe=TexGen.exe so they use the exact same code for this. Not sure why TexConv keeps trying instead of just failing.

 

It could be that something else is now active that wasn't while TexGen was running. Or maybe it is the larger size of the texture.

 

See what happens when you open a command prompt and run DynDOLOD\Edit Scripts\Texconvx64.exe without anything. See what it reports for and other stuff.

If it can not acquire a device it usually falls back to CPU automatically.

 

The full resolution 8888 input texture should exist at D:\Games\_Bethesda Utilities\DynDOLOD\DynDOLOD_Output\Textures\DynDOLOD\LOD\DynDOLOD_Flat_Atlas_Tamriel.dds already.

 

See if converting manually by running the command reveals anything more:

Texconvx64.exe -y -sepalpha -m 0 -f BC7_UNORM -bcquick -o "D:\Games\_Bethesda Utilities\DynDOLOD\DynDOLOD_Output\Textures\DynDOLOD\LOD" "D:\Games\_Bethesda Utilities\DynDOLOD\DynDOLOD_Output\Textures\DynDOLOD\LOD\DynDOLOD_Flat_Atlas_Tamriel.dds"

Unrelated, but clean the master files. The non default installation path or potentially not having a valid steam copy of the game may complicated things.

Edited November 22, 2018 by sheson

[gem2492]

  On 11/22/2018 at 2:11 PM, sheson said:

BC7 is a new option added in 2.48. See this post in case you want to use other texture compression like before, which is natively build into xEdit/DynDOLOD and does not rely on an external tool.

 

8000405 could mean there was a problem initializing the DirectX device. I would assume a general problem should have already happened when running TexGen and the BC7 compression selected. DynDOLOD.exe=TexGen.exe so they use the exact same code for this. Not sure why TexConv keeps trying instead of just failing.

 

It could be that something else is now active that wasn't while TexGen was running. Or maybe it is the larger size of the texture.

 

See what happens when you open a command prompt and run DynDOLOD\Edit Scripts\Texconvx64.exe without anything. See what it reports for <adapter> and other stuff.

If it can not acquire a device it usually falls back to CPU automatically.

 

The full resolution 8888 input texture should exist at D:\Games\_Bethesda Utilities\DynDOLOD\DynDOLOD_Output\Textures\DynDOLOD\LOD\DynDOLOD_Flat_Atlas_Tamriel.dds already.

 

See if converting manually by running the command reveals anything more:

Texconvx64.exe -y -sepalpha -m 0 -f BC7_UNORM -bcquick -o "D:\Games\_Bethesda Utilities\DynDOLOD\DynDOLOD_Output\Textures\DynDOLOD\LOD" "D:\Games\_Bethesda Utilities\DynDOLOD\DynDOLOD_Output\Textures\DynDOLOD\LOD\DynDOLOD_Flat_Atlas_Tamriel.dds"

Unrelated, but clean the master files. The non default installation path or potentially not having a valid steam copy of the game may complicated things.

About the installation path, I used this thing called Steam Mover.

 

I ran Texconvx64.exe using command prompt, but it closes too suddenly for me to inspect everything on it. So I just tried to press PrtScrn as soon as the program blinks. Here is what I got: https://www.mediafire.com/view/xvka1j1jj5k59y9/idk.png/file

 

It definitely detects the right adapter.

 

I tried your suggestion about the texture format. Indeed the file is smaller. Here is the updated TexGen log: https://www.mediafire.com/file/796mb21d6tpg1ss/TexGen_SSE_log2.txt/file

 

However DynDOLOD still failed with the same error code. And also, the folder D:\Games\_Bethesda Utilities\DynDOLOD\DynDOLOD_Output\Textures\DynDOLOD\LOD\ is empty.

 

Unfortunately I can't bring back the game to the default location because my C drive is already almost full, so I don't know anymore.

[sheson]

  On 11/23/2018 at 2:04 PM, gem2492 said:

About the installation path, I used this thing called Steam Mover.

 

I ran Texconvx64.exe using command prompt, but it closes too suddenly for me to inspect everything on it. So I just tried to press PrtScrn as soon as the program blinks. Here is what I got: https://www.mediafire.com/view/xvka1j1jj5k59y9/idk.png/file

 

It definitely detects the right adapter.

 

I tried your suggestion about the texture format. Indeed the file is smaller. Here is the updated TexGen log: https://www.mediafire.com/file/796mb21d6tpg1ss/TexGen_SSE_log2.txt/file

 

However DynDOLOD still failed with the same error code. And also, the folder D:\Games\_Bethesda Utilities\DynDOLOD\DynDOLOD_Output\Textures\DynDOLOD\LOD\ is empty.

 

Unfortunately I can't bring back the game to the default location because my C drive is already almost full, so I don't know anymore.

 

Open a "command prompt" first, then run the program in it. The standard output of a program can be forwarded into a text file by adding > file.txt at the end.

 

Since TexGen was creating textures with BC7 without problems, there is no need to change its compression settings or to rerun TexGen.

 

If DynDOLOD still shows a FAILED (xxxxxxxx) message, double check that not one or more of the INI settings in DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini is still set to use BC7. 

If you are sure none of the settings uses BC7, then it might mean the FAILED messages comes from trying to read a BC7 texture.

 

The game location or location of the tools themselves should not matter.

 

The system drive C being nearly full could the be a reason for the problem, as there might be not enough room for temp files in c:\windows\temp or C:\Users\[user]\AppData\Local\Temp, the paging file or other OS things.

 

You can use the -:t command line argument for DynDOLOD/TexGen/xEdit to set a different temp folder on another drive.

 

DynDOLODx64.exe -sse -t:"D:\Games\_Bethesda Utilities\DynDOLOD\temp\" for example might just do the trick.

 

Edit: Test with 2.51 in case there are still errors. I made some additions to the messages that should help better with troubleshooting

Edited November 23, 2018 by sheson

[Shadriss]

I've also been seeing consistent Error 5's with 2.50. This has not been previously the case - I've run both TexGen and DynDOLOD many times on previous versions from the same locations with no issues to this point. Managed to get one clean run out of about 7 attempts - that one clean run was after a fresh install. Cleaning out the generated files and cache files have made no difference.
 

Link to bugreport.txt here.

 

Not getting the FAILED messages (that I noticed), just the simple Access Denied. I haven't tried giving the program Admin rights yet (as I've seen that cause issues elsewhere before), but will be trying that as a next step in the T/S Process. File provided for your use and for any other T/S suggestions you might have.

[sheson]

  On 11/23/2018 at 10:14 PM, Shadriss said:

I've also been seeing consistent Error 5's with 2.50. This has not been previously the case - I've run both TexGen and DynDOLOD many times on previous versions from the same locations with no issues to this point. Managed to get one clean run out of about 7 attempts - that one clean run was after a fresh install. Cleaning out the generated files and cache files have made no difference.

 

Link to bugreport.txt here.

 

Not getting the FAILED messages (that I noticed), just the simple Access Denied. I haven't tried giving the program Admin rights yet (as I've seen that cause issues elsewhere before), but will be trying that as a next step in the T/S Process. File provided for your use and for any other T/S suggestions you might have.

 

System Error. Code: 5. Access is denied.

 

This is a message from the OS. There is nothing that DynDOLOD can do to circumvent the OS preventing access.

 

The obvious first thing is try using different folders.

 

It is possible that UAC or AntiVirus does not like any of the latest version of executables (including the ones in Edit Script subfolder) for some reason. 

 

From the bugreport I can tell you it happens when it is using TexConv to load a texture.

 

For a test you could try to use an older TexConv from the older DynDOLOD version. Should still work fine, may be a bit more log spam.

 

Running/setting things "as admin" is a workaround, but not really a recommended fix. Things should be set up in a way that everything works without that.  If right clicking on a file has an "Unblock", apply that. 

 

The Windows event log might have a bit more detail.

Edited November 23, 2018 by sheson

[Shadriss]

As an update, the Admin did give me a clean run. I agree it shouldn't be needed. UAC is turned off, and the executable files aren't in a UAC controlled location anyway. As I noted, the location it's currently in has run with no issues for years... essentially since STEP originally added this as part of its guide. Given that the only change has been the update to 2.50, I can only conclude that, unintentionally, something has changed that Windows in general doesn't like. I'm seeing this same report occur in many Discord reports as well.

 

Regardless, even if it is an undesirable workaround, it does work. At least in my case.

[gem2492]

  On 11/23/2018 at 2:48 PM, sheson said:

 

Open a "command prompt" first, then run the program in it. The standard output of a program can be forwarded into a text file by adding > file.txt at the end.

 

Since TexGen was creating textures with BC7 without problems, there is no need to change its compression settings or to rerun TexGen.

 

If DynDOLOD still shows a FAILED (xxxxxxxx) message, double check that not one or more of the INI settings in DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini is still set to use BC7. 

If you are sure none of the settings uses BC7, then it might mean the FAILED messages comes from trying to read a BC7 texture.

 

The game location or location of the tools themselves should not matter.

 

The system drive C being nearly full could the be a reason for the problem, as there might be not enough room for temp files in c:\windows\temp or C:\Users\[user]\AppData\Local\Temp, the paging file or other OS things.

 

You can use the -:t command line argument for DynDOLOD/TexGen/xEdit to set a different temp folder on another drive.

 

DynDOLODx64.exe -sse -t:"D:\Games\_Bethesda Utilities\DynDOLOD\temp\" for example might just do the trick.

 

Edit: Test with 2.51 in case there are still errors. I made some additions to the messages that should help better with troubleshooting

Here is what Texconvx64.exe says when I run it with cmd: https://www.mediafire.com/file/zjy9m4sy1fm9bf5/Texconvx64.txt/file

 

Since you said that BC7 is okay, I didn't bother changing the settings.

 

I tried 2.51 this time and it was successful, although I found the same error (80004005, kinda hating that number now. lol) in the log.

[00:05:56.012]	FAILED loading DDS (80004005) D:\Games\_Bethesda Utilities\DynDOLOD\temp\FD0D0E2B08764A7CBB97FCC0ACA8D1DB.dds
[00:12:33.302]	FAILED loading DDS (80004005) D:\Games\_Bethesda Utilities\DynDOLOD\temp\5A3A5AFFAD8B4A28860556B711EAE377.dds
[00:15:44.985]	FAILED loading DDS (80004005) D:\Games\_Bethesda Utilities\DynDOLOD\temp\4FFBA552DEAA4321AC0AB4BA7BFEC57D.dds

Here are all the logs: https://www.mediafire.com/file/8er3ri5625v8yq9/Logs.zip/file

[sheson]

  On 11/24/2018 at 6:10 AM, gem2492 said:

Here is what Texconvx64.exe says when I run it with cmd: https://www.mediafire.com/file/zjy9m4sy1fm9bf5/Texconvx64.txt/file

 

Since you said that BC7 is okay, I didn't bother changing the settings.

 

I tried 2.51 this time and it was successful, although I found the same error (80004005, kinda hating that number now. lol) in the log.

[00:05:56.012]	FAILED loading DDS (80004005) D:\Games\_Bethesda Utilities\DynDOLOD\temp\FD0D0E2B08764A7CBB97FCC0ACA8D1DB.dds
[00:12:33.302]	FAILED loading DDS (80004005) D:\Games\_Bethesda Utilities\DynDOLOD\temp\5A3A5AFFAD8B4A28860556B711EAE377.dds
[00:15:44.985]	FAILED loading DDS (80004005) D:\Games\_Bethesda Utilities\DynDOLOD\temp\4FFBA552DEAA4321AC0AB4BA7BFEC57D.dds

Here are all the logs: https://www.mediafire.com/file/8er3ri5625v8yq9/Logs.zip/file

 

OK, this looks like some broken texture. Replace DynDOLODx64.exe with this test version, it should let us know with yet another additional message what the original texture fie name is before it becomes the temp-file.dds that is failing.

 

You do not need to run the entire generation process for this test. You can change to expert mode, select a worldspace that had the problem and use the Rebuild Atlas button as explained in DynDOLOD_TexGen.html Update Texture Atlas section.

Edited November 24, 2018 by sheson

[gem2492]

  On 11/24/2018 at 11:51 AM, sheson said:

OK, this looks like some broken texture. Replace DynDOLODx64.exe with this test version, it should let us know with yet another additional message what the original texture fie name is before it becomes the temp-file.dds that is failing.

 

You do not need to run the entire generation process for this test. You can change to expert mode, select a worldspace that had the problem and use the Rebuild Atlas button as explained in DynDOLOD_TexGen.html Update Texture Atlas section.

If I were not mistaken, the worlds with error are arnimaDUPLICATE003, Tamriel, and Sovngarde.

 

Here is the log: https://www.mediafire.com/file/4eu786s78lmx9kk/RebuildAtlas.txt/file

 

It looks like swordferncluster04_000b8a66.dds was the problem. Is that right?

[sheson]

  On 11/24/2018 at 1:49 PM, Vokans said:

Hi,

 

sorry i am not a native english speaker.

 

I use the new version and now i have this issue.

 

Where can i get the previous version?

 

Thank you

Expand  

This is not how it works. There is no previous version. We do not ignore problems, we fix the cause of them in the one and only current version.

 

If problem persists post error report with entire contents (not just the last couple lines) of ..\DynDOLOD\bugreport.txt (if it exists) and ..DynDOLOD\Logs\DynDOLOD_[GAMEMODE]_log.txt or a screenshot of the error to https://forum.step-project.com/forum/101-shesons-dyndolod-support.