Jump to content

Recommended Posts

Posted
  On 1/14/2022 at 4:11 PM, adancau said:

I have the same issue, where I get the same error concerning DynDOLOD Resources.

I have just upgraded to DynDOLOD Resources SE 3.00 (Main, vAlpha-18) from Nexus (from the previous Alpha - it was the most routine upgrade). I have triple checked that I have installed the correct file (I'm in MO2).

I have also upgraded to the latest DynDOLOD 3.0 Alpha-63.

This is what I see in the log:

[00:01] DynDOLOD Resources SE: 3.00 <= 3.00 <= 3.00
[00:01] Error: DynDOLOD Resources SE issue. Do not install DynDOLOD Resources intended for other game versions. Do not modify any of the files. Verify the archive downloaded completely and all core files were installed.
[00:11] User says "Exit DynDOLOD"

For the record, I am using Skyrim SE (1.5.97)

EDIT: Downgraded to DynDOLOD Resources SE 3.00 (Main, vAlpha-17), problem disappears (using the same DynDOLOD 3.0 Alpha-63 executable)

Expand  
  On 1/14/2022 at 4:30 PM, Winterlove said:

+1 here, also seeing the issue, exactly as described, I'm using Alpha-63 DynDOLOD, Alpha-18 SE Resources.

Expand  
  On 1/14/2022 at 5:01 PM, ButchDiavolo said:

I too have this error with the latest versions (DynDOLOD alpha63 and DynDOLOD alpha18 Resources. TexGen went fine, but when starting DynDOLOD generation the error occurs

Here are the error logs.

Expand  

Uploading again as DynDOLOD Resource 3 SE as Alpha-19, see if that works.

  • Like 1
Posted (edited)

Can confirm the error is gone.

One small observation - the new file is called DynDOLOD 3.00 (Main, vAlpha-19), used to be DynDOLOD Resources SE 3.00 (Main, vAlpha-##) - it's not an issue though and installs with the proper mod name

Edited by adancau
Posted
  On 1/14/2022 at 5:10 PM, ButchDiavolo said:

Generating as we speak. I see you took out the giantfire thingie. Was that the issue?

Expand  

I think the publishing script really packed the LE version and gave it the SE filename. When I blame the script it probably means it was a firstborn pressing the wrong button.

Posted (edited)
  On 1/14/2022 at 5:12 PM, sheson said:

I think the publishing script really packed the LE version and gave it the SE filename. When I blame the script it probably means it was a firstborn pressing the wrong button.

Expand  

*nods* Probably mine then. Runs in the family.

EDIT: *looks around* Ok... it stumbles in the family

Edited by ButchDiavolo
Posted
  On 1/14/2022 at 5:02 PM, sheson said:

Uploading again as DynDOLOD Resource 3 SE as Alpha-19, see if that works.

Expand  

This did it for me, currently generating lod.  ty sheson, unfortunately I dont intend to have any first born to give you, but should it happen, the demon spawn is definitely yours.

Posted
  On 1/14/2022 at 5:01 PM, Thardrim said:

Using default settings for TexGen. Rendered and Stitched Objects are generated correctly - no crashing generating them when I enable only those options. The problem is with billboards. If I enable Grass and/or HD trees, it always crashes. If I don't enable those options and use the default options (no Grass - no HD trees) sometimes it crashes, sometimes it doesn't.

Here are the logs that were in \Logs after every sesion - unfortunately, no bugreport.txt is generated:

https://ufile.io/i6oy9cu1 (HD Trees and Grass - CRASH)

https://ufile.io/atfo3hkv (Default - no HD trees, no Grass - CRASH)

https://ufile.io/f/vhje4 (Default - no HD tress, no Grass - SUCCESSFUL)

 

Thanks again

P.S. As you can see, when it crashes, only the realtime log is generated.

Expand  

Check the Windows event log if there is a report in there.

While the tool runs, check main memory and video memory usage.

Maybe disable anything like Geforce experience or software from the graphics card maker, overlays etc. Everything else that is equally unnecessary running in the background.

Posted
  On 1/14/2022 at 5:02 PM, sheson said:

Uploading again as DynDOLOD Resource 3 SE as Alpha-19, see if that works.

Expand  

Confirmed, seems to be happy now. Well, at least as far as this problem is concerned. I seem to be getting a crash partway through running DynDOLOD itself (I don't have time right now to drill down into it, sadly). Still, thank you for fixing the original problem!

Posted
  On 1/14/2022 at 6:52 PM, chumik6000 said:

I get a crush with new latest version of DynDOLOD 3.00 alpha 63 (cant save a game, i can load my old save but when make a new one i get crush)

https://drive.google.com/file/d/1Jug0dJG_TkgfNWpvLgg2mUrz9SIgIQzt/view?usp=sharing

resaver says this: https://drive.google.com/file/d/1AvXnkzSfZJENglvi7YLfvSqjPiWZbCju/view?usp=sharing

Is there is a way to fix this? Ty!

Expand  

Why do you believe the game crashing while saving has anything to do with DynDOLOD or the latest Alpha?

On https://dyndolod.info/FAQ read answers for ILS or CTD

If there are problems saving in Skyrim Special Edition, install SSE Engine Fixes 4.8 or newer and set SaveGameMaxSize = true in the EngineFixes.toml. Alternatively add/set [SaveGame] uiCompression=1 in Skyrim.INI to change from the default 2 for LZ4 to 1 for zlib compression. 0 means no compression like games are saved in Skyrim.

Posted (edited)

I have engine fixes, SaveGameMaxSize = true. I played with [SaveGame] uiCompression=0 from start. After i reupdate my DynDOLOD, i cannt make a new save game. all new save game become corrupted. if i try to make a new save without DynDOLODs esp my new saves are normal.. 

Edited by chumik6000
Posted
  On 1/14/2022 at 8:02 PM, chumik6000 said:

I have engine fixes, SaveGameMaxSize = true. I played with [SaveGame] uiCompression=0 from start. After i reupdate my DynDOLOD, i cannt make a new save game. all new save game become corrupted. if i try to make a new save without DynDOLODs esp my new saves are normal.. 

Expand  

Are you sure the uploaded crash log is from a saving? Quicksave or save from game menu?

Test with a new game.

Make sure to follow proper clean save routine when updating. Consider using DynDOLOD DLL instead of PapyrusUtil.

Disable autosaves.

Carefully read all warning and error messages from the TexGen/DynDOLOD log.

Remove all other mods but DynDOLOD and its dependencies and whatever mods/plugnis are masters. Start new game. Save. If it still crashes with a new game, upload that crash log and the logs from DynDOLOD as explained on the first post.

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.