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 Fallout 4 Patch
Component: Fallout 4: Vanilla
Category: Papyrus
Assigned To: Sclerocephalus
Platform: All
Severity: Low
Votes: 0
Watching: N/A
Opened By BlackPete on Feb 8, 2018 5:33 am
Last Edited By Sclerocephalus on Aug 14, 2019 9:35 am
Closed By Arthmoor on Jun 24, 2022 12:52 am
Resolution: Fixed
Comment: Fixed for UFO4P 2.1.4.

Issue #23757: QF_DN011_000FF3C2: Cannot call Activate() on a None object

 
[02/08/2018 - 12:08:43AM] error: Cannot call Activate() on a None object, aborting function call
stack:
[DN011 (000FF3C2)].Fragments:Quests:QF_DN011_000FF3C2.Fragment_Stage_0200_Item_00() - "g:\_F4\Art\Raw\Scripts\Fragments\Quests\QF_DN011_000FF3C2.psc" Line 23
[02/08/2018 - 12:08:43AM] warning: Assigning None to a non-object variable named "::temp11"
stack:
[DN011 (000FF3C2)].Fragments:Quests:QF_DN011_000FF3C2.Fragment_Stage_0200_Item_00() - "g:\_F4\Art\Raw\Scripts\Fragments\Quests\QF_DN011_000FF3C2.psc" Line 23

Comments

2 comment(s) [Closed]
Sclerocephalus said:
 
Arthmoor said:
 
In order to address this in as simple a way as possible, the following has been done:

002485A9 and 002485A8 have been moved outside the playable areas. These triggers represent #1 in the above linked post. They are redundant.

000FF3F8 and 000FF3F7 have been expanded to a larger coverage area. These triggers represent #2 on the image. They both start Stage 0 of the quest.

This should provide for a large enough area to let the one second delay go through to fill the alias and allow trigger #3 to run as normal with no edits needed on that one.

Worst case, all of this does nothing and we're back to the same errors as before, but I find that to be very unlikely in this case.

Showing Comments 1 - 2 of 2