Jump to content

Algabar

Premium Member
  • Posts

    1494
  • Joined

  • Last visited

Everything posted by Algabar

  1. TBH, I'm not absolutely sure on this one. A lot of NPC data definitely gets baked into save games. This might also be the case for "essential" flags. So, NPCs in an existing save might be essential, although some mod changes their status. To get a clarification on this, I'd recommend testing with a new game. Also, a script based solution might help with already existing games. I'd try this one, although it might not be exactly what you wanted: https://www.nexusmods.com/skyrimspecialedition/mods/27985
  2. Good news first: XLodgen works for AE. No worries. It's just textures and meshes - and these haven't changed with the update to AE. That brings me to my second point: From my experience, it's rather unlikely, that Xlodgen would crash the game. If you chose extreme settings, you can definitely loose performance. But usually, Xlodgen output shouldn't make the game CTD. So, maybe the crashes come from a different mod. I'd also check for other mods you installed recently. Now to the bad news: Reverting changes done by Xlodgen is next to impossible, if the new meshes were created directly in the game directory. You woulld have to find and delete the single LOD files created by Xlodgen manually... If you simply started XLodgen and let the program run, your best bet would be to completely delete your Skyrim SE folder, reinstall the game and start over. To avoid issues like this in the future, you can specify a different output folder for XLodgen: 1. Rightclick the .exe file, choose "create shortcut" (I hope that's the correct term in English - I'm on a non English version of Windows...). 2. Once you have created the shortcut, rightclick on it. Find the "target" entry (again, hoping this is the correct English term...). By default, this entry only shows the path to SSELodgen.exe. Now you can add a command line parameter: The command for the output folder is "-o" ("o" as in "output"). After the file path, add -o:"[path to your desired output folder]". Caution: The quotation marks are needed! In my case the whole command line (which I added after the path to SSElodgen.exe) reads -o "D:\Games\Utilities\SSELODGen.93\xLODGEN\LODGenOutput". OFC, you can choose any location on your system - mine is just an example. Now save the changes to your shortcut. 3. Start XLodgen with this shortcut and let it do its work. After XLodgen is finished, zip up your output folder and install it with your mod manager. This way, you can always revert changes by simply uninstalling XLodgen output, if something goes wrong.
  3. Did you check the IHud MCM settings? AFAIK, you can turn it off completely. Or you can choose to have e.g. compass and crosshair always on. If "X" doesn't work, the key might be used by another mod. You can choose a different hotkey in the IHud MCM menu. There's also this patch to remove the IHud requirement for "Skills of the Wild": https://www.nexusmods.com/skyrimspecialedition/mods/62675
  4. Elder people are part of the game. This is by design. Some people are meant to look old - both males and females. Technically, old people in the game belong to a special "elder" race, that also (partly) has its own texture set. This mod makes elder women in the game look a bit "younger". Maybe that's something for you. Basically, it just replaces the face detailmaps for elder women. Detailmaps might indeed be a thing. Wrinkles and also complexions are applied to NPCs via detailmaps. So, if your skin mod doesn't contain its own detailmaps, in fact the Vanilla ones might be used. That's where the mod I linked above comes into play. BTW, detail maps aren't the same as "face textures". Think of them as an additional, semi-transparent layer on top of the actual face textures. If you want to have only young women in your game, you could change textures yourself: Replace the textures in Skyrim SE/data/textures/actors/character/femaleold with the ones from your skin mod. To remove "old" detailmaps completely, you could copy the "blankdetailmap.dds" from your skin mod into Skyrim SE/data/textures/actors/character/female. Replace anything named "femaleheaddetail_age[xx]" with the "blankdetailmap.dds" (meaning: copy and rename it). Regarding USSEP, I don't have a clue TBH. USSEP is basically a bug fix patch. As such, it obviously also makes changes to NPCs. It doesn't change their age or appearance though. In addition, USSEP is usually loaded at the very top of your load order, meaning it should be overwritten by almost any other mod. So, this one still remains a mistery for me. Regarding presets: Triple-check the requirements. Many presets depend on a lot of mods. You need to install all these mods, if you want the presets to look exactly like advertised. IMHO, using presets often means a lot of hassle. That's why I prefer to create my own characters...
  5. "Game files are verified" nowadays means "game updated to Skyrim 1.6.353 (this is Anniversary Edition - AE)". Some mods - including the .NEt script framework, where this log probably comes from - won't work in AE. Basically, you unintentionally updated your game without updating your mods. You have two options now: 1. Update SKSE, "Address library" and a lot of mods depending on SKSE and/or .dll files to AE. This list might help to find out, which mods need an update. 2. Downgrade your game to "SE" (1.5.97) with the "downgrade patcher".
  6. What exactly do you want to do? If you want to edit the content of the plugin, you need to select single objects or "branches" in XEdit: "Expand" the plugin's content in the left pane, click on the properties you want to delete, then rightclick and choose "remove". Somehow it seems you're trying to delete the whole plugin instead. If you really want the plugin to be gone, why not simply uninstall the mod with your mod manager? That's the "normal" way.
  7. TBH, I'm not a native speaker, so maybe that's why I missed something... But what exactly is the issue? NPCs looking "old" although they shouldn't? Player character looking "old"? You write about "broken" skin mods. So, how exactly are they "broken"? And why do you think, USSEP is the culprit? Any evidence for that? TBH, I really doubt USSEP changes skin textures or the like. I'd like to help, but we need more and clearer information.
  8. As 7531Leonidas said: Probably a patch you don't need. Nether's Follower Framework has compatibility options for some popular magic mods - among other things to to avoid "friendly fire" situations. Maybe you accidentally chose one of these options for "Elemental Magic", although you don't use the mod. Solution: Try reinstalling NFF, paying close attention to the options you choose in the FOMOD installer. This should solve the issue.
  9. First of all: 57~58 FPS is a good value for Skyrim. More than 60 FPS aren't recommended, since the game's physics engine can go haywire above 60 FPS. There are workarounds, but TBH, something near 60 FPS is perfectly fine for Skyrim. What you describe seems to be an issue with your settings. There are basically three things, that can influence your FPS: 1. The game's .ini settings. For optimal control, I'd recommend using BethINI. Make absolutely sure, that "clamped FPS" (or something like that, don't remember the exact name) is NOT checked in BethIni. Also disable the game's own Vertical Sync - it is worse than any other available option. BTW, that's exactly what "iVSyncPresentInterval=0" does - it disables the built in VSync, thereby letting ENB or your GPU driver take over. 2. Settings in ENB: The important parameters are in your enblocal.ini [ENGINE] ForceVSync=false VSyncSkipNumFrames=0 Change to "ForceVSync=true", if you want to use ENB's VSync. [LIMITER] EnableFPSLimit=true FPSLimit=60.0 This is pretty straightforward: "EnableFPSLimit" ("true" or "false") turns ENB's FPS-limiter on or off. "FPSLimit" is self-explanatory. 3. Your GPU driver settings: VSync and maximum FPS (among many other things) can also be adjusted in your GPU driver software. Recommendation: Disable VSync and everything FPS related in BethINI. Use either ENB or your GPU driver for these settings. Personally, I prefer Nvidia's VSync and ENB's limiter. But your milage may vary - find out, what works best for your system. On a side note: The "use effect" checkmark in ENB's in game GUI only toggles visual effects on and off. The "technical" settings from your enblocal.ini (like VSync and FPS limiter) stay in power though. Probably that's the reason why you get 61 FPS: With "iVSyncPresentInterval=0", you basically let ENB take over. And I assume, you got something like this in your enblocal.ini: [LIMITER] EnableFPSLimit=true FPSLimit=61.0 In fact, a lot of ENB presets contain that number. TBH, I never understood why, because 60.0 would be the "logical" value. But it's common practice to use 61 instead of 60....
  10. There's a mod specifically for books. You can choose between different fonts, among them non-cursive and almost "sans serif" ones. Maybe that's something for you? https://www.nexusmods.com/skyrimspecialedition/mods/17054 In general, I'd recommend searching the Nexus for "font". There are a lot of different ones. I really hope you can find something, that makes the game and especially the books more enjoyable.
  11. You have three options: 1. Don't use the mod in question. I don't know exactly, where this file comes from, but it should be something about "romance". 2. Look for an updated version. AFAIK, at least the most popular mods on LL were ported to SE. 3. Port the mod yourself. Depending on the mod, this can be tricky. Basically, everything that uses .dll files or heavily relies on SKSE is extremely hard to convert to SE. Refer to the guides on the internet. There are a lot of them. If you want to go that route, you also need to convert the animations. TBH, this is rather "advanced" stuff. So, unfortunately, options 1 or 2 are the most realistic.
  12. Well, there are already lots of collections - among them some, that focus on beautifying Skyrim. Just browse through the collections. In general, IMHO you need three things: - texture and mesh replacers, that fit your taste. In fact, one of the big texture overhauls alone will improve the look of the game tremendously: Noble Skyrim, Skyrim HD SE, Skyland. Choose what you like. - a weather mod you like (my recommendations would be Azurite or Obsidian, but therer are lots of nice options...) - an ENB you like (RUDY's work is always a good starting point) Especially ENB can make a huge difference.
  13. Sounds like these NPCs are flagged "essential". What you describe is the usual behaviour of "essential" NPCs, that took a "deadly" hit. Simply removing the "essential" status should help: Open the plugin file of your mod in the Creation Kit (or in SSEEdit). Under "actors" (or something like that), find your modded npc. Click trough the settings, look for the "essential" flag and remove it. That should do the trick.
  14. First of all, don't convert body meshes from LE. Only convert head parts and hair (OFC with the "head parts" setting) and replace the body .nif files with a SE body of your choice (CBBBE, 3BA, BHUNP - whatever you use otherwise). Converting LE body meshes can have unexpected results. Second, check the plugin file of your follower in SSEEdit. Have a close look at everything related to skin color, especially "QNAM texture lighting" and "Skin tone". TBH, I'm not exactly sure, what "QNAM texture lighting" really does, but the value must be identical to "Skin tone". Also, make sure that under "Skin tone", "Alpha" is set to 0 and TINV-Interpolation to 1.0000. Another critical entry is "[Neck] FemaleHead[your character's race]. It's somewhere below the other two entries I mentioned. Neck colour settings can do strange things. In doubt, set TINV-Interpolation to 0.000 - practically disabling neck colour.
  15. @Showler: Thanks for the correction. It looked so easy on my Windows system... So, something like Nexus Mod Manager might be the last ressort.
  16. IMHO, Ecotone Dual Sheath and Simple Dual Sheath are both equally "finicky" or "easy" - depending on your perspective. With both, you have to install the mod (easy) and then create left hand meshes (what some people might call "finicky"). Unfortunately, that's necessary due to the way Skyrim meshes work. And it's more or less the same with any dual sheath mod. In fact, it isn't that hard. I'm using Simple Dual Sheath myself. Works really fine. After you installed all your weapon mods, you have to run the Synthesis patcher once and install the output. That's a one time thing - unless you add new weapons.
  17. Make sure you got the right version of Engine Fixes. There's a version for SE (1.5.97) and one for AE (1.6.353). You also need to install "Part 2" (a dll plugin) manually. Check, if you installed this correctly.
  18. First of all, check your language settings in your Steam library. In theory, they shouldn't change on their own, but just to be sure... Then, check your mods. What you described sounds like you're using a mod in Russian language. If your game is partly Russian and partly English, you probably got something in Russian, that affects a lot of things. This could be something like a Russian mod making changes to characters or items, an overhaul of some kind... Something like that. You know best, what you installed and what might be the "culprit".
  19. Don't know about TKAA, since I don't use it myself. RS Children works fine with AE though - at least for me. If I remember right, there was an issue with RS Children and USSEP. Make sure you got both the latest versions of RS Children and the Unofficial Patch. This does the trick - at least in my game.
  20. I doubt this is possible with MO2 due to the way it works with its virtual file system. You might have a better chance with Vortex. Vortex really copies the installed files into your Skyrim SE folder. So, after everything is installed, you don't need to touch Vortex again. Just start the game with "SKSE64_loader.exe" from your game folder. I don't know if you really need to uninstall Vortex and what consequences this might bring. Simply ignoring it after you're done with your mod list should work though.
  21. TBH, I'm not good with crash logs. AFAIK, "EXCEPTION_ACCESS_VIOLATION" is a very common crash message, that can mean a lot of things. Maybe some testing coudl help: If the crash always occurs in the Bannered Mare, it's probably something in there, that causes it. This could be a mod changing interiors, but also some NPC or follower placed there - or a bugged quest connected with the location. Maybe it's also a problem with remnants from a now uninstalled mod, that are still baked into your save game. What you can do: 1. Test with a new game. If you CTD with a new game, too, it's very likely a mod issue. Otherwise it's probably your save game. 2. If it's a mod issue: Uninstall/disable mods, that change something about the Bannered Mare, until you finmd the culprit.
  22. Could be anything - e.g. a mod conflict or a problem with the custom UI you're obviously using. If I'm not mistaken, the dialogue is from "Alternate Start". So, I'd start there: 1. Load your complete loadorder in XEdit. Click and expand "Alternate Start Live another Life.esp". Go through the categories and check, if any records are red. That would mean, that these records are overwritten by another mod. In most cases, Alternate Start shouldn't be overwritten by anything. If that doesn't bring up soemthing useful, proceed with 2. Check everything related to UI: UI mods, but also fonts. I got a feeling that this is a UI / display issue.
  23. Windowed or fullscreen is normally controlled by your .ini settings. Maybe you changed them by accident? I'd recommend using BethINI: https://www.nexusmods.com/skyrimspecialedition/mods/4875 If I remember correctly, the setting for windowed or fullscreen mode is on the first tab.
  24. Infinite loading screen on the main menu often means, that there's a problem with SKSE, mods depending on SKSE and/or mods using .dll files. Another possible, but less common reason are severe mod conflicts or bugs. I'd focus on SKSE, SKSE dependant mods and .dll plugins first. First of all, check if all of them match your game version (SE or AE). Also check for updates. If you haven't already, also get SSE Engine Fixes.
  25. That's quite a common problem. The intro is heavily scripted. The game engine is already under high pressure. If your game is also heavily modded, mods are initializing, distributing items, creating MCM entries and what not at the same time. So, the opening scene with a modded game is an absolute "stress test". Crashes and hiccups are to be expected - even if there are no real mod conflicts or bugs. Sad, but true: Playing the Vanilla intro is often impossible with large load orders - although these might work perfectly fine otherwise. There are workarounds though: 1. You can use "Alternate Start". You can choose to start without the intro - or you can give your mods some time to initialize and then choose to play the Vanilla intro. Often this already helps. 2. If you absolutely want to play Helgen, you could also start with a more or less unmodded game. Vortex (and AFAIK also MO 2) allow the use of different profiles. You could start with an unmodded "Vanilla" profile (or with only some basic mods - especially those, that you need for character creation), play through Helgen, save your game and then switch to the fully modded profile.
×
×
  • Create New...