Jump to content

Recommended Posts

Posted
  On 4/14/2022 at 9:08 PM, 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.

Expand  

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
  On 4/15/2022 at 8:13 AM, 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!

Expand  

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
  On 4/15/2022 at 7:44 AM, 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.

Expand  

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
  On 4/15/2022 at 4:54 PM, 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

Expand  

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)
  On 4/15/2022 at 5:03 PM, 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.

Expand  

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
  On 4/15/2022 at 5:23 PM, 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?

Expand  

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

Hopefully that writes the needed info to the log file.

Posted
  On 4/15/2022 at 5:35 PM, sheson said:

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

Hopefully that writes the needed info to the log file.

Expand  

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.

 

  Reveal hidden contents

event.evtxFetching info... event2.evtxFetching info...

Posted
  On 4/15/2022 at 6:06 PM, 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.

 

 

  Reveal hidden contents

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

Expand  

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.txtFetching info... Modlist.txtFetching info... DynDOLOD_SSE_Dynamic_LOD.txtFetching info... DynDOLOD_SSE_Object_LOD.txtFetching info...

Posted
  On 4/15/2022 at 7:03 PM, 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

Expand  

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.