HarlequinWasTaken Posted June 9 Posted June 9 I've seen this posted to a few places but none of the posts actually had an answer, so hoping I can find one here. I'm running Clair Obscur: Expedition 33 via Games Pass and things had been going fine but all of a sudden I'm getting an error message of "Failed to start game through launcher" whenever I'm launching from Vortex. The error log is below: Quote GameEntryNotFound: Game entry not found at E:\Games\Vortex\resources\app.asar.unpacked\bundledPlugins\gamestore-xbox\index.js:2:3432 at tryCatcher (E:\Games\Vortex\resources\app.asar\node_modules\bluebird\js\release\util.js:16:23) at Promise._settlePromiseFromHandler (E:\Games\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:547:31) at Promise._settlePromise (E:\Games\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:604:18) at Promise._settlePromiseCtx (E:\Games\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:641:10) at _drainQueueStep (E:\Games\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:97:12) at _drainQueue (E:\Games\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:86:9) at Async._drainQueues (E:\Games\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:102:5) at Async.drainQueues (E:\Games\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:15:14) What's weird is that the game is installed on my C:\ drive, which I've confirmed in the local files for the game in Xbox Games Pass. In Vortex, I've also set the game's location to the "Sandfall" folder of the game's install location on the C:\ drive. So I'm not sure why it's trying to call stuff from a totally different drive. Checking the local files of the individual mods in Vortex, as well, they're all in sub-folders of the game install directory. These are the mods I'm trying to run: https://www.nexusmods.com/clairobscurexpedition33/mods/1 https://www.nexusmods.com/clairobscurexpedition33/mods/206 https://www.nexusmods.com/clairobscurexpedition33/mods/20 https://www.nexusmods.com/clairobscurexpedition33/mods/28 https://www.nexusmods.com/clairobscurexpedition33/mods/24 Any help would be appreciated.
Community Manager Solution Pickysaurus Posted June 9 Community Manager Solution Posted June 9 You can probably just start the game via Xbox Launcher? Given that Xbox's DRM is really weird. It might also be that the extension developer made a mistake in the implementation but I don't think you need to start via Vortex to use the mods.
ChemBoy1 Posted June 9 Posted June 9 You would be getting error messages about missing required files (Which is the Sandfall folder itself) if the selected install location was a problem. You should select the folder containing Sandfall folder, not going inside the Sandfall folder. The code is properly written for launching the Game Pass version of the game. I use that version myself. The main issue with supporting Game Pass versions is that the Xbox app will lock up the game folder at certain times. Make sure you have finished the game install and launched it at least once, then restart the Xbox app before adding to Vortex. Based on the fact that you had to select the install location manually, this suggests that you tried to add the game to Vortex before the Xbox app had unlocked the game folder, since that prevents Vortex from reading the game folder and finding the game location automatically. In any event, you can launch the game from the Xbox app and your mods will still work. Restarting the Xbox app and Vortex may resolve the error as well. You seem to have Vortex installed on your E Drive, based on the error text. You have to make sure you have the mod staging folder on C Drive (same as the game) since this game only works with hardlinks deployment.
HarlequinWasTaken Posted June 9 Author Posted June 9 1 hour ago, Pickysaurus said: You can probably just start the game via Xbox Launcher? Given that Xbox's DRM is really weird. It might also be that the extension developer made a mistake in the implementation but I don't think you need to start via Vortex to use the mods. Launching from the Xbox app does seem to load it with the mods, yeah. First game I've modded via XBGP, so that's new for me then. 27 minutes ago, ChemBoy1 said: You would be getting error messages about missing required files (Which is the Sandfall folder itself) if the selected install location was a problem. You should select the folder containing Sandfall folder, not going inside the Sandfall folder. The code is properly written for launching the Game Pass version of the game. I use that version myself. The main issue with supporting Game Pass versions is that the Xbox app will lock up the game folder at certain times. Make sure you have finished the game install and launched it at least once, then restart the Xbox app before adding to Vortex. Based on the fact that you had to select the install location manually, this suggests that you tried to add the game to Vortex before the Xbox app had unlocked the game folder, since that prevents Vortex from reading the game folder and finding the game location automatically. In any event, you can launch the game from the Xbox app and your mods will still work. Restarting the Xbox app and Vortex may resolve the error as well. You seem to have Vortex installed on your E Drive, based on the error text. You have to make sure you have the mod staging folder on C Drive (same as the game) since this game only works with hardlinks deployment. Restarting the apps didn't stop the errors from occurring but, as mentioned above, it doesn't seem to matter, I guess. I didn't know that about the game folder being locked until launch though; for what it's worth, I had tried to play the game un-modded at first. Played about three hours with my 3060ti struggling like hell before I turned to fix mods and the like. Is there a way inside Vortex to shift its install location from one drive to another? Or is it not worth it at this stage, and I should just check that the mod staging folder is correctly set for each game? (Though this is the first game I've had problems with, which I was just putting down to it being an Xbox thing.) Anyway, thanks for the input guys - guess I should've just tried re-launching via the xbox app from the start.
ChemBoy1 Posted June 9 Posted June 9 If mods are working, then the game directory must be set correctly, and the mod staging folder as well. Both on the same drive. Otherwise, mods would not be deployed and work in the game. So, it seems the issue is solely with launching the game. Which version of Vortex are you using? I'm on the beta channel, and this extension was only tested by me directly on the latest beta version of Vortex. A lot of users were getting similar errors on Nexus Mods' own Oblivion Remastered extension. It's not clear to me why these errors are occurring for some users, but not others. @Nagev - Checking if you have learned anything on this issue since I posted it on the Vortex Issues page. In both of our cases, the Xbox versions launch fine on our machines. I have no idea what aspect of the user's environment could cause this. https://github.com/Nexus-Mods/game-oblivionremastered/issues/7
Staff Nagev Posted June 10 Staff Posted June 10 This is most likely down to a bug in the game store helper which I fixed yesterday. https://github.com/Nexus-Mods/Vortex/pull/17627 This will get fixed in a patch release of 1.14 this week next week. 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now