search

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

XivAlexander not autolaunching when installed #268

Closed Thorgak closed 2 years ago

Thorgak commented 2 years ago

This only started becoming a problem for me since endwalker but when starting the game the program doesn't auto launch, I don't get any error messages or problems to indicate why and when using load once it works fine so i've been using that as a workaround.

Have tried uninstalling and reinstalling while deleting the config files that the installer prompts me to as well as doing that process in Administrator but no success. The installation seems to be successful each time but then the program doesn't launch. I'm using the quick launcher and have gshade installed.

Soreepeong commented 2 years ago

I guess it doesnt exactly work too well with gshade then. I'll see if anything can be done about it. Meanwhile, maybe try installing as DInput8?

Thorgak commented 2 years ago

Tried installing as DInput8 with no success, tried uninstalling gshade and reinstalling xivalexander but also no success so seems unrelated to gshade? Any other suggestions on things to try or information I can provide that can help?

Running without the quick launcher by using the "run game" option also doesn't appear to work, only way I can get the program to launch is by having the game open and loading once.

Thorgak commented 2 years ago

Potentially on an unrelated matter - XivAlexander just errored after having reinstalled and using the latest version, not sure if this warrants creating a separate issue, here's the log file. XivAlexander_20211231_202308_906.log

Soreepeong commented 2 years ago
  1. I've confirmed that GShade works fine, if XivAlexander installer is ran after GShade installation.
  2. That error log looks like nvidia drivers did something bad. XivAlexander just tries to catch all error and show, and this one probably isn't about XivAlexander.

Open up your FFXIV installation folder, go into game folder, and right click on d3d11.dll and open Properties to confirm that it's XivAlexander dll. If it's not, then run the installer again. Otherwise, I can't think of reasons that it wouldn't work at the moment.

Thorgak commented 2 years ago

Just confirmed the d3d11.dll file is the XivAlexander one and the program still didn't launch, there is another d3dd11.dll thats a .syslink file showing it belongs to GShade, could this be causing problems?

Soreepeong commented 2 years ago

Can you take a screencap of the game folder? Also, just to check, if you completely get rid of GShade, does it work? By completely removing it, you also need to delete symlink file from game directory.

Thorgak commented 2 years ago

I believe the other day when I first opened the ticket I tried uninstalling both XivAlexander and GShade and then reinstalling XivAlexander alone and the problem was still there. I didnt delete the Symlink file though, I'll give that a try now.

Heres a screenshot of my folder before deleting anything just now. image

Thorgak commented 2 years ago

After uninstalling GShade and deleting the symlink file and reinstalling XivAlexander alone the problem still persists. My folder now looks like this: image

Thorgak commented 2 years ago

Finally managed to resolve the problem partly - had the error pop up again relating to display drivers so I updated them and after restarting the PC XivAlexander automatically launched as intended.

However while auto launching the program is having no effect on double weaving. I've attached a picture of the log file incase it helps but unsure what steps to take next. Load once still works fine.

Update: After having the issue of no effect on double weaving, I uninstalled XivAlexander, installed version 1.14.8.41 which didnt work til i updated opcodes, it then worked so i uninstalled that and reinstalled a fresh download of 1.14.8.45 and everything now works fine.

Not sure if it was related to the known issue of needing to use a different folder when using load once as it can fail? Maybe extends to reinstalling from the same folder, or something else entirely as I performed the older version install, opcode update on the older version and reinstall of new version from different folder all at the same time :/