Jump to content

DynDOLOD 3.00 Alpha 182


sheson

Recommended Posts

On 11/29/2022 at 7:20 PM, kingpatzer said:

Getting an OpenGL: Invalid Operation error when performing the Run Texgen step. 

log attached (log file is slightly larger than limit, so zipped it up).

TexGen_SSE_Debug_log.7z

See if there is anything different with this test version of TexGen https://mega.nz/file/YcIRQZjD#Ea79ZZrTC5lpuR5ThtjN7TCxpvHAdUH9gHwFeULMpX0

If not, upload new log, debug log and bugreport.txt if it exists. Then install AMD recommended driver version instead of optional versions as in all the other cases before https://stepmodifications.org/forum/search/?q=OpenGL Invalid Operation&quick=1&type=forums_topic&item=17510

Link to comment
Share on other sites

On 11/25/2022 at 5:14 AM, sheson said:

Is there any change after saving and immediately loading that save without restarting? Anything different when saving and actually restarting the game and loading?

Hi Sheson, apologies for the delayed response. If I save the game when I start stuttering and reload - whether its reloading the save in game or quitting and reloading the game - the stutter will no longer be there, but will come back in the same manner after a bit.

I was also able to get almost all of my new computer built (just missing the 4090), and now with my 13900k and 6200mhz DDR5 RAM it does seem to play a bit better. In fact I do not get the same exact stutter in the same spot as before even with the default .toml (still starts to stutter around Riften),  BUT unfortunately its the same deal as before where I will still stutter after awhile. I still need to do a bit more testing with the .toml you provided - I was just wanting to see if it was going to be fixed with a faster computer and also just wanted to check and let you know there has been a small change with faster hardware.

Link to comment
Share on other sites

On 11/29/2022 at 8:28 PM, sheson said:

See if there is anything different with this test version of TexGen https://mega.nz/file/YcIRQZjD#Ea79ZZrTC5lpuR5ThtjN7TCxpvHAdUH9gHwFeULMpX0

If not, upload new log, debug log and bugreport.txt if it exists. Then install AMD recommended driver version instead of optional versions as in all the other cases before https://stepmodifications.org/forum/search/?q=OpenGL Invalid Operation&quick=1&type=forums_topic&item=17510


Sheson, 

first, the link for the recommended driver version doesn't go anywhere for me, not sure why. Can you tell me what the latest recommended driver for 6750 XT cards is? 

Second, the test version does behave differently. It's been running now for over 8 hours. IT seems to be doing stuff still. But I don't think this is expected behavior either. There is no log file created, but the output directory has folders in it that are growing, just very slowly. 

The last message on the console is "[8:28:21] [DLC2SolstheimWorld] Creating texture atlas C:\Modding\Tools\DynDOLOD\DynDOLOD_Output\Textures\DynDOLOD\LOD\DynDOLOD_DLC2SolstheimWorld_Glow.dds 1024 x 512"
 

Link to comment
Share on other sites

49 minutes ago, kingpatzer said:


Sheson, 

first, the link for the recommended driver version doesn't go anywhere for me, not sure why. Can you tell me what the latest recommended driver for 6750 XT cards is? 

Second, the test version does behave differently. It's been running now for over 8 hours. IT seems to be doing stuff still. But I don't think this is expected behavior either. There is no log file created, but the output directory has folders in it that are growing, just very slowly. 

The last message on the console is "[8:28:21] [DLC2SolstheimWorld] Creating texture atlas C:\Modding\Tools\DynDOLOD\DynDOLOD_Output\Textures\DynDOLOD\LOD\DynDOLOD_DLC2SolstheimWorld_Glow.dds 1024 x 512"
 

https://www.amd.com/en/support lists Adrenalin 22.5.1 Recommended (WHQL)

The test version is a link to TexGenx64.exe in reply to the problem you reported having with running TexGen. The single log line you posted is a log message from DynDOLOD...?

The messages log is saved once the program is closed.  You can mark and copy the entire messages log to the clipboardwith the standard keyboard shortcuts, e.g. CTRL+HOME, CTRL+SHIFT+END, CTRL+C.

https://dyndolod.info/FAQ "Long running time or output several GB in file size" See all answers and also:
Crapware installed with graphics drivers is known to prolong running times.

This refers to crapware installed in addition to the AMD graphics driver. https://stepmodifications.org/forum/search/?&q=crapware&type=forums_topic&quick=1&item=17510&search_and_or=and&sortby=relevancy

Link to comment
Share on other sites

1 hour ago, sheson said:

 

https://dyndolod.info/FAQ "Long running time or output several GB in file size" See all answers and also:
Crapware installed with graphics drivers is known to prolong running times.

This refers to crapware installed in addition to the AMD graphics driver. https://stepmodifications.org/forum/search/?&q=crapware&type=forums_topic&quick=1&item=17510&search_and_or=and&sortby=relevancy


Crapware removed and antivirus turned off and it's running fine now. Thanks!

Link to comment
Share on other sites

4 hours ago, kingpatzer said:


Sheson, 

first, the link for the recommended driver version doesn't go anywhere for me, not sure why. Can you tell me what the latest recommended driver for 6750 XT cards is? 

Second, the test version does behave differently. It's been running now for over 8 hours. IT seems to be doing stuff still. But I don't think this is expected behavior either. There is no log file created, but the output directory has folders in it that are growing, just very slowly. 

The last message on the console is "[8:28:21] [DLC2SolstheimWorld] Creating texture atlas C:\Modding\Tools\DynDOLOD\DynDOLOD_Output\Textures\DynDOLOD\LOD\DynDOLOD_DLC2SolstheimWorld_Glow.dds 1024 x 512"
 

I use AMD too. Just google "AMD drivers" and use their website to look up your Adrenaline package and it will list various versions. Use only the "recommended"  version, which is 22.5.1 now.

Link to comment
Share on other sites

5 hours ago, vektor9999 said:

Hey guys,

Is there a way to make the hybrid 3d tree lods darker? I know there is a way with billboard brightness but ofc as i use 3d hybrid, this feature does not work.

Thanks a lot in advance.

2 options:  You can adjust the direct and ambient lighting settings in TexGen or you can adjust the "Vertexcolor multipliers for tree LOD models used in object LOD" settings in the Dyndolod_SSE configuration settings.  You can read about these in the manual.

edit - actually, not my place to blurt out amateur hour answers, my apologies...this forum is for official support.

Edited by MisterMorden
Link to comment
Share on other sites

I just have a new Property Not Found In Scripts.  With Serana Dialogue Addon mod.  I included document of the errors.  I have Rally's Solstheim AIO mod too.  I also tried to install his individual mods that are in the AIO and got same message.  I contacted both authors and the one said if it doesn't cause any issues to kind of let it go, which does makes sense to a certain degree.  I just hate to have any messages.  I plan on going there and seeing if it ctd's or any weird stuff pops up. I have been to Solstheim a couple times.  But have not gone their using the AIO mod or dyndolod (any version).

 

Seranadialogueaddon.doc

Link to comment
Share on other sites

Hello,

I am trying to run TexGen and DynDOLOD through MO2 for Skyrim AE GOG version.

I added the arguments to the 2 executables in MO2, but I keep getting this error below.

 

Spoiler

[Window Title]
TexGen

[Main Instruction]
Skyrim.ini can not be found.

[Content]
The INI file is missing from its default location at c:\Users\ealaa\Documents\My Games\Skyrim Special Edition GOG\Skyrim.ini.

Current game mode: Skyrim Special Edition (SSE)

Click on this link for additional explanations and help for this message

[OK] [Exit TexGen]

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

 

I already have a Skyrim.ini in the documents folder, so I dunno what else am missing. Any help is appreciated and thanks in advance.

Link to comment
Share on other sites

14 hours ago, Kansas72 said:

I just have a new Property Not Found In Scripts.  With Serana Dialogue Addon mod.  I included document of the errors.  I have Rally's Solstheim AIO mod too.  I also tried to install his individual mods that are in the AIO and got same message.  I contacted both authors and the one said if it doesn't cause any issues to kind of let it go, which does makes sense to a certain degree.  I just hate to have any messages.  I plan on going there and seeing if it ctd's or any weird stuff pops up. I have been to Solstheim a couple times.  But have not gone their using the AIO mod or dyndolod (any version).

Seranadialogueaddon.doc 29 kB · 0 downloads

Read the first post which log and debug log to upload when making posts.

Read the explanations of the summary https://dyndolod.info/Help/Summary-Of-Messages and https://dyndolod.info/Messages/Property-Not-Found-In-Scripts:
It can be a sign of load order conflicts of two mods requiring different versions of a script

As explained, make sure the script from the mod is not being overwritten by other mods. If there is a conflict between mods, it should be investigated further.

Link to comment
Share on other sites

@sheson

Just reporting back to follow up on my issues with TexGen bombing coming back to DynDOLOD after all relevant mods have finally been updated since 1.6.640. No logs posted, since I'm only reporting confirmatory findings FYI.

See my system specs in signature.

  • My TexGen OpenGL issue was resolved by downgrading to AMD v22.5.1 drivers (thanks to Windows Update for updating my system drivers without my permission. I disabled driver updates through GP and the relevant system process directly ... I should still get OS and MS software updates)
  • My extreme processing times for a well-used and understood mod list with respect to DynDOLOD were resolved with aid of a statement in your FAQs that GFX driver bloatware can cause this issue (presumably by misidentifying one or more of the DynDOLOD processes as actual GFX processes and running some n/a routines during runtime)
    • Note that I have used a couple of alpha versions in the past that caused similar or related performance issues without ever understanding why, but they were almost always resolved in the next alpha release. Since I only update my drivers once or twice a year (WU GFX driver update was only a recent Win 11 issue for me), I presume that something in (or not in) the app code might conditionally trigger this issue of "mistaken identity". Obviously, I'm grasping for anything sensible, since IDK.
    • Cleaning out my GFX drivers and reinstalling using the AMD Adrenaline "Driver only" option completely resolved (Identical DynDOLOD runs that required well over an hour or more went back down to 37 minutes where they belong (including occlusion at 3 quality, terrain underside at 8 quality, and HD grass at 60%, mode 1). Arguably, this is the fastest I have experienced. Previous alphas (< 100) required between 30-50 minutes typically for the Step mod list (depending on if I ran occlusion).

PS: I'm using DynDOLOD defaults for all of the memory-management and related threads settings ... and latest alpha 106.

Link to comment
Share on other sites

1 hour ago, LouAshfield said:

Hello,

I am trying to run TexGen and DynDOLOD through MO2 for Skyrim AE GOG version.

I added the arguments to the 2 executables in MO2, but I keep getting this error below.

I already have a Skyrim.ini in the documents folder, so I dunno what else am missing. Any help is appreciated and thanks in advance.

Moved to the DynDOLOD 3 Alpha thread. See the first post which log and debug log to upload when making posts.

The message is self explanatory.
The INI file is missing from its default location at c:\Users\ealaa\Documents\My Games\Skyrim Special Edition GOG\Skyrim.ini.

Use the "Click on this link for additional explanations and help for this message" to open https://dyndolod.info/Messages/INI-Files
In case existing files can not be accessed, add an exception to whatever it is that is blocking access.

If the shown path is not correct, fix the wrong path you set for the -m command line argument.

Link to comment
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
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.