Soreepeong / XivAlexander

Double weave on high latency, and mishmash of modding tools - especially for fonts and internationalization for Final Fantasy XIV.
Apache License 2.0
715 stars 65 forks source link

Steam version either crashing or unable to connect to servers #161

Closed Marcelonn closed 3 years ago

Marcelonn commented 3 years ago

I always get the "The lobby server connection has encountered an error" error when trying to log in after having installed XivAlex. Running it without installing works fine.

Soreepeong commented 3 years ago

Some things to check:

Also, did "Uninstall XivAlexander" button work without hitch?

Marcelonn commented 3 years ago
  1. No, not using a VPN.
  2. This is what gets printed:

2021-10-02 08:14:32.452 General XivAlexander initialized. 2021-10-02 08:14:32.495 General Freed game mutex \BaseNamedObjects\6AA83AB5-BAC4-4a36-9F66-A309770760CB_ffxiv_game00. 2021-10-02 08:14:32.495 General Freed game mutex \BaseNamedObjects\6AA83AB5-BAC4-4a36-9F66-A309770760CB_ffxiv_game_common. 2021-10-02 08:14:53.321 SocketHook 15e8: API(socket) 2021-10-02 08:14:53.322 SocketHook 15e8: API(connect): 204.2.229.11:54994 2021-10-02 08:14:53.846 SocketHook 15e8: Found 2021-10-02 08:14:53.846 SocketHook 15e8: Local=192.168.0.8:65284 2021-10-02 08:14:53.846 SocketHook 15e8: Remote=204.2.229.11:54994 2021-10-02 08:14:53.848 SocketHook Ping 192.168.0.8 -> 204.2.229.11: Start tracking.

  1. If you mean if I can log in by doing that, then yes.
  2. Couldn't check that because for some reason I couldn't log in to the official launcher (probably because mine is a steam version of the game). EDIT: after trying again, I was able to log in by following those steps, but xivalexander wasn't loaded into the game.
  3. Doesn't work.

Yes, the uninstall function seems to work.

Soreepeong commented 3 years ago

XivAlexander_1_14_8_25_c06689b.zip

Can you test out this version? I've made XivAlexander hook socket functions after game main window becomes responsive, which is normally the case when you're using "load once", compared to "install" which makes XivAlexander hook socket functions almost immediately.

Marcelonn commented 3 years ago

I tried it and, unfortunately, same error.

Soreepeong commented 3 years ago

XivAlexander_1_14_8_25_TEST2.zip

Try this one! Make sure you go through installation step again via Loader. It will show you a message like the following:

image

See if you can log in without continuing from that button, and when you got to character selection screen, try continuing from the message box and then try logging into a character.

Marcelonn commented 3 years ago

I'm really thankful for your attention but it still doesn't work. I did what you said and didn't click "OK" until after I logged in. image

Soreepeong commented 3 years ago

I don't really have a clue at this point - I'll get back to you later, when I set up trial account for test with Steam installation. Otherwise, if do have a trial account to use that doesn't involve Steam, try logging in with that one while XivAlex installed. You can launch the game with normal Square Enix account if you launch the game manually via C:\Program Files (x86)\Steam\steamapps\common\FINAL FANTASY XIV Online\boot\ffxivboot.exe.

dsdamod commented 3 years ago

I seem to have the exact same issue unfortunately.

Only way i can get XivAlexander to work is if i use "load once without installation" after the game is already running.

Pageanator2000 commented 3 years ago

I was having the same issue, a clean download seems to have fixed it. though windows defender is picking up some of the files as malicious.

jekyll87 commented 3 years ago

I was having this issue yesterday after updating to the newest version. Did a complete uninstall and also uninstalled Gshade. I was then able to log in to the game and load XivAlexander.

ShinjukuCurry commented 3 years ago

Same problem here, installing causes game to not connect. I reverted back to using the portable version.

gozoge commented 3 years ago

same problem - i have done some testing and have found: 1: i can launch the game normally and play - 2: once game is launched and i have logged in - if i load xivalexander it will work 3: if i load xivalexander before launch or on launch with the installer - it won't even let me load my game, it gets to the ff14 launcher screen then once hitting play just closes. 4: if i load xiv alexander AND xiv launcher together - i can get the game started, but i get the same error 5006. 5: if in the xiv alexander launcher and i click run game without it installed - it will run my game fine but xiv alexander wont be running

Nypheena commented 3 years ago

I got this issue as well with version 25

Soreepeong commented 3 years ago

I'm pretty sure this happens with Steam installation. If any of you aren't using Steam to play xiv, then let me know which other addons or VPN programs you're using - like GShade, WTFast, and etc.

jekyll87 commented 3 years ago

I do not use Steam to play XIV. At the time I was having the error, I was using: GShade XIVLauncher BattlePing

I have never had a problem w/ XIVLauncher or Battleping (edit: I should note I did try running the game w/o both and the error persisted). The uninstallation of XIVAlexander and GShade corrected the 5006 error for me. I re-installed XIVLauncher and worked fine after but I have only tested the "load once" option and not the "install" option after reinstall.

Nypheena commented 3 years ago

I'm pretty sure this happens with Steam installation. If any of you aren't using Steam to play xiv, then let me know which other addons or VPN programs you're using - like GShade, WTFast, and etc.

no steam just xivlauncher integration to count time its mogstation version, protonvpn, IPs excluded. Dalamud plugins, none should be modifying network settings

tockity commented 3 years ago

Not using steam and VPN is not running, also running into issues and cannot run the game. The only other program used with XIV is XIVLauncher.

I've reverted back to 1.14.8.19 until a portable version is included again. This whole install business is wholly unnecessary when using xivlauncher.

Kamexe commented 3 years ago

Yep I'm having the same issue here when I tried it yesterday. I use XIVlauncher and ACT but nothing else. I get the same error though of cannot connect then force shuts down the game. I had to do uninstall this and now the game works fine again :/

Dima6767 commented 3 years ago

Having the same issue with the latest version after "installing it" I'm using Steam version and starting through XIVLauncher. For now I've resorted to using it without the "installation" part.

jamesczhang commented 3 years ago

I have encountered the same issue. XIVLauncher, Astrill VPN are also installed. "Loading once" works fine.

Soreepeong commented 3 years ago

https://github.com/Soreepeong/XivAlexander/releases/tag/v1.14.8.26

Try out the latest release. I got a steam sub to test, and in my case, the game wouldn't even start at all, so this one fixes the said problem. I don't know if this is going to fix networking problems as well (unreproducible for me), but wouldn't hurt to try it out. People who did try this out said that it did fix their issues.

herrhuml commented 3 years ago

I'm not on steam and I'm using both XIVLauncher and GShade. At first I was crashing, then I couldn't connect to the servers while XivAlexander was installed, loading it once worked fine though. This latest update seems to work just fine even while installed.

Marcelonn commented 3 years ago

I'm sorry if this doesn't pertain to the subject of this topic but still I gotta ask: what's the difference between the different install options available in the newest release?

Dima6767 commented 3 years ago

I'm able to connect to the game now using version 1.14.8.27 and "installing" it.

Soreepeong commented 3 years ago

It's literally "try the other one if the first one does not work", in case other addons using the conflicting DLL names do not support XivAlexander's method of resolving it.

Soreepeong commented 3 years ago

Additional fixes have been made to not cause problems when the full path to your Documents folder contains non-ASCII characters, and more miscellaneous command line argument stuff that might have been causing login failures.