sheson Posted June 14, 2023 Author Posted June 14, 2023 50 minutes ago, bargalarkh said: I've already followed all these steps. Can I take from your answer then that the ./skse/plugins/DynDOLOD_Worlds.txt and ./skse/plugins/DynDOLOD_Worlds.json files won't have any effect if they are overwritten? If generation 1 (for Skyrim worldspaces) gives me a file referencing Skyrim worldspaces and generation 2 (for Dragonborn worldspaces) gives me a file which references Dragonborn worldspaces, overwriting with the second generation will result in a DynDOLOD_Worlds.txt and DynDOLOD_Worlds.json which do not now reference Skyrim worldspaces. Will this have any effect at all? Alternatively, is it possible to just select Rebuild Atlas on the first run and then Execute LODGen on the second? Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which log, debug log and bugreport.txt (if it exists) to upload when making posts. DynDOLOD supports updating/adding new worldspace to existing output. If there are problems with features make a problem report as explained at https://dyndolod.info/Official-DynDOLOD-Support-Forum with the log and debug log as explained. If doing several session, secure the debug log, as it gets overwritten with every new session. Edit: I was able to reproduce this regression in the current alpha version. It will be fixed in the next alpha version. Rebuilding the atlas is a feature to replace the existing atlas textures.
sheson Posted June 14, 2023 Author Posted June 14, 2023 20 minutes ago, bargalarkh said: I just reran generation again for all worldspaces - the Taking Your Firstborn program closed itself without error message while one of the command line windows was still open. Here's the logs (no bugreport.txt) https://ufile.io/f/etyej TexGen/DynDOLOD do not close themselves without user interaction. The debug log you uploaded seems to show the tool was closed by the user. The debug log is not necessarily from that session, since logs are only saved when the program is allowed to handle its own shut down after user interaction. If a program "closes itself" without a exception message prompt and without being able to save the log, debug log, it means it was terminated by the OS (in that case there should be Windows event log entry), because of hardware issues like CPU overclocking, temps, memory etc. or the task manager for example. Install the latest WHQL Recommended graphics drivers only, without any crapware. The debug log shows that MaxLODGen and LODGenThreadSplit is still the default 0 and MaxLODGenPerWorldspace is still the default 2. Read https://dyndolod.info/Help/Seasons#Out-of-Memory-errors.
bargalarkh Posted June 14, 2023 Posted June 14, 2023 Yeah I did close the console window after noticing the DDL program itself was closed, but definitely the Taking Your Firstborn window closed without message or prompt from me. It's not installed in a UAC folder, I turned off Antivirus, and don't have any crapware that I know of (and I have checked). No overclocking etc either. By WHQL would that be the latest graphical drivers? I have an AMD card and have the most up-to-date version of it running. Following the advice in this thread i turned off the AMD named processes which helped initially. I just ran again with MaxLodGen limited to 2 (logs) This is my CPU (six cores). Should I try for LODGenThreadSplit=12 then? I have got Event Viewer up now to see the windows event logs but I'm not sure how to find logs pertaining to this program
bargalarkh Posted June 14, 2023 Posted June 14, 2023 I found the windows logs, here's a few that I found from around the time I last generated: -----1----- - System - Provider [ Name] Application Error - EventID 1000 [ Qualifiers] 0 Version 0 Level 2 Task 100 Opcode 0 Keywords 0x80000000000000 - TimeCreated [ SystemTime] 2023-06-14T15:13:07.0142052Z EventRecordID 13638 Correlation - Execution [ ProcessID] 0 [ ThreadID] 0 Channel Application Computer Beemo Security - EventData DynDOLODx64.exe 3.0.0.128 646a6e33 ntdll.dll 10.0.19041.2788 2f715b17 c0000374 00000000000ff449 4d90 01d99ed172d77282 F:\Skyrim Modding\Tools\DynDOLOD\DynDOLODx64.exe C:\WINDOWS\SYSTEM32\ntdll.dll 522a94fc-b26d-4fad-bd01-14aba092bba7 -----2----- - System - Provider [ Name] Application Error - EventID 1000 [ Qualifiers] 0 Version 0 Level 2 Task 100 Opcode 0 Keywords 0x80000000000000 - TimeCreated [ SystemTime] 2023-06-14T14:52:35.3364553Z EventRecordID 13627 Correlation - Execution [ ProcessID] 0 [ ThreadID] 0 Channel Application Computer Beemo Security - EventData DynDOLODx64.exe 3.0.0.128 646a6e33 ntdll.dll 10.0.19041.2788 2f715b17 c0000374 00000000000ff449 1b2c 01d99ece97605943 F:\Skyrim Modding\Tools\DynDOLOD\DynDOLODx64.exe C:\WINDOWS\SYSTEM32\ntdll.dll a7fe86b9-1e49-4c6b-a7a5-8ba0f979b813
sheson Posted June 14, 2023 Author Posted June 14, 2023 10 minutes ago, bargalarkh said: Yeah I did close the console window after noticing the DDL program itself was closed, but definitely the Taking Your Firstborn window closed without message or prompt from me. It's not installed in a UAC folder, I turned off Antivirus, and don't have any crapware that I know of (and I have checked). No overclocking etc either. By WHQL would that be the latest graphical drivers? I have an AMD card and have the most up-to-date version of it running. Following the advice in this thread i turned off the AMD named processes which helped initially. I just ran again with MaxLodGen limited to 2 (logs) This is my CPU (six cores). Should I try for LODGenThreadSplit=12 then? I have got Event Viewer up now to see the windows event logs but I'm not sure how to find logs pertaining to this program With WHQL I mean not to use a beta driver. Make sure to not install anything but the driver - or terminate all AMD services, background programs etc. The new logs show the tool being seemingly closed by the user right after start before any real work was done or any LODGen processes were started. They are probably not from another session. The tools can only save their log files when they are allowed to properly showdown after user interaction. Check the Windows event log for messages if TexGen/DynDOLOD are being terminated. Enable the realtime log as explained at https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs Keep an eye on memory usage of the main DynDOLOD process and the number of spawned LODGenx64Win.exe processes and their memory usage in task manager. Enable the "Peak Working Set" column to keep a record of the maximum. With the 6 cores the automatic split should be 6, so yes, see what happens with 12, but you can set any number in between as well or even lower to test what happens.
sheson Posted June 14, 2023 Author Posted June 14, 2023 11 minutes ago, bargalarkh said: I found the windows logs, here's a few that I found from around the time I last generated: -----1----- - System - Provider [ Name] Application Error - EventID 1000 [ Qualifiers] 0 Version 0 Level 2 Task 100 Opcode 0 Keywords 0x80000000000000 - TimeCreated [ SystemTime] 2023-06-14T15:13:07.0142052Z EventRecordID 13638 Correlation - Execution [ ProcessID] 0 [ ThreadID] 0 Channel Application Computer Beemo Security - EventData DynDOLODx64.exe 3.0.0.128 646a6e33 ntdll.dll 10.0.19041.2788 2f715b17 c0000374 00000000000ff449 4d90 01d99ed172d77282 F:\Skyrim Modding\Tools\DynDOLOD\DynDOLODx64.exe C:\WINDOWS\SYSTEM32\ntdll.dll 522a94fc-b26d-4fad-bd01-14aba092bba7 -----2----- - System - Provider [ Name] Application Error - EventID 1000 [ Qualifiers] 0 Version 0 Level 2 Task 100 Opcode 0 Keywords 0x80000000000000 - TimeCreated [ SystemTime] 2023-06-14T14:52:35.3364553Z EventRecordID 13627 Correlation - Execution [ ProcessID] 0 [ ThreadID] 0 Channel Application Computer Beemo Security - EventData DynDOLODx64.exe 3.0.0.128 646a6e33 ntdll.dll 10.0.19041.2788 2f715b17 c0000374 00000000000ff449 1b2c 01d99ece97605943 F:\Skyrim Modding\Tools\DynDOLOD\DynDOLODx64.exe C:\WINDOWS\SYSTEM32\ntdll.dll a7fe86b9-1e49-4c6b-a7a5-8ba0f979b813 If this happens while all physical memory is being used by all the processes and the OS starts to use virtual memory/paging, then we know the cause. Let the OS handle virtual memory with default settings. Enable the realtime log, so you can upload that if that type of crash happens again.
bargalarkh Posted June 14, 2023 Posted June 14, 2023 (edited) So I left it running, didn't close anything and enabled the realtime log as you said. Also increased that thread value to 12. I also have been using default paging the whole time. Logs Mentions an access violation, which i checked the wiki for. - I have disabled UAC and Antivirus - I ran DDL and Mod Organiser as admin - I have the latest version of the resources, exe, etc Edited June 14, 2023 by bargalarkh
bargalarkh Posted June 14, 2023 Posted June 14, 2023 I tried running again. It seems to alternate between crashing and hanging on creating texture atlases. In the most recent case, it's been running at this for a long time: [08:28] [Tamriel] Creating texture atlas F:\Skyrim Modding\Tools\DynDOLOD\DynDOLOD_Output\Textures\DynDOLOD\LOD\DynDOLOD_Tamriel_Glow.dds 1024 x 512 I have enabled the texture cache and max texture size ini options. There's no console window open for these, it just doesn't move past this point. I've found this is often where it will stop making progress even when left overnight.
bargalarkh Posted June 14, 2023 Posted June 14, 2023 (edited) Okay, I had a backup of my DynDOLOD output for all worldspaces except Bruma which worked. I generated and copied the output for Bruma into that DynDOLOD mod LOD works perfectly, no issues at all from testing, but I keep getting an error DynDOLOD can not find master data in DynDOLOD_Worlds DynDOLOD can not read DynDOLOD_None and variations of this... Now I read the advice from this thread but it didn't work for me. I made sure to copy over the json files when updating for the new worldspace, and have validated the JSON. The LOD is perfect now, just wondering how I can get rid of this error from showing up. Edited June 14, 2023 by bargalarkh
Roastlawyer Posted June 14, 2023 Posted June 14, 2023 (edited) Hello, I'm getting an issue where about every second run (or even more) DYNDOLOD seems to freeze at "[Tamriel] Generating object LOD". CPU usage for dyndolod goes to 0% (sometimes flickers to 0.1%) and the LODgen window doesn't come up (even after it sitting at that message for 15 or so minutes. Actually sometimes LODGen would come up but after it was done the rest of dyndolod would still freeze up just the same, however the last couple runs I couldn't even get that and the DynDOLOD_Output folder has only 4 smim lod textures generated. the only ini edits I've made to \Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini was to change it to boot to advanced mode & my grass LOD brightness settings. I'm using DYNDOLOD 3.00 Alpha 128 [DynDOLOD Resources SE v3.00 Alpha 37], [DynDOLOD DLL NG and Scripts 3.00 Alpha 6 for dyndolod 123+], [PapyrusUtil SE v3.9 for SSE 1.5.97], and I'm also using NGIO v8 with a generated grass Precache When I try and close DYNDOLOD it gives me the expected warning about generated output being incomplete, I click yes, then the window freezes up and DYNDOLOD.exe stops responding. Task manager can't kill it, and If I try to end it from the TM details panel I get "this operation could not be completed. Access is denied" and I have to hard reboot my PC. for log files there aren't many generated: No bugreport.txt, No Dyndolod_SSE_log.txt, No Dyndolod_SSE_Debug_log.txt, and no LODGen_SSE_Tamriel_log.txt EDIT: I ran it again with Verbose=1 in _SSE.ini and it worked, so I'll see if its consistent and if the problem immediately returns if I set it back to 0 EDIT 2: nope while the first 3 runs with verbose did work, this time cpu usage went down to 0%, elapsed time stopped counting, when I tried to save the in window log it froze and went unresponsive and I couldn't close it again. DynDOLOD_SSE.ini Edited June 15, 2023 by Roastlawyer
Suniasutei Posted June 15, 2023 Posted June 15, 2023 (edited) Hello, I am having issues getting DynDOLOD TexGen and DynDOLOD to run itself. I have installed the file here: C:\Games\Skyrim Anniversary Edition\Modding Tools\DynDOLOD I have set the paths within mod organizer as such : -sse -p:"C:\Games\Mod Organizer 2\profiles\My Skyrim Profile\plugins.txt" -m:"C:\Games\Mod Organizer 2\profiles\My Skyrim Profile\Skyrim.ini" -d:"C:\Games\Skyrim Anniversary Edition" I also tried -d:"C:\Games\Skyrim Anniversary Edition\data" I also checked that I had hkey records and I do I get an error on launch (image attached). Edited June 15, 2023 by Suniasutei
sheson Posted June 15, 2023 Author Posted June 15, 2023 8 hours ago, Roastlawyer said: Hello, I'm getting an issue where about every second run (or even more) DYNDOLOD seems to freeze at "[Tamriel] Generating object LOD". CPU usage for dyndolod goes to 0% (sometimes flickers to 0.1%) and the LODgen window doesn't come up (even after it sitting at that message for 15 or so minutes. Actually sometimes LODGen would come up but after it was done the rest of dyndolod would still freeze up just the same, however the last couple runs I couldn't even get that and the DynDOLOD_Output folder has only 4 smim lod textures generated. the only ini edits I've made to \Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini was to change it to boot to advanced mode & my grass LOD brightness settings. I'm using DYNDOLOD 3.00 Alpha 128 [DynDOLOD Resources SE v3.00 Alpha 37], [DynDOLOD DLL NG and Scripts 3.00 Alpha 6 for dyndolod 123+], [PapyrusUtil SE v3.9 for SSE 1.5.97], and I'm also using NGIO v8 with a generated grass Precache When I try and close DYNDOLOD it gives me the expected warning about generated output being incomplete, I click yes, then the window freezes up and DYNDOLOD.exe stops responding. Task manager can't kill it, and If I try to end it from the TM details panel I get "this operation could not be completed. Access is denied" and I have to hard reboot my PC. for log files there aren't many generated: No bugreport.txt, No Dyndolod_SSE_log.txt, No Dyndolod_SSE_Debug_log.txt, and no LODGen_SSE_Tamriel_log.txt EDIT: I ran it again with Verbose=1 in _SSE.ini and it worked, so I'll see if its consistent and if the problem immediately returns if I set it back to 0 EDIT 2: nope while the first 3 runs with verbose did work, this time cpu usage went down to 0%, elapsed time stopped counting, when I tried to save the in window log it froze and went unresponsive and I couldn't close it again. DynDOLOD_SSE.ini 21.17 kB · 1 download See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs When the OS needs rebooting , then there is something with the OS, drivers, hardware etc. Simple programs can not cause this. Verbose=1 does not change anything with DynDOLOD. It simply enables more log messages for the spawned LODGen processes write to their log.
sheson Posted June 15, 2023 Author Posted June 15, 2023 6 hours ago, Suniasutei said: Hello, I am having issues getting DynDOLOD TexGen and DynDOLOD to run itself. I have installed the file here: C:\Games\Skyrim Anniversary Edition\Modding Tools\DynDOLOD I have set the paths within mod organizer as such : -sse -p:"C:\Games\Mod Organizer 2\profiles\My Skyrim Profile\plugins.txt" -m:"C:\Games\Mod Organizer 2\profiles\My Skyrim Profile\Skyrim.ini" -d:"C:\Games\Skyrim Anniversary Edition" I also tried -d:"C:\Games\Skyrim Anniversary Edition\data" I also checked that I had hkey records and I do I get an error on launch (image attached). Read the first post which log and debug log to upload when making posts. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs Do not post screenshots of message, instead use the "Copy this message to clipboard" to copy and paste the text instead. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Copy-and-Paste-Text Make use of the "Click on this link for additional explanations and help for this message" as explained on the first post and at https://dyndolod.info/Official-DynDOLOD-Support-Forum#Read-Log-and-Error-Messages to open https://dyndolod.info/Messages/Path-Not-Allowed: Do not install DynDOLOD into special OS folders like 'Programs Files' or 'Program Files (x86)', User, Documents, Desktop, Download and also not into SteamApps, game or any mod manager folders. Follow the installation instructions at https://dyndolod.info/Installation-Instructions: Use 7-Zip to unpack the DynDOLOD Standalone archive into a new and empty 'DynDOLOD' directory that is outside of special OS folders like 'Programs Files' or 'Program Files (x86)', User, Documents, Desktop, Download and also not in SteamApps, game, Data or any mod manager folders. Also, read https://dyndolod.info/Help/Command-Line-Argument where to properly set the command line arguments. Point -p to the actual plugins.txt the game reads and which the mod manager maps to whatever profile is active. Do not point it to files in a a mod manager profile folder. Point -m to the actual folder where the game reads the Skyrim, SkyrimPrefs and SkyrimCustom from, instead of a specific file. Do not point it to a mod manager profile.
sheson Posted June 15, 2023 Author Posted June 15, 2023 12 hours ago, bargalarkh said: So I left it running, didn't close anything and enabled the realtime log as you said. Also increased that thread value to 12. I also have been using default paging the whole time. Logs Mentions an access violation, which i checked the wiki for. - I have disabled UAC and Antivirus - I ran DDL and Mod Organiser as admin - I have the latest version of the resources, exe, etc The logs show that there seems to be a problem reading Skyrim.esm by the xEdit background loader. This might be caused by corrupt files, reading errors or instability because of hardware (disk, CPU, memory problems) or software interfering with the loading. UAC, antivir should typically prevent loading of files entirely.
Roastlawyer Posted June 15, 2023 Posted June 15, 2023 1 hour ago, sheson said: See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs When the OS needs rebooting , then there is something with the OS, drivers, hardware etc. Simple programs can not cause this. Verbose=1 does not change anything with DynDOLOD. It simply enables more log messages for the spawned LODGen processes write to their log. When I tried it again just now it worked, but if it happens again I'll be back with the log
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now