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.
im new to modding this game and i installed this mod using vortex but its saying that im missing fish.esm, advGSGS.esm, curios.esl, and survivalmode.esl. i did see that it said something about an order to install these or something in the description but that didnt make much sense to me. i also tried downloading manually incase the missing files just didnt get installed with vortex, but then it got stuck at 32kb and i wasnt able to download it. i have no idea how to fix this.
I'm not sure what the two of you are getting but even with whatever it is we might have done for this I can barely hear tavern sounds whether I'm inside or not. So "so dang loud" isn't necessarily the case because I could wonder why it's still "so dang quiet" :P
Quick Question, I understand why you guys choose not to update/support older versions, but instead of archiving them, why not still make them available for download with a disclaimer that no support will be provided and anyone complaining about older versions not working will be ignored?
I mean, there's still links to the old files that allows people to thankfully still download it ( Thank you Nexus Staff )
Like I can understand that it would be annoying to have people still complain about a version not working properly or make bug reports on an outdated version, but seems like people are still doing that anyways, at least with the new version.
only reason I can think of revolves around a certain drama that happened a while back. and Question 4 in the FAQ only supports my theory.
We have a lot of the same points only admittedly I came off as more harsh and annoyed at their actions. I do not understand the point of archiving all previous versions just because you got triggered at the community over something. I hope they see reason and decide to unarchive the previous versions. So many mods I loved I can no longer play because of this.
You pretty much answered your own question. We do not provide the older versions specifically because it is inherently support of older versions to provide them even if we say "we do not support it". People will come here anyway, people will get angry when we say we won't support it.
Why do we not support older versions? Once again, you answered your own question. Because the Official patches change things that we now have to support, and we don't want to constantly have to be diagnosing problems in older versions we already fixed because of Anti-Patch Obstinacy. We'd have to make forks of the USSEP for every official version skewing off every which way to cater to such anti-patch obstinacy. It is already a considerable undertaking keeping up with the current Official Version. With a "No old patches" policy, we simply say "Update" instead of chasing down those old bugs yet again. This isn't our day job.
As for Nexuslover123, we are not "triggered" over it, you were. Your "harsh and annoyed" reaction has gotten you blocked, because you are hardly the first and certainly won't be the last that comes at us with a bad attitude and then take umbrage at us not wanting to deal with people like you ad nauseum. There are plenty of examples of commenters even on the very front page of comments lacking a bad attitude getting at worst a "Just update" and a simple threadlock or "That was vague, need more info". The drama is not from us.
Lastly, we are not the ones refusing to keep up with the latest version. Why are you putting the onus of the consequences of your choice on us?
Topic closed, because as indicated, this discussion is hardly new, and very tiresome.
everything i've found online about the ancient shrouded cowl says that ussep fixes that bug, but im still experiencing the bug with ussep in the game. not sure if theres a way to fix this or not, but all the sources of information for me have led back to here.
You'd need to be more specific about what you're seeing. The only thing we've done to that, according to the changelog, is to prevent the cowl from being invisible when worn by Argonians and Khajiit.
Hey there, I've recently downgraded my skyrim to 1.5.97. Will the current USSEP for 1.6.1130+ work with my downgraded version? For example, if a seperate mod requires the USSEP will it still be compatible? I've also downloaded the backported extended esl support, but idk if that will help in this case.
Don’t downgrade. There is literally no reason whatsoever to do so, all mods work on the current version. Even NGIO works on 1.6.1170. USSEP is built with the assumption you are using the current version and we will not support older versions.
When the Forelhost dragon cultists die from Dawnbreaker's proc fiery explosion, they drop both ash piles and ghostly remains.They otherwise do not drop ash piles when killed with magic that normally disintegrates, as far as I understand. I tried tracking down the source of this but it's beyond me--does it use a script to disintegrate enemies separate from the normal one for magic? Tested this on both a modded save, and a separate profile w/ new save and only USSEP, ASLAF and SkyUI. The results were the same.
Yes, ghosts are controlled by a different script, but they should also have a keyword that excludes them from normal disintegration... Maybe it's missing here.
Ah, that might be it. I was looking at the other disintegration script. Looking at it now, with my elementary understanding of papyrus I think it only checks for race / if the actor base is in the immunity list, but not for the 'no disintegration' "MagicNoDisintegrate" keyword. See above.
I honestly don't know if that' line is related after all. I'm not familiar enough with the logic here/scripting in general to know why this is happening. It's like it's getting its default ghostly pile with an added ashpile on top; so wouldn't it be not in the ghost script but the other one? Because it's still setting the normal ghostly remains pile like it should, but for whatever reason is also doing the ash...
EDIT: another note, maybe useful, maybe not. They are missing the 'is ghost' flag in their records still, seems like. Don't know if there was a reason for that, as it seems like some other ghost npcs are also missing that flag.
EDIT2: nevermind that flag did not do what I thought it did. I'm outta ideas otherwise.
EDIT3: Perhaps something to do with magicAttachAshPileOnDeath ?
Not sure if this is something to report here, or if it's covered somewhere else but here goes. Couldn't find anything regarding this issue anywhere else.
DawnstarExterior08, texture seam on landscape. In the CK if only Skyrim.esm is loaded the seam is not there. With Update.esm loaded, the seam shows up. Images below.
00095102 should be the rock (MountainTrim02_HeavySN) showing at the top-left edge of images Just noticed those were my old images with a few textures still active in MO2, tested again with zero mods active and same issue, I can post those if needed.
Well, I confirmed it exists, seems to be caused by Update.esm's edit to record 0009EB6, but it's most likely out of scope for ussep to fix, we try not to edit Landscape records for compatibility purposes.
Blocking achievements is a vanilla feature of the game (thanks Microsoft). You need the SSE Engine Fixes mod to be able to disable that block and start getting them again. I'm pretty sure it will tell you they're being blocked the first time you load with it after installing but it should be fine after that.
It's probably because there used to be people that viewed using mods on games as a form of cheating and convinced the game console manufacturers to implement some way to restrict access to achievements to only those people that played the game as it came from the developers.
That would be fine for consoles where achievements apparently have monetary value. On PC they're meaningless so it makes little sense to block them here too.
I may be misunderstanding, but isn't it normal that you can't turn in the quest if you've made both factions hostile? Try using a Calm spell to pacify one of them.
If she dies as a bandit leader and you go back to Cristen to tell, he turns hostile and dies. So you never can finish the quest. See bug section here Skyrim:Mistwatch (quest) - The Unofficial Elder Scrolls Pages (UESP) Also if he dies and she too because she turns hostile to the PC, you can't finish the quest too.
13363 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.
plz help!
I downloaded this to turn off that noise:
https://www.nexusmods.com/skyrimspecialedition/mods/45276?tab=files
I mean, there's still links to the old files that allows people to thankfully still download it ( Thank you Nexus Staff )
Like I can understand that it would be annoying to have people still complain about a version not working properly or make bug reports on an outdated version, but seems like people are still doing that anyways, at least with the new version.
only reason I can think of revolves around a certain drama that happened a while back. and Question 4 in the FAQ only supports my theory.
Why do we not support older versions? Once again, you answered your own question. Because the Official patches change things that we now have to support, and we don't want to constantly have to be diagnosing problems in older versions we already fixed because of Anti-Patch Obstinacy. We'd have to make forks of the USSEP for every official version skewing off every which way to cater to such anti-patch obstinacy. It is already a considerable undertaking keeping up with the current Official Version. With a "No old patches" policy, we simply say "Update" instead of chasing down those old bugs yet again. This isn't our day job.
As for Nexuslover123, we are not "triggered" over it, you were. Your "harsh and annoyed" reaction has gotten you blocked, because you are hardly the first and certainly won't be the last that comes at us with a bad attitude and then take umbrage at us not wanting to deal with people like you ad nauseum. There are plenty of examples of commenters even on the very front page of comments lacking a bad attitude getting at worst a "Just update" and a simple threadlock or "That was vague, need more info". The drama is not from us.
Lastly, we are not the ones refusing to keep up with the latest version. Why are you putting the onus of the consequences of your choice on us?
Topic closed, because as indicated, this discussion is hardly new, and very tiresome.
USSEP is built with the assumption you are using the current version and we will not support older versions.
When the Forelhost dragon cultists die from Dawnbreaker's proc fiery explosion, they drop both ash piles and ghostly remains.They otherwise do not drop ash piles when killed with magic that normally disintegrates, as far as I understand.
I tried tracking down the source of this but it's beyond me--does it use a script to disintegrate enemies separate from the normal one for magic?
Tested this on both a modded save, and a separate profile w/ new save and only USSEP, ASLAF and SkyUI. The results were the same.
(Also fun fact, it's actually misspelled as "MagicNoDistintegrate")
That line was in defaultGhostScript. I thought maybe it would've been due to magicAttachAshPileOnDeath but now I'm unsure.
EDIT: another note, maybe useful, maybe not. They are missing the 'is ghost' flag in their records still, seems like. Don't know if there was a reason for that, as it seems like some other ghost npcs are also missing that flag.EDIT2: nevermind that flag did not do what I thought it did. I'm outta ideas otherwise.
EDIT3: Perhaps something to do with magicAttachAshPileOnDeath ?
EDIT: NVM, misread. Dawnbreaker.
For some reason I read that as Dawnguard. Am checking now.
EDIT 2: I think I found the cause, working on a fix.
Pretty involved bug actually.
Not sure if this is something to report here, or if it's covered somewhere else but here goes. Couldn't find anything regarding this issue anywhere else.
DawnstarExterior08, texture seam on landscape. In the CK if only Skyrim.esm is loaded the seam is not there. With Update.esm loaded, the seam shows up. Images below.
Just noticed those were my old images with a few textures still active in MO2, tested again with zero mods active and same issue, I can post those if needed.
Skyrim:Mistwatch (quest) - The Unofficial Elder Scrolls Pages (UESP)
if both hostile, you will not be able to finish this quest
See bug section here
Skyrim:Mistwatch (quest) - The Unofficial Elder Scrolls Pages (UESP)
Also if he dies and she too because she turns hostile to the PC, you can't finish the quest too.