The open source Heroic Games Launcher for running Epic Games and GOG has another important bug-fix release now available.
Version 2.4.3 continues the fixing from the last version, to deal with Epic Games changing things behind the scenes so this should get everything working again for Linux and Steam Deck.
Here's what's new:
- Fixed games from Epic games not downloading due to HTTP Error. It seems Epic broke something on their side again.
- Fixed long issue with GOG games getting progress stuck while the game was being downloaded.
- Fix some errors on Windows that was making Heroic to break on start on some machines.
- Adds 7 new languages: Azerbaijani, Basque, Belarussian, Bosnian, Romanian, Norwergian Bokmål and Slovak.
- Other minor fixes and improvements.
Hopefully Epic won't continually change their API, as it will become quite a nuisance for both users and the Heroic developers to keep fixing it up. As mentioned previously though, it's a reminder that sticking to Steam (and legit Steam Key stores) is likely your best bet for Linux and the Steam Deck.
Some you may have missed, popular articles from the last month:
4 comments
Apparently Tim Sweeney now loves Linux https://twitter.com/TimSweeneyEpic/status/1564669527165702145
Meanwhile, the Epig (typed correct) game store doesn't have a controller support, nor a way for it to play Linux games. I wouldn't support Epig in any way, until they start to give Linux love technically.
Meanwhile, the Epig (typed correct) game store doesn't have a controller support, nor a way for it to play Linux games. I wouldn't support Epig in any way, until they start to give Linux love technically.
5 Likes, Who?
I wouldn't be surprised if those changes are really intended to frustrate devs of alternate clients tbh...
1 Likes, Who?
Quoting: TermyI wouldn't be surprised if those changes are really intended to frustrate devs of alternate clients tbh...Breaking their own cdn backend probably isn't done on purpose. The epic launcher had issues too :D
1 Likes, Who?
Quoting: TermyI wouldn't be surprised if those changes are really intended to frustrate devs of alternate clients tbh...
In this case, they broke (or maybe disabled or put on maintenance) on of their CDNs. Legendary was not prepared to deal with that, I mean try other CDNs in case one is offline, so that caused the issue.
The login issue beforehand was because they changed how powerful the SID code was, so they removed permissions to it so it could not handle the login in practice anymore.
But yes, we need to be prepared for something else break again in the future, I expect it doesn't.
1 Likes, Who?
See more from me