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: Closed
Issue Type: Bug Report
Project: Unofficial Fallout 4 Patch
Component: Fallout 4: Vanilla
Category: Quests
Assigned To: Sclerocephalus
Platform: All
Severity: Low
Votes: 0
Watching: N/A
Opened By BlackPete on Feb 1, 2018 3:20 am
Last Edited By Sclerocephalus on Oct 29, 2018 8:08 am
Closed By Sclerocephalus on Dec 3, 2018 1:16 am
Resolution: Fixed
Comment: Fixed for UFO4P 2.0.6

Issue #23698: QF_RETravelSC01_00026729: Unable to call Delete - no native object bound to the script object

[01/31/2018 - 11:09:58PM] error: Unable to call Delete - no native object bound to the script object, or object is of incorrect type
[None].ObjectReference.Delete() - "<native>" Line ?
[RETravelSC02 (00026729)].Fragments:Quests:QF_RETravelSC01_00026729.Fragment_Stage_0010_Item_00() - "g:\_F4\Art\Raw\Scripts\Fragments\Quests\QF_RETravelSC01_00026729.psc" Line 28

Related Issues: 24970  


3 comment(s) [Closed]
Sclerocephalus said:
Removed the 'Run on Start' flag from the stage 10 fragment.

That fragment is the first fragment to run on quest start anyway, but it appears that the 'Run on Start' flag lets the engine process it while the quest startup (i.e. filling the aliases and binding the script properties) is running, so the alias collection that throws this error (the fragment tries to remove an actor from that alias collection) is presumably not filled at the time the quest fragment tries to access it.

There's otherwise no reason for this error to occur: the alias collection is not optional and filled with actors created at run time, so there's no reason why it should be empty.

Sclerocephalus said:
Withdrawing this fix for now.

As it turned out, the quest may not properly start if the flag is removed. The RE logs will show it as running but return a stageID of zero (stage zero does not exist on any RE quest). Once this happens, the quest will not shut down, which indicates that the stage 10 fragment (that calls REScript to register for cleanup events) has never run.

We still don't know for sure whether the 'Run on Start' flag lets the engine process the respective fragment while the quest starts up. If so, accessing quest aliases from a fragment with tha flag is potentially unsafe. Removing the flag is not a solution though. Aa a workaround, one could move the unsafe stuff to a new stage and call that stage from the fragment tat runs on the stage with the flag.

Sclerocephalus said:
Made a new stage (stage 11) and moved all code from the stage 10 fragment there that is potentially unsafe to run from a fragment with the "Run on Start" flag. Also added a line to the stage 10 fragment to set stage 11.

Showing Comments 1 - 3 of 3