Jump to content

notcyf

Citizen
  • Posts

    34
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by notcyf

  1. Sorry for necro'ing this, but I found this while googling about NPC's randomly dying (I have the same issue) and thought of another idea. it might be a horrible idea, or not. If you don't care about NPC's not taking fall damage, couldn't you edit fJumpFallHeightMinNPC to something really high to see if it is caused by fall damage? I'm considering doing this in a plugin, but I wonder if there's anything I could break doing this? Can't really think of anything that has NPC's fall to death in a scripted way. I think the issue has to do with the infamous "loading falling" that maybe not only apply to mammoths, but could happen to all NPC's in the distance/away from vision?
  2. I don't use it. I just assumed it was possible. Did it one-by-one too, but figured it was possible to multi-select. Maybe a feature request for LOOT?
  3. That's what I did and suggested doing in LOOT in a previous post. Open LOOT->Select all UHDAP plugins->Right Click->Change Group->Creation Club->Save How I figured this out was by just checking the comment in the UHDAP comments section on NexusMods. I was checking whether the guide would suggest doing this too, but it doesn't. It's a fairly simple step and doesn't require some insane knowledge, so I think putting it in the guide instead of removing the mod is a better idea. I really don't think UHDAP will ever be removed and it's (in my own opinion) what we call "a storm in a glass of water" by the LOOT team. But having the mod load after USSEP is just a no-no. It's going to cause wrong sound files to play on a lot of characters and dialogue. USSEP fixes many of these wrong audio files by just replacing the audio files with the correct audio.
  4. UHDAP really does noticeably, even to the average listener (and that's the important part) improve the overall sound quality of the audio cache. It's also not just some PS4 rip, they've all been edited and remastered by the modder. As long as UHDAP exists on NexusMods (they're quite strict) and hasn't received a takedown (I don't think it ever will) I wouldn't remove it from the modlist. But it does need to load right after CC content and be overwritten by any other mod.
  5. Are you sure you don't have any user/custom metadata on those plugins? If I undo the custom metadata it goes back to loading after all ESM's.
  6. I guess those plugins are just placed randomly somewhere random in your load order because they have no masterlist entry, because for me they're loaded after USSEP, without any custom metadata: Manually putting them in the Creation Club group places them correctly on top of the load order:
  7. Hi. From what I know is that USSEP must run *after* UHDAP by putting UHDAP manually under CC content in LOOT. (Making sure UHDAP loads as early as possible so that all other mods overwrite its .bsa contents) This must be done because the LOOT team decided UHDAP is a legal grey area and removed all LOOT masterlist entries of that mod. This makes it so LOOT heuristics places it after USSEP. The reason USSEP must run after UHDAP is because otherwise UHDAP will undo most (if not all) audio cache fixes done by USSEP. This is because now UHDAP's .bsa contents take priority over USSEP's .bsa contents. A very good example is Sven saying some gibberish about his master. Fixed in USSEP, undone by UHDAP. See: https://github.com/loot/skyrimse/issues/785 TL;DR Put UHDAP as early as possible in your load order, right after CC content.
  8. The mod install instruction that shows the installation doesn't show it as ticked, where other mod instructions show default options as ticked in the instruction, so I wasn't sure whether this was intentional or left out mistakenly.
  9. Question: With Embers XD, do I also untick the Survival Mode patch? Won't use Survival Mode anyway, but is it necessary for the STEP CR patch?
  10. Is it now safe to use the STEP guide with the newest game version?
  11. This twitching plates bug will on google lead you to "capping your framerate at 60fps" but in reality, it always happens. My game is running at 60fps, locked and vsynced using the ingame vsync, and I still have the issue. The twitching only seems to occur when there's something on the plates. The objects keep colliding with each other causing them to constantly vibrate each other. The only way to temporarily fix it is by moving one of the items up and down manually, so that this cycle of the two objects moving each other stops. The collision issues can never be fixed unless someone very talented can replace the physics engine implementation with something more precise and less buggy. The way Havok is implemented is the reason physics will always be somewhat borked in this game. Remember that Skyrim is a very old game now.
  12. There's sadly the case of Nexus requiring consent by the original author (even if these are edited vanilla scripts, so copyright doesn't really apply, but it's Nexus etiquette) :/
  13. The Follower Trap Safety mod overrides a fix by USSEP that causes actors (or other objectref) that triggered the traps to persist in memory because of the lastTriggerRef attribute in the TrapTriggerBase.pex script. https://afktrack.afkmods.com/index.php?a=issues&i=28300 Any actor that uses this script that set off a trap never gets unloaded. The fix makes it so that when the cell is unloaded, the ref is set to None, so that actors no longer persist for no reason. @insaneplumber over at NexusMods recompiled the script with the fix included over here: https://drive.google.com/file/d/1xqBaT3trsrAcpYA-ErKoqaedNUFcsnbO/view https://forums.nexusmods.com/index.php?/topic/5019240-follower-trap-safety/page-6#entry84462058 This should be added to the guide ASAP as it will potentially reduce memory usage. You don't really need the main mod but for credit reasons people should install the main file and then override the other files. I don't think the mod author is active anymore to update his file.
  14. It really seems to depend on how their faces are lighted too. That mod imo makes their faces look way too "High Fantasy/JRPG"-like, Skyrim is nowhere near that in terms of art style. You could always try putting the default skyrim SE textures into an upscaler, maybe that makes their vanilla faces look better, without deviating from art style.
  15. For me, Update.esm is definitely backed up and put in the xEdit output folder as Update.esm.XXXXXXXXX(time/date of backup). From what I understood, we put the Cleaned masters in a separate mod, and then take the backed up Update/DG/HF/DB.esm, rename it back to original, so that when you verify integrity, Steam won't overwrite the cleaned masters. To be honest, it's probably easiest to just take the cleaned esm files out into Cleaned Vanilla Masters and then just verify integrity to redownload original files, but for some people that isn't an option.
  16. It seems that enabling/disabling indeed doesn't really do much. It really depends on the lighting. The wrinkles are way too subtle, even without the tintmasks. It must be a generic record that lots of elder NPC's use because the NPC's themselves aren't being altered by anything except AI Overhaul (which only adds some AI Packages and inherited an USSEP change) and USSEP. I'm poking around in SSEEdit right now to see if there are any references to other edited records in Hilde's records that more Elders are using.
  17. It's strange since I use the recommended FOMOD instructions. Like I said, I even reinstalled the mod to see if I accidentally chose the wrong option, but that's not the case here. The mod is also in the right position I believe. The CSV export in the OP should confirm that (copy paste it in Excel/Google Spreadsheets to make it more readable). But just to make sure I didn't install any of the lower mods wrong: These are the only file conflicts the mod has, this is hopefully correct right? Because I don't see which other mod could potentially overwrite the femaleoldhead textures. It's just a little strange, because this seems like it's not a really easy oversight. This mod makes all the female NPC's which use "/femaleold/femalehead_msn.dds" have rather young faces. I tested this out by starting a new save and spawning a bunch of female Elders (player.placeatme) in: https://en.uesp.net/wiki/Skyrim:Elder
  18. Perfect, thank you! Although we kind of steered away from the topic, this was all some good information! Maybe it's a good idea to make a new topic in the Step guide forum with instructions and add a note to it somewhere in the guide. Or maybe make a new wiki page with the instructions and add a link to it somewhere in the guide? And maybe it's a good idea to split the widescreen fix part of this topic into a new topic, since this is no longer about INI editing
  19. I fixed the issue: It's indeed the Tempered Skin Female mod. The way to fix this is doing this: The femalehead texture is the culprit, but I reckon the body should also be disabled in this case (for consistency). I kinda like the result. Hiding these 2 files makes Hilde look older again:
  20. I tried reinstalling Consistent Older People and Tempered Skins for Females, using the Step FOMOD instructions but neither did anything
  21. The only thing that seems to alter her is USSEP and AI Overhaul. So it's not a plugin, but a general texture causing trouble.
  22. Wow thank you! This is actually neat! I think I can just merge the Widescreen fixes into the relevant mods in MO2 right? I was afraid that i needed more than just the Widescreen fix, and you just gave me everything needed!
  23. I just started my playthrough using the STEP guide (full guide), and for some reason Hilde looks really young: Did I do something wrong with the guide? I have no custom mods, just followed the guide exactly with all recommended options, hidden files and FOMOD installer options. MO2 CSV export:
  24. The thing I'm trying to do is make sure the game is rendering at 16:9 with black borders, but without using Fullscreen exclusive mode. I don't know if that is possible, but using borderless at 16:9 (using BorderlessUpscale=false) will cause the taskbar to stay in the screen, with BorderlessUpsacale=true, the game acts like it's fullscreen and removes the taskbar, but makes the game stretched and ugly. Using 2560x1080 causes SkyUI to clip out of the screen, and make it unusable, so 21:9 just isn't an option. My only option might be to just completely change the monitor resolution to 1920x1080, but if there is any other way, your help would be truly appreciated! Maybe there's a way to force rendering of black borders, even in borderless windowed? And quite off topic, but 21:9 isn't as uncommon as it used to be anymore. It takes about 2.5% of the gaming market. That's 2 to the 3 people per 100 people. This number used to be much much lower(https://store.steampowered.com/hwsurvey/).
  25. I followed the recommendations fully, with some th I followed the entire guide word to word, this was my only issue. But thank you, that mod seems to be the one overwriting the fullscreen settings. A suggestion would be to add a guide to make SkyUI work on 21:9 displays, because I could use https://www.nexusmods.com/skyrimspecialedition/mods/1778 but I don't know if it would be incompatible with the STEP guide. Thank you though guys. Maybe it's an idea to add a warning for people with 21:9 displays that it will cause UI issues on the current guide Also I think you meant Borderless=false
×
×
  • Create New...

Important Information

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