Jump to content
  • 0

Can not read Root block from meshes


Dreifels

Question

When create a new output with 2.8.9 I got in log

[00:00:41.549]    Can not read Root block from meshes\effects\fxcreekflatlong01.nif Access violation at address 000000000130DEC8 in module 'DynDOLODx64.exe'. Read of address 0000000089DA0078

[00:00:42.939]    Can not read Root block from meshes\effects\fxcreekflatlong01.nif Access violation at address 000000000130DEC8 in module 'DynDOLODx64.exe'. Read of address 00000000975E0078

 

Edit: nif optimizer says file is fine

Edited by Dreifels
Link to comment
Share on other sites

3 answers to this question

Recommended Posts

  • 0

1) there was no bugreport.txt

2) deleted it in between, but have other issues:

log says at and: "[00:15:56.201]    There were errors in one or more LODGen logs (see report above) resulting in incomplete static object LOD."

When I check all logs related the worlds, all logs are same and end adter 3 lines, as sample

"Output: E:\Steam\SteamApps\common\Skyrim Special Edition\DynDOLOD\DynDOLOD_Output\Meshes\Terrain\tamriel\Objects\
Using UV Atlas: E:\Steam\SteamApps\common\Skyrim Special Edition\DynDOLOD\Edit Scripts\DynDOLOD\cache\DynDOLOD_SSE_atlas_map_tamriel.txt
Using Flat Textures: E:\Steam\SteamApps\common\Skyrim Special Edition\DynDOLOD\Edit Scripts\DynDOLOD\cache\DynDOLOD_SSE_flat_textures.txt"

 

nothing more, no error entry

I made a package with all logs for download here https://workupload.com/file/gumSxL2bjQX

 

Edit: all works fine with DynDOLOD-2-87 along with DynDOLOD Resources SE-2-852, just tested.

Edited by Dreifels
Link to comment
Share on other sites

  • 0

1) there was no bugreport.txt

2) deleted it in between, but have other issues:

log says at and: "[00:15:56.201]    There were errors in one or more LODGen logs (see report above) resulting in incomplete static object LOD."

When I check all logs related the worlds, all logs are same and end adter 3 lines, as sample

"Output: E:\Steam\SteamApps\common\Skyrim Special Edition\DynDOLOD\DynDOLOD_Output\Meshes\Terrain\tamriel\Objects\

Using UV Atlas: E:\Steam\SteamApps\common\Skyrim Special Edition\DynDOLOD\Edit Scripts\DynDOLOD\cache\DynDOLOD_SSE_atlas_map_tamriel.txt

Using Flat Textures: E:\Steam\SteamApps\common\Skyrim Special Edition\DynDOLOD\Edit Scripts\DynDOLOD\cache\DynDOLOD_SSE_flat_textures.txt"

 

nothing more, no error entry

I made a package with all logs for download here https://workupload.com/file/gumSxL2bjQX

 

Edit: all works fine with DynDOLOD-2-87 along with DynDOLOD Resources SE-2-852, just tested.

 

Install latest version of .NET and Framework and Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019

 

See if you can bring one of the LODGen command prompt windows to the front when ones is started for a worldspace. It may print more information to the prompt than it is able to write to log.

 

See if using Edit Scripts/LODGenx64.exe from older DynDOLOD version works with newer DynDOLOD version.

Maybe test DynDOLOD 3 Alpha, or just its Edit Scritps/LODGenx64.exe makes a difference.

 

Pay attention to the installation instructions:

 

From the DynDOLOD Standalone archive copy the content of the 'DynDOLOD' folder, which contains the files DynDOLOD.exe, TexGen.exe, DynDOLOD_QuickStart.html and the sub folders 'Docs' and 'Edit Scripts' with all their content into a new 'DynDOLOD' folder outside of special OS folders like 'Programs Files' or 'Program Files (x86)', the SteamApps or game folders and Mod Organizers virtual file structure. Do not mix with old versions or xEdit/xLODGen installation.

Edited by sheson
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
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.