So how do I set up my batch file that runs the python launcher to use the Lutris installation / environment?
echo "FFXIV DX11 Custom Python Launcher"
cd "/home/astump/Games/final-fantasy-xiv-a-realm-reborn/drive_c/Program Files (x86)/SquareEnix/FINAL FANTASY XIV - A Realm Reborn"
^ this is the batch file I have.
But the custom python launcher does not take arguments if I try to edit the ini file and put this in:
#Leave blank for windows or MacOS, ‘wine’ for Linux
pre_command = wine _staging_version=“a0708adf427a61acd2f68dda8ccf245d93909f15”
it says: [Errno 2] No such file or directory: ‘wine _staging_version=“a0708adf427a61acd2f68dda8ccf245d93909f15”’
I looked at what Lutris does and I tried running the command that it first executes to set the “runner”
this made some changes to my default wine prefix in ~/.wine , thinking - ok, maybe if I mock what Lutris does maybe it will let the ffxiv_dx11.exe run under Lutris’ configuration. No luck except a bunch of files changed in my default wine prefix.
I get there is a bug in the latest commit of wine staging, but I have not updated wine at all or lutris. All I did was copy files from the lutris installation to a virtual machine with a trial of Windows 10 enterprise edition, run the launcher there to update everything, and move all files back per some other instructions I saw. This bypasses having to use the launcher to download and in theory all I would have to do is use the custom launcher to launch Lutris and pass the custom launcher arguments, through lutris, to ffxiv_dx11.exe
In addition for some reason even after doing things this way the WINEPREFIX is not being passed to the custom FFXIV Launcher –
fixme:winediag:start_process Wine Staging 2.4 is a testing version containing experimental patches.
fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org.
Because when I run Lutris by default, it should be 3.1x w/ DXVK