Jump to content

rileymil

Citizen
  • Posts

    6
  • Joined

  • Last visited

Everything posted by rileymil

  1. Hello, I am getting an error I have never seen before upon regenerating LOD, it is just failing and saying to "fix the error" but not telling me what the error is. The link goes to the Unresolved Form ID page but I am seeing no errors like that in the log, so I don't know where to start. Here is my modlist, load order, attached is a screenshot of the error not telling me the source, and here is my realtime log from the failed generation. Do I just load up my whole modlist into xEdit and check for FormID errors?
  2. So after an hour and a half (lol) generation was successful with 1. no BSheartland worldspace checked, 2. RealTimeLogs=1 (checked periodically) and 3. an update to Microsoft Visual Studio! With that successful, can I now just run DynDOLOD again with only BSHeardland checked, change the name of the necessary output files (heartland esps, and then add the textures/meshes/skse folder to my Tamriel DynDOLOD folder)? Or do I now need to run it with everything checked at once for everywhere to work? I can leave it overnight and see how it does in a few hours if that is the case, but I would prefer the former option if that is a thing. Hope I'm making sense, been a few more hours at this than I was expecting.
  3. https://ufile.io/43rghcdx https://ufile.io/dp7vn940 Here are the full logs, sorry figured it would be easier for you to not have a few thousand lines to go through!
  4. Awesome gonna try that setting and run it without the Bruma worldspace as well. In the meantime here are my logs if that would help or interest you pertaining to this issue. Also restarted my computer before that second attempt, the same thing happened so I assume its not any leftover TexGen or other processes. Debug Log https://paste.ee/p/qiO4L Log https://paste.ee/p/3FjAp
  5. Really was hoping to not have to post but I'm at a loss here. Just regenerating my LOD for a new trees plugin/new mods and the DynDOLOD process keeps getting stuck 45 minutes into generation with no errors to be seen, it just kinda dies. See attached screenshot, it completes all the object LODGen.exe popups and then once the final window closes, DynDOLOD just doesn't update or generate the .esp/occlusion data. Just sits like this, not updating the time elapsed or anything. I also included folder information/current time/task manager useage to try to provide as much info as I can. Immediately after the exe's finished Taking Your Firstborn was at about 1,600 MB and since has dropped dramatically and is just staying around 436 MB. After about 30 minutes of non responsiveness I really don't know if it's just "taking a long time" or something is wrong, as I have never had problems with the LOD gen process like this before. Quick update, now, 45 minute after the exe's finished, memory usage has dropped to about 15 MB. I assume this means the process is not gonna complete and I have literally no idea what's going on to cause it to not.
  6. Hey all, So I have recently been finishing up my modlist (just upgraded to SE) and I am working on getting LOD generated. At the moment I have grass cache successfully generated and am trying to move on to TexGen. Unfortunately it seems I am running into a little problem. I’m on DynDOLOD 3 Alpha 100 (SSE 1.5.97) which it seems has a new method for enabling grass gen (as enableGrass=1 and such in the .ini is now outdated). I guess I am just confused, I have enabled Expert Mode yet my TexGen Grass billboards option is still greyed out. The HD grass option is not a replacer for the normal grass option as well, I assume, so both being checked is necessary. I’m thinking this is a little thing I am overlooking/misunderstanding but after 12 hours digging through outdated guides and the DynDOLOD site I figured I would ask here for some insight. Hope that made sense, I can post files configs or whatever you may need so let me know!
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.