Final Fantasy 14 (39210)

[nstgc]

Final Fantasy 14's installer (after Steam does it's own installing) doesn't have any fonts its seems, favoring [] over actual characters. Even the numbers, so its not that its trying to display Japanese characters and my system is missing them (which is not the case since I occasionally use them myself). Potential UTF-8 problem?

[HereInPlainSight]

Updated: 04-14-20, added WINE and GE-Proton build on 04-19-20:
If you are looking to run FFXIV via Proton, there's a few instructions for current installs:

1. Default Proton will not work. You will need to grab a release from GloriousEggroll's repo and follow his installation instructions.
2. You will need to run the following command:
   WINEPREFIX=$HOME/.steam/root/steamapps/compatdata/39210/pfx winetricks hidewineexports=enable assuming you use the default location for your library of a regular Steam installation. If you do not, adapt the path appropriately.

Other launcher / non-Steam versions instructions:

• If you want to run FFXIV outside of Steam, please use Lutris' Standalone - DXVK version installer.
• If you want to use Lutris to run FFXIV outside of Steam and your game is purchased through Steam, add the -issteam argument to your Lutris configuration for the game.
• If you want to use Steam to run a non-Steam version of FFXIV, set FFXIV's launch options to: echo "%command%" | sed 's/-issteam\(freetrial\|\)//' | sh. (Thanks to jbal91 for reminding me that sed is magic!)

Issues of note:

1. The new launcher is disabled by Steam / GE-Proton by default -- at some point, this will likely stop working. It has an open wine ticket here.
2. If you're using a post-processing injector (ReShade, GShade, etc), the game is hampered by a several-second stutter whenever the mouse is moved. It has an open wine ticket here. You can get a working WINE here (based on WINE 5.4) and a working Proton (built from GloriousEggroll's repo on 04-18-20) here.

Previous updates:
Updated: 07-31-19:
Hello, Warriors of Darkness / Light! If you are attempting to play FFXIV via Proton, it has been greatly simplified!

Once XIV is installed via Steam, simply open the file at ~/.steam/steam/steamapps/compatdata/39210/pfx/drive_c/users/steamuser/My Documents/My Games/FINAL FANTASY XIV - A Realm Reborn/FFXIV.cfg and change CutsceneMovieOpening 0 to 1. (If you are running the demo, always swap 39210 with 312060.)

If you do not see the option to install the game via Steam after purchase, you need to, inside of your Steam client, open Steam -> Settings -> Steam Play, then check both 'Enable Steam Play for supported titles' and 'Enable Steam Play for all other titles', restart Steam when prompted, and you should be set!

Welcome to the community!

---

Original post:
I'm not sure if this is the same issue directly. I've gotten XIV working via Proton, but I had to follow well-known wine answers to get it playable. Namely, I have to edit two files in the steamapps/compatdata/39210/pfx/drive_c/users/steamuser/My Documents/My Games/FINAL FANTASY XIV - A Realm Reborn/ directory.

In FFXIV_BOOT.cfg, I had to edit BrowserType to 2, and in FFXIV.cfg I have to edit CutsceneMovieOpening to 1.

The first change allows me to get to the launcher at this point -- if it's left to its default value I get 'A system error has occured: 404. HTTPS System Error'. Afraid I did the install mid-week, so I'm not sure if this is how I got past nstgc's issue during installation.
Obviously the latter change means I don't get to see the opening cutscene the first time I play the game, but if I leave it at default value, the game launches but hangs up after selecting a Data Center.

As these edit game configuration files I'm not sure if this is something Valve wants to consider for Proton, but at the least it's information.

[kisak-valve]

FFXIV Freezes when Real Time Reflections are enabled

Issue transferred from #627.
@ulzeraj posted on 2018-08-26T05:58:03:

Final Fantasy 14 (ID: 39210) works on DX11 mode after some manual workarounds which are editing the INI files to set browser type to 2, disable the opening cutscene and use winetricks xact into its prefix.

However… graphics stop working immediately after I enable “Real Time Reflections”. Enabling any level of this particular option freezes the game and X11. I can still log into through SSH and there are these messages:

[ 384.698959] [drm:amdgpu_job_timedout [amdgpu]] ERROR ring gfx timeout, last signaled seq=202749, last emitted seq=202751
[ 384.698964] [drm] GPU recovery disabled.

GPU is Saphire R9 390. System is OpenSUSE Tubleweed with kernel 4.18.0-1, using amdgpu and Mesa 18.1.6 LLVM6. Same hardware and game works fine on Windows 10 with Real Time Reflections on.

Thanks for the hard work.

---

@doitsujin commented on 2018-08-26T10:47:10

Please test with LLVM 7 and Mesa 18.2, as suggested in PREREQS.md.

---

@HereInPlainSight commented on 2018-08-26T15:37:13

System info: Gentoo x86_64 | 4.14.65-gentoo | i5-6500 | NVIDIA GeForce GTX 1070 | NVIDIA 396.51

I had previously done the config file edits, just emerged llvm7 and added the xact winetricks to the prefix, switched to DX11 and can confirm I'm able to run with Real Time Reflections at any setting I want.

---

@doitsujin commented on 2018-08-26T16:12:39

@HereInPlainSight The LLVM version is only relevant for AMD drivers because they use LLVM to compile shaders. Mesa needs to be built against LLVM 7 in order to work correctly.

---

@HereInPlainSight commented on 2018-08-26T16:50:18

@doitsujin I wasn't 100% on that because the DirectX11 info seems to indicate that LLVM7 is recommended to avoid GPU hangs, which is mentioned after the drivers section. My gaming on Linux before the new SteamPlay info was fairly casual, so I opted to go safe over sorry.

[ulzeraj]

Using the recommended libs fixed the issue for me but now I have the missing fonts issue described by @nstgc. I should mention that the fonts issue didn’t occurred in OpenSUSE Tumbleweed.

I’ve switched to Ubuntu Bionic in order to fill the requierements described on PREREQS.md. Installing from those repos gave me Mesa 18.3 compiled against LLVM 8.0. I also installed LLVM and CLANG 8 since the document does not make it clear if libllvm8 is enough. I’m still using amdgpu from kernel 4.18.5-041805 which I installed from UKKUU.

By the way the wine and winetricks from Ubuntu default repos are too old and applying xact through them will cause the game to fail on launch.

[ManaHime]

somehow I manage to add those fonts using "winetricks allfonts"
But I seem to be unable to actually input Japanese characters using iBus anthy on Ubuntu 18.04
Can anyone else confirm? (Or is able to write Japanese in FFXIV chat really)

[csos95]

Neither my steam controller or xbox 360 controller works.
They are they both show up in the gamepads list in the setting menu so they are detected, but button presses don't work.

[ulzeraj]

Here the controllers do not work through steam as they should but I've managed to use them through the SDL native system.

For DS4 this works by adding the following variable to your profile (.bashrc or /etc/environment) and disabling the steam controller system.

export SDL_GAMECONTROLLERCONFIG='030000004c050000cc09000011810000,PS4 Controller,a:b0,b:b1,back:b8,dpdown:h0.4,dpleft:h0.8,dpright:h0.2,dpup:h0.1,guide:b10,leftshoulder:b4,leftstick:b11,lefttrigger:a2,leftx:a0,lefty:a1,rightshoulder:b5,rightstick:b12,righttrigger:a5,rightx:a3,righty:a4,start:b9,x:b3,y:b2,platform:Linux,050000004c050000cc09000000810000,PS4 Controller,a:b0,b:b1,back:b8,dpdown:h0.4,dpleft:h0.8,dpright:h0.2,dpup:h0.1,guide:b10,leftshoulder:b4,leftstick:b11,lefttrigger:a2,leftx:a0,lefty:a1,rightshoulder:b5,rightstick:b12,righttrigger:a5,rightx:a3,righty:a4,start:b9,x:b3,y:b2,platform:Linux,'

Thing is... I should be able to disable the controller just for that game but Steam somewhat renames the device node paths so to make it work I need to disable everything. The device renaming thing do not happen in OpenSuSE.

[legluondunet]

The cinematics do not play, could be related to issue #1464.

[csos95]

I found the solution to my issue here: https://www.reddit.com/r/archlinux/comments/9bl3l7/steam_controller_not_working_with_protonsteam/

The issue was that two inputs were being created for one controller.
running sudo rmmod hid_steam and restarting steam fixed the issue.

[kisak-valve]

Failure to load embedded web page in game launcher (appid: 39210)

Issue transferred from #2183.
@TenaarFeiri posted on 2019-01-02T23:58:28:

Compatibility Report

• Name of the game with compatibility issues: Final Fantaxy XIV Online
• Steam AppID of the game: 39210

System Information

• GPU: GTX 980M
• Driver/LLVM version: nVidia 390.87
• Kernel version: 4.18.0-13
• Link to full system information report as Gist: https://gist.github.com/TenaarFeiri/2733a8f25f8818a5c3e85777eed9be22
• Proton version: 3.7-8

I confirm:

• that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.

https://gist.github.com/TenaarFeiri/9e560a89346b17cc2de0ac9b508259e8

Symptoms

The issue is Proton doesn't seem able to help ffxivlauncher.exe use the correct web browser to embed its login page with. I've had reports that the game itself is functional once you get past the launcher, but I'm unable to test it as this is a crucial step for downloading the game.

The launcher itself reports a HTTPS 404 error, as it can't find a browser to use for the launcher's landing page.

Reproduction

• Download and install Final Fantasy XIV Online.
• Launch the game. ffxivboot.exe will launch, and will give you no useful information as the font is broken.
• ffxivboot.exe will eventually finish its download, and then it will open ffxivlauncher.exe
• Inform the launcher that you already have an account with the game.
• Proceed through its prompts until it's done guiding you through it.
• Observe the launcher attempt to open a webpage necessary to initiate the running of the game and fail.
• Close and restart the game as many times as desired.