Jump to content

z929669

Administrator
 View Profile  See their activity

  • Posts

    13,086

  • Joined

  • Last visited

 Content Type 

Everything posted by z929669

  1. z929669
    Why do you want to merge these? It's unnecessary. Just install them as the guide instructs. If you merge them, then you constrain your entire setup to many of the Post-Processing AND Lighting and Weather mods. There is no thread on this, because it's not useful to merge these patches unless you are reaching the plugin limit ... in which case, you are doing something unsupported anyway.
  2. z929669
    It's not a master, but some of it's changes are included in the Step Patch. E.g., torch weight/value.
  3. z929669
    I agree and would opt for the version linked with MIT license on Nexus.
  4. z929669
    Looks like it may be a Win 11 issue with runtime requirements. If it was working previously without those mods, then it's obviously a mod though. Does a new game work without those added mods or does it CTD at some point?
  5. z929669
    See the MO command arguments for xLODgen in this table. I assume you are running for SSE, but other arguments exist for other games. You can also rename the EXE file itself, but this works for setting the proper game and launching the program via MO.
  6. z929669
    Try running the game launcher via Steam to initialize per Step 2 instructions first. Also be sure to configure your env per the System Setup Guide (Step 1)
  7. z929669
    Install crash logger from nexus and follow it's instructions for finding logs after a crash. Then perform your steps, which seem reasonable. I would do both #2 and #1 before trying to reproduce the CTD. You also may want to check that you have installed all 02-Extender mods correctly as well as certain 09-Fixes mods. Basically, anything related to SKSE.
  8. z929669
    Obscure undiscovered (location) in the map and/or on the HUD. No explanation necessary?
  9. z929669
    Marked as accepted for 2.1.0. We may yet modify the L/W patch and screenshots for this mod, but we seem to have admin and user consensus to make the switch next release.
  10. z929669
    This is a big change, but we have approval of > 2 admin and several users to swap this mod out for Ambiance (follow link for details). Marked as dropped as of 2.1.0
  11. z929669
    You can also set the game path in the registry by launching the game via Steam and quitting without clicking 'Play' or whatever it is in the launcher menu.
  12. z929669
    Yes, I will create that one and place into testing. Permissions on this mod are in question, so waiting for a reply before i link to it. It's also available from another source, but I prefer using nexus if it pans out. TBD.
  13. z929669
    It's just a game-engine GFX limitation, and ENB accentuates it. It can be limited by reducing certain fog settings, but that is at the expense of other visuals. As I said, the next ENB update will largely eliminate this issue.
  14. z929669
    I use separators rather than categories, but both work.
  15. z929669
    Same. I place xEdit Output early in my LO and temporary stuff late.
  16. z929669
    Got it. Yeah, I would go after the Image Space editor Ids with 'default' string by reducing the saturation to 0 and then try others until what you want is affected. I don't recall seeing one with 'menu' but there could be one with 'ui'. Once you find it, I would play with brightness/contrast and the two bloom settings.
  17. z929669
    You could get a screen of the part you want to alter. I am not clear on what aspect of the "Main Menu" you mean. Text? Images on loading screens? You should be able to capture a screen of anything on your monitor with the xbox gamebar (installed by default on Windows). Access this using windows key + G Capture screen using Windows key + Alt + PrtScn Images are saved by default in ..\Videos\Captures I know it's an Image Space record as you say, because lighting mods impact this. I believe it's the same record that affects the character setup screen. Maybe the 'default' Image Space (there is an editorID with a name like this ... look under Skyrim.esm and Updateesm in xEdit, change to some outlandish value(s), and test in game to check. Obviously, forward to a custon ESP in xEdit.).
  18. z929669
    Thanks. I will address this.
  19. z929669
    Screens updated (linked from OP) After looking more closely at Ambiance and the vanilla screens, I now see that Ambiance is actually enhancing shadows where they exist in the game (vanilla). This was done specifically with stealth gameplay in mind as possibly a way to assist the player in finding true vanilla shadows ("hide here") ... note the increased shadow depth of Ambiance in the interior screens. The mod description on Nexus also goes into some detail on this. The RAID MA also suggests this being the case in terms of true vanilla shadows. Night, certain weather and lighting mods and mods like EVLaS all can accentuate or even add shadows where they don't exist in the vanilla game to begin with (e.g., EVLaS in exteriors). These look like shadows, but the game doesn't interpret them as shadows, so this breaks sneaking realism, particularly outdoors. I believe Ambiance mitigates this indoors --and to some extent in exteriors ... and mods like Luminosity explicitly break this indoors. And the 'sun' lighting DY likes in Blackreach seems to be Luminosity now that we have the vanilla reference. Amazing what we can discover by having the vanilla reference ... this is why we always need a vanilla reference!
  20. z929669
    Once you downgrade, just be sure to strip out any foreign DLLs or other stuff the downgrade patcher leaves behind. then copy this to the adjacent * - SSE folder as described and let Steam validate against the original downgrade copy to give you your AE instance. Steam's manifest file will tell Steam you are all good even if you change the folder names. Just prevent Steam from auto updating while on the 1.5.xx instance. See this post (note links in the footer of the OP):
  21. z929669
    Yes, that's how I do it. Then all tools, including Steam just treat it as usual. You just need to remember to set your BethINI and MO configs to point to the correct MO profile before modding either one after the rename
  22. z929669
    I think it is related to the esoteric "EVLaS-ENB bug", but nobody seems to know for certain. Apparently, Boris is somewhat aware of the bug, but I don't know if this is a manifestation of said bug.
  23. z929669
    All I did was to copy my entire 1.5.97 "Skyrim Special Edition" Steam folder into "Skyrim Special Edition - SSE" adjacent to the original in Steam path. Then on 11/11/2021, Steam updated the original and left my 1.5.97 alone. All I need to do is rename "Skyrim Special Edition" to "Skyrim Special Edition - SAE" and "Skyrim Special Edition - SSE" back to "Skyrim Special Edition". Steam and all modding tools do not know the difference and work without any config changes outside of my having to switch to a compatible MO instance between the two and turning off Steam auto-updates. You can essentially do the same thing once you downgrade. I was proactive though and never had to fiddle with the downgrade tool
  24. z929669
    For Blackreach, I prefer the "Ambiance colors, CW fog distance & image spaces" patching method, as it gives the best result, IMO. I venture to guess that vanilla lighting will be very similar to Ambiance, so more orange than pink halo, which is apparently CW. However, that is easy to change in the patch, so I will have a look. Vanilla compares coming later this evening. I also want to 'fix' exterior flames in fires, braziers, and torches, so hopefully will track that down as well.
  25. z929669
    Indeed. The approach and mod lists are like 80% identical I would say.
×
×
  • Create New...

Important Information

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

  I accept