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: Confirmed
Issue Type: Bug Report
Project: Unofficial Fallout 4 Patch
Component: Fallout 4: Vanilla
Category: Placed References
Assigned To: Sclerocephalus
Platform: All
Severity: Low
Votes: 0
Watching: N/A
Opened By BlackPete on Jan 15, 2018 3:55 am
Last Edited By BlackPete on Jul 8, 2019 4:43 am

Issue #23490: defaultDisableOnResetIfLocWasCleared: Cannot call Disable() on a None object

 
[01/14/2018 - 02:45:19AM] error: Cannot call Disable() on a None object, aborting function call
stack:
[ (0021710C)].defaultDisableOnResetIfLocWasCleared.OnCellDetach() - "g:\_F4\Art\Raw\Scripts\defaultDisableOnResetIfLocWasCleared.psc" Line 12

Comments

3 comment(s)
Sclerocephalus said:
 
There's nothing wrong with the script. Instead, the ref in question is missing a linked x marker, without which the script doesn't work.

Therefore, this is a placed reference issue, not a script issue.

Comment #1 Jan 18, 2018 5:46 pm
Sclerocephalus said:
 
As it turned out, the offending ref has a DefaultEnableDisableTrigger linked to it that does the job supposed to be done by defaultDisableOnResetIfLocWasCleared. Thus, that latter script is no longer needed and has been removed.

Comment #2 Jan 23, 2018 3:19 pm
Sclerocephalus said:
 
Forget my last comment. This is more complicated than it seemed to be: the marker starts disabled, then gets enabled by the trigger, so the script might need to be used after all to disable it again. This needs more time to investigate, and also to find out what behaviour was actually intended here.

Comment #3 Jan 25, 2018 1:21 pm
Showing Comments 1 - 3 of 3