Pro-Worx Posted June 26 Posted June 26 G'day. Been running Dyndolod for what seems like forever with zero hassles and fully enjoyed it - Thanks Run 1170, was using Alpha-49, DLL SE 1 Scripts/2 Steam.Had to recently re-run it again but said I had to upgrade to Alpha-50. Did so, there was no other upgrades, so when I re-ran Textgen is came up with error; 'This alpha version of Textgenx64 has expired. Download and use the alpha latest' No idea what to do. Thank in advance.
sheson Posted June 26 Author Posted June 26 1 hour ago, Pro-Worx said: G'day. Been running Dyndolod for what seems like forever with zero hassles and fully enjoyed it - Thanks Run 1170, was using Alpha-49, DLL SE 1 Scripts/2 Steam.Had to recently re-run it again but said I had to upgrade to Alpha-50. Did so, there was no other upgrades, so when I re-ran Textgen is came up with error; 'This alpha version of Textgenx64 has expired. Download and use the alpha latest' No idea what to do. Thank in advance. The message explains the problem and its solution. The title of this thread, the first post, following links from https://dyndolod.info/Downloads to Nexusmods all show the current version of DynDOLOD Standalone is 3 Alpha-173. It seems you only updated the DynDOLOD Resources SE. Download and update to the latest Standalone. See https://dyndolod.info/Updating#New-DynDOLOD-Version https://dyndolod.info/ Always use the latest versions. https://dyndolod.info/FAQ#Older-versions
Pro-Worx Posted June 26 Posted June 26 54 minutes ago, sheson said: The message explains the problem and its solution. The title of this thread, the first post, following links from https://dyndolod.info/Downloads to Nexusmods all show the current version of DynDOLOD Standalone is 3 Alpha-173. It seems you only updated the DynDOLOD Resources SE. Download and update to the latest Standalone. See https://dyndolod.info/Updating#New-DynDOLOD-Version https://dyndolod.info/ Always use the latest versions. https://dyndolod.info/FAQ#Older-versions Firstly - don't I feel like an idiot. Forgetting to update the Dyndolod folder and thinking it is all in Vortex Secondly - thank you for not treating me like an idiot I deserve to be You could have easily roasted me for an absolute rookie noob mistake. It's been a while since I've had to upgrade my Dyndolod and I thought I knew it all - I was wrong. Thank you for the humbling and valuable lesson without the humiliation. Much appreciated. Thanks mate
tweedledumb99 Posted June 27 Posted June 27 (edited) I ran dyndolod a few months back with EVLaS and generated terrain underside through DynDOLOD and didn't have any problems with light shining through the ground (3 - Alpha 156). I just reran DynDOLOD (3 - alpha 173) with underside at the same quality/height, still using EVLaS, and now there's light shining through the terrain. I've tried adding mods to give mountains a double-sided feature so light doesn't shine through, and followed the instructions on terrain underside on the DynDOLOD site on that topic. Not sure what's wrong or how to fix it, I've reran the latest DynDOLOD 3 Alpha times now with different options and they all lead to light shining through the landscape. Is there a way I can just continue using Alpha 156 to regenerate LOD? since it seems like that version gave me working terrain underside (I still have my old output and if I swap it back in, everything's fixed). Only problem is when I try running the old one I get an error message saying I need to update to the new version, even though there isn't any feature from the new version I want to use over alpha 156. Edited June 27 by tweedledumb99
sheson Posted June 27 Author Posted June 27 9 hours ago, tweedledumb99 said: I ran dyndolod a few months back with EVLaS and generated terrain underside through DynDOLOD and didn't have any problems with light shining through the ground (3 - Alpha 156). I just reran DynDOLOD (3 - alpha 173) with underside at the same quality/height, still using EVLaS, and now there's light shining through the terrain. I've tried adding mods to give mountains a double-sided feature so light doesn't shine through, and followed the instructions on terrain underside on the DynDOLOD site on that topic. Not sure what's wrong or how to fix it, I've reran the latest DynDOLOD 3 Alpha times now with different options and they all lead to light shining through the landscape. Is there a way I can just continue using Alpha 156 to regenerate LOD? since it seems like that version gave me working terrain underside (I still have my old output and if I swap it back in, everything's fixed). Only problem is when I try running the old one I get an error message saying I need to update to the new version, even though there isn't any feature from the new version I want to use over alpha 156. Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log and debug log to upload when maing posts. Properly report the problem so we can troubleshoot it in order to actually fix it. https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-the-Latest-Versions https://dyndolod.info/FAQ#Older-versions There were no active changes to the underside generation or how it works since Alpha-157. Nobody else reported any similar problems with it since.
tweedledumb99 Posted June 27 Posted June 27 1 hour ago, sheson said: Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log and debug log to upload when maing posts. Properly report the problem so we can troubleshoot it in order to actually fix it. https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-the-Latest-Versions https://dyndolod.info/FAQ#Older-versions There were no active changes to the underside generation or how it works since Alpha-157. Nobody else reported any similar problems with it since. thanks, when I try rerunning it and generate logs, will post them along with the other requirements.
sheson Posted June 27 Author Posted June 27 1 hour ago, tweedledumb99 said: thanks, when I try rerunning it and generate logs, will post them along with the other requirements. Also make two screenshots to show the issue. One normal and the other after typing tll in console to disable all LOD.
drift123 Posted June 28 Posted June 28 (edited) I read the page about the Child/Parent Worldspace copies but it's still unclear to me. I know the Parent/Child settings affect what you see when inside Whiterun looking over the city walls. Does it affect what you see when you're outside of Whiterun looking over the city walls? It's unclear to me what the difference between Parent > Child and Child > Parent settings are in terms of in-game visuals. Edited June 28 by drift123
sheson Posted June 28 Author Posted June 28 35 minutes ago, drift123 said: I read the page about the Child/Parent Worldspace copies but it's still unclear to me. I know the Parent/Child settings affect what you see when inside Whiterun looking over the city walls. Does it affect what you see when you're outside of Whiterun looking over the city walls? It's unclear to me what the difference between Parent > Child and Child > Parent settings are in terms of in-game visuals. https://dyndolod.info/Help/Child-Parent-Worldspace-Copies Walled cities like Solitude, Riften, Whiterun, Windhelm etc. are child worldspaces that are embedded into the Tamriel parent worldspace that they use for LOD. The Child > parent option copies references that could have LOD from the child worldspaces to the parent worldspace. The Parent > child option copies references that have LOD from the parent worldspace to the child worldspaces. The Child > parent option makes sure that things only added to the inside of city can also be seen from the outside. The Parent > child option makes sure that things can also be seen when inside a city and peeking past the walls. 1
diziet Posted June 29 Posted June 29 I'm trying to use Texgen64.exe from the latest alpha-173 standalone download and I get the message: D:\modding_tools\DynDOLOD 3.x\Edit Scripts\DynDOLOD\Configs\DynDOLOD_SSE_TexGen_noalpha_realisticwatertwoesp.txt PapyrusUtil DLL: C:\Users\bascule\gog_games\Skyrim Anniversary Edition\Data\\SKSE\Plugins\PapyrusUtil.DLL, Version: 4.6, Game Version: 1.6.1179, Date: 2024-02-26 23:10:49 Error: Wrong version of DynDOLOD DLL NG Make sure to install the correct version of DynDOLOD DLL NG for the runtime . User says "Exit TexGen" However I have the alpha-30 version of dyndolod dll NG installed: I have GOG version 1179 of SkyrimSE and the correct SKSE64 and address library, when starting a new game my dyndolod.log says: DynDOLOD NG plugin version: 3.0.30.1130+ | SKSE version: 2.2.6.0 | Game version: 1-6-1179-1 DynDOLOD save/load handler installed. DynDOLOD Papyrus functions installed. Trampoline initialized. DynDOLOD Patch installed. Reading file Data/SKSE/Plugins/DynDOLOD_Data/DynDOLOD_NG_Worlds.txt Error opening file Data/SKSE/Plugins/DynDOLOD_Data/DynDOLOD_NG_Worlds.txt my texgen_sse_debug_log.txt is https://paste2.org/B5C7xUyw my texgen_sse_log,txt is https://paste2.org/7nXNV1tE diziet
sheson Posted June 29 Author Posted June 29 22 minutes ago, diziet said: I'm trying to use Texgen64.exe from the latest alpha-173 standalone download and I get the message: D:\modding_tools\DynDOLOD 3.x\Edit Scripts\DynDOLOD\Configs\DynDOLOD_SSE_TexGen_noalpha_realisticwatertwoesp.txt PapyrusUtil DLL: C:\Users\bascule\gog_games\Skyrim Anniversary Edition\Data\\SKSE\Plugins\PapyrusUtil.DLL, Version: 4.6, Game Version: 1.6.1179, Date: 2024-02-26 23:10:49 Error: Wrong version of DynDOLOD DLL NG Make sure to install the correct version of DynDOLOD DLL NG for the runtime . User says "Exit TexGen" However I have the alpha-30 version of dyndolod dll NG installed: I have GOG version 1179 of SkyrimSE and the correct SKSE64 and address library, when starting a new game my dyndolod.log says: DynDOLOD NG plugin version: 3.0.30.1130+ | SKSE version: 2.2.6.0 | Game version: 1-6-1179-1 DynDOLOD save/load handler installed. DynDOLOD Papyrus functions installed. Trampoline initialized. DynDOLOD Patch installed. Reading file Data/SKSE/Plugins/DynDOLOD_Data/DynDOLOD_NG_Worlds.txt Error opening file Data/SKSE/Plugins/DynDOLOD_Data/DynDOLOD_NG_Worlds.txt my texgen_sse_debug_log.txt is https://paste2.org/B5C7xUyw my texgen_sse_log,txt is https://paste2.org/7nXNV1tE diziet Do not install the game into special Windows folders like c:\Users\ to avoid issues with UAC, AntiVir etc. As explained, the command line argument for setting the games data path should look like this: -d:"c:\GOG Games\Skyrim Special Edition GOG\Data\" Note the single backslash at the end. The logs indicate there might be two backslashes \\ If that is not it, copy paste the entire command line
diziet Posted June 29 Posted June 29 (edited) My command line is: -sse -D:"C:\Users\bascule\gog_games\Skyrim Anniversary Edition\Data\" -P:"C:\Users\bascule\AppData\Local\Skyrim Special Edition GOG\plugins.txt" -I:"D:\Users\bascule\Documents\My Games\Skyrim Special Edition GOG\Skyrim.ini" the "Skyrim Special Edition GOG" folder is a junction with "Skyrim Special Edition" the install location for SkyrimSE is where it has been since the GOG version was released and I have successfully run Dyndolod several times since then so although I understand the point about UAC etc. I doubt that is the cause, but I can try moving just to see, - 83GB, it'll take a while:) diziet Edited June 29 by diziet
sheson Posted June 29 Author Posted June 29 16 minutes ago, diziet said: My command line is: -sse -D:"C:\Users\bascule\gog_games\Skyrim Anniversary Edition\Data\" -P:"C:\Users\bascule\AppData\Local\Skyrim Special Edition GOG\plugins.txt" -I:"D:\Users\bascule\Documents\My Games\Skyrim Special Edition GOG\Skyrim.ini" the "Skyrim Special Edition GOG" folder is a junction with "Skyrim Special Edition" the install location for SkyrimSE is where it has been since the GOG version was released and I have successfully run Dyndolod several times since then so although I understand the point about UAC etc. I doubt that is the cause, but I can try moving just to see, - 83GB, it'll take a while:) diziet https://dyndolod.info#Skyrim-Special-Edition-GOG-Skyrim-Anniversary-Edition-GOG or https://dyndolod.info/Mods/Skyrim-Special-Edition-GOG-Skyrim-Anniversary-Edition-GOG Use the -m, -p and -d command line arguments to set the INI, plugins.txt and Data paths when starting the tools. For example: -m:"c:\Users\[USERNAME]\Documents\My Games\Skyrim Special Edition GOG\" -p:"c:\Users\[USERNAME]\AppData\Local\Skyrim Special Edition GOG\plugins.txt" -d:"c:\GOG Games\Skyrim Special Edition GOG\Data\" Set the -d command line to the actual physical data folder where the game is installed. Fix whatever is causing the log to report 2 backslashes at the end of: Using Skyrim Special Edition Data Path: ...\Data\\ The log needs to show the path to end in 1 single backslash ...\Data\ with a single backslash in the end. Also try not adding any backslash after \Data in the command line at the end - xEdit should add it automatically. The SkyrimSE.exe needs to be one folder up from the shown data path. Replace the -i command line to the single Skyrim.INI file with the-m command line to the INI folder.
diziet Posted June 29 Posted June 29 Well what do you know, I've been using that command line since the GOG version came out and I had to look up the arguments for he Vortex dashboard:) I removed the slash at the end of -D:"C:\Users\bascule\gog_games\Skyrim Anniversary Edition\Data\" and it now works, thankyou! diziet
Chromatic Posted July 1 Posted July 1 (edited) On 6/26/2024 at 12:52 PM, sheson said: That is unfortunate. If nothing else helps, I would try reinstalling driver only again as you did already or maybe try an older version, just to be sure. To be honest, this isn't the first time I've been having these issues. I guess you have already noticed, but I had the same problem in November too and we couldn't find a conclusive answer back then either. On 6/26/2024 at 12:52 PM, sheson said: Interestingly in the last log it went past SIworld and had a problem one worldapace later in MerDesFantomes. I already have high performance settings enabled on Windows each time I run xlodgen/texgen/dyndolod. The monitor does shut off by its own still due to the settings used, but I noticed the same issue happening even if I didn't let it shut off anyway. On 6/26/2024 at 12:52 PM, sheson said: There should be a related entry in the Windows Event log for Access violation at address 00007FFDF089C337 in module 'atio6axx.dll'. It probably won't help us much either, but it might indicate a driver/hardware problem. Typically problems when using the OpenGL API should be reported as OpenGL errors and not cause crashes in the driver. I am looking for it, but haven't noticed such an entry in the Event Log. However: After doing some research in this thread, I decided to install an older driver version like you also suggested. I went back all the way to 22.5.1 which was mentioned here in the past and surprisingly, everything worked fine and lod generation was successful even without a minimal driver install or shutting off AMD related processes. In fact, I ran DynDOLOD two different times with successful lod generation for each one (let me know if you still want me to post the logs anyway). Does this mean that newer AMD drivers are a no-go? Edited July 1 by Chromatic
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