Welcome to the AFK Mods bug tracker. In order to report an issue, 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.

An account will be required to submit an issue, so if you need one and are unable to register, please contact us via the forums at https://afkmods.iguanadons.net/
       

Issue Data
Status: New
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 Sep 13, 2018 1:00 am
Last Edited By Sclerocephalus on Sep 14, 2018 6:24 pm

Issue #25150: CIS_ManagerScript: Cannot call IsInFaction() on a None object

[09/11/2018 - 05:10:10PM] error: Cannot call IsInFaction() on a None object, aborting function call
stack:
[AO_CIS_Manager (00175526)].CIS_ManagerScript.StartCompanionInteractionScene() - "C:\Users\Dr. Peter Haas\AppData\Local\Temp\PapyrusTemp\CIS_ManagerScript.psc" Line 94
[AO_CIS_Manager (00175526)].Fragments:Quests:QF_AO_CIS_Manager_00175526.Fragment_Stage_0000_Item_00() - "g:\_F4\Art\Raw\Scripts\Fragments\Quests\QF_AO_CIS_Manager_00175526.psc" Line 16
[09/11/2018 - 05:10:10PM] warning: Assigning None to a non-object variable named "::temp12"
stack:
[AO_CIS_Manager (00175526)].CIS_ManagerScript.StartCompanionInteractionScene() - "C:\Users\Dr. Peter Haas\AppData\Local\Temp\PapyrusTemp\CIS_ManagerScript.psc" Line 94
[AO_CIS_Manager (00175526)].Fragments:Quests:QF_AO_CIS_Manager_00175526.Fragment_Stage_0000_Item_00() - "g:\_F4\Art\Raw\Scripts\Fragments\Quests\QF_AO_CIS_Manager_00175526.psc" Line 16

       

Comments

1 comment(s)
Sclerocephalus said:
This error can occur with Deacon or Curie but not with any other companion. There are apparently attraction onjects that call the StartCompanionInteractionScene() function on CIS_ManagerScript with a set of parameters that cannot be handled by that function - either because the parameters themselves are faulty (this would make this issue a placed ref issue since these parameters are defined on the individual attraction objects) or because CIS_ManagerScript is simply missing sanity checks. Whichever applies cannot be told for sure however if we do not know which references are causing this error to occur. And that's a problem, because these error messages do not tell us the offending refIDs.

Therefore, I modified CIS_ManagerScript a while ago to spot the suspects and print them on the papyrus log. So far, I have logged the following refs that all cause an error on the vanilla script if Curie is your companion (I have no hits for Deacon so far):

0018F00F, 0018F013, 0018F015, 0018300C

       
Showing Comments 1 - 1 of 1