Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
1 of 2 tasks
TenaarFeiri opened this issue Jan 2, 2019 · 1 comment
Closed
1 of 2 tasks

Comments

@TenaarFeiri
Copy link

Compatibility Report

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

System Information

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.
@kisak-valve
Copy link
Member

Hello @TenaarFeiri, we're using one issue report per unofficially supported game title, so I've gone ahead and transferred this issue report to #580 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants