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: Very Low
Votes: 0
Watching: N/A
Opened By Sclerocephalus on Dec 3, 2018 11:08 pm
Last Edited By Sclerocephalus on Dec 3, 2018 11:22 pm
Closed By Arthmoor on Feb 12, 2019 2:03 pm
Resolution: Fixed
Comment: Fixed for UFO4P 2.0.7.

Issue #25517: DNMasterQuest - Inappropriate condition checks on ElevatorGoingUpDownScene

This scene plays the "Going Up" and "Going Down" lines when an elevator starts moving. It is used by any and all elevators and load elevators in this game.

To discern which line to play, the two dialog topics on this scene (one for "Going Up", the other for "Going Down" ) have to check which state the elevator is in (i.e. whether it's at its top or at its down position) when it starts moving (because that's when the scene is called from ElevatorMasterScript and LoadElevatorMasterScript, respectively)..

However, load elevators and normal elevators are stroing this information in different variables because they are running entirely different scripts:
(1) Normal elevators store the information in the bElevatorIsAtTop bool on ElevatorMasterScript. This bool is flagged as conditional, so can be used in condition checks.
(2) Load elevators store the information in the LoadElevatorDown global.This global is used by any and all load elevators in the game.

Using the same global for all load eleavtors does usually not cause any conflicts (at least not in elevator handling) because the player can't use more than one elevator at a given time. It creates a problem for the condition checks on the aforementioned scene dialog topics though. The check for the "Going Down" line are currently looking as follows:

GetGlobalValue        LoadElevatorDown                         == 1.0000   OR
GetVMScriptVariable   elevatormasterscript, bElevatorIsAtTop   == 1.0000   AND
GetGlobalValue        LoadElevatorDown                         != 0.0000

This only works for load elevators. If the elevator is not a load elevator, the global can have any value (it:s unpredictable), so the first check may return 'true' even if no load elevator is used, and as a result, the elevator announcer will not say the right line.

Related Issues: 23149  


1 comment(s) [Closed]
Sclerocephalus said:
To make this work in all cases, the check must strictly discern between a load elevator and a normal elevator. Since I cannot check for a specific script running on the subject here, I solved this by adding a keyword, "UFO4P_IsLoadElevator" to the load elevator master base object and modifying the check as follows:

HasKeyweord           UFO4P_IsLoadElevator                     == 1.0000   AND
GetGlobalValue        LoadElevatorDown                         == 0.0000   OR
HasKeyweord           UFO4P_IsLoadElevator                     == 0.0000   AND
GetVMScriptVariable   elevatormasterscript, bElevatorIsAtTop   == 1.0000

Also fixed the check for the "Going Up" topic in the same way.

Comment #1 Dec 3, 2018 11:12 pm  Edited by Sclerocephalus on Feb 10, 2019 8:04 am
Showing Comments 1 - 1 of 1