Game Crashing at Final Battle

[Jeral]

My game keeps crashing at the same point of the final battle!

Specifically, this would be after the fight with Ishmelga Rean and right before starting Phase 2 of the fight using Soldats.

I will see the loading icon right before the fight starts and then the game just crashes - no error messages, just quits.

1) Drivers updated
2) Verified integrity of files
3) Meet Recommended (not minimum) system requirements
4) Windowed mode, changed graphic settings to the lowest for this

Any idea how to troubleshoot this?

NGL, having the game crash right at the final battle after spending days at this is gonna drive me insane.

[Durante]

We had a crash that was discovered during the final battle in QA, but that was completely fixed before release, at least according to all our tests, so this is really surprising to me.

It's particularly strange that you are not even getting an error message.

Can you please post your system specs (including HW and software, e.g. Windows version) and settings file?
The latter can be found in "%LOCALAPPDATA%\Falcom\ed8_psv5\settings.toml", e.g. "C:\Users\[Username]\AppData\Local\Falcom\ed8_psv5\settings.toml".

Please also post your savegame, found in "C:\Users\[Username]\Saved Games\Falcom\ed8_psv5".

[Durante]

One more thing that you can try, in case this applies to you, is unequipping any costume parts you have equipped on your characters. The crash we fixed was related to that, and, well, was fixed in all circumstances our testers were able to reproduce, but it might still be worth a try.

[Gacktdirge17]

Hi, got the same issue, play through phase 1 without problem and it always crash in the cutscene leading to phase 2, precisely when the the antagonist calls for his mech.
Weird because i had 0 crash the entire game.

[megax1234]

Adding a +1 to this... Just made it to the final boss on version 1.0.6 and killed the first phase. Crashes when going into the second phase battle every single time no matter if I remove all costumes, change settings, etc. Playing on Steam Deck at the moment.

Update:
Installed the game on my PC and was able to get passed the crash that way. Nvidia GPU on my PC. Maybe issue is AMD related?

[barunaru]

I also got this issue. I am on PC. One time it did crash a little bit later, but usually when he calls for the mech.

[LL-woLf]

+1

[OddSaidAlex]

+1, crashed twice on delivering what should have been the final blow during Phase 2. Went through fine the third time I ran the fight though.

[supertales]

+1 please fix the game cant progess.

[Thom]

Also having this issue. Very frustrating after completing phase 1 but unable to finish.

EDIT: For anyone still having this issue, changing the game version back to 1.0.2 fixed it for me. Right click your game in your library, in the Betas tab change back to older version.

[soulreaver99]

Have the same issue. As of Feb 2024 this still has not been resolved

[MrCake]

Still having this issue on Legion Go (amd), even while removing costume parts etc...
The crash occurs after the 3 'tutorial' popups at the very beginning of the mech fight after phase 1.
Tried 1.0.2 also, to no avail.

Edit: Tried on another desktop PC with nvidia, also crashing at the same point...

[( . Y . )]

+1 also having this issue June 2024. also tried removing all costume stuff. crashes at the beginning of phase 2

edit: i reverted to 1.0.2 and then reverted back and somehow it worked after this, not sure what got fixed

[Foxtrot]

Dealing with this. Reverting versions, uninstalling/reinstall, removing costumes, no skips, no v-sync, nothing is working. I'll never get to finish this game.

[Silver274]

Having this issue as of August 10th 2024. The games crashes everytime without fail on the second phase of the Ishmelga Rean fight. I haven't been able to find a working fix for it yet

[Silver274]

Originally posted by Silver274:

Having this issue as of August 10th 2024. The games crashes everytime without fail on the second phase of the Ishmelga Rean fight. I haven't been able to find a working fix for it yet

As others have mentioned it looks like going back to version 1.0.2 on the betas section for the game fixed it for me