search

PlayEveryWare / eos_plugin_for_unity

Repository for PlayEveryWare's EOS Plugin for Unity, bringing the functionality of Epic Online Services to the Unity Game Engine.
https://eospluginforunity.playeveryware.com
MIT License
274 stars 52 forks source link

"eac_launcher" app not opening #554

Closed The-RealBobi closed 5 months ago

The-RealBobi commented 6 months ago

Describe the bug Whenever I make a build in MacOS, and launch my game using the provided "eac_launcher" app, I'm always greeted by a "The application eac_launcher can't be opened" error.

To Reproduce

Make a build with EAC and launch your game with the "eac_launcher" app.

Expected behavior To have my game launched.

Desktop (please complete the following information):

Additional context This issue doesn't happen if I use the "start_protected_game" app provided with the EOS SDK, executing that app launches the game perfectly fine, with EOS and EAC.

arthur740212 commented 6 months ago

Did you have Epic Launcher installed on the Mac device?

The-RealBobi commented 6 months ago

Did you have Epic Launcher installed on the Mac device?

Hi, yes. Epic Games Launcher is installed.

arthur740212 commented 6 months ago

That might indicate our EAC implementation for Mac has something missing. We'll take a closer look on how EAC is set up for Mac.

arthur740212 commented 6 months ago

Have you enabled use EAC in Edit -> Preferences -> EOS Plugin. The EAC related configurations might need to be filled as well for eac_launcher.app to work.

The-RealBobi commented 6 months ago

Have you enabled use EAC in Edit -> Preferences -> EOS Plugin. The EAC related configurations might need to be filled as well for eac_launcher.app to work.

Hello, yes, the "Use EAC" option is checked, and all the paths are filled correctly.

arthur740212 commented 5 months ago

Hello, we found out that the permission flags for the EACLauncher have some interesting behavior on Windows, which is the platform we mainly build with, causing the upm to have missing info.

Quick fix is to run the command chmod +x eac_launcher (preferably on the launcher in the package, as modifying the one in the build might be considered violation by the anti cheat detection), this will allow the user to execute the file.

We will look for a more elaborate way to fix this issue in following releases. Thanks for the report.

paulhazen commented 5 months ago

Closing this issue as it has been resolved in the development branch.