-
-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Games are not added or not working #209
Comments
@Cr0wTom interesting OK thank will continue to look at the coding. Each scanner has its individually way of parsing in the NSLGameScanner.py file |
Couple of questions @Cr0wTom:
|
Yes, it has, and I also tried changing the Proton version, but in the end it doesn't even make sense as inside GOG it runs correctly with the GOG assigned Proton. Directory is in the SD card, and it's the one I selected during installation from inside EA, didn't move the game, but yes I changed from the default during installation. |
@Cr0wTom thanks for confirming.
|
These are the default contents, I did not change anything.
OK, though I did this with both the Epic and GOG and it worked. |
Ok @moraroy, I think it's the same root issue with both Fallout and It Takes Two. I've installed Fallout on my deck to the default directory and it works fine, but @Cr0wTom's shortcut is totally missing the "/path=" argument in the launch options. So shortcuts don't work for GoG or EA if they're not installed in the default directories. |
@sysmoon14 yeah I noticed that, I think we have to derive the path from the registry, everyone's uuid is different for their SD card, which it would need to be translated to a lettered path for example path=D: |
True, changing the path, fixed the issue on the Fallout. Update: Adding the EA game manually, by using the exact options used by your script also works. |
@Cr0wTom, the GoG issue should now be fixed. It should work regardless of where you installed it. You'll need to make sure it's using the latest version of the script from the git repo |
@Cr0wTom has this since been fixed for you? Also please confirm if your cloud saves and local saves still work. I was under the impression that in order for the shortcut to work it needed that path in the launch options. When it comes to Gog, you can run the .exe straight from the directory because there is no DRM. However doing so, doesn't allow for the cloud saves and local saves to sync via the gog Launcher. Just wanted to make sure now if the gog Launcher was being opened in the background of your games and they are syncing for both cloud and local saves! |
I basically fixed it by adding the appropriate path on the Launch Options, so it runs properly by launching GOG on the backround. I did the same on the EA game from the SD. So basically as you said the only issue to fix, is to find a way to discover the unique SD card ID of each target SD. I guess for this dmesg or fdisk -l should work, but I don't have my Deck in front of me now to propose the proper way of doing it. I will follow up. |
@sysmoon14 I'm not sure if the path is needed anymore? |
I think im still having this same issue. I installed Hollow Knight from GOG and it did not even have a "/path=""" thing, and when attempting to launch the game it just failed. Using the default directory or installing it elsewhere did not change anything. I've used the newest proton from valve and the newest GE proton as well. I am not installing on an SD card, and whether i install to the default GOG Games directory to straight to the "root" drive, at C:/HollowKnight, makes no difference. I have not made any changes to the launch commands, target, or start in directory. I can put those in here, but its a bit of a pain to get them off the steam deck. If i go straight to the executable "Hollow Knight.exe" and add it to steam and use proton, it works fine. It also boots through GOG, but the shortcut created by the script in steam just wont launch. It just switches to "Cancel" and then immediately goes back to "play". Edit: just tested - cloud saves don't work if I launch it through the executable. Likely because of the different virtualized directories, unfortunately. Target: "/home/deck/.local/share/Steam/steamapps/compatdata/NonSteamLaunchers/pfx/drive_c/Program Files (X86)/GOG Galaxy/GalaxyClient.exe" Launch options: STEAM_COMPAT_DATA_PATH="/home/deck/.local/share/Steam/steamapps/compatdata/NonSteamLaunchers/" %command% /command=runGame /gameId=1308320804" The game is not installed in an SD card, either. Its installed in the default installation directory. |
Same exact issue here, if I install it all as default and use the defaulted created entry, it's the same as above for all my GOG games. Changing to the direct .exe works fine as normal but this command launch method doesn't seem to be working at all for me. I want to add you will need to keep this for your saves This is telling Steam to look into this directory for the data, without it will create it's own directory based on the games name and create a new string folder (numbers) and store everything there instead of the "non steam launcher" folder. |
Ok reverted the change and now the path is added to GOG games. This will only work for games that are installed in the default GOG directory though. |
Sure. I managed to fix the issue by just adding a /path="Install directory" option at the end of the launch options. That got the game to boot through GOG even when i selected a different install directory. One day i'll have to figure out how to install games to the SD card and do this, but I don't have an SD card at the moment. Still a fantastic app, super convenient. Wish steam would let us edit non-steam metadata, but oh well. |
Hi @moraroy, and thanks for your tool! I had issues with not having games added as well, and via a bit of investigation I found the reason, at least on my system. Maybe this could be a reason for the issues other users are having. |
Thank you for this amazing tool. Made my deck 1000x better.
But one issue I have is that it's inconsistent with the games added.
I am also attaching my log, I would appreciate some help, and if needed I can help debugging the issue further.
NonSteamLaunchers-install.log
The text was updated successfully, but these errors were encountered: