HGL
absent-sapphire
Unable to launch any game and 'Cannot get game info'
Every time I press 'Play Now', a green 'Playing' pops up in the upper-left corner for around 2 seconds, and afterwards, nothing happens. I wanted to verify the game files, but upon clicking in the game to view it's info, to access the verification button, I got a message 'Cannot get game info'.
Full Heroic log: https://paste.debian.net/1275976/
24 Replies
absent-sapphireOP•3y ago
Found a different log too, might be helpful: https://paste.debian.net/hidden/7e079ff2/
harsh-harlequin•3y ago
I think Tim Sweeney said no https://mobile.twitter.com/TimSweeneyEpic/status/1490759707841159174
Tim Sweeney (@TimSweeneyEpic)
@leanuxguy @Blastermaster77 @Stormy178 @FortniteGame With regard to anti-cheat on the Linux platform supporting custom kernels and the threat model to a game of Fortnite's size, YES THAT'S EXACTLY RIGHT!
Likes
156
Twitter
absent-sapphireOP•3y ago
Isn't that about Linux?
harsh-harlequin•3y ago
Oh I'm sorry
I didn't realise heroic ran on non Linux oses
I'll shut up and leave it to people who have a clue lol
statutory-emerald•3y ago
looks like legendary is trying to do something when the official Epic Games Launcher app, did you have that and then uninstalled it? trying reinstalling it to see if the error disappears
absent-sapphireOP•3y ago
I reinstalled the Epic Games Launcher, the error is still there.
I used to have the Epic Games Launcher, I uninstalled it. After uninstalling it, I realized it also deleted all game files, which were installed with Heroic. After reinstalling the games through Heroic, the aforementioned errors came.
fascinating-indigo•3y ago
Probably the install.json is corrupted
absent-sapphireOP•3y ago
How could I make the file regenerate/fix the issue?
conscious-sapphire•3y ago
remove the
~/.config/legendary/installed.json
, it should do the trick
oh, wait, you're on windows
the file is somewhere else then, find it and remove itTry disabling EGL Sync completely:
I'd be curious how you came to that conclusion
absent-sapphireOP•3y ago
When opening the
legendary.exe
, the terminal almost immediately closes.fascinating-indigo•3y ago
Soen json is corrupted maybe not installed.json but some json is corrupted else it would not throw json syntax error in the log
Right, but that's just because we expect Legendary to give us its launch config, but it doesn't (since it's throwing that exception, and that exception isn't JSON)
Run the whole command in a terminal
absent-sapphireOP•3y ago
The term 'legendary' is not recognized as the name of a cmdlet, function, script file, or operable program.
That's not the full command. Copy exactly what I've sent, paste it in (with a right-click)
absent-sapphireOP•3y ago
Nevermind, I just forgot to start the command with
.\
The games seem to work now.
Can something bad happen if EGL Sync is disabled?EGL Sync syncs your Heroic-installed games with the EGL & your EGL-installed games with Heroic
If you don't use the EGL, you don't need it at all
absent-sapphireOP•3y ago
OK, thanks.
fascinating-indigo•3y ago
In the log that does not exist anymore it was defently a json parse error
statutory-emerald•3y ago
what command means is that legendary is failing with this output:
and we are trying to parse that output as json, so the error parsing json is caused because the legendary output is an error and not json, not because legendary can't parse a json file
fascinating-indigo•3y ago
Ok gotcha now
Can we catch the error before we parse it? Probably this should be ozogged to stderr or if spawn is used it should be
spawn.on('error')
statutory-emerald•3y ago
we can, just somebody has to do it haha
I mean game will fail to launch but we could also use that catch to suggest the user to disable the egs-sync with a click on a button that runs the legendary command and then relaunch the game, I think it would the most userfriendly option, like saying "this happened, it is common if you uninstalled EGS, do you want to disable this legendary feature and re-launch the game? yes / no"
fascinating-indigo•3y ago
Its more about that i feel we don't log all legendary error but maybe i am incorrect. At least the json pasre should not be done on error
Spawn's
error
signal only means "something went wrong while spawning the process" (as in, file doesn't exist, file isn't executable, that stuff)
All Legendary output is written to Legendary's own log file. Having everything in Heroic's log would be a mess