After upgrading to Catalina yesterday, I was unable to run the FFXIV launcher. Today I decided I was going to wipe my computer and start fresh from scratch but when I tried to run the launcher, same problem. It executed several launcher updates but now I get the following before it even ask me to log in:
The program ffxivlauncher64.exe has encountered a serious problem and needs to close. We are sorry for the inconvenience.
This can be caused by a problem in FINAL FANTASY XIV ONLINE, or a deficiency in Wine, the compatibility layer which is being used to run FINAL FANTASY XIV ONLINE. Contact the makers of FINAL FANTASY XIV ONLINE for help.
I then have 2 buttons. Show Details and Close
Show Details gives me the following....it's long:
Unhandled exception: page fault on write access to 0x00000000 in 64-bit code (0x00007fff6c1d7d5d).
Register dump:
rip:00007fff6c1d7d5d rsp:0000000000238d20 rbp:0000000000238d20 eflags:00010206 ( R- -- I - -P- )
rax:0000000000000000 rbx:0000000000000000 rcx:0000000000000000 rdx:0000000000000024
rsi:0000000000dd62e0 rdi:0000000000000000 r8:00000000000100a8 r9:0000000000005342 r10:0000000000000000
r11:ffffffffff229d20 r12:0000000000000000 r13:0000000000000044 r14:000000000c6ee5b0 r15:000000000001007e
Stack dump:
0x0000000000238d20: 0000000000238e60 000000004b25c9db
0x0000000000238d30: 000000000c6ee5b0 0000000000dd5380
0x0000000000238d40: 0000000000000001 0000000000107aa0
0x0000000000238d50: 0000000000000044 0000000000000000
0x0000000000238d60: 0000000000000190 0000000000dd54c2
0x0000000000238d70: 0000003000000000 0000000000dd5480
0x0000000000238d80: 0000000000000000 0000000000000000
0x0000000000238d90: 0000000000000000 0000000000000000
0x0000000000238da0: 0000000000000000 0000000000000000
0x0000000000238db0: 0000000000000000 0000000000000000
0x0000000000238dc0: 0000000000000000 0000000000000000
0x0000000000238dd0: 0000000000000000 0000000000000000
Backtrace:
=>0 0x00007fff6c1d7d5d (0x0000000000238d20)
0x00007fff6c1d7d5d: ldsl %esp,%edi
Modules:
Module Address Debug info Name (62 modules)
PE 9250000- 948e000 Deferred nss3
PE 49210000- 49213000 Deferred wow64cpu
PE 49220000- 49227000 Deferred winevulkan
PE 49260000- 49265000 Deferred version
PE 49270000- 49274000 Deferred api-ms-win-core-synch-l1-2-0
PE 493a0000- 493af000 Deferred shlwapi
PE 495c0000- 495c6000 Deferred jsproxy
PE 496e0000- 496e4000 Deferred api-ms-win-core-fibers-l1-1-1
PE 4ac40000- 4ac45000 Deferred dxgi
PE 4ad20000- 4ae10000 Deferred user32
PE 4af60000- 4af6c000 Deferred gdi32
PE 4b0d0000- 4b0db000 Deferred advapi32
PE 4b160000- 4b173000 Deferred urlmon
PE 4b210000- 4b23c000 Deferred ole32
PE 4b380000- 4b38b000 Deferred rpcrt4
PE 4b400000- 4b40d000 Deferred oleaut32
PE 4b560000- 4be37000 Deferred shell32
PE 4bf30000- 4bf35000 Deferred shcore
PE 4bf50000- 4bf70000 Deferred wininet
PE 4bfd0000- 4bfdd000 Deferred mpr
PE 4c000000- 4c006000 Deferred ws2_32
PE 4c040000- 4c0ba000 Deferred winmm
PE 4c100000- 4c106000 Deferred iphlpapi
PE 4c120000- 4c127000 Deferred winhttp
PE 4c1f0000- 4c1f6000 Deferred imm32
PE 4c220000- 4c227000 Deferred winemac
PE 4c790000- 4c794000 Deferred api-ms-win-core-localization-l1-2-1
PE 4c7b0000- 4c7b4000 Deferred api-ms-win-core-sysinfo-l1-2-1
PE 4c930000- 4c934000 Deferred api-ms-win-appmodel-runtime-l1-1-1
PE 4c940000- 4c944000 Deferred atlthunk
PE 4c950000- 4c975000 Deferred ieframe
PE 4c9e0000- 4ca33000 Deferred comctl32
PE 4cb20000- 4cb24000 Deferred usp10
PE 4cb60000- 4cb72000 Deferred mshtml
PE 4cd60000- 4cd70000 Deferred msvcrt
PE 4ce20000- 4ce27000 Deferred wsock32
PE 4ce40000- 4cee5000 Deferred comdlg32
PE 4cf30000- 4cf3d000 Deferred winspool
PE 4cf80000- 4cf84000 Deferred msimg32
PE 4cf90000- 4cf97000 Deferred netapi32
PE 4cfc0000- 4cfc5000 Deferred psapi
PE 4cfd0000- 4cfd5000 Deferred rasapi32
PE 4cff0000- 4cff4000 Deferred rasdlg
PE 4d000000- 4d004000 Deferred secur32
PE 4d040000- 4d057000 Deferred setupapi
PE 4d0b0000- 4d0b4000 Deferred userenv
PE 4d0d0000- 4d0d5000 Deferred uxtheme
PE 4d100000- 4d106000 Deferred wintrust
PE 4d140000- 4d185000 Deferred crypt32
PE 4d220000- 4d225000 Deferred bcrypt
PE 4d240000- 4d249000 Deferred wineps
PE 4d2b0000- 4d2b4000 Deferred kerberos
PE 4d4e0000- 4d4e5000 Deferred dwmapi
PE 4d500000- 4d506000 Deferred dnsapi
PE 4d620000- 4d625000 Deferred msctf
PE 65fc0000- 660aa000 Deferred mozglue
PE 69c40000- 6dcd6000 Deferred xul
PE 70880000- 70963000 Deferred lgpllibs
PE 7b410000- 7b5cf000 Deferred kernel32
PE 7bc20000- 7bc33000 Deferred ntdll
ELF 7c400000- 7c404000 Deferred <wine-loader>
PE 140000000- 140cde000 Deferred ffxivlauncher64
Threads:
process tid prio (all id:s are in hex)
00000008 winewrapper.exe
00000009 0
0000000c services.exe
00000036 0
00000022 0
0000001f 0
0000001a 0
00000016 0
00000011 0
0000000e 0
0000000d 0
0000000f winedevice.exe
00000017 0
00000015 0
00000014 0
00000010 0
00000018 plugplay.exe
0000001c 0
0000001b 0
00000019 0
0000001d winedevice.exe
00000024 0
00000023 0
00000021 0
00000020 0
0000001e 0
00000025 explorer.exe
00000029 0
00000028 0
00000027 0
00000026 0
00000030 (D) C:\Program Files (x86)\SquareEnix\FINAL FANTASY XIV - A Realm Reborn\boot\ffxivlauncher64.exe
0000004e 0
0000004d -1
0000004c -1
0000004b 0
0000004a 0
00000049 0
00000048 0
00000047 0
00000046 0
00000045 0
00000044 0
00000043 0
00000042 0
00000041 0
00000040 0
0000003f 0
00000032 0
00000031 0 <==
00000034 rpcss.exe
0000003c 0
0000003b 0
0000003a 0
00000039 0
00000038 0
00000035 0
System information:
Wine build: wine-4.0-7854-g7f50cfe753c
Platform: x86_64
Version: Windows 7
Host system: Darwin
Host version: 19.0.0
MacOS Catalina - Launcher Can't Run
Printable View
-
10-09-2019, 11:18 AMSynfulMacOS Catalina - Launcher Can't Run
-
10-10-2019, 02:05 AMworldofneil
Sorry, but Catalina isn't supported yet and it's not expected to be until "late November":
https://eu.finalfantasyxiv.com/lodes...53c7cb0549f5cb -
10-10-2019, 06:45 AMCatwhoI overheard the Help Desk guys in my office warning everyone to NOT install Catalina. It broke a bunch of things, including the testing software we use.Quote:
Originally Posted by worldofneil
-
10-10-2019, 08:16 AMHyperiaThere are quite a few issues with the OS, it got pushed out too early. I probably would't recommend upgrading an Apple OS until its on its .2 update. With Steve gone, their quality control has gone down hill.Quote:
Originally Posted by Catwho
-
10-10-2019, 08:28 AMSebazy
It's not so much a quality control thing, rather there's a few fundamental changes to the file system as well as 32bit software getting cut off hard (Which has been looming for a few years now).
-
10-10-2019, 08:44 AMSynful
Honestly, this whole thing is completely ridiculous. I just purchased Shadowbringers, reactivated my SE account subscription, only to not even be able to run it. No warnings when I was buying the game from the SE store, nada. Now I can sit here and not play for 2 months (hopefully it's out by then) or reward SE for this failure by buying another platforms version? $40 + $15 wasted.
...and no, I'm not interested in wiping my computer and trying to go back to a previous version of MacOS just for 1 game and to cover for this screw up. I just want my money back at this point. -
10-10-2019, 10:49 AMCleanse
You should be able to restore your Mojave data if you have a Time machine backup.
-
10-10-2019, 11:00 AMsavageink
I saw the message that catalina wouldn't work on the lodestone and when i opened my imac and it said it wanted to update, i told it "no" and turned off auto update until the problem is fixed. It's not like all my software that worked yesterday will magically stop working because i'm not running catalina. And frankly, since i have a lot of apps I need I probably won't bother until I'm absolutely sure they won't break. At least it's not like the good old days where I had to run OS9 and X seperately to complete projects.
The reason I mention the lodestone, is that it's listed in special messages. So, it's been on the Lodestone and in the App and on your Launcher since it was posted on the 1st. -
10-12-2019, 02:12 PMDurianGray
I'm having the same issue! Sad to see there's no current resolution! :(
-
10-12-2019, 03:42 PMArngrim_GreyasheYou do realize that it's not SE's fault that Apple's OS broke, right?Quote:
Originally Posted by Synful
-
10-12-2019, 05:08 PMSebazy
The flip side of that is that Apple has been putting out warnings that this was impending for roughly 2 years, not to mention that the new OS has been available for developers to test and preview for a month or so.
-
10-12-2019, 11:12 PMSynfulYou do realize you just showed you have absolutely no idea what's going on, right?Quote:
Originally Posted by Arngrim_Greyashe
-
10-13-2019, 12:37 AMSaefinnIt is Apple that's broke it, that's not really something the devs have control over. But they are making a work around to support whatever changes Apple have made with the new OS release. So I don't think it's ridiculous on SE's part, or heck, Apple's.Quote:
Originally Posted by Synful
New OS releases can break games and other software. This is nothing new and is one of the things I've always been wary of before upgrading, and is one reason not everybody jumps into a new OS release when it has just come out. There are risks and this is one of them. This is also where console gamers laugh at us. This is less likely to happen to them.
And Apple, Linux and Windows users have had this issue for years. These issues get resolved by companies patching software, people finding work-arounds and people releasing unofficial patches. The dev team is working on patching it, but depending on what broke, that isn't necessarily a quick and easy fix.
As for the lack of a warning at purchase? But they list the System Requirements. I just checked the Square Enix store and it only gives macOS Mojave 10.14.3 as the OS requirement for the Mac version of the game, Catalina isn't advertised as working and there's no "and later" to suggest later versions work (interestingly, it does for Windows).
It is the purpose of the System Requirements to communicate what system configurations it should run on. Whilst yes, they could put out a big warning label at purchase but who does that? And they would only have control in that respect with the Square Enix store, if people bought from Steam, Amazon etc. then they're not going to see it. But then, before they buy people should really check the system requirements.
If your operating system isn't listed, then the sensible thing is to look up if it will run or just take the risk and see if it works then accept the consequences if it doesn't (I fit into that category). It's a new OS release, so there's a chance for compatibility issues.
And you only need to open the lodestone to see there's a notice about MacOS Catalina, which is where SE keeps the community up-to-date with news. -
10-15-2019, 02:42 AMOriWhitedeer
This literally just happened to me as well. Im going to uninstall and reinstall Mojave to see if that works. Unfortunately Apple changed the way it does Time Machine so its practically non functional, I tried to revert only to find that none of my prior snapshots were saved...so I'll post back if that's a viable option.
-
10-15-2019, 04:33 AMArngrim_GreyasheThis response proves that you have no idea what's going on. Maybe do some research.Quote:
Originally Posted by Synful
-
10-15-2019, 04:56 AMSebazySE's client is literally a multi layered bodge. The only surprise here is that they still have the gall to charge for it, it should either be a proper native client or it should be a free addition to the Windows licence.Quote:
Originally Posted by Arngrim_Greyashe
-
10-16-2019, 06:01 PMSynful
People have a seriously weird idea of "broke". Catalina is working as intended and exactly how everyone had been told it would be for well over a year. It's on SE and whoever they have contracted that in over a year, they couldn't properly update their client to 64-bit. If other people did THEIR research, they would know this. FFXIV is literally the only still updating piece of software I have that was not properly updated to 64-bit in time for Catalina.
As for the whole "this happens sometimes and they'll fix it" idea...sure. My problem is that we are looking at nearly 2 months until their estimated fix and even that can slip further. 2 months to fix the launcher is, yes, ridiculous.
Amazing the people that will make excuses for SE's poor support for a platform they still charge full price for. -
10-16-2019, 06:12 PMLalaRu
Upgrading an operative system, before checking if all your software inside is ready for it, is always a bad move.
The "poor support" you are referring to, is the one that warned its users even before the o.s. was released (warning issued Oct,2, and o.s. released Oct,7) ? Ok.Quote:
Originally Posted by Synful
-
10-17-2019, 10:42 AMGilroyKilroyTrue they did but you are assuming people read these messages on a daily basis and noticed it. If they cared it would have been on the launcher weeks before Catalina, not a post here 5 days before. I personally came to research the issue only after I upgraded to Catalina and saw it didn't work. So in order to keep playing I had to create a Mojave partition to boot into just to play FFXIV.Quote:
Originally Posted by LalaRu
If SE truly wanted to support the Mac they would have been on top of betas and had a working version on day 1. I'm sorry, this is SE's fault, not Apple's.
P.S. It didn't even occur to me FFXIV would be a problem since they did do a 64-bit upgrade a few months ago. I thought that was to have Catalina support. -
10-17-2019, 11:01 AMGilroyKilroyI decided it was easiest to just create a Mojave volume to boot into. You have to copy the game itself, and all parts (like from ~/Library/Application Support/FINAL FANTASY XIV ONLINE and ~/Preferences/com.square-enix.finalfantasyxiv.plist), to the volume. The biggest issue was finding the Mojave installer to install with. Google is your friend for that ("mojave installer download").Quote:
Originally Posted by OriWhitedeer
-
10-17-2019, 12:16 PMMistyregions
Lets back track to the real problem. You dont buy a Apple product to play video games.
-
10-17-2019, 05:35 PMXiomara
The problem is that the Mac client uses Wine to power the Windows version of the game, and Catalina gutted everything Wine uses to run it's Windows emulation. So it's not SE's fault, they are waiting on CodeWeavers (the Wine developers) to fix Wine, and they've been working on this for months.
If anything it's SE's fault for offering a non-native Mac client in the first place. -
10-17-2019, 06:27 PMSaefinn
With using Wine, yeah that's not an ideal implementation. but Mac development can present its own issues, particularly in porting something that wasn't built to work on Mac in the first place. As I understand it Mac support was something considered at a later date.
So I can understand why getting it to work through Wine was a given solution, especially if they've got it to work and if the alternative was "no mac support" should a proper implementation be too time consuming, but the downside is they are relying on a third party.
Even on the assumption people don't read the notices, it isn't sensible to upgrade without checking your software still works, this wouldn't have taken much to do as the information is easily accessible.Quote:
Originally Posted by GilroyKilroy
As for how soon they release the notice. If they left it to the last minute to test, then yes that doesn't look good for how they see Mac support. I hope this isn't the case, but I accept it is perfectly possible that it was an after thought
There too also exists the possibility they were working on trying to get a fix implemented for Catalina release but hit a wall and figured better to set an alternative deadline and put a notice out of the issue. -
10-18-2019, 06:35 PMReih
For me it just means I can't play FFXIV and won't be paying this month's fee. Going back to Mojave is because work not possible. See ya'all when this gets fixed.
-
10-18-2019, 11:56 PMLalaRu
Well, if Nintendo's Switch were powerful enough, I don't be surprised to see xiv there. I remember Mr. Yoshida told he will like have the game on every platform possible. "possible".
Maybe Mac platform were on the edge of do it/ do't do it but it was decided to do it.
To Mac users, I hope the "Catalina incident" won't reflect on future decisions if continue to support Mac or not. You know, SE is a business not a charity and if costs/revenue for a given platform passes the red line... -
10-19-2019, 12:08 AMDumdogsWorld
I have no experience with Macs, but if Macs use WINE to run Windows games, then I'll speak with my experience with WINE on Linux. WINE always seems to be outdated in its support of DirectX and other Microsoft apis that are updated on a per-OS basis. Even if it runs some DirectX 11 games, others are likely to just flat-out crash.
Have you tried the 32 bit client and launcher? They are still being shipped out to computers, but without technical support.
Also, the launcher, unlike the client, makes heavy use of Internet Explorer apis. Have you tried one of the various third party launchers around the web? I don't think they're against the TOS because they don't really interact with the game at all - they just log you in and launch the client. -
10-19-2019, 12:16 AMLalaRuFor which reason they exists in first place?Quote:
Originally Posted by DumdogsWorld
-
10-19-2019, 12:21 AMVesparThey warned users of this a few weeks back. They did what they can do. It's not their fault Apple rushed Catalina.Quote:
Originally Posted by Synful
-
10-19-2019, 12:49 AMDumdogsWorldThey're usually just independent programming projects written by hobbyists and what-not. Often for reasons like this.Quote:
Originally Posted by LalaRu
If you find one that just does the bare minimum to securely encrypt/decrypt the connection request and then passes control to the client, it might have a higher chance of working due to having a simpler executable. -
10-24-2019, 10:30 PMXiomaraThat's the problem, Catalina's kernel has had it's 32 bit support gutted. WINE was using the 32 bit windows libraries to get stuff done, but it can't because the Catalina kernel refuses to run 32 bit code, so CodeWeavers are currently working on some sort of wrapper to bypass this restriction as the hardware will always be 32 bit compatible.Quote:
Originally Posted by DumdogsWorld
-
11-05-2019, 04:56 AMTenchiNoRyu
Kinda funny. I knew this was going to happen, but had to update laptop for work (software developer). So I'm back to having my Linux desktop run it through Lutris (via WINE and DXVK) and then stream it to my laptop via Steam stream play^^ Works flawlessly on linux with DXVK in dx11 mode!
I look forward to being able to play away from home again, but am just glad that I had a mac client for a while... maybe someday we'll get a native client, but until then I'm grateful for being able to play it at all^^ That said, this is the danger in non-native "ports"... Hoping this wont leave a sour taste in anyone's mouth, SE's or customer's. -
11-05-2019, 05:07 AMMsQi
Always research before moving to a new version of any OS. This goes for anything. There are a lot of Mac users advising against using Catalina for various reasons.
I'm still on High Sierra and it works fine. -
11-05-2019, 05:52 AMTenchiNoRyu
so...
I just tried the client.... after a bootloader update it seems to be working again!... if it still doesn't work for you, the only thing I've changed is giving "Full Disk Access" in Privacy&Security. -
11-05-2019, 08:15 AMKacho_Nacho
Just goes to show, not everyone reads the warnings on the Lodestone.
-
11-05-2019, 12:34 PMrance-samaThis. It's not difficult.Quote:
Originally Posted by Mistyregions
With an overpriced Apple computer you can get a decent, stable gaming rig. -
11-05-2019, 01:06 PMMsQiSometimes people have to get or only have access to a particular computer. Not everyone can just go out and buy a computer.Quote:
Originally Posted by rance-sama