Current State Mac (June/2020)

[reiichi]

The trick is that the macOS version would probably need to draw more from the PS4 version than the Windows one in other areas; PS4's "Orbis" operating system is derived from FreeBSD, and macOS's userspace derives from FreeBSD as well. But Orbis has diverged in a number of places and has custom functionality that wouldn't exist on macOS or Linux/BSD systems. Add to that the fact that while older versions had to have been processor-agnostic (i.e., back when PS3 was supported), there's no guarantee they aren't using assembly blocks in the code to speed up processing of certain tasks; the PS4 is an x86-64 architecture a'la Windows PCs (and current Mac hardware), and if they have blocks like that in there, that'd be an obstacle to porting to ARM-based systems.
/

Gonna focus only on this part because I'm in general agreement with everything else.

While Darwin does hail from BSD roots, the overlap with actual BSD when it comes to anything graphical is basically nonexistent as Apple's frameworks are nothing like what you'd get out of something more generic. It's fine for dev/cli stuff, but that's about where compatibility ends. But even on that note, the kernels are completely different and even projects like porting a BSD driver over to macOS is a monumental task, like the projects for intel wifi cards.

I'd imagine they can probably compile for general platforms, but that there's nothing currently done to target Vulkan, let alone Metal in their Luminous-ish Crystal Tools+ fork. So at a minimum, we're likely to still see DirectX calls being converted over, but that's honestly not super horrible overhead when you consider some games on DXVK are performing better on Linux than natively on Windows.

So there's maybe a chance we'll see a future version of the Mac port maybe being a weird amalgamation of Windows client bases compiled with WineLib. ...but most likely, we'll see WINE/Crossover getting custom x86 to ARM support if Rosetta 2 doesn't perform well enough or when it's eventually dropped in like 2 years. It wouldn't be the first time as the ancient DarWINE project had x86 to PPC for pre-Intel Macs with varying success.

[Packetdancer]

While Darwin does hail from BSD roots, the overlap with actual BSD when it comes to anything graphical is basically nonexistent as Apple's frameworks are nothing like what you'd get out of something more generic. It's fine for dev/cli stuff, but that's about where compatibility ends. But even on that note, the kernels are completely different and even projects like porting a BSD driver over to macOS is a monumental task, like the projects for intel wifi cards.

Sure, which is why I focused on Vulkan for the graphical stuff; you can map Vulkan to Metal (Apple's graphical API) via MoltenVK. (And the kernel is, as you rightly point out, completely separate; Darwin uses Mach as the basis of its kernel, and just takes the userspace and general library APIs from FreeBSD.) Where I meant the BSD similarities were for things like general system APIs; saving off configuration files, dealing with timers, networking APIs, etc. The Windows client likely uses Win32 APIs for that, but the PS4 Orbis system uses standard FreeBSD APIs for that and so the PS4 version likely uses those APIs, and those are available on macOS.

I.e., a translation/port would want to take the DirectX graphics layer (since you can do DirectX -> DXVK -> Vulkan -> MoltenVK -> Metal, and there's no similar GSMX -> Metal translation path that I'm aware of) or write a native Vulkan one (longer-term) to pick up Linux and then use MoltenVK directly, but probably would have less work if it took the PS4 filesystem/networking layers. Because while the kernel drivers for WiFi would be very different between FreeBSD and macOS, the actual networking calls in a userspace application are the same.

So I think we're actually on the same page there.

[justinhuang]

With Apple's recent announcement they're moving their entire platform to their custom ARM chips, this should be getting a bit more interesting.

I imagine SE will not be making any major changes aside from waiting for WINE to ensure it's safely compatible with Rosetta 2 to translate x86 code while also running all of the DX -> OGL/Vulkan things too. I would not be surprised if we see instances of "FFXIV cannot be run on the newest Macbook" messages come the official release.

Indeed. I watched the presentation and I’m also interested in what this transition change Mac version in the future. Whatever the case may be I hope it improve what we have now.

I am also having neutral thoughts on these transition. We saw other companies transition to ARM as well but much of it was not successful. Regardless, as long as it doesn’t affect my day to day tasks, and hopefully not ffxiv, I don’t mind the transition that much.

[pizzy]

I also run a mac with an eGPU My system is a late 2015 iMac, I also was experiencing issues with FPS as well as notices some graphical issues occasionally.

I started messing with the settings and under the Graphics settings, I turned the "Glare" off. By turning that off I am now running between 55 to 65 FPS and no more graphic issues. I was running in the low 40's prior to turning that off.

Maybe this will help you increase performance?

Cheers!

[justinhuang]

I also run a mac with an eGPU My system is a late 2015 iMac, I also was experiencing issues with FPS as well as notices some graphical issues occasionally.

I started messing with the settings and under the Graphics settings, I turned the "Glare" off. By turning that off I am now running between 55 to 65 FPS and no more graphic issues. I was running in the low 40's prior to turning that off.

Maybe this will help you increase performance?

Cheers!

I will try that. Thank you for sharing

[EggySong]

Square Enix ought to consider just building a full-fledged port for Apple silicon. Not only will it future-proof the game for Macs moving forward, but will also likely improve the experience significantly for intel-based macs running Big Sur or later. Not to mention open a pathway onto iOS devices.
Even starting with an iOS port and working it up to Mac via catalyst would give us something that would just work.

[justinhuang]

Square Enix ought to consider just building a full-fledged port for Apple silicon. Not only will it future-proof the game for Macs moving forward, but will also likely improve the experience significantly for intel-based macs running Big Sur or later. Not to mention open a pathway onto iOS devices.
Even starting with an iOS port and working it up to Mac via catalyst would give us something that would just work.

I hope they would take that into consideration but I guess numbers "kinda" influence their decisions.

[Eriane_Elis]

If I were you, I would install Windows 10, you don't have to register, the permanent trial is good. Then install custom signed drivers https://www.bootcampdrivers.com/ Make sure you read the instructions on how to do it because there's only the right way to do it and it's not just click and install.

The reason why you would want the custom signed bootcamp drivers is because Apple doesn't really give AF about it. Now you might ask.. Why would you play it on windows and not mac? Isn't a mac the faster OS? Well, not necessarily. There's a few reasons why but most importantly is that this is a Windows made game and it just works better on it. Plus DX12 support is even better!

On OSX I wasn't getting optimal frame rates and on windows with default drivers I was getting 16fps with 2K screen res set. After installing the drivers I got 60fps at 2k res. So it makes a huge difference.

It's worth the dual boot. I can't stand OSX anyways so I primary boot in windows on an imac, go figure :P