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: Dragonborn
Category: Papyrus
Assigned To: Garthand
Platform: All
Severity: Very Low
Votes: 1
Watching: N/A
Opened By Garthand on Jan 22, 2020 8:19 pm
Last Edited By Garthand on Jan 22, 2020 9:08 pm
Closed By Arthmoor on Jan 23, 2020 6:05 pm
Resolution: Fixed
Comment: Fixed for USSEP 4.2.2.

Issue #28455: Solstheim Dragon Mound Papyrus Error

 
Approaching the Solstheim dragon mound generates the following Papyrus error:

[01/22/2020 - 07:20:31PM] error: Cannot call IsDead() on a None object, aborting function call
stack:
[ (04034ED7)].FXDragonMoundScript.OnCellLoad() - "FXDragonMoundScript.psc" Line 64
[01/22/2020 - 07:20:31PM] warning: Assigning None to a non-object variable named "::temp4"

The issue seems to be that the Solstheim dragon mound base inherited the default dragon mound script but set no properties, so the dragonRef is set to None and this causes an error.

Based on the fact that both the nearby dragon and the dragon mound dirt cap have DefaultDragonEnableMarker set as their enable parent, it appears that this mound was supposed to be set up similarly to those dragon mounds with the inherited dragon mound script removed. That is, the dragon is already present and the dirt cap disabled once DefaultDragonEnableMarker is enabled. Proposed fix is to simply remove/uninherit the script from the mound base.

Fix attached.



Attached Files:

Solstheim Dragon Mound Fix.zip