Welcome to the AFK Mods bug tracker. In order to report an issue, you need to have a VALIDATED account to post one. Once you have followed the link the registration email sent you, please select a project from the drop down menu below. Select “Open New Issue” and fill out the form with as many details as possible.

Please also consider sending your bug report to Bethesda if you are reporting on an issue with Skyrim Special Edition, Fallout 4, or Starfield. Doing so will help everyone on all platforms.

Issue Data
Status: Closed
Issue Type: Bug Report
Project: Unofficial Skyrim Legendary Edition Patch
Component: Skyrim LE: Vanilla
Category: Quests
Assigned To: Nobody
Platform: Windows PC
Severity: Low
Votes: 1
Watching: N/A
Opened By RobinHood70 on May 13, 2016 9:46 pm
Closed By Arthmoor on May 15, 2016 12:49 am
Resolution: Fixed

Issue #20429: Galmar gets stuck in Season Unending

 
During Season Unending, as everyone files into the council room, Galmar sometimes gets stuck up near Delphine's chair. Some astute person on UESP figured out that he was the source of the problem and noticed that disabling and re-enabling him fixed it. I just tried a mod-based fix, by increasing his target radius (from 0 to 5) in his Action in Phase2 of MQ302CouncilSceneBegin, and sure enough, he pathed straight there, as he should have. I'm not entirely sure that that's the best solution, but it would seem to confirm that Galmar not reaching his target is the problem here.

Comments

4 comment(s) [Closed]
RobinHood70 said:
 
Oh, I forgot to say that him not reaching the target brings the quest to a standstill, since everyone has to hit their targets before you can move on to Phase 3, completing the "Take your seat" objective.

Comment #1 May 13, 2016 9:48 pm
Arthmoor said:
 
What target radius are you referring to?

Comment #2 May 15, 2016 12:15 am
RobinHood70 said:
 
Sorry, that could've been clearer, couldn't it? In the package MQ302CouncilGalmar1, Place to Travel, I set the Radius to 5.

I suspect that's more of a workaround than the preferred solution. I'm assuming that it's actually some kind of pathing or marker placement problem. I don't have much experience with that, though, so I can't pinpoint the actual issue.

Comment #3 May 15, 2016 12:30 am
Arthmoor said:
 
Fixed for USLEEP 3.0.4.

Comment #4 May 15, 2016 12:49 am
Showing Comments 1 - 4 of 4