1. WE DO NOT SUPPORT VR IN ANY WAY!!! Bethesda has intentionally not provided it with mod support. It was built from an ancient fork of SE from before the Creation Club came into existence. The price of VR gear is too expensive for members of the team to justify. Plus the master files don't match up at all. There are currently no modder supported methods to auto-patch for VR since VR does not have any of the new content from SE 1.6.
2. We will not tolerate support requests for anyone using a jailbroken console. These activities are ILLEGAL and any posts on the subject will be instantly deleted, your access to this thread blocked permanently, and you WILL be reported to Nexus Staff for piracy.
3. This is NOT a general troubleshooting area. This topic is specifically for support of the patch. Please keep any general troubleshooting to the forums where you will get a more useful response for yourself and others.
4. Under no circumstances will we provide you with old copies of the patch. Do not ask. We will also NOT provide support for the archives which Nexus is forcing people to maintain. Do not ask about those either. All posts asking us to provide support for older versions of the game will be summarily deleted from now on.
6. If you're using any of the additional DLCs from the Anniversary Edition Upgrade, you need to also download Garthand's Unofficial Skyrim Creation Club Content Patches as these will resolve the conflicts between USSEP and the DLCs, as well as addressing other bugs in them that we are not covering.
7. Yes, you understood correctly, as of the June 2022 update, fixes for the 4 free DLCs that were downloaded with the 1.6 game update are now incorporated with the USSEP.
Will the recent version work with 1.6.640? If not, then why hide the old mod version downloads? I have mods I won't be able to play in 1130+ and I'm not willing to sacrifice them because they're too good.
No we do not. We are not beholden to neglectful modders who do not put in the due diligence that we do to keep up with the latest official game version. You should go persistently ask the neglectful modders to update their mods.
And no, providing them "without support" will not be done either. because... 1: the endless persistence will just transfer to demands to provide support for old USSEP versions, and 2: providing them at all is tacticly a level of support.
I noticed that several base game bandits got the perks Bone Breaker and Skullcrusher removed, though they can spawn with weapons that benefit from them. If I understand templates correctly they wouldn't get those perks in vanilla, because Use Spells was checked. So this looks a vanilla bug to me. Wouldn't the correct bug fix be to add the perks to the template or uncheck Use Spells where necessary?
It's always something to do with the environment or animals, i think. this last time (3) i was crouching outside a house in ivarsted waiting so i can pick the lock.
i've always assumed the "baseline" textures should be installed first, let USSEP win. but lately been wondering if maybe the cleaned / remastered textures and meshes should win. maybe it's subjective so just wondering what others thoughts or practice is.
It doesn't really matter either way, USSEP only changes a couple of textures. That said, I know Vanilla remastered has a patch for USSEP that upscales it's bugfixed textures.
EDIT: Actually, upscaled USSEP textures are integrated into Vanilla remastered by default, so you don't even need a patch. It should load after USSEP though.
I'm getting a pretty annoying bug in which the quest markers on the compass are forcing me to use a certain door or they will not update. For example, I just left Dayspring Canyon on my way to a quest Crystaldrift Cave and the compass wants me to go through Riften entering via the south gate and exiting via the door from the main area to the docks. If I do not do that, the markers on the compass refuse to show me the way to Crystaldrift cave, say I exit Riften via the north gate; the compass will instruct me to reenter Riften via the north gate and exit through the dock door it wanted me to use from the beginning. Then, after doing the Crystaldrift cave quest, I then must make my way back to Riften entering from the dock door and exiting through the north gate for the compass to show the way to all my other quests. The only way I've found to get around this is to fast travel, which seems to behave as if I went through the doors the compass wants me to use.
While Riften is particularly troublesome, this applies to many other places and times too, another thing that happened was that there was some person I was supposed to find and then kill just north of Mistwatch (I think from the Saints and Seducers stuff?). Upon getting close to the area, the objective updated from find to kill, but despite the quest marker being the same place on the map, in order to get the compass to show it, I had to go through Mistwatch backwards (from a trapdoor on the top to the main entrance at the bottom), I'd never even been to Miswatch before so doing this required cheats to get through the locked door that Fjola's husband is supposed to give you the key to. And this has happened repeatedly over the past week or so, i.e. not that long. I've tried everything I can thing of to update the quest marker, untracking all but one quest, untracking and retracking quests, fast traveling to my location, entering and exiting a different area, and several others, none of these had any effect
I disabled all mods and the issue vanished so I went through my modlist and determined USSEP to be the offending mod, which is really annoying since several of my mods have a heavy dependency on it. It seems not to be a conflict, because I disabled every mod other than USSEP and still had the issue. I am using game version 1.6.1170.0.8, downloaded via steam if that matters. What I find strangest is that when I built this modlist in early April I didn't seem to have this issue (I find it hard to believe I'd have missed it, it's pretty noticeable), not even a couple weeks ago when I started playing this save, it only started happening recently. But, unless Skyrim or USSEP were updated recently (which from what I can find they weren't), I don't know why I would just now be getting this issue.
EDIT: Forgot to mention this, but one of the first things I checked was if it was the save, this problem carries over to other saves that I'm sure I didn't have this issue with before.
Okay, maybe I missed something, but if this mod is only intended for patch 1.6, then it is no longer the SE patch, but the AE patch now? Not sure, but I play through Steam, but I am not "up(down)grading" to AE edition, so this mod is useless to me now?
EDIT: Nevermind, I am just still sleepy I guess. My game version is 1.6.1
"SE" and "AE" are frustratingly still misused terms to refer to 1.5 and 1.6 after over three years. "AE" is the Anniversary Edition, which is SSE v1.6 plus the Anniversary Upgrade, a comprehensive Creation Club content bundle. Misuse of these terms leads to confusion just like this.
USSEP has only ever required the latest version of SSE for use.
Also, the latest version of SSE is 1.6.1170 on Steam, v1.6.1179 on GOG. We list 1.6.1130 here because technically the only change done from there has been in the executable or asset files outside of our purview (like UI stuff).
I just reinstalled the game yesterday, and was trying to get some mods working, and was seeing alot of people mentioning that AE was 1.6, and so they degraded their games back to 1.5 to be able to use mods, so I just assumed 1.5 was the version before the latest upgrade. That's on me. Thanks for clearing that up more for me.
Hey guys. I have a question I want to verify with you about the recent changes to the Head Data in race records. Primarily Dark and Wood elves. Are the changes going to have any negative affects with older patches created using the older Dark elf, wood elf records. You guy reverted both elves Head Data records back to vanilla dawngaurd. I'm guessing no, but since I have a ton of patches for race records, I thought I'd better verify it with you instead of simply ignoring a potential problem.
I have already solved this problem. Im just download separatly this file(it turns out many who have the GOG version of Skyrim SE were missing this .esl on base installation) and all fixed now.
Hey, I've been looking into the situation with the Riften jail secret entrance bug and I just had a couple questions. I read that Bethesda eventually "fixed" this if the source is accurate. Is this patch still implemented in USSEP? Also is the passage a one-time use feature with the fix? I'm creating a mod that uses the passage, and I'm just trying to figure out what I'm dealing with and if I need to list USSEP as a requirement. The most up to date info I can find is a decade old.
14502 comments
1. WE DO NOT SUPPORT VR IN ANY WAY!!! Bethesda has intentionally not provided it with mod support. It was built from an ancient fork of SE from before the Creation Club came into existence. The price of VR gear is too expensive for members of the team to justify. Plus the master files don't match up at all. There are currently no modder supported methods to auto-patch for VR since VR does not have any of the new content from SE 1.6.
2. We will not tolerate support requests for anyone using a jailbroken console. These activities are ILLEGAL and any posts on the subject will be instantly deleted, your access to this thread blocked permanently, and you WILL be reported to Nexus Staff for piracy.
3. This is NOT a general troubleshooting area. This topic is specifically for support of the patch. Please keep any general troubleshooting to the forums where you will get a more useful response for yourself and others.
4. Under no circumstances will we provide you with old copies of the patch. Do not ask. We will also NOT provide support for the archives which Nexus is forcing people to maintain. Do not ask about those either. All posts asking us to provide support for older versions of the game will be summarily deleted from now on.
5. Regarding the "AE vs SE" misinformation that's going around, please do yourself a favor and read this: https://www.afkmods.com/index.php?/topic/5954-skyrim-anniversary-edition-and-you/ It will clear up any confusion on the subject that other forums are causing.
6. If you're using any of the additional DLCs from the Anniversary Edition Upgrade, you need to also download Garthand's Unofficial Skyrim Creation Club Content Patches as these will resolve the conflicts between USSEP and the DLCs, as well as addressing other bugs in them that we are not covering.
7. Yes, you understood correctly, as of the June 2022 update, fixes for the 4 free DLCs that were downloaded with the 1.6 game update are now incorporated with the USSEP.
And no, providing them "without support" will not be done either. because... 1: the endless persistence will just transfer to demands to provide support for old USSEP versions, and 2: providing them at all is tacticly a level of support.
If I understand templates correctly they wouldn't get those perks in vanilla, because Use Spells was checked. So this looks a vanilla bug to me.
Wouldn't the correct bug fix be to add the perks to the template or uncheck Use Spells where necessary?
Crash Log 3
Crash Log 2
Crash Log 1
It's always something to do with the environment or animals, i think. this last time (3) i was crouching outside a house in ivarsted waiting so i can pick the lock.
Your load order is also gorged on SKSE plugins.
It's also not correct, because USSEP is placed in the wrong position.
i've always assumed the "baseline" textures should be installed first, let USSEP win.
but lately been wondering if maybe the cleaned / remastered textures and meshes should win.
maybe it's subjective so just wondering what others thoughts or practice is.
EDIT: Actually, upscaled USSEP textures are integrated into Vanilla remastered by default, so you don't even need a patch. It should load after USSEP though.
While Riften is particularly troublesome, this applies to many other places and times too, another thing that happened was that there was some person I was supposed to find and then kill just north of Mistwatch (I think from the Saints and Seducers stuff?). Upon getting close to the area, the objective updated from find to kill, but despite the quest marker being the same place on the map, in order to get the compass to show it, I had to go through Mistwatch backwards (from a trapdoor on the top to the main entrance at the bottom), I'd never even been to Miswatch before so doing this required cheats to get through the locked door that Fjola's husband is supposed to give you the key to. And this has happened repeatedly over the past week or so, i.e. not that long. I've tried everything I can thing of to update the quest marker, untracking all but one quest, untracking and retracking quests, fast traveling to my location, entering and exiting a different area, and several others, none of these had any effect
I disabled all mods and the issue vanished so I went through my modlist and determined USSEP to be the offending mod, which is really annoying since several of my mods have a heavy dependency on it. It seems not to be a conflict, because I disabled every mod other than USSEP and still had the issue. I am using game version 1.6.1170.0.8, downloaded via steam if that matters. What I find strangest is that when I built this modlist in early April I didn't seem to have this issue (I find it hard to believe I'd have missed it, it's pretty noticeable), not even a couple weeks ago when I started playing this save, it only started happening recently. But, unless Skyrim or USSEP were updated recently (which from what I can find they weren't), I don't know why I would just now be getting this issue.
EDIT: Forgot to mention this, but one of the first things I checked was if it was the save, this problem carries over to other saves that I'm sure I didn't have this issue with before.
Okay, maybe I missed something, but if this mod is only intended for patch 1.6, then it is no longer the SE patch, but the AE patch now? Not sure, but I play through Steam, but I am not "up(down)grading" to AE edition, so this mod is useless to me now?EDIT: Nevermind, I am just still sleepy I guess. My game version is 1.6.1
USSEP has only ever required the latest version of SSE for use.
Also, the latest version of SSE is 1.6.1170 on Steam, v1.6.1179 on GOG. We list 1.6.1130 here because technically the only change done from there has been in the executable or asset files outside of our purview (like UI stuff).