Jump to content

Recommended Posts

Posted
7 hours ago, Youss123123 said:

Most of my tree LODs have no leaves but just particles floating around the tree instead of leaves, But the leaves load after I get closer to them, What is the cause for this? I did generate Texgen and Dyndolod, I did download the Hybrid LODs from the mod author's page, I did everything I could possibly think of image.thumb.png.0cf2939751e2a42e117c95d043bbcc4f.png

 

Read the first post which log and debug logs from TexGen/DynDOLOD to upload when making posts

Since almost no information do this obvious test first:
Check that the trees in question are actually LOD by toggling LOD off with tll in console. If the trees remain, they are not LOD but the full models.

If this are 3D tree LOD models/textures from a 3rd party mod (which name you did not mention), check its mod page, comments. If leaves are thinning out in the distance it is typically because of the their textures and their mipmaps. If you want DynDOLOD to fix the alpha of the mipmaps, the UV of the leaves using the textures needs to be between 0.0 and 1.0. https://dyndolod.info/Help/3D-Tree-LOD-Model. Otherwise the mipmaps of the textures shipping with the mod should be created anew with alpha-to-coverage.

Posted
6 hours ago, NBBEAST said:

Awesome. Thank you for the response. So I opened the texgen output and I do have the tamrielicgrass.esp folder, and the various .dds files for each grass type within tamrielic grass. So i went to the data tab within mo2 and scrolled to "textures", and then opened up "lod" folder and saw a bunch of files from texgen output. Included in these files were some .dds lod files for the grass. So I have to think it did load the grass in actually, because its all there. 

To be honest with you, I'm pretty sure the grass lod is working for me now. I don't know what happened exactly but a few nights ago as I was playing, the grass lod seemingly loaded in for me. I think If i remember correctly, I deleted the old xlodgen output within mo2. I think that may have been overwriting any grass lod, I also didn't have xlod installed correctly. Either way, Whiterun looks ridiculously beautiful now, with seemingly endless grass. I can attach a couple photos and perhaps you could assure me that the lod is working as intended? I have noticed that I have alot more stuttering now, I think thats because I generated grass lod in mode 2 (and changed the adjacent ini within ngio) right? From what I hear grass lod mode 1 is alot more performance friendly. 

Also thank you Sheson. For being so gracious and helping me out here with my questions. Also great job on dyndolod 3.0, my game has been aggressively astonishing lately thanks to you and hlt, tamrielic grass and ngio. You've really brought Skyrim to a new level. 

Edit: Another question. Sorry. Should I disable "happy little trees addon- dyndolod 3" if i choose to generate hd trees within texgen for ultra trees in dyndolod 3.0? I ask this because I was trying to do just that and it failed on me when It was generating lod for Arnima (Worldspace within Beyond reach mod). Also what is the performance impact of hd trees with ultra trees? Is it much higher than just ultra trees? I imagine I probably shouldn't since my specs are 1050 gtx 1050ti with 4gb ram. I have ultra trees right now and it feels great. Thank you.

xLODGen can only overwrite grass LOD which is part of object LOD, if you generated object LOD with xLODGen. Use xLODGen to generate terrain LOD only.

Happy Little Trees Add-On - DynDOLOD 3 contains 3D tree LOD assets. If you do not install it, then ultra tree LOD will always use the billboards instead. If the intention is to only use billboards, then 3D tree LOD assets do not need to be installed.

https://dyndolod.info/Help/Ultra-Tree-LOD
"Billboard1 has 4 triangles per tree, while billboard 4 has 8 triangles per tree." 
This is negligibly if the game runs well above 60 FPS and has headroom or when using grass LOD.

If there is a problem generating LOD, carefully check the error message.

Posted
10 hours ago, DarthVitrial said:

After updating to alpha 88 I'm getting an error when generating Winter LOD for the Tundra Homestead CC (tamriel worldspace): Error processing meshes\creationclub\eejsse001\architecture\eej_towerroof.nif Object reference not set to an instance of an object.

 

Other than reinstalling dyndolod resources, I haven't made any changes between this run and the prior (successful) run,only change was going to alpha 88.

Logs are too big to upload here so here's a mega link (there might be remnants from a  prior run in the start of the logs though - I think I cleared out the older stuff but I might have missed one): https://mega.nz/file/ss1SDLQS#SpluHqI8fKtTDdZTUwWEhg7fHmhAR0Ub9NX4NMFumwc
 


(Edit - it seems to be random where that "object reference not set" error happens, rerunning it it happened on Autumn one time and Winter twice, and on different nifs/different worldspaces each time. The common thread seems to be that it's always on a season other than default.)

EDIT 2: definitely seasons specific, turning off season LOD it works just fine.

EDIT 3: Seems specifically caused by the SeasonsCombineAtlas ini setting, when I change that to 0 the seasons lod works too.

I am not able to replicate this. You have the right mesh from DynDOLOD Resources and it is does not seem to have any season replacement.
What is odd that the mesh only sporadically causes a problem. It should always be processed exactly the same for all seasons.

Download https://mega.nz/file/oMBlAAaa#y6nXWUwL6L9rlfKV_5jUhksPmYgJQMLaTqH8q_J5xnE and replace LODGenx64.exe in the Edit Scripts folder. It will print a stack trace to the log. Then run again, upload the LODGen log for whatever season the error happened.

Posted

@sheson I have found two things that might be good for you to know(unless you already know them...)

First, After a lot of trial and error, I have found that at least I will always get an access violation error unless I have dyndolod open and in focus for the entire process in which case it will 99% of the time work fine. Don't know if I am just stupid and that is supposed to be the case or if it is a bug or smt.

Second, that 1% of the times that it doesn't work I have narrowed down to it either being because the HTML file that gets generated brings my browser into focus or because of some random one time bug and because I haven't found a way to stop the HTML file from being opened I can't rly find which of them is the cause.

PS: If the first one isn't a bug then to save yourself headaches and also other people's headaches you should probably give some clear warning either on the download page or before dyndolod starts. Also I hope this helps in any way possible! We all love you for making such an amazing tool!

Posted
23 minutes ago, ArrowFX said:

@sheson I have found two things that might be good for you to know(unless you already know them...)

First, After a lot of trial and error, I have found that at least I will always get an access violation error unless I have dyndolod open and in focus for the entire process in which case it will 99% of the time work fine. Don't know if I am just stupid and that is supposed to be the case or if it is a bug or smt.

Second, that 1% of the times that it doesn't work I have narrowed down to it either being because the HTML file that gets generated brings my browser into focus or because of some random one time bug and because I haven't found a way to stop the HTML file from being opened I can't rly find which of them is the cause.

PS: If the first one isn't a bug then to save yourself headaches and also other people's headaches you should probably give some clear warning either on the download page or before dyndolod starts. Also I hope this helps in any way possible! We all love you for making such an amazing tool!

Upload the log, debug log and bugreport.txt if it exists as explained in the first post when making reports.

Occlusion calculations (that is what the  bugreport.txt you uploaded a while ago showed)  do not work any differently if the program is in focus or not. Such randomness often  means there could be a problem with the hardware, BIOS setting etc.  for example memory related.

By the time the summary is created or the browser is opened, the occlusion calculations are long done. It could be an entirely different problem or just a secondary problem as the result of another. Needs logs and bugreport.txt using the latest version.

Posted
8 hours ago, sheson said:

I am not able to replicate this. You have the right mesh from DynDOLOD Resources and it is does not seem to have any season replacement.
What is odd that the mesh only sporadically causes a problem. It should always be processed exactly the same for all seasons.

Download https://mega.nz/file/oMBlAAaa#y6nXWUwL6L9rlfKV_5jUhksPmYgJQMLaTqH8q_J5xnE and replace LODGenx64.exe in the Edit Scripts folder. It will print a stack trace to the log. Then run again, upload the LODGen log for whatever season the error happened.

OK, running that now.

As a note, the thing is it seems totally random where it fails on and why, the only common thread seems to be having the seasons option enabled?

Posted
19 minutes ago, DarthVitrial said:

Ok, ran it again with that lodgen you linked. Here's all the logs.
it failed in a few places this time (Dimfrost, Tamriel AUT)
I dont see anything in those specific logs so probably the debug log has the info

https://mega.nz/file/NtsjTaLb#LALCmAXgXHjrxK695FJSDlj2JRaSDrxbjJaOiP9Nvsg

Unfortunately the logs are incomplete and do not contain the error message or the trace log.

Did you also copy the LODGenx64.pdb with the LODGenx64.exe into the Edit Scripts?

Can you check the Windows Event log what it says?

Check the c:\Windows\Minidump\ if it contains files with the timestamp.

Posted (edited)
35 minutes ago, sheson said:

Unfortunately the logs are incomplete and do not contain the error message or the trace log.

Did you also copy the LODGenx64.pdb with the LODGenx64.exe into the Edit Scripts?

Can you check the Windows Event log what it says?

Check the c:\Windows\Minidump\ if it contains files with the timestamp.

Yes, I copied them both there.

 

The Minidump folder is completely empty.


Event log:

Faulting application name: LODGenx64.exe, version: 3.0.0.0, time stamp: 0x625923b7
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00007ffb9ccfbfaa
Faulting process id: 0x0x1884
Faulting application start time: 0x0x1D850E8B5B57F65
Faulting application path: D:\Dyndolod\Edit Scripts\LODGenx64.exe
Faulting module path: unknown
Report Id: 5c53a2bb-dae0-4083-a99f-113ca29d23ef
Faulting package full name:
Faulting package-relative application ID:


What other diagnostics can I do?

Edited by DarthVitrial
Posted
27 minutes ago, DarthVitrial said:

Yes, I copied them both there.

 

The Minidump folder is completely empty.


Event log:

Faulting application name: LODGenx64.exe, version: 3.0.0.0, time stamp: 0x625923b7
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00007ffb9ccfbfaa
Faulting process id: 0x0x1884
Faulting application start time: 0x0x1D850E8B5B57F65
Faulting application path: D:\Dyndolod\Edit Scripts\LODGenx64.exe
Faulting module path: unknown
Report Id: 5c53a2bb-dae0-4083-a99f-113ca29d23ef
Faulting package full name:
Faulting package-relative application ID:


What other diagnostics can I do?

Try with this version https://mega.nz/file/sZx3RA6a#VG_SIq43RyOiz3E1flddHOGqOVLbLjkXNCAV5izWt_8

Hopefully that writes the needed info to the log file.

Posted
38 minutes ago, sheson said:

Try with this version https://mega.nz/file/sZx3RA6a#VG_SIq43RyOiz3E1flddHOGqOVLbLjkXNCAV5izWt_8

Hopefully that writes the needed info to the log file.

hm
Ran with that version, logs still seem kinda empty though, and still no minidump... (Heres the logs: https://mega.nz/file/wssl0LIb#z42pFcJZ1Eixv-ztQr1lXsJ3RZo5YwUQdGt0d3TaCsg
BUT, the event log seems useful. I've attached those.

 

Application: LODGenx64.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
   at LODGenerator.Geometry.MergeVertexColors(Boolean)
   at LODGenerator.LODApp.RemoveUnseenFaces(LODGenerator.QuadDesc, LODGenerator.ShapeDesc)
   at LODGenerator.LODApp.TransformShape(LODGenerator.QuadDesc, LODGenerator.StaticDesc, LODGenerator.NiFile, LODGenerator.NifMain.NiTriBasedGeom, LODGenerator.Common.Matrix44, Single, Int32)
   at LODGenerator.LODApp.IterateNodes(LODGenerator.QuadDesc, LODGenerator.StaticDesc, Int32, LODGenerator.NiFile, LODGenerator.NifMain.NiNode, LODGenerator.Common.Matrix44, Single, Int32 ByRef)
   at LODGenerator.LODApp.ParseNif(LODGenerator.QuadDesc, LODGenerator.StaticDesc, Int32)
   at LODGenerator.LODApp+<>c__DisplayClass84_0.<DoLOD>b__0(Int32)
   at System.Threading.Tasks.Parallel+<>c__DisplayClass17_0`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].<ForWorker>b__1()
   at System.Threading.Tasks.Task.InnerInvokeWithArg(System.Threading.Tasks.Task)
   at System.Threading.Tasks.Task+<>c__DisplayClass176_0.<ExecuteSelfReplicating>b__0(System.Object)
   at System.Threading.Tasks.Task.Execute()
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.Tasks.Task.ExecuteWithThreadLocal(System.Threading.Tasks.Task ByRef)
   at System.Threading.Tasks.Task.ExecuteEntry(Boolean)
   at System.Threading.ThreadPoolWorkQueue.Dispatch()

Application: LODGenx64.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ArgumentOutOfRangeException
   at System.ThrowHelper.ThrowArgumentOutOfRangeException(System.ExceptionArgument, System.ExceptionResource)
   at LODGenerator.Geometry.Optimize()
   at LODGenerator.Geometry.ToBSSubIndexTriShape(Boolean, Int32)
   at LODGenerator.LODApp.CreateLODNodesSSE(LODGenerator.NiFile, LODGenerator.NifMain.NiNode, LODGenerator.QuadDesc, System.Collections.Generic.List`1<LODGenerator.ShapeDesc>)
   at LODGenerator.LODApp.DoLOD(LODGenerator.QuadDesc, Boolean)
   at LODGenerator.LODApp.<GenerateLOD>b__85_0(LODGenerator.QuadDesc)
   at System.Threading.Tasks.Parallel+<>c__DisplayClass31_0`2[[LODGenerator.QuadDesc, LODGenx64, Version=3.0.0.0, Culture=neutral, PublicKeyToken=null],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].<ForEachWorker>b__0(Int32)
   at System.Threading.Tasks.Parallel+<>c__DisplayClass17_0`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].<ForWorker>b__1()
   at System.Threading.Tasks.Task.InnerInvokeWithArg(System.Threading.Tasks.Task)
   at System.Threading.Tasks.Task+<>c__DisplayClass176_0.<ExecuteSelfReplicating>b__0(System.Object)

Exception Info: System.AggregateException
   at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean)
   at System.Threading.Tasks.Task.Wait(Int32, System.Threading.CancellationToken)
   at System.Threading.Tasks.Parallel.ForWorker[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](Int32, Int32, System.Threading.Tasks.ParallelOptions, System.Action`1<Int32>, System.Action`2<Int32,System.Threading.Tasks.ParallelLoopState>, System.Func`4<Int32,System.Threading.Tasks.ParallelLoopState,System.__Canon,System.__Canon>, System.Func`1<System.__Canon>, System.Action`1<System.__Canon>)
   at System.Threading.Tasks.Parallel.ForEachWorker[[LODGenerator.QuadDesc, LODGenx64, Version=3.0.0.0, Culture=neutral, PublicKeyToken=null],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.Collections.Generic.IEnumerable`1<LODGenerator.QuadDesc>, System.Threading.Tasks.ParallelOptions, System.Action`1<LODGenerator.QuadDesc>, System.Action`2<LODGenerator.QuadDesc,System.Threading.Tasks.ParallelLoopState>, System.Action`3<LODGenerator.QuadDesc,System.Threading.Tasks.ParallelLoopState,Int64>, System.Func`4<LODGenerator.QuadDesc,System.Threading.Tasks.ParallelLoopState,System.__Canon,System.__Canon>, System.Func`5<LODGenerator.QuadDesc,System.Threading.Tasks.ParallelLoopState,Int64,System.__Canon,System.__Canon>, System.Func`1<System.__Canon>, System.Action`1<System.__Canon>)
   at System.Threading.Tasks.Parallel.ForEach[[LODGenerator.QuadDesc, LODGenx64, Version=3.0.0.0, Culture=neutral, PublicKeyToken=null]](System.Collections.Generic.IEnumerable`1<LODGenerator.QuadDesc>, System.Threading.Tasks.ParallelOptions, System.Action`1<LODGenerator.QuadDesc>)
   at LODGenerator.LODApp.GenerateLOD(System.Collections.Generic.List`1<LODGenerator.StaticDesc>)
   at LODGeneratorCMD.Program.Main(System.String[])

event.evtx event2.evtx

Posted
1 hour ago, DarthVitrial said:

hm
Ran with that version, logs still seem kinda empty though, and still no minidump... (Heres the logs: https://mega.nz/file/wssl0LIb#z42pFcJZ1Eixv-ztQr1lXsJ3RZo5YwUQdGt0d3TaCsg
BUT, the event log seems useful. I've attached those.

 

 

  Hide contents

 

Application: LODGenx64.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
   at LODGenerator.Geometry.MergeVertexColors(Boolean)
   at LODGenerator.LODApp.RemoveUnseenFaces(LODGenerator.QuadDesc, LODGenerator.ShapeDesc)
   at LODGenerator.LODApp.TransformShape(LODGenerator.QuadDesc, LODGenerator.StaticDesc, LODGenerator.NiFile, LODGenerator.NifMain.NiTriBasedGeom, LODGenerator.Common.Matrix44, Single, Int32)
   at LODGenerator.LODApp.IterateNodes(LODGenerator.QuadDesc, LODGenerator.StaticDesc, Int32, LODGenerator.NiFile, LODGenerator.NifMain.NiNode, LODGenerator.Common.Matrix44, Single, Int32 ByRef)
   at LODGenerator.LODApp.ParseNif(LODGenerator.QuadDesc, LODGenerator.StaticDesc, Int32)
   at LODGenerator.LODApp+<>c__DisplayClass84_0.<DoLOD>b__0(Int32)
   at System.Threading.Tasks.Parallel+<>c__DisplayClass17_0`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].<ForWorker>b__1()
   at System.Threading.Tasks.Task.InnerInvokeWithArg(System.Threading.Tasks.Task)
   at System.Threading.Tasks.Task+<>c__DisplayClass176_0.<ExecuteSelfReplicating>b__0(System.Object)
   at System.Threading.Tasks.Task.Execute()
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.Tasks.Task.ExecuteWithThreadLocal(System.Threading.Tasks.Task ByRef)
   at System.Threading.Tasks.Task.ExecuteEntry(Boolean)
   at System.Threading.ThreadPoolWorkQueue.Dispatch()

Application: LODGenx64.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ArgumentOutOfRangeException
   at System.ThrowHelper.ThrowArgumentOutOfRangeException(System.ExceptionArgument, System.ExceptionResource)
   at LODGenerator.Geometry.Optimize()
   at LODGenerator.Geometry.ToBSSubIndexTriShape(Boolean, Int32)
   at LODGenerator.LODApp.CreateLODNodesSSE(LODGenerator.NiFile, LODGenerator.NifMain.NiNode, LODGenerator.QuadDesc, System.Collections.Generic.List`1<LODGenerator.ShapeDesc>)
   at LODGenerator.LODApp.DoLOD(LODGenerator.QuadDesc, Boolean)
   at LODGenerator.LODApp.<GenerateLOD>b__85_0(LODGenerator.QuadDesc)
   at System.Threading.Tasks.Parallel+<>c__DisplayClass31_0`2[[LODGenerator.QuadDesc, LODGenx64, Version=3.0.0.0, Culture=neutral, PublicKeyToken=null],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].<ForEachWorker>b__0(Int32)
   at System.Threading.Tasks.Parallel+<>c__DisplayClass17_0`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].<ForWorker>b__1()
   at System.Threading.Tasks.Task.InnerInvokeWithArg(System.Threading.Tasks.Task)
   at System.Threading.Tasks.Task+<>c__DisplayClass176_0.<ExecuteSelfReplicating>b__0(System.Object)

Exception Info: System.AggregateException
   at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean)
   at System.Threading.Tasks.Task.Wait(Int32, System.Threading.CancellationToken)
   at System.Threading.Tasks.Parallel.ForWorker[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](Int32, Int32, System.Threading.Tasks.ParallelOptions, System.Action`1<Int32>, System.Action`2<Int32,System.Threading.Tasks.ParallelLoopState>, System.Func`4<Int32,System.Threading.Tasks.ParallelLoopState,System.__Canon,System.__Canon>, System.Func`1<System.__Canon>, System.Action`1<System.__Canon>)
   at System.Threading.Tasks.Parallel.ForEachWorker[[LODGenerator.QuadDesc, LODGenx64, Version=3.0.0.0, Culture=neutral, PublicKeyToken=null],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.Collections.Generic.IEnumerable`1<LODGenerator.QuadDesc>, System.Threading.Tasks.ParallelOptions, System.Action`1<LODGenerator.QuadDesc>, System.Action`2<LODGenerator.QuadDesc,System.Threading.Tasks.ParallelLoopState>, System.Action`3<LODGenerator.QuadDesc,System.Threading.Tasks.ParallelLoopState,Int64>, System.Func`4<LODGenerator.QuadDesc,System.Threading.Tasks.ParallelLoopState,System.__Canon,System.__Canon>, System.Func`5<LODGenerator.QuadDesc,System.Threading.Tasks.ParallelLoopState,Int64,System.__Canon,System.__Canon>, System.Func`1<System.__Canon>, System.Action`1<System.__Canon>)
   at System.Threading.Tasks.Parallel.ForEach[[LODGenerator.QuadDesc, LODGenx64, Version=3.0.0.0, Culture=neutral, PublicKeyToken=null]](System.Collections.Generic.IEnumerable`1<LODGenerator.QuadDesc>, System.Threading.Tasks.ParallelOptions, System.Action`1<LODGenerator.QuadDesc>)
   at LODGenerator.LODApp.GenerateLOD(System.Collections.Generic.List`1<LODGenerator.StaticDesc>)
   at LODGeneratorCMD.Program.Main(System.String[])

 

event.evtx 68 kB · 0 downloads event2.evtx 68 kB · 0 downloads

Did you also unpack the *.pdb to Edit Scripts?

What alpha version were you using before 88?

Posted

Hello,

I was trying to run DynDOLOD 3 in order for it to generate some Seasons of Skyrim LODs in order to test it out before I do some more work on my mod list.

I downloaded the Alpha-88 version of DynDOLOD 3.00, with the Alpha-24 resources. I was able to run TexGen, and have its output activated as a mod in Mod Organizer 2. The thing is, any time I run Dyndolod after that, it just closes after making my selection when it gets to this point:

imagen.thumb.png.64c810cde3995ca4e60533fa89d98807.png

The options I chose are Tamriel (Skyrim) - Skyrim.esm [Seasons], and then Medium. I've also tried with the Low option, but I get the same result. Same thing happens if I run MO2 with or without administrator mode. I have attached my load order, my modlist up until now and the two logs that generate when I run DynDOLOD.

Does anyone have any idea what might be causing this issue? If there's anything that I'm missing, please tell me and I will be happy to provide it if I can.

Thank you in advance.

loadorder.txt Modlist.txt DynDOLOD_SSE_Dynamic_LOD.txt DynDOLOD_SSE_Object_LOD.txt

Posted
23 minutes ago, Surtensoita said:

Hello,

I was trying to run DynDOLOD 3 in order for it to generate some Seasons of Skyrim LODs in order to test it out before I do some more work on my mod list.

I downloaded the Alpha-88 version of DynDOLOD 3.00, with the Alpha-24 resources. I was able to run TexGen, and have its output activated as a mod in Mod Organizer 2. The thing is, any time I run Dyndolod after that, it just closes after making my selection when it gets to this point:

imagen.thumb.png.64c810cde3995ca4e60533fa89d98807.png

The options I chose are Tamriel (Skyrim) - Skyrim.esm [Seasons], and then Medium. I've also tried with the Low option, but I get the same result. Same thing happens if I run MO2 with or without administrator mode. I have attached my load order, my modlist up until now and the two logs that generate when I run DynDOLOD.

Does anyone have any idea what might be causing this issue? If there's anything that I'm missing, please tell me and I will be happy to provide it if I can.

Thank you in advance.

loadorder.txt 1.08 kB · 0 downloads Modlist.txt 2.31 kB · 0 downloads DynDOLOD_SSE_Dynamic_LOD.txt 25.76 kB · 0 downloads DynDOLOD_SSE_Object_LOD.txt 413.16 kB · 0 downloads

See the first post of the DynDOLOD 3 Alpha thread where to make posts. I moved your post to the thread.

See  the first post which log, debug and bugreport.txt to upload when making post. If none of them exist because the OS, antivir or whatever just killed the program, check the Windows event log for related messages and post that.

Set realtimelog=1 in ..\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini and try again. Upload the log from the logs folder.

Make sure the hardware (CPU, memory in particular), BIOS setting, OS etc. are stable.

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.