Jump to content

z929669

Administrator
 View Profile  See their activity

  • Posts

    12,588

  • Joined

  • Last visited

5 Followers

About z929669

Contact Methods

Profile Information

  • Preferred Pronoun
    He/Him/His/Himself
  • Location
    Nebraska, USA
  • Favorite Mod(s)
    Requiem

Recent Profile Visitors

6,536 profile views

z929669's Achievements

Akatosh

Akatosh (12/12)

0

Reputation

59

Community Answers

  1. z929669
    Apologies, I should have read the OP more carefully. Defaults in instanced for me, and it works without issue. Assuming that when "uninstalled and reinstalled Skyrim", the game directory is totally clean of any third-party binaries and the like. Since this is specific to SSE/MO and other games run fine though MO, it has to be something associated with the SSE MO profile, SSE itself, or the SSE registry settings. Running via the Steam Launcher should properly set the registry. It might be a good idea to verify the game files via Steam and re-launch via Steam just to satisfy any lingering OCD. The only thing in the posted MO log I see that stands out is that there is no profile set, so it's reverting to default. Maybe set a profile, and tick all three boxes for profile specific * and auto archive invalidation. This is a shot in the dark. Can MO be configured to produce a more verbose log? I would also examine files under \Documents\My Games\Skyrim Special Edition.
  2. z929669
    Sheson actually is able to read crash logs, so I think he could help you finally succeed if you follow through on that topic. Just sayin'. ... anyway, I'm off topic here. Sorry.
  3. z929669
    I Just checked the location and see what you mean now. COC bloodskalbarrowexterior01 and then move a few feet to the right. But it only happens from inside that cell, just moving a few feet resolves. I don't think it's worth dropping WTT, personally. Have you reported this on the xLODGen support topic? Also, you should probably finish up with your CTD troubleshooting before moving on to this one
  4. z929669
    Wouldn'tsomething like this also work?
  5. z929669
    "seems to be a bug" doesn't sound like a good reason to disable this mod. First, verify that there is a bug that you cannot live withn (validate that the bug exists and under what conditions if any). Otherwise, you are going off in your own direction and setting up a cascade of potential issues, given you are troubleshooting your long-standing CTDs with sheson, and I don't believe you have come to any definitive resolution with that. I think it's too soon to begin deviating and muddying the waters with more variables.
  6. z929669
    Just throwing in my 2 cents here (ultimately, follow GSDFan's advice)... The default Base Dir Path for instances is %LOCALAPPDATA%\ModOrganizer\{instanceName} The advantage here is that your Windows user profile has full access/privileges under this path, since it exists under %USERPROFILE%. This circumvents any potential security restrictions (like UAC issues). The root of C:\ could be problematic if the OS is installed on C:\. The root of any other drive should be fine, but you probably don't have explicit, user-based privileges there. You might need to mess with advanced security settings under paths outside of %USERPROFILE%. Step's advice is to use MO Instances and their default paths. It "just works".
  7. z929669
    We haven't bothered adding that one because it really doesn't matter. BethINI will find your config files either way. If you want certain settings different in a given profile, then you would tick profile-specific INIs. Same goes for save games. I don't think auto archive invalidation matters either way, because BethINI takes care of it, I think. I believe if you tick that one, it adds more data to SkyrimCuston.ini, which I don't like, so I leave it unticked. You can always toggle these options in the profile settings after you install MO.
  8. z929669
    Yes, I know what you mean. Thanks
  9. z929669
    Without the required logs, it's all just shooting in the dark, but your DynDOLOD installation path or %USERPROFILE% path likely include unsupported characters or are too deep. It could also mean that the version of textures\cubemaps\ShinyBright_e.dds is problematic. It could also be an issue with the output file format you have chosen (or the input file format). Check which mod is providing this texture and see if replacing it or hiding it resolves. That error code is a general error.
  10. z929669
    The Step Skyrim SE 2.3 guide requires the Anniversary Upgrade. There is no other version of the guide. SSE 1.6.1170 is NOT the Anniversary Upgrade. It's the latest version of the game, Anniversary Edition (AE). The top of the guide says exactly what you need to use the guide. It even provides a link to the AU. The SSG provides instructions for SSE that only make sense if you have the AU. The Step Patches don't need to be 'fixed'. They require the AU. The guide, in turn, requires all of the patches. If you don't want to run the AU, then the guide and patches won't explicitly apply. Just get the AU and you will be sorted.
  11. z929669
    Drive is fine, but from the guidelines: ...using text sharing services...
  12. z929669
    See the forum guidelines for tips on third-party file-sharing services. Use zip or 7z to archive the files first.
  13. z929669
    You can save your 'good' TexGen and DynDOLOD output by moving them into a different path. Then delete (or move/archive) all content under DynDOLOD\Logs, and regenerate TexGen and DynDOLOD NG output. Then see if you get a new crashlog to go with that. The logs are important for troubleshooting.
  14. z929669
    You didn't provide the DynDOLOD debug log, which provides key information required to understand the issue. Just guessing from the crash log, I suspect that you are not executing the application as expected. Install DynDOLOD by extracting it into an empty folder on your drive. Delete any previous DynDOLOD install first. Do not install the DynDOLOD application as a mod. After you ensure the application is installed correctly, carefully read how to set up the executable and run DynDOLOD.
  15. z929669
    Because NG includes the LR Workaround and theoretically better results. It's simpler to use as well.
×
×
  • Create New...

Important Information

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

  I accept