-
Notifications
You must be signed in to change notification settings - Fork 32
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
parse error in 3rd party module #23
Comments
What is the issue here? |
Sorry, I was asked to create this issue here, because my issue is very strange. FriendsOfGalaxy/galaxy-integration-steam#7 (comment)
parse error in 3rd party module. You should create an issue here: https://github.com/ValvePython/vdf/issues pasting folowing part of your log and uploading the acf file
this apparently is on our side. Could you send us this file? e:/steam\steamapps\appmanifest_416680.acf or e:/steam\steamapps\appmanifest_247080.acf ? Those error appears every second. Looks like regresion with #10 despite #11 . That is not good. I'll check one more time. there is nothing in log file that shows your plugin total crash. I will appreciate i you send log file just after the crash. This way proper information won't be misssed. I added again all missing covers and it has not been erased again That's nice that Galaxy fixed it. Not all games are shown. By example: My Sherlock Holmes collection does not appear complete in GOGalaxy 2.0 but it does on Steam launcher. This is Galaxy gamesdb problem. I see 3 games that are send from plugin to Galaxy that contains "Sherlock" in title. How many do you have in Steam? Note, that DLCs are not handled by plugin/Galaxy yet. If you Galaxy is missing a game and its title appears in plugin log (under "owned_games"), then this game is probably spammed by their filters, and should be fixed within a few weeks if you send a bug report via the client cogwheel menu. — |
I see. There are two errors I see.
This is error comes from other code thats not the |
appmanifest_.zip
plugin-steam-ca27391f-2675-49b1-92c0-896d43afa4f8.log.zip
The text was updated successfully, but these errors were encountered: