valarnin / ffxiv-tools

Tools for FFXIV
MIT License
77 stars 21 forks source link

worst guide. errors everywhere #31

Open karmaspcs opened 1 month ago

karmaspcs commented 1 month ago

used it today on nobara 39 and nothing workes. ffxiv over lutris is fine BUT every setup.sh is not working. errors all over.

setup.sh:

Checking for dependencies... Checking required 64-bit dependencies... Missing dependency libFAudio.so.0... Checking recommended 64-bit dependencies... Missing dependency libgcrypt.so... Checking for required tools... Found tool unzip... Missing tool patchelf... Found tool wget... Checking miscellaneous requirements... Detected a sufficiently high ulimit value (1048576). Found required wine dependencies.

Required dependencies are missing. Failed to load dependency resolver Dependency check failed. Aborting setup.

///////////////////////////////////////////////////////////////////////

setup1.sh:

Setting up the FFXIV Environment scripts.

This script will require you to open the FFXIV launcher from Lutris as if you were going to play the game normally

Please open the XIVLauncher Launcher. Checking for process "XIVLauncher.exe"...

(XIV Launcher is via .exe installed)

///////////////////////////////////////////////////////////////////////

setup2.sh:

Setting up the Proton environment to run ACT with network capture This script will set up your wine prefix and proton executables to run ACT, as well as set up a default ACT install for you If this process is aborted at any Continue prompt, it will resume from that point the next time it is run Please make sure nothing is running in the wine prefix for FFXIV before continuing The FFXIV environment hasn't been configured yet. Please run the stage1 setup first!

////////////////////////////////////////////////////////////////////////

setup3.sh:

Setting up the FFXIV helper scripts.

This script will set up helper scripts in /home/USER/.local/share/ffxiv-tools/ to launch FFXIV, ACT, or both.

Current script version: 3.

grep: /home/USER/.local/share/ffxiv-tools/ffxiv-env-setup.sh: Datei oder Verzeichnis nicht gefunden Your /home/USER/.local/share/ffxiv-tools/ffxiv-env-setup.sh script does not have a FFXIV_PATH variable. This likely indicates that you're running setup-stage3.sh against an environment built before it was created. Please edit the script at /home/karmas/.local/share/ffxiv-tools/ffxiv-env-setup.sh and add a line like the following, with the path corrected for your FFXIV install location: export FFXIV_PATH="/home/valarnin/.local/share/Steam/steamapps/common/FINAL FANTASY XIV Online"

valarnin commented 1 month ago
  1. You do not have libFAudio.so.0 installed natively, which means that the default process in setup-stage2.sh will break game audio. This can be worked around by modifying setup-stage2.sh to not setcap or patchelf the wine binaries, and instead use Deucalion Injection in ACT itself.
  2. setup-stage1.sh is failing because XIVLauncher itself must be running through lutris for this set of scripts to work. Not the game. XIVLauncher needs to be running to detect the correct environment variables, which will be written to scripts at ~/.local/share/ffxiv-tools, so that ACT can be run under the same environment
  3. setup-stage2.sh and setup-stage3.sh are failing because setup-stage1.sh did not generate the required scripts.

It is likely that even if you work through these issues, you'll have further problems with running ACT unless you manually remove mono from the prefix and install .NET 4.8. These steps were not required when the scripts were originally written, but XIVLauncher no longer installs .NET 4.8 itself. To do so, you'll have to get setup-stage1.sh to actually generate the required scripts first, then you can run ~/.local/share/ffxiv-tools/ffxiv-env.sh to launch to a bash prompt which has the correct environment variables set, then run wine64 uninstaller and remove mono, then wine64 dotnet48.

My ability to update these scripts to address changes that have been made in XIVLauncher is currently limited, as I'm stuck on Windows in order to continue the active development of OverlayPlugin.