Skip to content
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

Chiaki Shortcut destroys Shortcuts NonSteamLaunchers ? #562

Open
Valekj86 opened this issue Jan 16, 2025 · 16 comments
Open

Chiaki Shortcut destroys Shortcuts NonSteamLaunchers ? #562

Valekj86 opened this issue Jan 16, 2025 · 16 comments

Comments

@Valekj86
Copy link

Valekj86 commented Jan 16, 2025

Hello there,

I have used NonSteamLaunchers for the EA, GOG, and Epic Launchers.
Yesterday, I installed the Chiaki app for PS5 streaming.
After using the shortcut function from the Chiaki app (see the screenshot in the attachments), I could no longer use the installed launchers.
You can see the EA App and the GOG App prior to creating the Chiaki shortcut.

After creating the shortcut, the icons for the EA App and the GOG App disappeared.
The games I have installed won’t start either.

I have tried this multiple times, and the result is always the same.
On the screen, there are no games from NonSteamLaunchers installed because I was just trying to recreate the error with the EA and GOG launchers.

How to fix this?

i am using the newest NonSteamLaunchers Decky Version

Image

Image
Image
Image
Image
Image

Image

@moraroy
Copy link
Owner

moraroy commented Jan 16, 2025

@Valekj86 to be honest with you...not sure if it's an NSL issue or a chaiki issue... what do you mean by the icons are missing?

@moraroy
Copy link
Owner

moraroy commented Jan 16, 2025

Ohhh never mind I saw your last picture.

@moraroy
Copy link
Owner

moraroy commented Jan 16, 2025

@Valekj86 based on what you have shown me here it seems your .vdf file is becoming corrupted. Most likely because chaiki isn't creating shortcuts properly. The decky plugin uses its own way of creating shortcuts, it actually doesn't use the .vdf file like chaiki seems to be doing. I would bring this to the attention of the developer of chsiki and see if we can work together to fix this problem. I'm open to suggestions and fixes.

@moraroy
Copy link
Owner

moraroy commented Jan 16, 2025

@Valekj86 a good way to test this actually would be to open up the NonSteamLaunchers.desktop, then delete then EA APP and see if the desktop version of NSL clashes with your chaiki. Then restart steam. If you see both shortcuts are now made then yes it may have to do with the plugin version creating shortcuts not sure yet though as I don't have chaiki nor a Playstation console.

@Valekj86
Copy link
Author

Hello, i only have installed the NSL Decky plugin. So to test this i should install the desktop version? And decky plugin stays installed?

Then delete the shortcut EA App? Or deinstall it?

if you give me the instructions i will test it tomorrow.

Chiaki is free and you dont need a playstation console for it.

@moraroy
Copy link
Owner

moraroy commented Jan 16, 2025

@Valekj86 ah OK I'll download and test chaiki later today and see if I can make a shortcut with it and see what the issue is, thanks for letting me know! Just fyi, when you run the desktop version of NSL there is nothing to install or Uninstaller. It's all the same thing. The only thing that nsl creates is shortcuts essentially. Just in different ways.

@moraroy
Copy link
Owner

moraroy commented Jan 16, 2025

@Valekj86 i havnt tested yet, but in the chaiki picture up above it says it "created successfully" your shortcut vdf. if this is in fact the same shortcut vdf file, as far as i know that will create issues if the shortcuts.vdf file is being created again. i think the chaiki developer needs to be told this is happening.

@Valekj86
Copy link
Author

hello, i created a bug report at the github page from chiaki

streetpea/chiaki-ng#529

@moraroy
Copy link
Owner

moraroy commented Jan 18, 2025

@Valekj86 I tested yesterday and yes you were correct, my nsl artworks were also deleted, surprisingly it only happened to a few of them not all of them. Hopefully we can see what's going on.

@Valekj86
Copy link
Author

@moraroy a solution has been posted.

streetpea/chiaki-ng#528 (comment)

@PianoMan2112
Copy link

I haven’t gotten to testing the dev build yet, but I just wanted to note that it was both much worse and much better than I thought: Because the file ID changes (see the other bug report), not only do the images fail to load, but so do the apps, possibly because they still reference the old ID. (1 out of 4 I tested worked, the other 3 closed immediately.) The good news is that copying the shortcuts.vdf.YYYY-MM-DD-HH:MM:SS.bak backup that Chiaki apparently creates just before editing the file (THANK YOU!) on top of shortcuts.vdf fixes the issue. (Note that in debugging, I also cleared my download cache, but this probably has no effect on the problem or repair.)

@PianoMan2112
Copy link

PianoMan2112 commented Jan 18, 2025

I just tested creating a non-Steam game entry with the test version successfully; thank you!

@Valekj86
Copy link
Author

@PianoMan2112 a new chiaki testversion? Where can i download it? i doesnt show an update with the steam deck.

@streetpea
Copy link

streetpea commented Jan 23, 2025

@Valekj86 version 1.9.5 (which was released 3 days ago) fixes this by using a patched version of the shortcut creation library. Once you restore from the backup file that the library chiaki-ng uses for this creates you can try again and it shouldn't cause any issues for you anymore. @PianoMan2112 the app not launching is related. The proton prefixes also relies on that id (which may be calculated differently by different programs creating the shortcuts) so if the images are gone the proton prefixes are gone too. Both are restored by restoring from backup. Neither issue should occur in 1.9.5

@moraroy
Copy link
Owner

moraroy commented Jan 25, 2025

@streetpea has this been fixed? Great work on chiaki by the way!

@streetpea
Copy link

@moraroy yes it’s been fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants