DynDOLOD 3.00 Alpha 190

[VulKun]

I have a problem..what can i do for this idk really 

[sheson]

  On 9/28/2021 at 5:55 PM, VulKun said:

I have a problem..what can i do for this idk really 

Expand  

Read the first post. it explains:

"Click help for this message"

"Copy message to clipboard" and paste as text instead of posting screenshots.

Which log files to upload when making posts.

[VulKun]

 

  On 9/28/2021 at 5:59 PM, sheson said:

Read the first post. it explains:

"Click help for this message"

"Copy message to clipboard" and paste as text instead of posting screenshots.

Which log files to upload when making posts.

Expand  

Its worked texgen..How idk

[VulKun]

And again another problem

[sheson]

  On 9/28/2021 at 6:09 PM, VulKun said:

And again another problem

Expand  

No point in answering if you do not read the answers, the first post or error messages for that matter.

Also, it will probably "magically" fix itself like the other two times.

[VulKun]

Now texgen closed itself..I want to use 3.0 alpha but i cant. and just working 2.96  but not good a version..really bullcrap

[z929669]

  On 9/28/2021 at 7:06 PM, VulKun said:

Now texgen closed itself..I want to use 3.0 alpha but i cant. and just working 2.96  but not good a version..really bullcrap

Expand  

Run it again, and this time, as was mentioned "click 'help for this message'" if the error box appears again. Then copy/paste that. Then look for bugreport.txt in root of DynDOLOD dir. Then find relevant log and debut_log in /Logs. Then post.

This way, you will get the path to answers.

Otherwise, only a remote Vulkan mind meld would maybe help

[VulKun]

  On 9/28/2021 at 7:24 PM, z929669 said:

Run it again, and this time, as was mentioned "click 'help for this message'" if the error box appears again. Then copy/paste that. Then look for bugreport.txt in root of DynDOLOD dir. Then find relevant log and debut_log in /Logs. Then post.

This way, you will get the path to answers.

Otherwise, only a remote Vulkan mind meld would maybe help

Expand  

There is no help for this message because just closed itself

[z929669]

  On 9/28/2021 at 7:33 PM, VulKun said:

There is no help for this message because just closed itself

Expand  

Run it again, and this time, as was mentioned "click 'help for this message'" if the error box appears again. Then copy/paste that. Then look for bugreport.txt in root of DynDOLOD dir. Then find relevant log and debut_log in /Logs. Then post.

Also try rebooting or generally resetting your modding environment if you know how to do it manually without a reboot. Part of the problem could be OS related.

[VulKun]

  On 9/28/2021 at 7:35 PM, z929669 said:

Run it again, and this time, as was mentioned "click 'help for this message'" if the error box appears again. Then copy/paste that. Then look for bugreport.txt in root of DynDOLOD dir. Then find relevant log and debut_log in /Logs. Then post.

Also try rebooting or generally resetting your modding environment if you know how to do it manually without a reboot. Part of the problem could be OS related.

Expand  

When i tried first time run texgen it is good worked but now closing itself  but im trying

[z929669]

  On 9/28/2021 at 7:37 PM, VulKun said:

When i tried first time run texgen it is good worked but now closing itself  but im trying

Expand  

Be sure to clear out previous TexGen output and that all required mods are active and none of those contribute files conflicting with that output. If all else fails, load a vanilla-only profile (if using MO or Vortex) and try that. If that runs, you know it's an issue with one or more mods in your mod list (or plugins in your load order, which should always be sorted with LOOT prior to running any of these apps)

[VulKun]

2.96 while working , why 3.0 alpha doesnt work ?

[VulKun]

  On 9/28/2021 at 7:44 PM, z929669 said:

Be sure to clear out previous TexGen output and that all required mods are active and none of those contribute files conflicting with that output. If all else fails, load a vanilla-only profile (if using MO or Vortex) and try that. If that runs, you know it's an issue with one or more mods in your mod list (or plugins in your load order, which should always be sorted with LOOT prior to running any of these apps)

Expand  

And i tried vanilla only profile.Its same..closed itself so not about mods

[z929669]

  On 9/28/2021 at 8:23 PM, VulKun said:

And i tried vanilla only profile.Its same..closed itself so not about mods

Expand  

In that case, keep testing the vanilla profile, and ensure some best practices as described in our system setup guide.

Also ensure that this isn't an issue by following the best answer here:

Lastly, see first post and provide your logs as instructed. There should be at least two logs and possibly a bugreport.txt in root of your DynDOLOD installation. Truncate the debug log to last run or simply delete all logs before running again against vanilla profile. Otherwise, they are too big.

[matashina]

  On 9/28/2021 at 5:34 PM, sheson said:

The "file in question" is the destination path that can not be written to, because the OS, UAC, anti vir, or another process blocks write access.
C:\Modding\DynDOLOD\TexGen_Output\DynDOLOD-temp\textures\clutter\stockade\stockadewood01snow_n.dds

DynDOLOD Resources contain LOD assets for LOD generation with DynDOLOD. TexGen generates LOD assets from full models/textures to a new and empty output folder outside of the game and mod manager folders. Hence for this error message it does not matter at all if DynDOLOD Resources are installed or not when running TexGen - if the instructions are followed correctly.

I suggest to pay at least some attention to log messages and read the help file what they mean. ..\DynDOLOD\docs\help\LogMessages.html

It seems you are trying to generate grass LOD. Something seems off with the grass  cache files. Did you use the new scale setting by any chance?

Expand  

Yeah, I think the file thing was just windows defender not like believing that I actually wanted the rules I'd set to work until I'd restarted my computer or something. Sorry to make you reiterate.

You're on to something with my grass cache files. I tried out SuperDenseGrass and really like the results in-game before running my LOD stuff, but now that I think about it, uh, yeah, that could do it with ballooning my DynDOLOD times. Is that setting not compatible? I just grepped through the DynDOLOD docs and searched this forum thread and I don't think anyone has mentioned SuperDenseGrass before, but I could be wrong...?