ValveSoftware / ValveSoftware/Proton

Final Fantasy XIV Free Trial (312060)

Open
#1,162 8 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Game compatibility - Unofficial
Dominant language
C++
Stars
32.8k
Forks
1.6k
PR merge metrics
PR metrics pending

Description

I don't know if this should be posted in the FFXIV Full Version (39210) issue, since the client and the launcher are almost identical, but I will open a new issue for correctness. Merge it if you think it doesn't deserve its own issue.

Whenever I launch the launcher, it does not seem to detect my DXVK, and it simply greys out the DirectX 11 switch in the options. I am only able to launch it in DirectX 9.0c mode.

Things I tried
  • Used Proton 3.7-3 and 3.7-5 Beta. Neither of those work.
  • Reinstalled the game.
  • Used winetricks to install xact and/or set d3d11 and dxgi to native.
  • Used /tmp/proton_run to run the launcher outside Steam. More info on this later.
  • Launched the game with PROTON_USE_WINED3D11=1. The switch now works, but the game crashes on launching, so it is not what I actually want.
  • Opening Steam from CLI and watching the output. The CLI seems to be mute in this.

Whenever I use /tmp/proton_run to launch the game outside of Steam, two things happen:

  • It spews some stuff to the console about not being able to initialize OpenVR, 'failed to create Vulkan instance', and 'extension "NV-GLX" missing on display ":0"' (which is weird, considering I do not even have an Nvidia card here, and this error is apparently related to Nvidia's proprietary drivers, from what I have seen). You can find a sample of the console output here.
  • Setting the PROTON_USE_WINED3D11=1 environment variable seems not to enable the switch, unlike when it is run from Steam.
Things to note about the game's system detection tool

The game comes with a tool to obtain information about your system, running processes, and other things that can help with technical support, similar to Steam's system report.

  • It lists my OS as Windows XP Professional, despite the Proton prefix being set to Windows 7.
  • It lists the DirectX version of the system as "DirectX 9.0c (4.09.0000.0904)", even when the switch has been enabled by using the WINED3D11 flag.
  • It lists my GPU as a Radeon R9 285, even though it is a R9 380.
  • It detects the GPU driver as aticfx.dll
  • The install information section just says "Wine Gecko (32-bit)". Can confirm the prefix is actually 64-bit, according to winetricks.
  • Nothing seems to change between the WINED3D11 version and the DXVK version.
System info
  • AMD FX-8350 CPU
  • AMD R9 380 GPU
  • Debian Sid, updated just today
  • Kernel 4.17.0-3
  • Mesa 18.1.7
  • i3 window manager
  • Running inside firejail. Wanna note that no other game seems to have a problem with this, just in case. Can post sandbox profile if necessary.
Other info
  • The game is confirmed to work flawlessly in other users' systems, after installing some stuff with winetricks.
  • Even before installing xact and tweaking the prefix, users report they can actually try to launch the game in DX11 mode, but it crashes. Not in my case, I can't even attempt to run it in DX11 mode, and I suspect it would actually run if it could.
  • I can confirm DXVK works in my system. Tried it with Slap City, and even though the characters appear invisible, the DXVK_HUD was showing, so I know it was running well.
  • These are the Proton logs for running without PROTON_USE_WINED3D11=1, and for running with PROTON_USE_WINED3D11=1
  • Setting the d3d11 and dxgi libraries to native makes the game not enable the switch even if PROTON_USE_WINED3D11=1 is passed.

All in all, it appears my DXVK isn't reporting itself correctly to FFXIV in my system, which makes it think it is not capable of running DX11 games, when it is. But why is WINED3D11 reporting itself correctly, and not DXVK?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the linked Proton logs and the reported system-detection observations; the issue names no source file or test. Reproduce the FFXIV launcher behavior with DXVK and PROTON_USE_WINED3D11=1 in the described Proton environment. Done means determining why DX11 is disabled under DXVK and verifying the corrected behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
debian, linux
Domain
desktop, game-dev, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.