Issue Data
|
Issue #34107: Alduin's Wall MQ203 bug: Delphine is stuck at entrance and doesn't light the sconces
Skyrim AE 1.6.1170.0 Steam version. Alduin's Wall MQ203 stuck, Delphine doesn't light the torch sconces when entering Sky Haven Temple, Esbern just stands next to the wall and doesn't start interpreting it, quest stuck. I have searched the old reports and I am sure I have the latest version of USSEP installed correctly.
Steps to reproduce: Load Skyrim to the title screen, run "coc SkyHavenTempleEntrance" and "setstage MQ203 60", walk to the beginning of the temple entrance where Delphine and Esbern should be (you might need to wait an hour), solve the two puzzles, activate the blood seal, and go inside after Delphine and Esbern do. See Delphine stand next to the sconce and not light it. Attached is a save made after activating the blood seal. Fix was to revert the deletion of the isHammerWall keyword from the Furniture object LightSconceMarker, so the keyword is there again (esp attached). Repeating the above steps with this fix has Delphine light the sconces as normal. Attached Files: Save1_00000000_1_507269736F6E6572_KarthspireRedoubtWorld_000004_20240617062000_1_1.ess test.esp |
This is with only USSEP and no other mods installed. Could an update to Skyrim AE have changed something under the hood so the isHammerWall keyword is necessary, causing this bug to reappear?
Comment #1 Jun 17, 2024 2:39 am
Edited by nerevar009 on Jun 17, 2024 2:42 am
I'm not sure what LightSconceMarker would have to do with the torch thing because that was addressed in MQ203SkyHavenEntryScene.
That said, the edit to LightSconceMarker appears to be an undocumented edit since that term, and isHammerWall, do not appear anywhere in any of the changelogs, and only come up in the tracker for this ticket here. So there's no telling when this happened or why.
That said, the edit to LightSconceMarker appears to be an undocumented edit since that term, and isHammerWall, do not appear anywhere in any of the changelogs, and only come up in the tracker for this ticket here. So there's no telling when this happened or why.
Showing Comments 1 - 2 of 2