search

goatcorp / FFXIVQuickLauncher

Custom launcher for FFXIV
https://goatcorp.github.io/
GNU General Public License v3.0
2.79k stars 325 forks source link

Game won't open via XIVLauncher v5.5.8.0 after downloading mods for Textools #474

Closed bkp455 closed 3 years ago

bkp455 commented 3 years ago

"The application was unable to start correctly (0xc0000142). Click OK to close the application." upon clicking play.

System.Exception: Game exited prematurely at XIVLauncher.Game.Launcher.LaunchGame(String sessionId, Int32 region, Int32 expansionLevel, Boolean isSteamIntegrationEnabled, Boolean isSteamServiceAccount, String additionalArguments, DirectoryInfo gamePath, Boolean isDx11, ClientLanguage language, Boolean encryptArguments) in D:\a\FFXIVQuickLauncher\FFXIVQuickLauncher\XIVLauncher\Game\Launcher.cs:line 269 Version: 5.5.8.0 Git Hash: 5.5.8-0-ge76118e Context: XG LaunchGame OS: Microsoft Windows NT 6.2.9200.0 64bit? True DX11? True Addons Enabled? True Auto Login Enabled? True Language: English LauncherLanguage: English Game path: C:\Program Files (x86)\SquareEnix\FINAL FANTASY XIV - A Realm Reborn

Addons: []

reiichi001 commented 3 years ago

This is being caused by one of two things:

  1. Textools did such a good job of fucking up your client's index files that it can't open
  2. Textools' modification of your index files is causing a plugin to crash because client data is no longer in the appropriate places.

In the case of 2, which is the most likely cause, we can try to help find which plugin[s] are crashing. Please upload your dalamud.log file from %appdata%\xivlauncher either here or in the XIVLauncher Discord server and reference this issue.

bkp455 commented 3 years ago

dalamud.log

bkp455 commented 3 years ago

I've also tried disabling all modpacks in Textools and trying to run the game with either launcher. No dice. Also not sure if I should have Textools open when trying to run the game.

reiichi001 commented 3 years ago

Textools should not be open while the game is. (And it should pop up an error if you try to open Textools while the game is running).

Disabling a mod won't actually fix your index files. Only a start over (or a download index backups and start over) will.

Right now, I'm not seeing any textool-related errors in your log, but that could just mean it's crashing before then. The only logged error right now is coming from the PriceCheck plugin.

2021-07-08 07:35:47.055 -05:00 [ERR] [PriceCheck] Failed to get remote resource version so defaulting to 0.
System.Net.WebException: The remote server returned an error: (404) Not Found.
   at System.Net.WebClient.DownloadDataInternal(Uri address, WebRequest& request)
   at System.Net.WebClient.DownloadData(Uri address)
   at PriceCheck.ResourceManager.GetRemoteResourceVersion()

It may help to manually remove the plugin. Or all of them at first, and then reinstall when back in-game. Plugin settings are saved separately from the plugin files, and will be preserved across reinstalls on the same computer.

General "how to delete a plugin" steps:

  1. Close the game and xivlauncher
  2. Go to %AppData%\XIVLauncher\installedPlugins
  3. Remove the folder[s] for the plugin[s]
  4. Start the game now
  5. Let us know if the issue persists
reiichi001 commented 3 years ago

Closing this issue.

The actual cause was from multiple reshade injectors.

palindrome3d commented 2 years ago

"The application was unable to start correctly (0xc0000142). Click OK to close the application." upon clicking play.

System.Exception: Game exited prematurely at XIVLauncher.Game.Launcher.LaunchGame(String sessionId, Int32 region, Int32 expansionLevel, Boolean isSteamIntegrationEnabled, Boolean isSteamServiceAccount, String additionalArguments, DirectoryInfo gamePath, Boolean isDx11, ClientLanguage language, Boolean encryptArguments) in D:\a\FFXIVQuickLauncher\FFXIVQuickLauncher\XIVLauncher\Game\Launcher.cs:line 269 Version: 5.5.8.0 Git Hash: 5.5.8-0-ge76118e Context: XG LaunchGame OS: Microsoft Windows NT 6.2.9200.0 64bit? True DX11? True Addons Enabled? True Auto Login Enabled? True Language: English LauncherLanguage: English Game path: C:\Program Files (x86)\SquareEnix\FINAL FANTASY XIV - A Realm Reborn

Addons: []

Textools messes with the games files, so sometimes it can corrupt them, why? CAUSE WELCOME TO THE WORLD OF MODDING. When ever i get to a point where my game is crashing or not opening its always been 2 files. the .ver and the .bck files. For my convenience, and now hopefully someone with the same problem , i've put th em in a google drive - https://drive.google.com/drive/folders/18FzJo4y9iCNvspD2utb9NwyOnv2lNQ5P?usp=sharing

NotNite commented 2 years ago

Please don't necropost. This is not how you fix corrupt game installs. Use the Repair game feature in XIVLauncher.

palindrome3d commented 2 years ago

there are different kinds of crash errors that keep you from accessing the game, and the ones i've experienced the repair game feature did not work. If your files are get corrupted, a repaid doesnt always correct that, at least in my experience. And accessing or finding those files is hard to do which is why i keep them on hand.

NotNite commented 2 years ago

A repair will always bring your game back to the intended state. Manually overriding the version files does not fix the game - you merely trick the game into thinking everything is fine when it is not. Do not do this.

reiichi001 commented 2 years ago

The steps in this thread are for a version of the launcher that is a year old and we have better tooling now. A user should not be be adjusting their ver/bck files. (Textools also doesn't touch those.)

This thread was closed and should have stayed that way, as NotNite has pointed out.

If someone encounters the same issue in the future, they should open a new issue.

palindrome3d commented 2 years ago

and again, i've been through issues caused from modding that no repair will fix, not a normal repair, or a quick launcher repair, remember you dont need quick launcher to use textools and mods. I've literally had an issue that gave me a damn dx11 error on boot up every time and a regular repair did NOT fix it. Replacing the ffxivgame.ver and ffxivgame.bck with clean versions of both was the fix, they are what gets corrupted, so yes replacing them DOES fix it. Maybe we're talking about different issues.

https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon Virus-free. www.avast.com https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Fri, Aug 26, 2022 at 12:41 AM R @.***> wrote:

The steps in this thread are for a version of the launcher that is a year old and we have better tooling now. A user should not be be adjusting their ver/bck files. (Textools also doesn't touch those.)

This thread was closed and should have stayed that way, as NotNite has pointed out.

If someone encounters the same issue in the future, they should open a new issue.

— Reply to this email directly, view it on GitHub https://github.com/goatcorp/FFXIVQuickLauncher/issues/474#issuecomment-1228046308, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2XTMGP3GVC5IM6HX6PBNL3V3BDJBANCNFSM5AA4WR2A . You are receiving this because you commented.Message ID: @.***>

reiichi001 commented 2 years ago

No, textools does not touch ver/bck files. You can even check that in its source code if you like. You are conflating two unrelated issues as the same thing. And you picked a year old closed issue to do that. WHY?!

When applying a mod, textools only changes index files. That's it. Those are the only client files that get modified. That can lead to dat file corruption if the users disregard all safety and warnings and ignores textools own best practices of "remove all mods before updating the game" because of how updates work in FFXIV. But XIVLauncher can repair those. But not in version 5.5.8 because that feature didn't exist yet.

The ver and bck files are used by the official launcher to determine which patches have been applied. It will update the one file when it starts to apply a patch and then then updates the other when it finishes applying thst patch. A game version check will only use one of the files though, which can cause issues if they aren't correct for the actual version of the game that's installed. Running an integrity check from xivlauncher's settings can check if that's the case.

So yes, you are confusing two separate things while commenting on a closed issue.

The official launcher doesn't have a repair feature. It only has a button thst deletes the game install.

tldr: you have no idea what you're talking about. Please open a separate github issue if you actually need xivlauncher troubleshooting and stop posting on this issue. It was closed for over a year and github really shouldn't let anyone comment in it.