Jump to content

Glow

Watcher
  • Posts

    3
  • Joined

  • Last visited

Everything posted by Glow

  1. Turns out Mod Organizer was pointing to Appdata Local despite me telling it to install in Games, which I think is the most likely cause. Moved it over, unfortunately deleting the load order in the process, but I'll fix that tomorrow after some sleep. Should hopefully let TexGen work without issue. Thanks for the help!
  2. No, it did not show anything on the output; I've only closed it each time I've tried because it says it has generated successfully. And sorry, I meant through Virus and Threat Protection; I had a read up and saw that was the most common issue with this so attempted that first. Edit: upon looking, my Skyrim does not appear to have an architecture folder in textures. I had a look at another thread which seemed to be relevant to the issue and I'm going to try running TexGen again with the tweaks to the ini.
  3. Hi there, I'm using DynDOLOD 3.0 alpha 62, and I'm coming up with an issue; after successfully generating (as far as I can tell, considering there's 227MB in the folder) textures and billboards through TexGenx64, DynDOLODx64 is telling me it can't detect TexGen output. I've granted both DynDOLOD (the program) and all involved folders access through firewall, and I've got the Texgen_Output folder moved and checkmarked in Mod Organizer 2.4.4. I've tried turning the firewall off entirely, and DynDOLOD has run happily in the past using the same method, just not the 3.0 version. I'm using NGIO-generated grass cache, if that is relevant. Here are the logs from the TexGenx64 output, the start & end of the debug log (the full log being too large to attach) and DynDOLODx64 attempts to run. Thanks for the help! TexnGen_SSE_Debug_log (start and end).txt TexGen_SSE_log.txt DynDOLOD_SSE_Debug_log.txt DynDOLOD_SSE_log.txt
×
×
  • Create New...

Important Information

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