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: Quests & Dialogue
Assigned To: Sclerocephalus
Platform: All
Severity: Low
Votes: 0
Watching: N/A
Opened By BlackPete on Dec 11, 2019 2:16 am
Last Edited By Sclerocephalus on Dec 13, 2019 7:16 pm
Closed By Sclerocephalus on Apr 19, 2020 9:02 pm
Resolution: Can't Fix - Engine Issue
Comment: see my comment

Issue #28187: RESceneKMK07: Index 0 for GetAt is outside max range (0)

 
[12/10/2019 - 07:00:35PM] error: alias Dogs on quest RESceneKMK07 (0018605A): Index 0 for GetAt is outside max range (0).
stack:
[alias Dogs on quest RESceneKMK07 (0018605A)].recollectionaliasscript.GetAt() - "<native>" Line ?
[RESceneKMK07 (0018605A)].rescript.::remote_REParentScript_RECheckForCleanup() - "C:\Users\Dr. Peter Haas\AppData\Local\Temp\PapyrusTemp\REScript.psc" Line 272

Comments

1 comment(s) [Closed]
Sclerocephalus said:
 
This is an error that still can occur on any RE quest if two cleanup events are received within a short period of time. If the first event finds that the stop conditions are fulfilled, it will shut down the quest; at this point, the second event is still being processed and will then fail eventually with an error that is otherwise impossible to occur (such as this one).

To avoid this, I modified REScript in a previous patch to set a tracking bool when the event processing starts running. While this bool is 'true', handling of other events that come in while the first event is being processed will be skipped. However, it's still possible that a second event fires before the tracking bool is set. Thus, the error will occur less likely now but there's nothing I can do to avoid it entirely.

Showing Comments 1 - 1 of 1