Jump to content

z929669

Administrator
 View Profile  See their activity

  • Posts

    11,672

  • Joined

  • Last visited

2 Followers

Contact Methods

Profile Information

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

Recent Profile Visitors

5,514 profile views

z929669's Achievements

Akatosh

Akatosh (12/12)

0

Reputation

59

Community Answers

  1. z929669
    You need to add all third-party EXEs to exclusions if they are being quarantined by your AV as mentioned previously. If you use your own custom AV and also Windows Security, then you must do so in both. Once that's done, you may need to reinstall xEdit and any other tools with EXEs your AV quarantined. Read the SSG to understand how these tools should be installed and configured.
  2. z929669
    Moved to the relevant FO4 mod forum.
  3. z929669
    Latest version resolves the FOMOD issue with Vortex. I also updated the Description with some new info, mesh rule recommendations, and to omit some dated information.
  4. z929669
    Depends on your AV and Windows Security. Google has the answers.
  5. z929669
    This is your antivirus probably deleting them. You need to list the xEdit executables, including TexGen, DynDOLOD, LODGen, etc. as 'authorized' or 'exceptions' in your AV. Always use the x64 versions if you use 64-bit architecture (most do now). List all the EXE files in xEdit and DynDOLOD.
  6. z929669
    No worries BD. We'll miss you and hope for a speedy return to normalcy in your world
  7. z929669
    Go for it. I will add it next update. I commented on Nexus Posts RE Vortex. Vortex seems to have overly strict FOMOD XML requirements that expect n/a tags. Really dumb that we must do this to make that application happy for evidently no reason at all :/
  8. z929669
    Mod updated: Changelog Version 2.36.2 Updated LOD models for treeaspen04, treeaspen05, and treeaspen06, since the corresponding full models were changed in AA 2.36 Updated FOMOD
  9. z929669
    "They are gone" ... xEdit executables or your mods? Either way, follow Step 1 and Step 2 of the Step SSE guide. Make sure to click/open all spoilers for detailed instructions. Carefully read the SSG and "Tools Setup".
  10. z929669
    Our System Setup Guide goes into some detail about setting up G-SYNC and Freesync as well as monitor calibration. Your GPU and monitor work together to utilize G-SYNC/Freesync. The game doesn't know anything about it. As a result, Vsync and frame caps are unnecessary.
  11. z929669
    You completed the first troubleshooting step by disabling mods to confirm it's a mod or combination of mods causing this issue. Unfortunately, I'm not familiar with many of your mods. Next step is to reenable all mods you know don't alter NPCs to confirm the same using a new game (with ASLAL this time). Then enable half of your NPC mods, test, enable the other half, test, etc (sorting with LOOT each time you reenable a block of mods). Do this until you isolate the culprit(s).
  12. z929669
    Wrong forum for this. Moved into the correct forum. Also, you should use a spoiler for long lists like this.
  13. z929669
    All I see here is a brightness difference. Are you certain that you didn't change LOD32 gamma?
  14. z929669
    We recommend installing LOOT from the 7z archive rather than the Win EXE: Just move the files from the archive into your LOOT install location. LOOT doesn't integrate files into Windows or the Win registry that I know of, so uninstalling it via the EXE isn't necessary, AFAIK. Windows should give you the option to remove the LOOT installer if it isn't working.
  15. z929669
    DDDM has a FOMOD option for reskinning the UIExtensions wheel menu. I simply included this to test this one feature. From the DDDM FOMOD "Wheel Menu Replacer" section:
×
×
  • Create New...

Important Information

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

  I accept