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: Confirmed
Issue Type: Bug Report
Project: Unofficial Skyrim Special Edition Patch
Component: Skyrim SE: Vanilla
Category: Quests & Dialogue
Assigned To: Nobody
Platform: All
Severity: Medium
Votes: 1
Watching: N/A
Opened By Alaebasta on Jan 21, 2024 8:15 am
Last Edited By DarthVitrial on Jan 23, 2024 11:52 am

Issue #33789: Scene 2 Property in MQ101

 
The property is not filled and the scene is called.

I checked everywhere and i did't saw a fix to this

This result in a error in the papyrus log that causes crashes >>> Error: Cannot call "thescene" on a None object, aborting function call

Here enclosed the ck screenshots



Attached Files:

Screenshot 2024-01-21 1500510.png

Comments

9 comment(s)
DarthVitrial said:
 
Well, that wouldn't be able to cause a crash, the worst that can happen is a harmless papyrus warning.
But yes the property is unfilled, in fact no Scene 2 exists at all. Seems to be cut content for an older Elenwyn scene. Easiest fix is just to comment out the unnecessary "Scene2.Stop()" call - Bethesda already did that for the Start call, they just forgot the Stop.

DarthVitrial said:
 
Should fix it. Had to comment out three Stop() calls for the nonexistent scene.
Property is still unfilled in the CK but now the script will never attempt to access it.

Comment #2 Jan 21, 2024 3:38 pm  Edited by DarthVitrial on Jan 21, 2024 6:35 pm
Alaebasta said:
 
Ehm the scene is on MQ101 not MQ201

DarthVitrial said:
 
Yep, I attached the wrong script.

Comment #4 Jan 21, 2024 6:35 pm  Edited by DarthVitrial on Jan 23, 2024 11:52 am
Alaebasta said:
 
good job

DarthVitrial said:
 
That script doesn't seem to fix it, will need further investigation.

DarthVitrial said:
 
OK, should be properly fixed for next ussep.

Alaebasta said:
 
May i ask why the corrected script was still causing problems?

DarthVitrial said:
 
It just needed to be recompiled, it's fine now and will be included in the update.

Showing Comments 1 - 9 of 9