Jump to content

Recommended Posts

7 hours ago, MITSUYOMI said:

Apparently, my issue with the access error or something is because the new Beyond Skyrim Bruma version deletes a cell in Tamriel. Disabling the file while running dyndo works but it is not a fix either. Hoping that it will get patched soon tho.

Problems can not be investigated or fixed if people do not upload log files and bugreport.txt as explained in the first post.

LOD generation runs through without a problem with Beyond Bruma 1.5.1 installed and enabled in the load order.

Share this post


Link to post
Share on other sites

Hey sorry to bother you guys again, I just had a final question of something more obscure and I don't have time IRL to test on yet.
When you change the Top Grass RGB brightness values in DynDOLOD_SSE.ini do you need to regenerate TexGen or DynDOLOD each time? Or is this something that can be changed after generating a DynDOLOD_Output or Texgen file in some way?

Thank you as always, even if its just reading it.

Share this post


Link to post
Share on other sites
4 minutes ago, Sandcom said:

Hey sorry to bother you guys again, I just had a final question of something more obscure and I don't have time IRL to test on yet.
When you change the Top Grass RGB brightness values in DynDOLOD_SSE.ini do you need to regenerate TexGen or DynDOLOD each time? Or is this something that can be changed after generating a DynDOLOD_Output or Texgen file in some way?

Thank you as always, even if its just reading it.

The second post / ..\DynDOLOD3\docs\help\GrassLOD.html ""Updating" section explains how to update / test different settings.

Share this post


Link to post
Share on other sites
7 hours ago, sheson said:

The second post / ..\DynDOLOD3\docs\help\GrassLOD.html ""Updating" section explains how to update / test different settings.

Thank you! I'll read it on my plane ride, I really appreciate it, and sorry for making you repeat things you've told others.

Edited by Sandcom
Apology needed for inconveniencing Author and Mod Team with what is likely self-explanatory questions.

Share this post


Link to post
Share on other sites

Hello Sir Sheson. First of all, thank you for your amazing work and for being so active and helpful. 

I recently restarted modding skyrim after a longer break and built my LO.
I've been using DyndoLod 2.0 for a long while and tried out 3.0 months ago without any issues. 



The problem came when I tried to run DYNDOLOD 3.0 (pre AE version, using Papyrus Logs) with Ultra Settings etc. 
My game would literally crash after launching either a new game or getting into an already existing save file. I tracked the crashes down to the Dyndolod.esp.
After a loooong while of constantly running dyndolod again and again. I came across an old post where you pretty much told the person to manually disable chunks of DYNDOLOD Output and check if it works. I did that and came across empty meshes (file size 235b, name of NiNode ''obj'') in the meshes/terrain/objects folder, which I disabled afterwards. No crashes happened afterwards. (Netscript Framework Crash Logs would also mention this mesh in the crash logs)
Screenshot-272.png
Desktop-Screenshot-2021-11-22-19-02-03-8

Do you perhaps know what type of mods could cause these types of meshes to be generated via dyndolod? I have never had this issue before.

(Here is my LO if u rly need it)
https://paste.ee/p/B9mYE

(Edit: NTOverhaul.esp is tree replacer and NTADDON.esp tree addon, NGOverhaul.esp is grass mashup)
 

With kind regards,
Noah

Edited by NoahR

Share this post


Link to post
Share on other sites

Edit: Actually scrap that.
I hid the whole meshes/terrain/tamriel/objects folder and not only these few meshes from the screenshot - and I'm still getting crashes...
So my stupid a## didn't fix anything and I hope I didn't waste your time when reading this.
I guess I will have to test more... Unfortunately, I can't get rid of my original post so I'm sorry 'bout that.

Wish you a nice day :)

Share this post


Link to post
Share on other sites
5 hours ago, NoahR said:

Hello Sir Sheson. First of all, thank you for your amazing work and for being so active and helpful. 

I recently restarted modding skyrim after a longer break and built my LO.
I've been using DyndoLod 2.0 for a long while and tried out 3.0 months ago without any issues. 



The problem came when I tried to run DYNDOLOD 3.0 (pre AE version, using Papyrus Logs) with Ultra Settings etc. 
My game would literally crash after launching either a new game or getting into an already existing save file. I tracked the crashes down to the Dyndolod.esp.
After a loooong while of constantly running dyndolod again and again. I came across an old post where you pretty much told the person to manually disable chunks of DYNDOLOD Output and check if it works. I did that and came across empty meshes (file size 235b, name of NiNode ''obj'') in the meshes/terrain/objects folder, which I disabled afterwards. No crashes happened afterwards. (Netscript Framework Crash Logs would also mention this mesh in the crash logs)
Screenshot-272.png
Desktop-Screenshot-2021-11-22-19-02-03-8

Do you perhaps know what type of mods could cause these types of meshes to be generated via dyndolod? I have never had this issue before.

(Here is my LO if u rly need it)
https://paste.ee/p/B9mYE

(Edit: NTOverhaul.esp is tree replacer and NTADDON.esp tree addon, NGOverhaul.esp is grass mashup)
 

With kind regards,
Noah

 

3 hours ago, NoahR said:

Edit: Actually scrap that.
I hid the whole meshes/terrain/tamriel/objects folder and not only these few meshes from the screenshot - and I'm still getting crashes...
So my stupid a## didn't fix anything and I hope I didn't waste your time when reading this.
I guess I will have to test more... Unfortunately, I can't get rid of my original post so I'm sorry 'bout that.

Wish you a nice day :)

Read the DynDOLOD FAQ and the DynDOLOD Readme how to troubleshoot CTD. Pay attention to the log messages, especially warning and errors about textures.

Read the first post what log files to upload when making reports. Include the LODGen log Tamriel, too. A load order includes all mods not just the list of plugins. Use modwatch if you want to provide that information.

If I had to guess it's the invalid texture from RedBag's Rorikstead.esp as discussed before.

Share this post


Link to post
Share on other sites
13 hours ago, sheson said:

 

Read the DynDOLOD FAQ and the DynDOLOD Readme how to troubleshoot CTD. Pay attention to the log messages, especially warning and errors about textures.

Read the first post what log files to upload when making reports. Include the LODGen log Tamriel, too. A load order includes all mods not just the list of plugins. Use modwatch if you want to provide that information.

If I had to guess it's the invalid texture from RedBag's Rorikstead.esp as discussed before.

1. Sorry. Next time (hopefully, a next time won't happen since dyndolod usually run perfectly fine for me) I will keep this in mind! 
2. Thank you SO MUCH! It fixed all my problems - I ran dyndolod without RedBag's Rorikstead.esp and I haven't experienced any CTD for 50 min now. Just shows how incompetent I was when trying to fix it myself. Such a simple and fast solution. <3

Share this post


Link to post
Share on other sites
37 minutes ago, NoahR said:

1. Sorry. Next time (hopefully, a next time won't happen since dyndolod usually run perfectly fine for me) I will keep this in mind! 
2. Thank you SO MUCH! It fixed all my problems - I ran dyndolod without RedBag's Rorikstead.esp and I haven't experienced any CTD for 50 min now. Just shows how incompetent I was when trying to fix it myself. Such a simple and fast solution. <3

Temporarily disabling plugins or mods is a troubleshooting step. It does not fix errors / invalid textures.

The mod contains an invalid texture that needs to be updated. Either download the fix provided by the mod author (check the bug section) or remove the mod permanently.

Share this post


Link to post
Share on other sites

I keep getting an Out of Memory error when trying to start TexGenx64 in the new Alpha 55.

[00:05] Background Loader: finished
[00:00] Loading configuration files
[00:00] Game: D:\SteamLibrary\steamapps\common\Skyrim Special Edition\SkyrimSE.exe, Version: 1.6.323, Date: 2021-11-22 19:06:19
[00:00] SKSE: D:\SteamLibrary\steamapps\common\Skyrim Special Edition\skse64_loader.exe, Version: 2.1.3, Date: 2021-11-23 00:46:30
[00:00] DynDOLOD DLL: D:\SteamLibrary\steamapps\common\Skyrim Special Edition\Data\SKSE\Plugins\DynDOLOD.dll, Version: 2.45, Game Version: 1.6.323, Date: 2021-11-23 01:45:00
[00:00] PapyrusUtil DLL: D:\SteamLibrary\steamapps\common\Skyrim Special Edition\Data\SKSE\Plugins\PapyrusUtil.dll, Version: 4.1, Game Version: 1.6.323, Date: 2021-11-23 08:53:56
[00:00] Program: D:\Game Apps\Manual Mods\DynDOLOD\TexGenx64.exe, Version: 3.0.0.0, Date: 2021-11-23 16:31:58
[00:00] Started by: C:\Windows\explorer.exe, Version: 10.0.22000.120, Date: 2021-10-07 18:40:59
[00:00] External: D:\Game Apps\Manual Mods\DynDOLOD\Edit Scripts\Texconvx64.exe, Version: 1.0.0.0, Date: 2021-10-20 01:00:00
 

Strange since I ran DynDOLOD on the same setup 5 days ago with no problem, on the new AE build. Is this related to the 1.6.323 update?

Share this post


Link to post
Share on other sites
16 minutes ago, jpteixeira said:

I keep getting an Out of Memory error when trying to start TexGenx64 in the new Alpha 55.

Strange since I ran DynDOLOD on the same setup 5 days ago with no problem, on the new AE build. Is this related to the 1.6.323 update?

Read the first post which log files and bugreport.txt to upload when making posts.

Share this post


Link to post
Share on other sites
8 minutes ago, sheson said:

Read the first post which log files and bugreport.txt to upload when making posts.

Sorry, this must be all. Bugreport.txt not uploaded as the file doesn't exist. Below is a copy of the error.

[Window Title]
TexGen

[Main Instruction]
Error: Memória esgotada.

[Exit TexGen]

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

 

TexGen_SSE_Debug_log.txt TexGen_SSE_log.txt

Share this post


Link to post
Share on other sites
34 minutes ago, jpteixeira said:

Sorry, this must be all. Bugreport.txt not uploaded as the file doesn't exist. Below is a copy of the error.

[Window Title]
TexGen

[Main Instruction]
Error: Memória esgotada.

[Exit TexGen]

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

TexGen_SSE_Debug_log.txt 501.44 kB · 1 download TexGen_SSE_log.txt 378.36 kB · 0 downloads

The out of memory message happens while testing the graphics card. This part did not really change in the past 10 alphas or so.

If there is more than one graphics card, it is supposed to use the first / better one. See that the primary card is set correctly in the OS/driver.

Make sure VRAM is not used up too much by other processes.

Share this post


Link to post
Share on other sites
32 minutes ago, sheson said:

The out of memory message happens while testing the graphics card. This part did not really change in the past 10 alphas or so.

If there is more than one graphics card, it is supposed to use the first / better one. See that the primary card is set correctly in the OS/driver.

Make sure VRAM is not used up too much by other processes.

Device manager correctly recognizes the GPU. Last driver update was 16 of november, and the last I used DynDOLOD successfully was 18th of november. GPU is a Radeon RX6900 XT (16 GB VRAM). I tried lauching TexGenx64 with Task Manager opened and neither RAM or VRAM passed 50% usage.

Share this post


Link to post
Share on other sites
8 hours ago, sheson said:

The out of memory message happens while testing the graphics card. This part did not really change in the past 10 alphas or so.

If there is more than one graphics card, it is supposed to use the first / better one. See that the primary card is set correctly in the OS/driver.

Make sure VRAM is not used up too much by other processes.

I'm having same issue, with latest alpha. Exactly. VRAM is fine, GFX card is fine as always. I'm running against SAE 1.6.323. Same mod list as I recently ran without issue using Alpha 53 against SAE 1.6.318. No bugreport.txt. Repeated 4x.

TexGen_SSE_log.txtTexGen_SSE_Debug_log.txt

7 hours ago, jpteixeira said:

Device manager correctly recognizes the GPU. Last driver update was 16 of november, and the last I used DynDOLOD successfully was 18th of november. GPU is a Radeon RX6900 XT (16 GB VRAM). I tried lauching TexGenx64 with Task Manager opened and neither RAM or VRAM passed 50% usage.

 

Share this post


Link to post
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

  • Similar Content

    • By Mousetick
      Discussion topic:
      Labyrinthian Shalidor's Maze Fixes by wSkeever
      Wiki Link
      This fixes a bunch of small layout glitches by repositioning objects and replacing meshes in the Shalidor's Maze area, and it adds sunlight.
      Install: if used with Assorted Mesh Fixes, they should overwrite it. There is an ESL plugin, which must be enabled.
      Conflicts: there is a minor conflict with Atlas Map Markers, which AMM wins using LOOT. It must be patched if sunlight is desired (see below). Otherwise no conflict with the current WIP STEP setup as far as I can tell.
      Before > After of one of the more noticeable fixes:

      Before > After of sunlight and shadows - only works if conflict with AMM is resolved:

      See Nexus page for more comparison screenshots.
    • By Crimson13
      Discussion topic:
      Security Overhaul SKSE - Lock Variations by powerofthree
      Wiki Link
      SKSE file that turns the default lock into different kinds based on what you're opening; Dwemer, Falmer, Snow Elf, Apocrypha, and snowy chests/doors. Looking at it I feel like I might actually manually open locks now instead of using autopick, haha. There's even an addon already which adds even more, including locks from other mods like VIGILANT.
    • By R3tro
      Hello so I am brand new to all of this and I have been having TWO issues with DynDOLOD, I have searched for quite a while and have no found a sufficient fix to my problem so I thought I would ask here.

      I keep getting the message when I enter the game "DynDOLOD requires PapyrusUtil" I have already downloaded Papy and there are a few things I have done myself to try and work around the issue.
      - re-downloaded Papyrus
      - re-downloaded DynDOLOD 
      Now I know these are obvious and basic things to list but I wanted to list them anyway for reference.

      Now the second issue which I am almost certain is linked to the first problem I get TWO messages that read 
      "DynDOLOD can not find Tamriel in DynDOLOD_Worlds"
      "DynDOLOD can not find master data in None"

      The issue seem pretty specific on where the problem lies but since I am new to modding I do not want to go around messing with my files and then accidently mess up my mod list, So instead I decided to ask for help here before I go scrounging around.

      Normally I would brush these two things off because DynDOLOD is actually working in my game, It fixed my tree textures and none of my textures/meshes are broken as far as I can tell. The only reason I am trying to fix this issue is that every 5 Seconds those two messages are spammed in the corner of my screen and it is irritating to watch. 

      I have linked both pictures of the messages.

      I would appreciate any help or info on this! Thank you!


       


  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.