Closed Nutzzz closed 2 years ago
PR #50 has both Legendary and Epic Games Launcher enabled by default. If legendary.exe is found in the same directory as GLC (or the provided path in glc.ini), then it is used; otherwise EGL is used. If Legendary is disabled in the .ini or is not found, and if EGL is disabled in glc.ini, then the .exe from the Epic .item file is used instead.
NOTE: I still need to add downloading of not-installed images. EDIT: See issue #55 .
With Epic games, we're currently launching straight from the game's .exe. This is great because (at least on my system) Epic takes forever to load and start a game. However, cloud saves aren't synchronized in this case, and I believe some games have issues with online multiplayer with this method [note to self: check whether this affects Origin, etc.].
Obviously we could (optionally) switch to using the Epic protocol to do the launching (com.epicgames.launcher://).
Another solution that addresses the slow response and games requiring Epic for online play is to allow users to (optionally) use Legendary, a lite command-line Epic client written in Python and compiled to .exe. However, note that syncing isn't automatic there either, and requires a separate command, i.e., you'd need to (optionally) run sync-saves, launch, then sync-saves again.
Not sure how this would be implemented as we move to the 2.0 plugin model (i.e., a separate Legendary plugin and/or plugin-specific configuration options [PlatformAttribute]).