SteamGridDB / SGDBoop

A program used for applying custom artwork to Steam, using SteamGridDB. Supports both Windows and Linux, written completely in C.
https://www.steamgriddb.com/boop
zlib License
253 stars 10 forks source link

Could not find "ModInstallPath (either in regedit or registry.vdf) [97] #57

Open RandomLegend opened 1 year ago

RandomLegend commented 1 year ago

System Specs: OS: Garuda Linux Kernel: 6.4.4-zen1-zen DE: KDE Plasma 5.27.6


Clicking the "APPLY WITH BOOP" button on any given cover the menu to select the correct game properly appears. I then select the game and click on "OK". Then nothing happens. Restarting steam doesn't show me any new artworks or icons.

Looking into ~/.local/state/sgdboop_error.log shows me: Could not find "ModInstallPath (either in regedit or registry.vdf) [97] with a timestamp of everytime i tried to add artwork.

I installed it via the AUR but also tried the flatpak version, both of them give me the exact same error.

I have tried to start Steam as the Native Version or the Runtime version.

I saw that this error got posted here before but no one ever provided a solution. This is my try aswell. I'd love to have a solution for this issue.

Thanks and have a nice day!

XZYW7 commented 11 months ago

I found that maybe your resource is relatively large so that the backend is still downloading the resource.

XZYW7 commented 11 months ago

I found that maybe your resource is relatively large so that the backend is still downloading the resource.

you can test some smaller image. If it works, your can just wait for downloading.Maybe this plugin can support downloading info in the future

ExpatUK commented 2 weeks ago

On a fresh Windows 11 and Steam install, it seems the ModInstallPath registry key is no longer created.

You can create this key as a workaround but the source should be fixed here.

To use the workaround, create the key string value, or paste the following into a reg file and run it:

ModInstallPath.reg:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Valve\Steam]
"ModInstallPath"="C:/Games/Steam/steamapps/common"

This resolves the error and symlink moaning in the logs and the tool works again.