TL;DR
Quick Facts
Official problem list
Processing overload, co-op instability, overheating, cluttered effects
First settings check
Do not use 60 FPS unless your device has clear headroom
Best readability fix
Turn the virtual pad display off
When to suspect hardware
If you are below or barely on the current store floor
Quick Answer
Quick Answer
The official CBT report already tells us what the real performance pain points are: processing overload, co-op connection stability, devices overheating, and graphical effects making attacks hard to read. So the safest fix order is: first verify your phone still meets the current store requirement, second stop forcing expensive settings like 60 FPS if the phone has no spare headroom, third reduce visual clutter with options like virtual pad off and cutscene off, and fourth test whether the problem only happens in co-op or other effect-heavy modes. This page stays with low-risk fixes because the public sources do not yet publish a big advanced graphics menu.
Fix Order That Matches the Evidence
| Priority | What to check | Why it comes first |
|---|---|---|
| 1 | Store-page compatibility | If the hardware is below the live floor, the rest of the fixes are guesswork |
| 2 | Frame-rate and visibility settings | Game8 publishes concrete launch settings advice here |
| 3 | Heat and session length | Official feedback specifically flags overheating and processing overload |
| 4 | Mode-specific testing | Co-op and other busy modes can fail even when story play feels fine |
The Safest Fixes to Try First
- Recheck your device against the live App Store or Google Play requirement.
- If your phone is already warm or stuttering, do not force 60 FPS. Game8 recommends 60 FPS only when the device has room to spare.
- Turn virtual pad display off. Game8 recommends it because it improves visibility without removing movement control.
- Turn cutscene playback off for repeat farming. This will not solve raw lag, but it does remove wasted time and helps long sessions feel lighter.
- Restart before co-op or shrine marathons if the phone is hot. This is an inference from the official overheating and overload reports, but it is a low-risk one.
How to Read the Symptom Correctly
If the problem is blurry or unreadable combat
Treat it as a performance issue too. The official CBT report specifically links poor readability to excessive effects, especially in busy runs.
If the problem only appears in co-op
Do not assume your whole account is broken. The official CBT report separately calls out co-op connection stability as an issue area.
If the phone gets hot before it fully lags
Treat that as an early warning, not as a side issue. Official feedback already puts overheating in the same problem cluster as sluggish performance.
What This Page Will Not Pretend to Know
The public sources used for this site do not currently publish a full PC-style graphics breakdown with shadow quality, particle sliders, or exact thermal profiles by device model. That means the honest launch answer is a short troubleshooting ladder, not a fake “perfect settings” spreadsheet.
When to Stop Tuning and Upgrade Expectations
| Situation | Better conclusion |
|---|---|
| Device is below the current store floor | This is a hardware-support problem first |
| Device only barely meets the floor and still overheats | Expect compromises in long or busy sessions |
| Story feels okay but co-op feels bad | Treat it as a mode-specific load problem |
| You already lowered obvious settings and the phone still struggles immediately | Move back to compatibility and thermal limits instead of endlessly tweaking |
FAQ
Should I always use 60 FPS because Game8 recommends it?
No. Game8 explicitly qualifies that advice with “if your device has headroom.” If the phone is already hot or unstable, forcing 60 FPS is the wrong direction.
Why talk so much about visibility instead of only frame rate?
Because Square Enix’s CBT feedback report calls out unreadable enemy attacks caused by excessive effects. If you cannot read the screen, that is already a real performance problem.
Can this page fix every crash or disconnect?
No. It can help you rule out the obvious causes that public sources actually support. Some launch issues may still need game-side client updates.