Jump to content

Recommended Posts

Posted
  On 2/3/2023 at 9:02 PM, sheson said:

Thanks. That helps.

Expand  

No problem.  Is there a way to get notified on Nexus (or perhaps another site) when new versions of DynDOLOD DLL NG are available?  Seems only the SE version is able to be browsed.

Posted
  On 2/3/2023 at 8:24 PM, sheson said:

Fingers crossed...

Expand  

I am now on my new video card and will be running tests again here soon, doing a windows update that showed up right before i was going do a new full run with a newly made texgen file.

Tested on call of duty already and the new video card is working great.

Posted (edited)
  On 2/3/2023 at 10:42 PM, Rozen said:

Okay test run 1 got a crash, it also did not make any of the logs you been getting me to send.

be4135c2e93b2d39da6b64a6125f58ca.png

Expand  

Just adding this, ran it again with task manager up and it is doing this, and brings a lot of those sub processes up and closes them fast more than one time then goes on without doing it again, on this run it got stuck on [19:50] [DLC01FalmerValley] Creating texture atlas C:\DynDOLOD 3.00-68518-Alpha-111-1673607327\DynDOLOD\DynDOLOD_Output\Textures\DynDOLOD\LOD\DynDOLOD_DLC01FalmerValley.dds 4096 x 4096 and went to 0% COU usage.

Also did not make the logs you been getting me to send.

https://i.gyazo.com/db40b4056769fb7a8f57bbc8098e16a1.mp4

Ops update it did make the logs this time but only after fully crashing it did they show up.

Logs> https://ufile.io/f/cnhhu

Edited by Rozen
Posted

Did a 3rd run, made a video of this run and uploading it to youtube, i will post the link when the video is done uploading, it did not do what it did last with the sub processes and this time it did not make the logs again, but in windows event viewer I got a crash log.

Faulting application name: DynDOLODx64.exe, version: 3.0.0.112, time stamp: 0x63dd1986
Faulting module name: ntdll.dll, version: 10.0.22621.900, time stamp: 0xa97a9ed6
Exception code: 0xc0000374
Fault offset: 0x000000000010c249
Faulting process id: 0x0x24E4
Faulting application start time: 0x0x1D938277974CBBA
Faulting application path: C:\DynDOLOD 3.00-68518-Alpha-111-1673607327\DynDOLOD\DynDOLODx64.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: c417aa56-1e63-467d-8f9a-a8ac44d4ac79
Faulting package full name: 
Faulting package-relative application ID: 

Fault bucket 1804213948848729828, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: DynDOLODx64.exe
P2: 3.0.0.112
P3: 63dd1986
P4: StackHash_d3f8
P5: 10.0.22621.900
P6: a97a9ed6
P7: c0000374
P8: PCH_6B_FROM_ntdll+0x000000000009F957
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.a8b2ca69-337d-4478-a7a5-659ffd65293d.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.a9e9642b-98ee-447a-94a3-ef8206ce9b3e.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.ce918e57-6074-4a76-980c-a49d1408169d.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.fcd4933c-c558-4d64-afc1-d0e58c7c17af.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.58c0948a-6e07-400c-841c-82e2238439f6.tmp.xml

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_DynDOLODx64.exe_11eda9e46b74a64dd9c765c1165be24c312a23_209c72da_debb94ce-78bc-4f27-98d6-f47527ba8b8d

Analysis symbol: 
Rechecking for solution: 0
Report Id: c417aa56-1e63-467d-8f9a-a8ac44d4ac79
Report Status: 268435456
Hashed bucket: c57391a73b2bb2bea909db06ffeeeee4
Cab Guid: 0

Posted

just a heads up I just noticed that you updated the DynDOLOD DLL NG and Scripts 3.00 from alpha 2 to alpha 3 so I am updating that now and doing a few new runs to see what happens.

Run 1: Seemed to go faster now making the files on a lot of parts, did not make the logs you been getting me to send again until it was done, Logs> https://ufile.io/f/3clrk

Run 2: Same as run 1, Logs for run 2> https://ufile.io/f/e1wta

I don't know if I just got lucky runs again but seems like updating the DynDOLOD DLL NG and Scripts 3.00 from alpha 2 to alpha 3 did the trick, I will do a few more test runs when I wake up and let you know what happens and test any new version you need tested if you need me too.

Posted
  On 2/3/2023 at 7:53 PM, sheson said:

This does not show if the latest alpha-111 was used or not. Upload the accompanying TexGen/DynDOLOD logs and debug logs for which the checks have been done.

"Grass mapping not found" means that those grasses found in the cgid will not have grass LOD. This is expected for underwater grasses and grasses that do not have billboards generated.

If some BTOs have no grass LOD, it means there should be corresponding no "mapping not found" or "no grass data" messages. The first tells you which grass LOD billboards are missing, which you can then double check for creation in the ..\textures\terrain\lodgen\TexGen_[GAME MODE]_[Tree|Grass]_Billboards.txt log file as explained at  https://dyndolod.info/Help/TexGen-Configuration#Tree-Grass-LOD-Billboards.

Use expert mode to only generate a specific BTO again, so you only have log message for those 16 cells it covers. https://dyndolod.info/Help/Expert-Mode#Specific-Chunk

Use the DynDOLOD SkyUI MCM - You Are Here to know the coordinates for a BTO.

Expand  

The rest of my logs are here. I have version 111.
https://drive.google.com/drive/folders/13LSsNUuoOHZKBMdbsvJdJi_OpDp8Ok07?usp=share_link

Posted
  On 2/3/2023 at 11:09 PM, Rozen said:

Just adding this, ran it again with task manager up and it is doing this, and brings a lot of those sub processes up and closes them fast more than one time then goes on without doing it again, on this run it got stuck on [19:50] [DLC01FalmerValley] Creating texture atlas C:\DynDOLOD 3.00-68518-Alpha-111-1673607327\DynDOLOD\DynDOLOD_Output\Textures\DynDOLOD\LOD\DynDOLOD_DLC01FalmerValley.dds 4096 x 4096 and went to 0% COU usage.

Also did not make the logs you been getting me to send.

https://i.gyazo.com/db40b4056769fb7a8f57bbc8098e16a1.mp4

Ops update it did make the logs this time but only after fully crashing it did they show up.

Logs> https://ufile.io/f/cnhhu

Expand  

DynDOLDO/TexGen uses texconvx64.exe to convert textures. Nothing new there. Really no need for videos.

As long as the program is not killed by the OS or you, it should write the logs when shutting down when left alone.

  On 2/4/2023 at 2:57 AM, Rozen said:

just a heads up I just noticed that you updated the DynDOLOD DLL NG and Scripts 3.00 from alpha 2 to alpha 3 so I am updating that now and doing a few new runs to see what happens.

Run 1: Seemed to go faster now making the files on a lot of parts, did not make the logs you been getting me to send again until it was done, Logs> https://ufile.io/f/3clrk

Run 2: Same as run 1, Logs for run 2> https://ufile.io/f/e1wta

I don't know if I just got lucky runs again but seems like updating the DynDOLOD DLL NG and Scripts 3.00 from alpha 2 to alpha 3 did the trick, I will do a few more test runs when I wake up and let you know what happens and test any new version you need tested if you need me too.

Expand  

The DynDOLOD DLL NG and Scripts is used by the game only.

Use this test version https://mega.nz/file/AAJzzJAB#y9Yo8cYuN8V9hhB3xQVMd-cMRbgjs4MKyL_8MMrLFfg

Posted
  On 2/4/2023 at 3:47 AM, LordIceWolf said:
Expand  

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

  • Thanks 1
Posted
  On 2/4/2023 at 7:56 AM, sheson said:

DynDOLDO/TexGen uses texconvx64.exe to convert textures. Nothing new there. Really no need for videos.

As long as the program is not killed by the OS or you, it should write the logs when shutting down when left alone.

The DynDOLOD DLL NG and Scripts is used by the game only.

Use this test version https://mega.nz/file/AAJzzJAB#y9Yo8cYuN8V9hhB3xQVMd-cMRbgjs4MKyL_8MMrLFfg

Expand  

ah okay so i just got lucky again lol, testing it now and I will stop with the video then, just thought it would be helpfully to you sense you can see what it is doing and that last video you can see what file it was at before crashing, showing it was around the dds file types.

Posted (edited)

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

 

Edited by Rozen
Posted
  On 2/3/2023 at 9:24 PM, Kattmandu said:

No problem.  Is there a way to get notified on Nexus (or perhaps another site) when new versions of DynDOLOD DLL NG are available?  Seems only the SE version is able to be browsed.

Expand  

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.

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  

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.

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.