View Full Version : Missing 9-2 Cutscene Workaround
Ziyyigo-Tipyigo
07-14-2013, 01:40 AM
Threw enough linkshell minions at this longstanding bug (http://forum.square-enix.com/ffxi/threads/34446-Cutscenes-still-skipped-in-Throne-Room-%28probably-Full-Moon-Fountain-as-well%29) to find a work around.
The bug will affect (a) the first person to enter the battlefield (b) after first entering the area. Even if everyone leaves the battlefield and re-enters (without leaving the area entirely), that same person still will not get the CS.
In order to get the opening CS, you need (a) the "Battlefield" status icon (b) the first time you try entering the battlefield after entering the area.
Therefore, the work-around is to have everyone enter, then leave one person (at least) in the battlefield while anyone who missed the CS leaves the battlefield and the area entirely before trying to enter again.
Remember not to engage any enemies before then, or anybody outside will be denied entry.
Soloers are obviously out of luck and are stuck with having to come back to check the Goblin Footprints after officially completing the mission entirely (i.e. reaching rank 10)
Ziyyigo-Tipyigo
07-30-2013, 10:54 AM
This is not an option for Bastok 9-2, where the battlefield cannot be escaped voluntarily. So it's either a matter of bringing two people who need the mission, or being stuck with coming back after reaching rank 10 to view what was missed.
Ziyyigo-Tipyigo
08-04-2013, 12:11 PM
Just learned that this problem affects Rise of the Zilart mission "Return to Delkfutt's Tower." Same exact problem, same required solution of exiting the battlefield and Stellar Fulcrum entirely before re-entering, leaving someone else in the battlefield the entire time.
Ziyyigo-Tipyigo
08-23-2013, 05:18 AM
This bug does not seem to affect the final battlefield for San d'Oria mission 9-2.
Ziyyigo-Tipyigo
09-29-2013, 01:18 AM
Having someone in the party watch the affected cutscene at the Goblin Footprint first does not fix the problem.
Ziyyigo-Tipyigo
10-16-2013, 06:49 AM
It should be noted that, thanks to a new bug, "Where Two Paths Converge" now has neither beginning or ending cutscenes played.
Rifaran
12-23-2013, 06:33 AM
yes this bug affects Return to Delkfutts Tower and The Celestial Nexus as when I beat both of the end bosses, Both cutscenes were skipped.
Rifaran
01-11-2014, 03:58 PM
This bug also affected Darkness Named, as I just beat the boss in that mission and there was NO cutscene :(
Draylo
01-11-2014, 04:22 PM
They are fixing it in a week.
Rifaran
01-14-2014, 08:58 AM
it also affected The Savage, yes I know you said that they are fixing it, but i'm just posting just in case.
Rifaran
01-21-2014, 07:13 PM
so was this fixed in the update?
Ziyyigo-Tipyigo
01-22-2014, 01:54 AM
Just wanted to point out that I started this thread with the years-old bug that ate opening battle cutscenes in various original area and Rise of the Zilart missions and quests in mind. This bug has been around for over three years or so, and only affects the first person entering the battlefield. Adjustments were made to the Rank 5 Final Mission in 2011 or so to fix this problem for that particular battle, but nothing has been done anywhere else, or even for other affected battlefields in the Throne Room.
Starting around the time of the 2013 October 8 version update, a new bug was introduced that eats closing battle cutscenes. Personally I've seen Rise of the Zillart (including rank 6+ missions), Chains of Promathia and Treasures of Aht Urhgan mission battlefields affected. This bug affects all participants.
There was a recent news posting about the first, older bug (opening cutscenes), wherein the developers said that it would finally be fixed in the "next version update," but that version update has come and gone with no mention of the problem in the update notes. Either way I've yet to have the opportunity to test things first-hand, for lack of newb victims to experiment with/on. (If you're on Sylph and...)
The newer bug (ending cutscenes) was not mentioned at all in the above-mentioned posting. It was last acknowledged in the 2013 November 5 version update notes as a "Known Issue."