Final Fantasy XIV

After typing in your username and password, just hit enter, instead of clicking the "Log In" button.

Works perfectly fine for me, game plays about the same as windows for the most part.

The launcher gave me no issues whatsoever, ironically.

However, when clicking Log In the game returned a error:

A system error has occurred: -2147467263.
Javascript:ctrEvent('mainForm');

and did not launch.

I opened a bug: bugs.winehq.org/show_bug.cgi?id=47637

The login and launcher window is a web browser. It is not a special FFXIV browser, it is normally Microsoft Internet Explorer.
As many have previously stated, changing the browser window variable may prevent this error from occurring.
Please look over the test result submissions from other users and report whether or not the workaround fixes this issue.
This is not a bug in the FFXIV program, it is a bug in the chosen web browser.

Do you mean edit ~/Documents/My Games/FINAL FANTASY XIV - A Realm Reborn/FFXIV_BOOT.cfg

Changing

BrowserType to 2

From the How-to? I couldn't see anything about browser in Test Result workarounds.

Don't click the "Login" button, just hit enter after having entered your login details.

Thank me later.

Is there any word on when that'll be available? I don't imagine the current Stormblood version works but I've yet to try it.

Give it a try the game engine hasn't changed. If you have problems post here we can raise a bug report, get it working.

I can't get the game to run.
I created a fresh wine prefix and installed DXVK v1.2.1 there. Wine exports are also hidden. The launcher works but when it tries to start the game ffxiv_dx11.exe it opens a message window saying "The latest version of DirectX is required to play FINAL FANTASY XIV. Please download and install DirectX End-User-Runtime, then restart then game. -----(0)". The same happens if I try to start ffxiv_dx11.exe directly.
DXVK seems to be working correctly as I can see its output when running the launcher. I'm using wine-staging with wine commit 1d9a3f6d12322891a2af4aadd66a92ea66479233, as this version seems to have the 404 error fixed.

I fixed it by installing DirectX directly using the installer from www.microsoft.com/en-gb/download/details.aspx?id=8109
I was trying to do it via winetricks previously but that didn't show any effects.

I'm able to get the installer to run, and I can get around the 64bit launcher's 404 error, however, both the 32bit and 64bit launchers give me a -2146697208 HTTPS error.

I remember awhile ago the solution was to just remove the Web folder, but I don't actually *have* a Web folder to remove, so I'm very lost.

You can run the "old" launcher. See How-To.

The droid fonts are fine for running the launcher--allfonts or corefonts are not required. Simply run:

```
WINEPREFIX=$HOME/.local/share/wineprefixes/ffxiv WINEARCH=win32 wine wineboot
winetricks prefix=ffxiv d3dx11_43 d3dx9_43 droid quartz xact
```

If you do not have an OSX license, you will also need, or else you will not be able to log in:
```
winetricks prefix=ffxiv hidewineexports=enable
```

This doesn't fix the 404 issue; that runs deeper: bugs.winehq.org/show_bug.cgi?id=47069.

Hey there,
I had FFXIV running for a while under wine....3.something. However, I then upgraded to wine 4.4, and since then I haven't even been able to get the launcher to load :-( I have since upgraded to 4.6 but nothing changed.
All I get now is "Unable to load patch files [11003] [20402] [19901] [13]

Anyone else had this problem? I tried creating a new 32-bit wine prefix as I know 64 bit can cause problems but that didnt help

If you are getting a 404 error on the Launcher then your issue is the new update has broken wine support (Launcher version 2019.04.19.1. I've been looking around for fixes but have not come across one that works yet.

A bit late to be responding, but could you possibly provide logs if you're still encountering this?

Haven't used FFXIV for a few months so was disappointed with outcome today.

I'm using staging-319 and DX9 in 32-bit prefix and the game launches and the graphical output is OK. Sadly, when I move or pan the camera the game becomes jerky, smooth, jerky. I created a fresh prefix and installed xact and quartz with winetricks but any other tips would be much appreciated.

[On a side note I created a 64-bit prefix and installed dxvk 0.91 with winetricks and the launcher came up then crashed.]

First line of Program Error Details when trying to run dx11, 64-bit prefix+dxvk0.90/0.91:

Unhandled exception: unimplemented function vulkan-1.dll.vkGetInstanceProcAddr called in 32-bit code (0x7bc77b1

So I've been using DXVK with great sucesses recently on a multitude of games like WoW, GTAV, etc etc, but for some reason, when I try to use it for ffxiv, upon clicking Play (DirectX 11) I get a pop-up saying I must have the DirectX Runtime installed.

For other games, this isn't an issue at all, in fact I've been playing DX11+ only games perfectly fine on the same wineprefix for some time now, WoW, D3, Warframe and EvE Online all detect and use the Dx11 offered by DXVK, however FFXIV won't.
At first I thought it may have something to do with how the launcher handles launching the game, perhaps the 'export DXVK_FAKE_DX10_SUPPORT=1 line isn't getting passed from the ffxivboot to the launcher then to the game, but then trying to just launch ffxiv.exe vs ffxiv_dx11.exe provided more insight.

Upon attempting to just launch ffxiv.exe I get the error 'Unable to launch application. Launch using the ffxivboot.exe file.(0)'
but when I try to launch the dx11.exe file, through a terminal passing env DXVK_FAKE_DX10_SUPPORT=1, it still gives me the directX runtime error.

How do you all get DXVK working? What script do you use to launch the game? What am I missing?


version: wine-3.16 (Staging) using dxvk .80

Updating my NVIDIA driver from 396.51 to 396.54.06 seems to have resolved this issue.

Before I post a negative test, I wanted to ask the community if there's an obvious fix. This is my very first time using Wine for anything so I'm sure I'm just missing something small.

OS is Kubuntu 18.04. I am using Wine 3.14 (devel). Installed winetricks. Created a 32 bit prefix. Installed steam & used that to download & install FFXIV. Installed DirectX9 and xact using winetricks. Changed the three settings in the config files as described in the instructions (DirectX setting, Browser setting, and Cutscene setting).

Had absolutely no problems getting the launcher up and running - I logged in and it downloaded all of the game updates. The DirectX9 button came up to launch the game. I clicked it. It took me to the upcoming maintenance reminder (in the launcher). Then when it tries to load the main menu of the game, I get "An unexpected error has occurred. Exiting Final Fantasy XIV." with the error codes
ffxiv.exe+DA500B
ffxiv.exe+F2D261
ffxiv.exe+DDB780
ffxiv.exe+19649A
and four other similar ones.

Searching for those error codes didn't really get me anything. Thoughts? What step am I missing?

Are you launching the appropriate executable from the wineprefix?

"WINEARCH=win32 WINEPREFIX='~/.ffxiv_prefix/' wine '/your/path/SquareEnix/FINAL FANTASY XIV - A Realm Reborn/boot/ffxivboot.exe'

What is the console output from your version of this?

Console output:

009d:fixme:msg:ChangeWindowMessageFilter 4a 00000001
009e:fixme:ver:GetCurrentPackageId (0x106fe9c (nil)): stub
009d:fixme:win:EnumDisplayDevicesW ((null),0,0x33f194,0x00000000), stub!
009d:err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
009d:fixme:winsock:WSALookupServiceBeginW (0x33eb38 0x00000ff0 0x33eb80) Stub!
[0906/160749:ERROR:network_change_notifier_win.cc(160)] WSALookupServiceBegin failed with: 8
009d:fixme:iphlpapi:NotifyAddrChange (Handle 0x33ea10, overlapped 0x3278dc8): stub
009d:fixme:winsock:WSALookupServiceBeginW (0x33eb78 0x00000ff0 0x33ebc0) Stub!
[0906/160749:ERROR:network_change_notifier_win.cc(160)] WSALookupServiceBegin failed with: 8
00a8:fixme:ntdll:NtLockFile I/O completion on lock not implemented yet
009f:fixme:d3d:state_linepattern_w Setting line patterns is not supported in OpenGL core contexts.
00b9:fixme:ver:GetCurrentPackageId (0x44bfe9c (nil)): stub
00ba:fixme:thread:SetThreadIdealProcessor (0xfffffffe): stub
00bb:fixme:thread:SetThreadIdealProcessor (0xfffffffe): stub
00bc:fixme:thread:SetThreadIdealProcessor (0xfffffffe): stub
00bd:fixme:thread:SetThreadIdealProcessor (0xfffffffe): stub
00be:fixme:thread:SetThreadIdealProcessor (0xfffffffe): stub
00bf:fixme:thread:SetThreadIdealProcessor (0xfffffffe): stub
00b8:fixme:win:EnumDisplayDevicesW ((null),0,0x33f064,0x00000000), stub!
00b8:fixme:win:EnumDisplayDevicesW ((null),0,0x33f474,0x00000000), stub!
00b8:fixme:d3d9:D3DPERF_SetOptions (0x1) : stub
00b8:fixme:d3d:debug_d3dformat Unrecognized 0x5a574152 (as fourcc: RAWZ) WINED3DFORMAT!
00b8:fixme:d3d:wined3d_get_format Can't find format unrecognized (0x5a574152) in the format lookup table.
00b8:fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24) WINED3DFORMAT!
00b8:fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the format lookup table.
00b8:fixme:win:EnumDisplayDevicesW ((null),0,0x33f0e4,0x00000000), stub!
00b8:fixme:driver:D3DKMTOpenAdapterFromHdc (0x33f47c): stub
ERROR: Could Not Get Primary Adapter Handle
009d:fixme:iphlpapi:CancelIPChangeNotify (overlapped 0x3278dc8): stub
009d:fixme:msg:ChangeWindowMessageFilter 4a 00000002
00b8:fixme:xaudio2:XAudio2CF_LockServer (0x192cb3d0)->(1): stub!
AL lib: (EE) SetChannelMap: Failed to match front-center channel (2) in channel map
00b8:fixme:msctf:ThreadMgr_ActivateEx Unimplemented flags 0x4
00b8:fixme:msctf:ThreadMgrSource_AdviseSink (0x195e4530) Unhandled Sink: {ea1ea136-19df-11d7-a6d2-00065b84435c}
00b8:fixme:imm:ImmDisableTextFrameService Stub
00b8:fixme:imm:ImmDisableTextFrameService Stub

"ERROR: Could Not Get Primary Adapter Handle"

What type of card do you have and do you have the appropriate drivers installed?

having weird jerky mouse problems with panning the camera
doesnt do the same when panning with keyboard

on top of that a lot of left clicks act like click and holds instead of just single clicks. has a tendency to drag hotbars around.

Are you having these issues in wine-staging or with Wine-staging + dxvk?

it was winestaging + dxvk but i switched to wine 3.0 x86_64 and now everything runs perfectly. I would honestly give it platinum rating with dxvk if i could get dx9 to work with it instead of dx11

3.1 not 3.0

Have you tried the latest release? It's winehq-staging 3.11.

I'm having this exact issue on 3.16-staging right now, did anyone ever come up with an actual solution for this?

game does run in 64bit wine prefix. i have been into game and played it. also directx 11 does work for me slightly better then directx 9 in limsa by like +3fps. to not galium nine doesnt work with intel graphics cards and has trouble with nvidia. it does work for amd from what i have read not able to confirm.

That's great Stephen, now tell us how you did it and we're in your debt.

on fresh arch build install wine - staging from official repository then run ffxiv setup.exe thats about it. to get equal performance on dx 11 vs dx 9 if you have good dx 11 compatible graphics card use DXVK.

"Gallium Nine does something interesting that few other Linux programs do — it re-implements a technology from Windows. In this case Gallium Nine is an open-source implementation of DirectX 9. As a result it matches Windows in DX9 performance and allows you to play DirectX 9 games at as [sic] performance as close to native as possible...You need to be running the Mesa open-source drivers in order to take advantage of Gallium Nine...This also means that you need to be running the open-source AMDGPU or Nouveau drivers.

"[Y]ou need to be running the open-source AMDGPU or Nouveau drivers", I've never really tried gaming with an integrated Intel GPU. They don't made discrete graphics cards do they it's just shared graphics isn't it?

"If you’re using a NVIDIA card, it’s probably best that you keep running the proprietary drivers and use Wine Staging instead. The performance increase that you’ll see from Gallium Nine will be outweighed by the decrease in performance from Nouveau." So Nvidia owners won't see any advantage.

intel will be releasing dedicated graphics cards in next few years

tried using galium nine get direct x error.

Two things, Stephen;

1) If you would like help troubleshooting your problem, some initial information is essential.
"Not working..." is not enough, what is not working? "get direct x error" What error messages are you receiving, what have you tried to do to rectify the issue yourself?

2) Gallium Nine isn't really supported here, you'd do better seeking advice and support (see point 1) at the Gallium Nine forum.
I. like many, use the proprietary Nvidia driver so I cannot advise you at all.

error is because i am using intel gpu

game wont load character selection screen. fps is great before hand but black screen with forever spinning wheel.

Stephen have you followed the setup instructions. This usually occurs when the game attempts to initiate the opening movie.

yep fixed that a few days ago.

I'm really interested in replicating your results, Thijs. Are you using winehq-devel or staging.

I've already tried -devel on my test build:

Installed winehq-devel (3.9)
Created a ~/ffxiv 64-bit WINEPREFIX.
Installed xact with winetricks to ~/ffxiv.
Ran setup_dxvk thus:
WINEPREFIX="~/ffxiv" bash setup_dxvk.sh
...in both folders, x32 and x64.

I have not have any luck launching FF yet...

I ripped out winehq-devel 3.9 and my current Nvidia drivers (396.24), installed winehq-staging 3.9 and Nvidia drivers with Vulkan support, for my Geforce 1050 Ti, v396.24.02...

I recreated all my WINEPREFIXES and created two for Final Fantasy: ~/.ffxiv32 and ~/.ffxiv64 I installed the dxvk 0.53 drivers (the x32 to the 32-bit WINEPREFIX and the x64 ones to the ...64 prefix).

I installed xact to both prefixes with winetricks.

I couldn't even start the game in Directx 11 (either prefix), I couldn't change to DX11 in the launcher the button would not move across to enable, or by seting DX11Enabled 0 in FFXIV_BOOT.cfg...
The 64 bit prefix caused display problems (dual monitors) it opened on the correct monitor (the primary) but would take any keyboard or mouse input...so no improvement with dxvk...

So I guess there is a lot more involed in setting up dxvk or wine play FFXIV in Directx 11...

After install python-dev, and several other components need to get the alt-launcher working I was able to force DX11 in a 64-bit context...performance was meh, and movement cause tearing. I had th usual fight to get the game full screen on the only monitor it wanted to work on and respond to mouse input and I'm serious beginning to wonder if this simply an exercise in futility (in a multi-monitor setup).

I gaveit one more shot and got Dirext11 working with dxvk 0.53, with the python launcher - MUST USE - 32-bit WINEPREFIX...setup is more than a little clunky and I will have to retrace my steps on another test build if anyone is to emulate me. The python launcher assumes the game is run with the default WINEPREFIX (.wine) so you have want to create prefixes for other games before you start that delete .wine and buld the prefix 32-bit from scratch...happy days.

I spent all day on this, so wait for my instructions before you set out, or you may end up in hell. YMMV

Sorry for the late-ish reply.
So first off, the dx11 client is 64 bit only so you should only have to install the 64 bit dxvk dll's in a 64 bit prefix. I'm using stable wine 3.9 from the arch linux repositories. If you build wine yourself, make sure you have the vulkan headers package installed, otherwise wine will skip building the vulkan parts. For me, staging has a bug with dropping some mouse input in both d3d9 and d3d11 clients so I'm not using staging.

In my experience the official launcher does not work very well in general, so I recommended the custom launcher. This launcher has not been updated in over a year so it should definitely not require any sort of python dev version. I took a quick look at the modules it uses, and all of them are part of standard python 3, for me on arch it worked out of the box. I personally use the default prefix, but using another prefix with this launcher should be as simple as WINEPREFIX=/path/to/your/prefix ./launcher.py

Performance-wise I'm getting a constant 60 fps with all settings on max except real-time reflections and shadow cascading on my RX570 + i7-2600.

I don't have dual monitors myself so I can't really comment on issues about that.

I needed to double check all of my work. So I recreated a 64-bit prefix, installed xact and used the script to install the 64-bit dxvk components. I used the custom python launcher to run Final Fantasy from the 64-bit prefix in DirectX 11 mode.

The result were more as expected. Severe clipping during mouse look / movement. The mouse was looked to monitor 1, which was irritating since the game was opening on monitor 0 (the primary). I could alt-tab out of the game, right click the Xfce4 'task bar' entry and select move to drag the game window to monitor 1. Then I resized the window with practice (alt-tabbing and dragging the window back to to 1 so I could click Yes to confirm applying new settings...) Playing fullscreen, borderless fullscreen and fullscreen were all the same, severe clipping, mouse locked to *monitor* area (so if the game window was smaller than the monitor resolution the mouse would pass out of the game window would was trapped in monitor 1 and would not pass to the monitor 0.

This is all stuff I've seen before with badly working DX11 games and Wine.

I should note that I am not using wine-stable as I couldn't get anything working with it. I'm using wine-staging 3.9, the nVidia proprietary, Vulkan version and dxvk 0.53...I haven't built anything myself.

i have an intel 530hd as my gpu and i dont have any of those issues with wine 3.11 staging. not using DXVK. will test with dxvk

dxvk has almost neligible gains considering potential risk for ban.

Anyone else have this issue?

When I log in, it says "Unable to complete version check. [30410][30607][10009][19900][-2146893051]"

I've pretty much installed the game using everything at default using Wine 3.2 x86_64 through the Lutris frontend. The only Winetrick I used was to download Quartz, WinHTTP, wininet, ie6 through 8, and MS Core Fonts. xact and xinput were also enabled already. I've installed DirectX 9 from the game's installer and they all show up as installed on Winetricks.

Using browsertype=2 as well.

Bit late in the day, but for others as well, try creating a fresh 32-bit wineprefix. Use winetricks to install xact (only). If you are using a wine staging post 3.4 add a dll override for xaudio2_7 set to native. Good luck.

Gallium nine isn't working properly for me, I usually get 80-90 fps, but it sometimes drops to 15-25 and stays that low for a few minutes. At the same time, the UI sometimes starts flickering which usually results in a crash.

Wine version: wine-staging-nine 2.21 from the arch community repository.
Mesa version: 17.3.3

Using wine 3.0 with nine support and turning on the LOD settings seems to resolve these issues. There's some minor graphical issues with distant models not being lighted correctly a few seconds after they are loaded though.

How did you get nine support in Wine 3.0 if you don't mind. The game is very stable minus the framerate.

I compiled it from github.com/iXit/wine

I have FFXIV installed on an NTFS disk accessible to both Linux and WIndows. I changed the cfg file in the prefix folder with a '0', and also in ~/Documents/My Games for good measure. Despite that, I couldn't get past the infinite loading screen when it tries to load a cutscene at the start. It keeps acting as if I don't have a character created already (loaded into Windows, created a character there, and also tried copying over some files and portions of the cfg file). Any ideas?

Disregard that, I was supposed to put 1, not 0.

Hi mate, I had exactly the same problem on Ubuntu 18.04 LTS.

Resolved by setting "CutsceneMovieOpening 1" in the ffxiv.cfg (was set to 0 on a new install).

Now it works perfectly :)

Lately I've had really bad UI flicker in the game. Sometimes the UI even disappear entirely. I haven't been able to figure out a clear cause, but a few things seem to affect it fairly consistently:
- There's more flicker in the major cities
- There's less flicker in battle
- Non-cutscene conversations have very bad flicker and I often have to hunt for a camera angle that lets me read the text
- Cutscenes are free of flicker
- Having the system configuration dialog open drastically reduces flicker, often eliminating it entirely
- Setting a lower fps cap reduces flicker; 15 fps makes it almost entirely disapper

It's as if the game somehow performs a SwapBuffers without properly flushing the graphics pipeline first. I have no clue how that could happen though.

The flicker seems to have gotten worse after updating 381 Nvidia drivers to 387. A lot of other things were updated at the same time too so it might be something else.

I have Debian unstable, i7-6700k, 16 GB RAM and GTX 980. I'm using Wine 2.22 through PlayOnLinux.

I found out that changing gamma correction to something other than 50 eliminates flicker. Apparently 50 is the default and deviating from it forces the game to take a different rendering path that doesn't have the issue.

The game has a memory leak which will start to cause stuttering and artifacting after about 30 minutes. Turning on LOD and LOD Streaming slows down the leak by a factor of 3 to 5.

Gallium-Nine is completely unnecessary. I have been playing with Wine-Staging since StormBlood launch, and the game runs relatively well at moderate-low settings (between 25-55 FPS with an RX470, running towards the lower end in newer areas of the game) with CSMT and Staging CSMT. Gallium-Nine is also not always available or functional for users, especially those using nVidia cards.
Additionally, you failed to test DX11, which may be partially playable considering recent advances.
The rest of the workarounds may need updating, as I believe but cannot confirm that the opening video no longer breaks the game (perhaps it only broke on the first launch?), and the game can be installed on 64-bit prefixes. The Winetricks workarounds may need testing to see if they are still necessary.

For me the game is unplayable without Gallium Nine. I'm glad you can run it well with wine-staging but for me I get 10-20fps while moving on wine-staging and 80-100 on Gallium Nine.

I have tried to enable DX11 through winetricks and the game wouldn't launch, but maybe someone more experienced with the software could get it working, I don't know.

As for the workarounds I had to do them both. I got a black launcher and an infinite loading screen at separate times before editing the cfg.

Game is also unplayable for me without Nine.