DynDOLOD 3.00 Alpha 182

[HiroMiro]

After updating Dyndolod 3 Alpha to the latest version, for some reason glowing windows no longer appear. I've used Dyndolod for years and have always loaded the medium settings and ticked the windows checkbox. Nothing in my load order has changed except updating Dyndolod. Is there a known issue or will I have to go use my backed up files to restore my previous Dyndolod output since you're not allowed to run older versions of Dyndolod (which I find a bit unfriendly)?

[AenSeidhe]

21 minutes ago, sheson said:

As usual, all the DynDOLOD DLL NG and Scripts Alpha archives for the experimental large references bugs workarounds are hidden on Nexus on purpose.

https://dyndolod.info/Help/Large-Reference-Bugs-Workarounds

without DynDOLOD DLL NG and Scripts 3.00 [version Alpha-7] can i use DynDOLOD Alpha-129?

[sheson]

13 minutes ago, HiroMiro said:

After updating Dyndolod 3 Alpha to the latest version, for some reason glowing windows no longer appear. I've used Dyndolod for years and have always loaded the medium settings and ticked the windows checkbox. Nothing in my load order has changed except updating Dyndolod. Is there a known issue or will I have to go use my backed up files to restore my previous Dyndolod output since you're not allowed to run older versions of Dyndolod (which I find a bit unfriendly)?

Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which log and debug log to upload when making posts.

From the first post:
This is an ALPHA version to test things and iron out bugs. Certain things may be incomplete, not work as expected or change considerably between versions. 

If you do not want to participate in the alpha test, use DynDOLOD 2.98

[sheson]

52 minutes ago, AenSeidhe said:

without DynDOLOD DLL NG and Scripts 3.00 [version Alpha-7] can i use DynDOLOD Alpha-129?

Read https://dyndolod.info/Downloads for requirements. Note that DynDOLOD DLL NG and Scripts is not mentioned, so it is not a requirement.
If you read https://dyndolod.info/Help/Large-Reference-Bugs-Workarounds, then you will notice, that using and testing the experimental large reference bugs workarounds is optional.

Read https://dyndolod.info/Installation-Instructions how to install everything.
Read https://dyndolod.info/Generation-Instructions how to generate things.

[sheson]

1 hour ago, RuinedRun said:

Downloaded newest version of Dynodolod 3 Alpha, Dynodolod Resources SE 3. Using DLL for 1.6.640. Got error that made TexGen exit mid-generation.

Already made Terrain with xLODGen using "xLODGen Resource - SSE Terrain Tamriel".

Bugreport.txt and logs in Google Drive folder: https://drive.google.com/drive/folders/1OwNEL4pnksRKMJaAZHrXJDDrWISn0xNU

Download DynDOLOD Standalone 3.00 Alpha-130. it should fix that access violation.

If not upload new log, debug log and bugreport.txt

[FinalCraneFall]

I deactivate in interior, save, load, save, update, then load the last save, but DynDOLOD does not activate when I go to exterior, even after hours. 

[sheson]

3 hours ago, FinalCraneFall said:

I deactivate in interior, save, load, save, update, then load the last save, but DynDOLOD does not activate when I go to exterior, even after hours.

Moved to the DynDOLOD 3 alpha thread based on the assumption it is about DynDOLOD 3 Alpha.

Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which log and debug log to upload when making posts.
Also upload the papyrus logs as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs

Dynamic LOD can only activate for exterior worldspaces for which it has been generated.

See the https://dyndolod.info/FAQ "DynDOLOD Game Questions" for related error messages that might have show top left in the game, the DynDOLOD SkyUI MCM last message or in the papyrus logs.

[megablackk1d]

16 hours ago, vektor9999 said:

Reverted back to 1.7.5.2 and worked like a charm, as always you are the GOAT

Thanks a lot

 

16 hours ago, z929669 said:

Please do not post your logs as text

Also, please do not double post identical topics.

I'm not sure why you are posting this in this particular forum, when the DynDOLOD application and Nexus mod pages all point clearly to the official support forum elswhere on this site. If you had read the basic info provided to everyone that obtains the application, you likely wouldn't have an issue or would have enough information to properly request support for your issue.

Moved to the DynDOLOD support forums for further input/investigation.

Sorry didn't mean to double post, and this is my first time using the site, and I thought my first post didn't go through. I'm learning how this works.

[megablackk1d]

15 hours ago, sheson said:

Moved to the DynDOLOD 3 Alpha thread. See the first post which log and debug log to upload when making posts. https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs

I will list the things that worked for people in the past. Try one at time until it hopefully works:

Make sure UAC and antivirus are not interfering. Add exceptions for all executables, also for in ..\Edit Scripts\Texconvx64.exe for example.

Update the graphics driver to the latest version. Install the driver only without the crapware or terminate the crapware before using the tools.

Check the task manager for stuck Texconvx64.exe that TexGen might be waiting for. If you terminate all Texconvx64.exe TexGen should have a related error message and stop.

Add LockTexconv=1 under [TexGen] in ..\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.INI to see if that changes anything.

If not, test if adding RenderSingle=1 under [TexGen] in ..\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.INI lets it run through.

If not, test if adding RenderTexturesSingleThread=1 under [TexGen] in ..\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.IN changes anything.

If not, test if instructing Texconv to not use the GPU by adding TexconvAdapterIndex=-1 under [TexGen] in ..\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.IN changes anything.

If it still gets stuck, upload both the log and the debug log.

Ok thank you. Sorry if I sounded frustrated because I was haha. I been trying to get it to finish running for days. Anyways I finally got textgen to finish, but now when trying to run Dyndolod it makes it about 16 minutes in and spits out this error message "C:\Mod Tools\dyndolod\DynDOLOD\DynDOLOD_Output\textures\landscape\reachmoss01noalpha.dds". The process cannot access the file because it is being used by another process [C:\Mod Tools\dyndolod\DynDOLOD\DynDOLOD_Output\textures\landscape\reachmoss01noalpha.dds]. I don't get it nothing else was running except Mo2, and antivirus has been shut down.

DynDOLOD_SSE_log.txt bugreport.txt

[sheson]

22 minutes ago, megablackk1d said:

Ok thank you. Sorry if I sounded frustrated because I was haha. I been trying to get it to finish running for days. Anyways I finally got textgen to finish, but now when trying to run Dyndolod it makes it about 16 minutes in and spits out this error message "C:\Mod Tools\dyndolod\DynDOLOD\DynDOLOD_Output\textures\landscape\reachmoss01noalpha.dds". The process cannot access the file because it is being used by another process [C:\Mod Tools\dyndolod\DynDOLOD\DynDOLOD_Output\textures\landscape\reachmoss01noalpha.dds]. I don't get it nothing else was running except Mo2, and antivirus has been shut down.

DynDOLOD_SSE_log.txt 815.94 kB · 0 downloads bugreport.txt 254.85 kB · 0 downloads

For future references, read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which debug log to upload as well.

The program (process) tries to read/write the file C:\Mod Tools\dyndolod\DynDOLOD\DynDOLOD_Output\textures\landscape\reachmoss01noalpha.dds using OS functions. 
The OS tells the program that it is not possible because: The process cannot access the file because it is being used by another process.

Such messages state a fact.

You could try to check the the manager for all current processes (including hidden ones and services) in order to determine which one it might be and terminate it.
Otherwise a reboot typically clears that up.

[megablackk1d]

11 minutes ago, sheson said:

For future references, read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which debug log to upload as well.

The program (process) tries to read/write the file C:\Mod Tools\dyndolod\DynDOLOD\DynDOLOD_Output\textures\landscape\reachmoss01noalpha.dds using OS functions. 
The OS tells the program that it is not possible because: The process cannot access the file because it is being used by another process.

Such messages state a fact.

You could try to check the the manager for all current processes (including hidden ones and services) in order to determine which one it might be and terminate it.
Otherwise a reboot typically clears that up.

Ok thanks, but even if I reboot I still get the same error. I'll try and see what I can do.

[sheson]

35 minutes ago, megablackk1d said:

Ok thanks, but even if I reboot I still get the same error. I'll try and see what I can do.

Are you able to delete the incomplete output before trying again?

If that is the case, try with this test version of DynDOLODx64.exe https://mega.nz/file/4BQk3C7Z#cHinjlNTRVcUyG4jL5zhFz32bf4eCbsk7IE_E612cEI

If problem persists upload new log, debug and bugreport.txt.

[megablackk1d]

8 hours ago, sheson said:

Are you able to delete the incomplete output before trying again?

If that is the case, try with this test version of DynDOLODx64.exe https://mega.nz/file/4BQk3C7Z#cHinjlNTRVcUyG4jL5zhFz32bf4eCbsk7IE_E612cEI

If problem persists upload new log, debug and bugreport.txt.

Ok I tried the new exe, and it never got past 6 minutes before it would hang, and do nothing for hours. So I reverted back and once again I get the same error message no matter what. I just want to say thanks for the help, but I have been at this for a week now haha. I think I may just continue to play without it like I have been for all these years. You made a great program by the way, I don't think it's meant to be. For me at least. Here are the files you asked for anyway. The debug file was 300mb so I couldn't upload it here. Here is the link to the debug file https://www.mediafire.com/file/8ewcfg0077vgmzg/DynDOLOD_SSE_Debug_log.txt/file. Again thanks for the help!

bugreport.txt DynDOLOD_SSE_log.txt

 

Well I unticked beyond reach from creation lod's and it worked. I was able to complete it.

[Spike2112]

Hi, using Alpha 130. I have never had this problem before. Xlodgen fine, Texgen fine, No error summary. Then I go to install DynDOLOD Outputzip and I get Extraction failed:CRC error. This is in MO2. No other mod nor have yours ever done this. To test I disabled almost all my mods and I still get the error. Any ideas? Thanks

[sheson]

15 hours ago, megablackk1d said:

Ok I tried the new exe, and it never got past 6 minutes before it would hang, and do nothing for hours. So I reverted back and once again I get the same error message no matter what. I just want to say thanks for the help, but I have been at this for a week now haha. I think I may just continue to play without it like I have been for all these years. You made a great program by the way, I don't think it's meant to be. For me at least. Here are the files you asked for anyway. The debug file was 300mb so I couldn't upload it here. Here is the link to the debug file https://www.mediafire.com/file/8ewcfg0077vgmzg/DynDOLOD_SSE_Debug_log.txt/file. Again thanks for the help!

bugreport.txt 511.68 kB · 1 download DynDOLOD_SSE_log.txt 830.03 kB · 1 download

 

Well I unticked beyond reach from creation lod's and it worked. I was able to complete it.

For future reference, do not post screenshots of message, use the 'Copy message to clipboard' link instead and post the text. https://dyndolod.info/Official-DynDOLOD-Support-Forum#Copy-and-Paste-Text

See if you have more luck with this test version https://mega.nz/file/oUZi2JDA#e0mpNTqTcSaZQRpL1U0CrxkN-4W0rvSUhf---qUqycA
Upload new log, debug log, bugereport.txt in case it has an error. If it stalls, check task manager for stuck texconv processors and kill them top get it to have an error.

It is normal that when something that has an error is not done, the error is not happening. Kind of like staying in bed to not have accidents outside.