Jump to content

z929669

Administrator
  • Posts

    13,028
  • Joined

  • Last visited

Everything posted by z929669

  1. Moved into the SSE Q&A forum, since this is a question about SSE and may have a "best answer" for posterity.
  2. Moved post to the mod topic that exists. See the OP.
  3. 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.
  4. Moved to the relevant FO4 mod forum.
  5. 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.
  6. Depends on your AV and Windows Security. Google has the answers.
  7. 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.
  8. No worries BD. We'll miss you and hope for a speedy return to normalcy in your world
  9. 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 :/
  10. 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
  11. "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".
  12. 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.
  13. 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).
  14. Wrong forum for this. Moved into the correct forum. Also, you should use a spoiler for long lists like this.
  15. All I see here is a brightness difference. Are you certain that you didn't change LOD32 gamma?
  16. 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.
  17. 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:
  18. THat's great. Been waiting for this one to update finally.
  19. Makes sense then. We can drop from testing to narrow the scope a teeny bit.
  20. BEES is necessary for game runtime versions 1.5.97-1.6.640 but not for the current version (1.6.1170). It's a hard requirement to have this mod installed if you are using mods with the new plugin format. It has nothing to do with DynDOLOD. See the BEES Nexus Description for more info.
  21. I'm guessing you are using the Milk Drinker Step ENB then?
  22. You can try editing these two values to be '2' in enbseries.ini of the game directory. [COMPLEXPARTICLELIGHTS] NormalMappingShadowsQuality=1 ShadowQuality=0
  23. Double click the 7z line so that 7-zip is listed under the two columns, click [Apply].
  24. If the Step guide was followed (assumed by the OP), then there should be no parallax compatibility issues.
  25. So you need to install the correct versions of all software/mods to correspond with whatever game version you are running. You environment is a factor as well, so this is really a question about meeting the requirements of DynDOLOD + DynDOLOD DLL NG and is hereby redirected to DynDOLOD support where you will get links to suggested reading. Providing your logs will convey a lot about your environment, so take a look at the logs needed (and requirements) in the DynDOLOD Alpha OP. Also, read all text on the official requirements.
×
×
  • Create New...

Important Information

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