After updating to 5.0, game always launches in window at an unscaled resolution

[logancollins]

Apologies if this is something obvious, but I've been trying to tweak the display settings both in-game and in the FFXIV.cfg file this morning to no avail.

After updating to XIV on Mac 5.0, the game now always launches in a window (despite it being set to "Full Screen"), and that window is about 4x larger than my actual screen size, so the game is mostly offscreen (which makes tweaking configuration a process of trial and error. 😅). I'm guessing the 4x issue is an issue somewhere scaling the actual display pixel resolution to account for Retina (as this is on my 2020 M1 MacBook Pro's built-in display.) AFAIK, none of my settings have changed recently, and are pretty much standard. My in-game resolution is set to 3456x2234 @ 120Hz, which is what it's been set to for as long as I can remember with XIV on Mac (aka 2x the "logical" resolution of my MacBook Pro's Retina display).

Switching the in-game settings to Windowed, then back to Full Screen doesn't seem to change anything. Lowering the game resolution does scale the window down to bring it fully on-screen, but no resolution I seem to set seems to properly account for the Retina display, so getting it on screen will leave everything slightly pixelated. The "Enable macOS Scaling" option is still enabled in the XIV on Mac preferences.

However, as I make changes to the in-game settings, I'm regularly also getting an "An unexpected error has occurred. Exiting FINAL FANTASY XIV" error message from, I presume, the game and Wine. I'm not sure if this is related to all this, or just another issue around the underlying updates to Wine and such, but I wanted to mention it too.

I'm attaching screenshots of the XIV / Wine game window, the in-game settings from the title screen, and the actual relevant config file section on disk.

For the time being, I'm going to roll back to 4.17.5 (which appears to be the latest version still on the website). Again, this is very likely just something obvious that's changed between 4.17.x and 5.0 that I'm not taking into account, but I'd appreciate any direction on how to get it fixed! If it isn't, and might actually be a bug, then I'm happy to provide any details or try anything that might help diagnose things.

Thank you!