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, Starfield, or Oblivion Remastered. Doing so will help everyone on all platforms.

Issue Data
Status: Closed
Issue Type: Bug Report
Project: Unofficial Fallout 4 Patch
Component: Unofficial Fallout 4 Patch
Category: Papyrus
Assigned To: Sclerocephalus
Platform: All
Severity: Very Low
Votes: 0
Watching: N/A
Opened By DarthVitrial on Jul 29, 2022 8:10 pm
Last Edited By Sclerocephalus on Aug 7, 2022 8:23 am
Closed By Arthmoor on Mar 6, 2025 10:51 pm
Resolution: Fixed
Comment: Fixed for UFO4P 2.1.8.

Issue #32548: Possible papyrus error in RadioFailsafeScript

 
 error: Unable to call GetOwningQuest - no native object bound to the script object, or object is of incorrect type
stack:
	[<nullptr form> (0019D6C2)].Scene.GetOwningQuest() - "<native>" Line ?
	[DNMasterQuest (000AEC4F)].RadioFailsafeScript.StartAllScenes() - "C:\Users\Samson\AppData\Local\Temp\PapyrusTemp\RadioFailsafeScript.psc" Line 30
	[DNMasterQuest (000AEC4F)].RadioFailsafeScript.OnTimer() - "C:\Users\Samson\AppData\Local\Temp\PapyrusTemp\RadioFailsafeScript.psc" Line 56



Maybe vanilla, maybe related to the UO4P changes that touch those refs? (the retroactive fixes? This is on a brand new game)
Figured I'd report it.

Comments

3 comment(s) [Closed]
Sclerocephalus said:
 
This error message is left over from the vanilla bug and cannot be avoided. The script starts running very early on, and while it's on the stack, it will not accept the UFO4P modifications to its properties.
Nonetheless, this works as intended: the script will remain silent after the error has occurred once (or twice, at worst). In a vanilla game, it keeps re-occurring in short intervals of time, and this never stops.

Glitchfinder said:
 
As Sclerocephalus noted, this is the result of inherent race conditions tied to how quest startup is handled for this game engine. However, the error can be prevented by changing line 28 of RadioFailsafeScript from this:
		if theScene

To the following:
		if theScene && theScene.IsBoundGameObjectAvailable()

The bound game object check will silence the error if it happens during startup, and the next time the script runs (in approximately fifteen minutes after startup), it should be able to properly resolve any missed radio scenes and start them up as desired.

Arthmoor said:
 
In reference to the timer issue, I think if this thing is going to run into problems on immediate start, then what the UFO4P should be doing is instantiating the first timer for the loop at a lower value than normal. Like 2 minutes instead of the expected 15. That will be more than enough time on a new game to get everything taken care of before someone can exit Vault 111. Then the timer will roll for the infinite 15 minute intervals after that as usual.

I'm not sure why it was said that the quest won't accept the property changes either, because on a new game they're set already and don't need to be changed, while on an existing one the most you'd have to wait is 2 of the normal cycles to take the changes.

Showing Comments 1 - 3 of 3