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 Special Edition Patch
Component: Skyrim SE: Vanilla
Category: Locations
Assigned To: Nobody
Platform: All
Severity: Very Low
Votes: 0
Watching: N/A
Opened By BlackPete on May 10, 2024 8:32 pm
Last Edited By Arthmoor on Oct 13, 2024 3:41 pm
Closed By Arthmoor on Oct 13, 2024 3:41 pm
Resolution: Fixed
Comment: Fixed for USSEP 4.3.3.

Issue #34019: Riften Fishery workers route through Black-Briar Meadery

 
The workers at the Riften Fishery go through the Black-Briar Meadery instead of using the main door down to the docks on the west side of Riften (directly to the left of the meadery). Given that it takes much less time, it would make a lot more sense for them to use the main door instead of winding their way through the meadery.

I can't recall if issues like this can be addressed in some way by adding or modifying navmeshes or if the "supposed" shortest route is calculated solely at the engine level.

Comments

1 comment(s) [Closed]
Arthmoor said:
 
This could be due to 2 things:

1. There are no preferred pathing lanes leading to the west city gate. So they may choose to go through the Meadery since a preferred path passed by the door there.

2. There were several navmesh nodes sunken below the walkway outside the west gate. As we now know, this sort of thing causes issues if the nodes are not perfectly placed.

Could also be a combination of the two problems so both have been corrected and should resolve this issue.

Comment #1 Oct 13, 2024 3:41 pm
Showing Comments 1 - 1 of 1