DynDOLOD 3.00 Alpha 190

[fattyzhouse]

Ayleid Aquarium is a modified version of The Dragonborn's Aquarium by Betalille. I made quite a few changes so it's entirely possible that I'm the culprit here. LoL! I don't have a discord but I'll sign up and snag the experimental version if need be. I have my load order opened up in xedit 4.0.4 now. It opened up without a hitch.

[fattyzhouse]

I have permission from Betalille to upload my version to Nexus so if I've made a mistake now would be a perfect time to catch it. I could copy it to my google drive and drop a link to it if you want to have a look see. 

[sheson]

  On 3/19/2022 at 3:29 PM, fattyzhouse said:

Ayleid Aquarium is a modified version of The Dragonborn's Aquarium by Betalille. I made quite a few changes so it's entirely possible that I'm the culprit here. LoL! I don't have a discord but I'll sign up and snag the experimental version if need be. I have my load order opened up in xedit 4.0.4 now. It opened up without a hitch.

Expand  

Note that xEdit often continues to load despite a plugin having problems so that it can still be worked on and fixed. Pay attention to the log messages.

See if loading/saving plugin in CK makes a difference.

Since DynDOLOD is based on the 4.1.4 experimental, test with that if possible. Otherwise send me link in a PM.

[fattyzhouse]

Will do. Be back in a few with a report. Thanks!

[fattyzhouse]

Found it. TexGen fired up and is running as it should. The xedit log messages pointed me right to it. I think I realize now how I messed up. I had made one single change to the Ayleid Aquarium plugin using the creation kit AFTER I flagged the esp as an esl using xedit. That one change gave me a bad form id. (Or an un-compacted form id?) I have several of what they call 'twinkle lights' scattered about the interior and I remember adding one more 'twinkle light' after flagging as an esl. 
My solution here was to
(1)unflag the esp. (2)Resave it without the esl flag. (3)Close xedit. (4)Reopen xedit. (5)Recompact the form id's and reflag the plugin as esl.
That eliminated the error in xedit and TexGen fired up and is running proper. I'll come back if there's anything else worth reporting, or if you have any questions about my ramblings. Have a great one you holy cow you! Thanks for the help!

[sheson]

  On 3/19/2022 at 4:57 PM, fattyzhouse said:

Found it. TexGen fired up and is running as it should. The xedit log messages pointed me right to it. I think I realize now how I messed up. I had made one single change to the Ayleid Aquarium plugin using the creation kit AFTER I flagged the esp as an esl using xedit. That one change gave me a bad form id. (Or an un-compacted form id?) I have several of what they call 'twinkle lights' scattered about the interior and I remember adding one more 'twinkle light' after flagging as an esl. 
My solution here was to
(1)unflag the esp. (2)Resave it without the esl flag. (3)Close xedit. (4)Reopen xedit. (5)Recompact the form id's and reflag the plugin as esl.
That eliminated the error in xedit and TexGen fired up and is running proper. I'll come back if there's anything else worth reporting, or if you have any questions about my ramblings. Have a great one you holy cow you! Thanks for the help!

Expand  

Oh yeah, CK is the one that ignores the ESL flag when editing plugins, meaning it happily creates new form IDs outside the allowed limits.

Odd that this resulted in an assertion error and not the invalid object ID error message.

[Vernon]

LODGenx64.exe randomly stops using CPU, even with antivirus turned off. It uses all of my RAM but has CPU usage at 0%

[sheson]

  On 3/20/2022 at 3:30 AM, Vernon said:

LODGenx64.exe randomly stops using CPU, even with antivirus turned off. It uses all of my RAM but has CPU usage at 0%

Expand  

See if using the LODGenThreadSplit setting explained at https://dyndolod.info/Help/LODGen#Out-of-Memory helps.

If problem persists, set verbose=1 in DynDOLOD_SSE.INI, run and then upload LODGen log and DynDOLOD log, debug as explained on the first post.

[MysticElodie]

Heya! I've been running into an issue with the latest alpha where the snow shader isn't appearing on snowy rock/mountain LOD meshes; mountains far across the map look fine, but around the LOD4-8 range they seem to lose the shader.

Thought it might've been something with my majestic mountains/snow setup, but I'm running into the same thing generating LODs on a fresh MO2 profile- not sure if something else in my install might be causing it. Here's the logs: https://ufile.io/wco3q129

[capticetrice]

Updated from previous build od DynDOLOD3 to Alpha 83 build causes a "Windows can not access the specified device, path or file" window. 
Restoring the previous D3 build however works like a charm. 
Permissions are set to me and the application and its folder is accepted to antivirus and ransomware whitelist.
That's all i wanted to report.

[sheson]

  On 3/21/2022 at 1:04 AM, capticetrice said:

Updated from previous build od DynDOLOD3 to Alpha 83 build causes a "Windows can not access the specified device, path or file" window. 
Restoring the previous D3 build however works like a charm. 
Permissions are set to me and the application and its folder is accepted to antivirus and ransomware whitelist.
That's all i wanted to report.

Expand  

Read the first post which log, debug log and bugreport.txt to upload when making reports.
If no such logs exists check the Windows Event log.

https://support.microsoft.com/en-us/topic/-windows-cannot-access-the-specified-device-path-or-file-error-when-you-try-to-install-update-or-start-a-program-or-file-46361133-47ed-6967-c13e-e75d3cc29657

It is unclear when and how this message appears. Such file access issues directly from the OS itself are typically unrelated to the simple program itself.

[sheson]

  On 3/20/2022 at 9:20 PM, MysticElodie said:

Heya! I've been running into an issue with the latest alpha where the snow shader isn't appearing on snowy rock/mountain LOD meshes; mountains far across the map look fine, but around the LOD4-8 range they seem to lose the shader.

Thought it might've been something with my majestic mountains/snow setup, but I'm running into the same thing generating LODs on a fresh MO2 profile- not sure if something else in my install might be causing it. Here's the logs: https://ufile.io/wco3q129

Expand  

Open Tamriel.4.-4.-12.bto, Tamriel.8.-8.-16.bto and Tamriel.16.-16.-16.bto in ..\Meshes\Terrain\Tamriel\Objects\Tamriel.16.-16.0.bto in NifSkope.

Click on the Bleak Falls Barrow arcs to open its BSSubIndexTriShape in the Block List to check that their name contains "snow", for example objSnow-LargeRef or objSnow for the higher LOD Levels.

If they do, check which plugin is the last to change the Snow LOD Shaders https://dyndolod.info/Help/Snow-Ash-LOD-Shader, though based on the logs there probably aren't any.

[MysticElodie]

Looks like the meshes do have objSnow (or a variation) at all three levels, and nothing past the official plugins is overriding either snow shader on this profile.

 

[sheson]

  On 3/21/2022 at 8:28 AM, MysticElodie said:

Looks like the meshes do have objSnow (or a variation) at all three levels, and nothing past the official plugins is overriding either snow shader on this profile.

 

Expand  

You should have the same problem with vanilla LOD meshes then?

Test with default INIs.

If that all works, upload the mentioned BTO files from the output.

[MysticElodie]

Tested with the default Ultra INIs, no luck there. Disabling DynDOLOD's output files makes the snow appear as you'd expect from the vanilla LODs.

Noticed glancing again at the meshes that the LOD4 mountain's BSSubIndexTriShape has the name "objSnow-LargeRefobjSnowHD-LargeRef", which doesn't quite look right? But I'm not sure if that's anything.

meshes.zipFetching info...

Edited March 21, 2022 by MysticElodie