Forum Discussion
Yea, it's by no means a priority since the mission can still be completed, it's just an oddity and minor bug, just throwing the info out there so it will maybe get fixed eventually.
I thought I should chime in here. This never got fixed. Probably never will. I’m playing the Legendary Edition on PS4 and it’s happening to me too.
- 4 years ago
Just replayed this mission three times to examine it. The mech appears to be focused on, or targeting, a singular point. I followed the mech’s point of view, and it only deviates from that point when the script tells it to shoot up the canyon wall the second time. That singular point is the same point in three dimensional space that it shoots to destroy the first rock wall.
My guess is that the scripting uses a “pseudo target” to aim the mech for the first rock wall, and this target isn’t properly being destroyed, despawned, reassigned, etc, after the first rock wall is destroyed. Thus, the mech remains focused on the first rock wall until told otherwise (focus on the second rock wall)
- draconiam4 years agoSeasoned Ace@PakunaMatata Could the Trilogy be affected by a massive Scripting issue? This might be bigger than we thought.
- 4 years ago@draconiam Not likely. It’s more likely an error that popped up as an unexpected result of the fact that they upgraded the UE3 engine in the game. Sort of like how sometimes when you upgrade Windows, occasionally you get things that suddenly don’t work properly, because a subroutine the app used handles things differently. If this were a trilogy wide error, any cutscene that also uses the ghost or pseudo target would be malfunctioning in exactly the same way.
I think it’s just a problem with this script and despawning or destroying the individual pseudo target.
Of course, I don’t have the source code, so all this is purely speculation, and only based upon observations.