Jump to content

Wolfpack49

Citizen
  • Posts

    34
  • Joined

  • Last visited

Recent Profile Visitors

372 profile views

Wolfpack49's Achievements

Noble

Noble (3/12)

0

Reputation

  1. Thanks Sheson -- rebooting and clearing out the old log files did the trick. It did take awhile to get to the AUT step, but I could see the SUM and SPR windows processing from the taskbar, and it completed in just a couple hours. LOL! Thanks again.
  2. HI all, I've been running the latest Lodgen (118) and Dyndolod (180) and both Lodgen and Texgen ran fine, but I am getting a hang when running Dyndolod at the following line: Waiting for LODGenx64Win.exe generating object LOD for Tamriel AUT. Dyndolod_logs.zip DynDOLOD_settings..zip I thought it might be due to running seasons, but I let it run overnight and it didn't progress past this line. I do have Open Cities and this run is for the first pass with OCS disabled. Thanks for any suggestions and all the effort over the years on Dyndolod!
  3. Okay, removed the line, rebooted and successfully run! I really do think some nvidia services weren't running because it ran much more quickly this time.
  4. Hmm, okay, I got another error message, but this time different, and I think maybe because of the LockTexconv=1 setting. Try again without the line?
  5. I will give that a try. I did try the command prompt as Admin and got the below; when I look at the path, I do see that there is no /DynDOLOD_SSE directory in /Temp, but maybe that's only created at Dyndolod runtime? I'm also going to simply try rebooting -- maybe the nvidia services aren't starting properly?
  6. Hmm, interesting -- attached is the bugreport.txt file. Would setting to LODGenThreadSplit=0 in DynDOLOD_SSE.ini possibly help? I do notice it's taking quite a few cycles. i haven't run into access issues previously, but running seasons is certainly adding to the runtime load. I did recently update nvidia drivers so perhaps that's a concern. Looking at DirectCompute now... bugreport.txt
  7. Getting an error when running Dyndolod with alpha 73. I didn't get a bug report or crash log after Exiting Dyndolod. DynDOLOD_SSE_log.txt
  8. Alpha 72 TexGen just completed with no errors. On to DynDOLOD...
  9. I seem to be getting a Texconv error with alpha-71. Double checked and re-downloaded and reinstalled the Win C++ redistributable, but still occuring. Error message below: Logs attached: TexGen_SSE_Debug_log.txt TexGen_SSE_log.txt
  10. I see what happened. I had brought over the Presets folder from the previous alpha. Removing the folder allowed TexGen to run.
  11. This is the message received when clicking the Start button. Here is the copied text: [Window Title] TexGen [Main Instruction] Exit TexGen, check log or restart? [Exit TexGen] [Check log] [Restart] [Footer] DynDOLOD FAQ | Support Forum | Copy message to clipboard The Dyndolod Standalone is is out of all special folders: E:\Skyrim Tools\DynDOLOD_300_A39\
  12. Hmm, well I am probably doing something dumb, but Alpha 39 is the first time I have received an Exit message from TexGen without any reason in the popup box. See: Below is my debug log for TexGen: https://1drv.ms/t/s!Ar9_fJKmnT2Kh9xwu2wyAur5P0UV8A?e=FytthG I checked that occulsion.esp was removed and that my old Texgen and Dyndolod outputs were removed. Using the latest resource file (Alpha-11 and latest MM 3.0 lodpack). Grass cache is present in /data/grass/. No billboards being used. Could there be something else that needs to be present or disabled?
  13. Sounds like something that should be taken up with T4gtr34um3r.
  14. Yep, good point and will do.
  15. Hi Sheson, Just a question on the referenced Majestic Mountain LODs for Alpha 35. Is the referenced 7z on the first post here more recent than the latest MM LOD version on the Nexus (v1.2)?
×
×
  • Create New...

Important Information

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