Jump to content

DynDOLOD 3.00 Alpha 180


sheson

Recommended Posts

13 minutes ago, S-Matrix said:

Here it is: https://imgur.com/a/7Df35ed
Not sure if it's normal for there to be two instances of it appearing in the asset window search results, but the assets listed for both entries are the exact same.

That's odd that it shows twice. Which xEdit version are you using? This is a Windows OS, not Wine/Proton on Linux?

Before we spend much time on the textures lets do another check first:

Make a backup of DynDOLOD.esm. Start xEdit and bring up 1D0422B9 again, double click on the entry SBlackSmith [STAT:0008618F] in the row NAME - Base row in order to edit it. Type 3B then hit enter to change it to the XMaker [STAT:0000003B].

If that does not crash, restore DynDOLOD.esm, start xEdit and this time bring up 0008618F. Double clock the entry Architecture\Solutide\SBlackSmith.nif in the row MODL - Model FileName in the right column for DynDOLOD.esp and replace it with MarkerX.nif (it is just the filename without folders). Test if that still crashes.

Link to comment
Share on other sites

1 hour ago, sheson said:

That's odd that it shows twice. Which xEdit version are you using? This is a Windows OS, not Wine/Proton on Linux?

Before we spend much time on the textures lets do another check first:

Make a backup of DynDOLOD.esm. Start xEdit and bring up 1D0422B9 again, double click on the entry SBlackSmith [STAT:0008618F] in the row NAME - Base row in order to edit it. Type 3B then hit enter to change it to the XMaker [STAT:0000003B].

If that does not crash, restore DynDOLOD.esm, start xEdit and this time bring up 0008618F. Double clock the entry Architecture\Solutide\SBlackSmith.nif in the row MODL - Model FileName in the right column for DynDOLOD.esp and replace it with MarkerX.nif (it is just the filename without folders). Test if that still crashes.

Using xEdit 4.04, I believe - I saw today that there's an update available, so it's probably a good idea to move to the newest version. Gonna be afk for an hour or two, so I'll post with news later in the day.

Link to comment
Share on other sites

I'm having difficulty with the BSHeartland worldspace for DynDOLOD.  The Beyond Skyrim people gave an answer in their bug report that their own custom LODs are preferred to those in DynDOLOD, and that they advise not generating LOD files via DynDOLOD for the Beyond Skyrim mod.

So I followed your instructions and figured out how to make the BSHeartland worldspace show up in the list of worldspaces available for DynDOLOD.  I unticked BSHeartland in the selection window, selected everything else, and ran DynDOLOD.

Except it didn't work.  At the end, I got the same list of warnings about missing meshes and textures in BSHeartland.  I'm sure I unticked it, but it appears to have ignored me.  Don't know what to do except uninstall Beyond Skyrim.

Edited by aristotle
Link to comment
Share on other sites

5 hours ago, aristotle said:

I'm having difficulty with the BSHeartland worldspace for DynDOLOD.  The Beyond Skyrim people gave an answer in their bug report that their own custom LODs are preferred to those in DynDOLOD, and that they advise not generating LOD files via DynDOLOD for the Beyond Skyrim mod.

So I followed your instructions and figured out how to make the BSHeartland worldspace show up in the list of worldspaces available for DynDOLOD.  I unticked BSHeartland in the selection window, selected everything else, and ran DynDOLOD.

Except it didn't work.  At the end, I got the same list of warnings about missing meshes and textures in BSHeartland.  I'm sure I unticked it, but it appears to have ignored me.  Don't know what to do except uninstall Beyond Skyrim.

https://dyndolod.info/Mods/Beyond-Skyrim-Bruma

Changing the setting to show the worldspace in the list and then not ticking it, means that nothing is done differently. LOD for the worldspace will still not be generated.

Changing the setting does not change the fact that the mod has missing assets. In this case that typically won't affect LOD being generated for other worldspaces.

Link to comment
Share on other sites

On 11/27/2023 at 2:11 PM, sheson said:

Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log and debug log to upload when making problem reports.

See https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots how to make use full screenshots of the full model with more informative console, both with and without DynDOLOD enabled.

By default DynDOLOD is not doing anything to the vanilla reference for the bridge when running in the TES5 game mode.
When DynDOLOD is running in TES5 game mode, it does not load any patch files for the SSE game mode.
The cause of the problem will be most likely something else entirely.
Making manual edits to generated files or patches is not really solving the cause of the problem.
Making baseless assumptions without having any understanding how anything works is not going to help with finding the actual cause of problems. Proper troubleshooting with the help of the log files and screenshots is.

Do not use DynDOLOD and do not participate in the alpha test until you are able to meet the requirements to do so which includes being able to provide repeatedly requested logs and screenshots so the problem can be properly troubleshooted and solved.

 

Honestly, why would I waste my time on that? I've already fixed my problem myself, now I understand what you did and how you did it so I can fix similar problems in the future, and most importantly you've already decided it's not a problem with your plugin even though you haven't seen any logs yet, so you wouldn't even read said log.

 

Link to comment
Share on other sites

1 hour ago, TioDrakul said:

 

Honestly, why would I waste my time on that? I've already fixed my problem myself, now I understand what you did and how you did it so I can fix similar problems in the future, and most importantly you've already decided it's not a problem with your plugin even though you haven't seen any logs yet, so you wouldn't even read said log.

Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log and debug log to upload when making problem reports.

See https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots how to make use full screenshots of the full model with more informative console, both with and without DynDOLOD enabled.

If you use DynDOLOD and participate in the alpha test, then you are required to upload the repeatedly requested logs and screenshots. This will ensure nobody, including you is wasting time doing useless things. You do not seem to know how anything works. You do not seem to know how to properly troubleshoot the problem to find the actual cause. So you already wasted days.

You are wasting time by actively refusing to simply upload the repeatetly requested logs and screenshots. The actual cause could have probably been found and fixed by now.

You are wasting time by making up reasons for the cause of the problem. I am trying to reply to these assumptions as best as possible by explaining how things normally work for everyone else. It doesn't help anyone, including you, to find the actual cause of the problem.

I have not decided anything because you did not upload any of the repeatedly requested logs and screenshots.

I suggest to read the past decade of posts being made here. You are making a fool of yourself with your attitude, behavior and and wrong claims.

If you know how to fix the actual cause of the problem in DynDOLOD, then provide your fix so it can be applied for everyone.

Do not use DynDOLOD and do not participate in the alpha test until you are able to meet the requirements.

Link to comment
Share on other sites

Greetings! Ultra noob here. This is my first time modding anything.

I successfully completed the STEP build, then used that to add on more mods. I've gone all out with lots of terrain and graphics mods, city overhauls, and a few worldspaces. I meticulously as possible put it all together, got my Loot dam near perfectly clean (there are like 3 cases of LOOT telling me there is a patch or update were I swear to god no such patch/update exists that I can find), I searched for errors in xEdit and removed all the "could not be resolved" errors. There are some other errors, but I found some threads on reddit that explained those types are safe to be ignored. Now I'm re-running xLod, ACMOS, and DynDOLOD. Click yes on "Update existing Plugin(s)?". 

About 10 minutes in I get this 100% repeatable error. 
Error: Assertion failure (G:\Delphi\Projects\DynDOLOD3\Core\wbImplementation.pas, line 7687)

Looking through the thread I see Sheson telling people to clean, fix, or remove faulty plugins. DynDOLOD also says to use xEdit to fix errors. I would do that, but I have no idea where to look. In other people examples, the Assertion error indicated a specific reference or plugin. Mine just says "wblmplementation.pas, line 7687" and I have no idea what that means.
I also saw sheson tell someone to put -speed in the DynDOLOD arguments. I tried that but no dice. My versions are up to date. I've read through every reference to assertion failures I can find in this forum and on reddit, but I could have missed something. 

Debug log: https://ufile.io/lgikmxit
SSE log: https://ufile.io/emoxui9i
Bugreport, Mod list, Plugin list: https://paste.ee/p/ePow1

Many thanks to Sheson and the other admins here. I started this from ZERO knowledge of modding or how games work and I've learned so much in such a short time.

 

Link to comment
Share on other sites

46 minutes ago, Brambleshire said:

Greetings! Ultra noob here. This is my first time modding anything.

I successfully completed the STEP build, then used that to add on more mods. I've gone all out with lots of terrain and graphics mods, city overhauls, and a few worldspaces. I meticulously as possible put it all together, got my Loot dam near perfectly clean (there are like 3 cases of LOOT telling me there is a patch or update were I swear to god no such patch/update exists that I can find), I searched for errors in xEdit and removed all the "could not be resolved" errors. There are some other errors, but I found some threads on reddit that explained those types are safe to be ignored. Now I'm re-running xLod, ACMOS, and DynDOLOD. Click yes on "Update existing Plugin(s)?". 

About 10 minutes in I get this 100% repeatable error. 
Error: Assertion failure (G:\Delphi\Projects\DynDOLOD3\Core\wbImplementation.pas, line 7687)

Looking through the thread I see Sheson telling people to clean, fix, or remove faulty plugins. DynDOLOD also says to use xEdit to fix errors. I would do that, but I have no idea where to look. In other people examples, the Assertion error indicated a specific reference or plugin. Mine just says "wblmplementation.pas, line 7687" and I have no idea what that means.
I also saw sheson tell someone to put -speed in the DynDOLOD arguments. I tried that but no dice. My versions are up to date. I've read through every reference to assertion failures I can find in this forum and on reddit, but I could have missed something. 

Debug log: https://ufile.io/lgikmxit
SSE log: https://ufile.io/emoxui9i
Bugreport, Mod list, Plugin list: https://paste.ee/p/ePow1

Many thanks to Sheson and the other admins here. I started this from ZERO knowledge of modding or how games work and I've learned so much in such a short time.

What other errors are reported by xEdit that you choose to ignore?

You said Yes to this message prompt:
Update existing plugin(s)? If this is not successful start from scratch.

https://dyndolod.info/Generation-Instructions#2-Generate-The-LOD-Mod-with-DynDOLOD
Pay attention to all log messages. 

For example these messages which are repeated many times:
<Warning: File [B9] DynDOLOD.esp with Group GRUP World Children of [..] is missing an overriden record for[..]

Delete the output folder log folder, delete bugreport,.txt and then generate DynDOLOD from scratch - that means to disable/remove old DynDOLOD output in the load order. If problem persists, upload new log, debug log and bugreport.txt.

https://dyndolod.info/Updating

Link to comment
Share on other sites

On 11/27/2023 at 8:25 PM, sheson said:

Thanks. RIght now here is what I am seeing: it reserves memory for a texture with X*Y resolution, and a few milliseconds later asks for the X*Y of the reserved memory and at some point the values returned are wrong, while everything worked perfectly fine for the same texture several times before for the earlier worldspaces.

So this seems to be something random. Can you double check that there are no instabilities caused by CPU overclocking, memory timings, other BIOS settings etc?
Can you double check main and video memory usage while the tool runs. Maybe really close everything else, including browsers and whatever else might be using video memory.

Run this test version https://mega.nz/file/9FYRHZ5C#dNqoWMpDrH9LRN1nmGq5Brwnjo29MjQ9eBmVTn4GieY and upload new bugreport.txt, log and debug log.

No overclocking is done on this system, and the only setting enabled in the BIOS is XMP. I haven't run long stress tests yet but everything seems stable otherwise. I also pretty much closed all other programs during the latest DynDOLOD run except from Vortex and DynDOLOD itself but I still got an error. As for memory usage, I haven't checked it this time but system memory is 16GB and the GPU has 8GB of video memory so I assume it should be plenty with everything else closed.

Let me know if you need me to test this further though, I can do another run and closely monitor memory usage and maybe even do some long hardware stress tests if needed.

Latest logs: https://ufile.io/dj87ufng 

Edited by Chromatic
Link to comment
Share on other sites

2 hours ago, Chromatic said:

No overclocking is done on this system, and the only setting enabled in the BIOS is XMP. I haven't run long stress tests yet but everything seems stable otherwise. I also pretty much closed all other programs during the latest DynDOLOD run except from Vortex and DynDOLOD itself but I still got an error. As for memory usage, I haven't checked it this time but system memory is 16GB and the GPU has 8GB of video memory so I assume it should be plenty with everything else closed.

Let me know if you need me to test this further though, I can do another run and closely monitor memory usage and maybe even do some long hardware stress tests if needed.

Latest logs: https://ufile.io/dj87ufng 

Use this test version https://mega.nz/file/5IhWEABT#kXwLkR67UPnTaDIy-QCug_OgnO2deupYmqxPBPndRzc and upload new logs.

Try to keep an eye on memory just in case.

Link to comment
Share on other sites

Error window:

[Window Title]
TexGen

[Main Instruction]
Error while loading images from memory E3571008 (357914116 Bytes) (file format: dds).

[Content]
Exception Message: Access violation at address 004BBEC9 in module 'TexGen.exe'. Write of address 00000000.

[01:05] <Error: OpenGL: out of memory for textures\architecture\whiterun\wrslatefloor01_n.dds>
[01:05] <Error: OpenGL: out of memory for textures\clutter\stockade\stockadeplanks01snow.dds>
[02:13]     Creating C:\AETools\DynDOLOD\TexGen_Output\textures\lod\wrplasterint01lowlod.dds from 4 textures
[02:28] Error while loading images from memory E3571008 (357914116 Bytes) (file format: dds). Exception Message: Access violation at address 004BBEC9 in module 'TexGen.exe'. Write of address 00000000
[02:28] Removing temporary files
[02:29] TexGen completed successfully
[02:29] Created a summary of log messages C:\AETools\DynDOLOD\Summary\TexGen_Index.html.
Error while loading images from memory E3571008 (357914116 Bytes) (file format: dds). Exception Message: Access violation at address 004BBEC9 in module 'TexGen.exe'. Write of address 00000000
Error: Error while loading images from memory E3571008 (357914116 Bytes) (file format: dds). Exception Message: Access violation at address 004BBEC9 in module 'TexGen.exe'. Write of address 00000000.
The message dialog has been copied to the clipboard

has anyone encountered this before, if so can someone please help?

Link to comment
Share on other sites

17 minutes ago, Husqvarna1 said:

Error window:

[Window Title]
TexGen

[Main Instruction]
Error while loading images from memory E3571008 (357914116 Bytes) (file format: dds).

[Content]
Exception Message: Access violation at address 004BBEC9 in module 'TexGen.exe'. Write of address 00000000.

[01:05] <Error: OpenGL: out of memory for textures\architecture\whiterun\wrslatefloor01_n.dds>
[01:05] <Error: OpenGL: out of memory for textures\clutter\stockade\stockadeplanks01snow.dds>
[02:13]     Creating C:\AETools\DynDOLOD\TexGen_Output\textures\lod\wrplasterint01lowlod.dds from 4 textures
[02:28] Error while loading images from memory E3571008 (357914116 Bytes) (file format: dds). Exception Message: Access violation at address 004BBEC9 in module 'TexGen.exe'. Write of address 00000000
[02:28] Removing temporary files
[02:29] TexGen completed successfully
[02:29] Created a summary of log messages C:\AETools\DynDOLOD\Summary\TexGen_Index.html.
Error while loading images from memory E3571008 (357914116 Bytes) (file format: dds). Exception Message: Access violation at address 004BBEC9 in module 'TexGen.exe'. Write of address 00000000
Error: Error while loading images from memory E3571008 (357914116 Bytes) (file format: dds). Exception Message: Access violation at address 004BBEC9 in module 'TexGen.exe'. Write of address 00000000.
The message dialog has been copied to the clipboard

has anyone encountered this before, if so can someone please help?

Moved to the DynDOLOD 3 Alpha thread. Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which entire log, debug log and bugreport.txt to upload when making posts.

https://dyndolod.info/Messages/Exceptions
If there are any kind of memory errors, make sure to use the x64 versions of the tools. Check FAQ answers for High memory usage.

https://dyndolod.info/Messages/Exceptions#OpenGL
If they are memory related also check FAQ answers for High memory usage.

https://dyndolod.info/FAQ#High-memory-usage-Out-of-memory

https://dyndolod.info/Installation-Instructions
Use the x64 versions of DynDOLOD/TexGen. The x86 versions may run into memory errors especially with large texture resolution settings and are included in case a x86 OS is used. They are functionally identical, the only difference is the supported CPU architecture.

Link to comment
Share on other sites

Error  Load Order(if it matters my specs are r7 7735hs 16gb ddr5 mobile rtx 4060 8gb and everything is on an ssd)I installed dyndolod following this guide and everything worked correctly i installed silent horizons 2 universal core enb as well no issues after that was just following a list of mod recommendations and i got to majestic mountains after installing it i followed as the mod said and tried to re run tex gen and dyndolod at first i forgot to disable the previous outputs so after dealing with that tex gen gave me this error
my game reaches skyrim logo i get the enb binaries thing and then it crashes to desktop.

p.s: I have missing masters of CC content with COTN I dont know if i can resolve that i was planning on just ignoring them but i can try disabling those mods to see if that is causing the issue

p.s2:im not new to modding but its my first time using dyndolod and enbs and i have no idea what im doing

p.s3:im on vortex sse 1.5.97 latest enb binaries and skse 2_00_20 i think.

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.