![]() Eventually I will have to drop Win7 and move exclusively to linux, but not today. I can copy the command line params from the VM to Win7 and run that way. This all works with no command line params for non-DRMed, but fails for DRMed of course. Since I cannot use Legendary.exe on Win7 anymore due to dependency changes with it, I have experimented with using legendary latest on a linux VM for downloading, then running without legendary on the Win7 host. "the hunter call of the wild" works fine on Windows if I supply the parameters generated from a -dry-run from legendary. Ok, looks like it's not possible to run Epic DRM titles without legendary command line auth parameters which is what I have been doing for Epic non-DRMed titles. Installing Epic Games Launcher on Windows. ![]() The only way that I can imagine to get around this problem would for Heroic to install the EpicGamesLauncher within the game wine bottle and use that to invoke the launch of the game the user would like to launch from Heroic UI. This is the same behaviour when running Eratus from Epic from within Heroic as well (in my case in with PopOS). Meanwhile the log file has this error: HttpStatus=, ErrorCode=, NumericErrorCode=, ErrorMessage= (as seen in local file: C:\Users\AppData\LocalLow\Unfrozen\Iratus\output_log.txt). What the usual behaviour is, for running an Epic game downloaded only with Legendary.exe is that the game will launch and get as far as a black screen.įor example, when downloading and running Eratus in Windows with Legendary.exe, I get presented with a black screen and a visible in-game custom Iratus mouse pointer and nothing else. ![]() These games (on Windows) require to be launched from Epic Games Launcher to get past the Epic native DRM protection. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |