Jump to content

Recommended Posts

Posted
  On 2/4/2023 at 4:10 PM, Rozen said:

It does not, I didn't get any update notice for alpha 3 at all, when I found out there was an update it was by going to your link to it in the Large Reference Bugs Workarounds area and seeing it was a newer version.

Expand  

Nexus does not enable update tracking of archived files. You must check the documentation for updates at present: https://dyndolod.info/Help/Large-Reference-Bugs-Workarounds#Requirements

Posted
  On 2/4/2023 at 8:27 AM, sheson said:

According to the TexGen debug log, there seem to be a lot 0 bounds in Grass FPS Booster.esp.

Those grasses will have no billboards generated and show up as ",False" in the mentioned C:\Games\DynDOLOD 3.0\TexGen_Output\Textures\Terrain\LODGen\TexGen_SSE_Grass_Billboards.txt https://dyndolod.info/Help/TexGen-Configuration#Tree-Grass-LOD-Billboards

Expand  

OMG. I feel so stupid now. I checked my actual grass mods but I never checked that one. I figured it was just an add-on and not a Grass Replacer. Gonna take a look now. Thanks.

Posted (edited)

I am running dyndolod 3.0 to find the use of found these problems, how should be solved?

  Reveal hidden contents

 

Edited by Greg
Added spoiler tag
Posted
  On 2/4/2023 at 5:33 PM, bgon said:

I am running dyndolod 3.0 to find the use of found these problems, how should be solved?

Expand  

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

Read https://dyndolod.info/Messages for explanations of warning and error messages and/or the summary https://dyndolod.info/Help/Summary-Of-Messages

If you have questions about a particular message then ask a specific question.

Posted
  On 2/4/2023 at 3:50 PM, sheson said:

It does fix itself when you travel away and come back, right? Nevertheless, this will be fixed in the next DynDOLOD DLL NG and scripts version.

As long as the workarounds and the DynDOLOD DLL NG are experimental, the uploads are hidden at https://www.nexusmods.com/skyrimspecialedition/mods/57264 on purpose, though based on users asking about it, I still think Nexus notifies about an update to it.

Expand  

I just checked.  It does appear to fix itself after walking away and coming back to it.  Had not tried that previously.  Looking forward to Alpha-4.  I'll keep checking for it.

Posted
  On 2/4/2023 at 2:06 PM, Rozen said:

Run 1: It toke a long time to get past DynDOLOD_Tamriel.dds 16384 x 8192 then got stuck at DynDOLOD_Tamriel_Glow.dds 1024 x 1024 CPU usage stayed around 20% and longer I waited the memory usage went down all the way to only 111.1 MB. After telling it to close it went to the background processes and stayed around 20% CPU usage but the memory jumped up to 890.6 MB, waited a little to see if it would go away but never did so had to end task on it. Logs> https://ufile.io/f/1rfci

Run 2: went faster to get past  DynDOLOD_Tamriel.dds 16384 x 8192 and got past DynDOLOD_Tamriel_Glow.dds 1024 x 1024 but did not lock up or crash, Logs> https://ufile.io/f/p9z2c

 

Expand  

Let me know what happens with this test version https://mega.nz/file/YMZHhabZ#mEYVLmGV7ryiEcHLb5hPCqUUNRCxwJb0MUwQ6e0HqIs

Posted (edited)
  On 2/4/2023 at 7:38 PM, sheson said:

Let me know what happens with this test version https://mega.nz/file/YMZHhabZ#mEYVLmGV7ryiEcHLb5hPCqUUNRCxwJb0MUwQ6e0HqIs

Expand  

Run 1: Crashed and made none of the logs.

Edit: adding the windows crash report from run 1.

Faulting application name: DynDOLODx64.exe, version: 3.0.0.112, time stamp: 0x63deaedc
Faulting module name: ntdll.dll, version: 10.0.22621.900, time stamp: 0xa97a9ed6
Exception code: 0xc0000374
Fault offset: 0x000000000010c249
Faulting process id: 0x0x48A8
Faulting application start time: 0x0x1D938D1662D4CD6
Faulting application path: C:\DynDOLOD 3.00-68518-Alpha-111-1673607327\DynDOLOD\DynDOLODx64.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: bd918364-0a2e-4c01-b06b-12c2c98b187e
Faulting package full name: 
 

Edited by Rozen
Posted (edited)

Okay so this time it might have been my drivers, I went to load up a game and got a driver crash, going back to do a few runs and hope and pray it was just a driver slowly failing this time.

Did a full driver clean re-install and told it to reset its settings on install.

Edited by Rozen
Posted
  On 2/4/2023 at 9:37 PM, sheson said:

Is there a bugreport.txt for this one?

Expand  

there was not, and it might be due to like I said about my driver just crashing trying to load up a game.

Love AMD's hardware but their software is really tweaky at times lol.

Posted (edited)

New Run: Right off the bat it's moving through files so much faster than before, got the OpenGL error again but this time I got a please wait message and it made a bug report log but not the other 2 logs.

Here is the bug report log for this run> https://ufile.io/b7wish01

Edit: also looking at your bug report log I see it says I am on windows 10 but I am not I am on windows 11.

Edited by Rozen
Posted
  On 2/4/2023 at 10:02 PM, Rozen said:

New Run: Right off the bat it's moving through files so much faster than before, got the OpenGL error again but this time I got a please wait message and it made a bug report log but not the other 2 logs.

Here is the bug report log for this run> https://ufile.io/b7wish01

Edit: also looking at your bug report log I see it says I am on windows 10 but I am not I am on windows 11.

Expand  

You didn't install the crapware with the driver, did it get an update or did you just do a clean install so maybe some settings got reset?

Build numbers of Windows 11 start with 10. The build is 10.0.22621. The bugreport is made by madexcept.

Let me know what happens with this test version https://mega.nz/file/8Zx3nL4b#JgL8vWl-jdA2z_QF0A2481bpyC1sP-E85_-y-zmezPI

Posted
  On 2/4/2023 at 10:36 PM, sheson said:

You didn't install the crapware with the driver, did it get an update or did you just do a clean install so maybe some settings got reset?

Build numbers of Windows 11 start with 10. The build is 10.0.22621. The bugreport is made by madexcept.

Let me know what happens with this test version https://mega.nz/file/8Zx3nL4b#JgL8vWl-jdA2z_QF0A2481bpyC1sP-E85_-y-zmezPI

Expand  

ah okay I just seen windows 10 and I was like wait what, but I am on 11 lol and I uninstalled the software and drivers that AMD uses to control their GPU and got the drivers and software from the AMD website here> AMD Drivers and Support | AMD

Going to go test that new version now.

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.