Skip to content

OS X Steam install not supported #88

@nbara

Description

@nbara

The current launcher currently only works with GOG. The reason is that the data structure is slightly different on Steam.

Here are the locations of the relevant folders on Mac/Steam :
/Users/username/Library/Application Support/Steam/SteamApps/common/Pillars of Eternity/
/Users/username/Library/Application Support/Steam/SteamApps/common/Pillars of Eternity/PillarsOfEternity.app
/Users/username/Library/Application Support/Steam/SteamApps/common/Pillars of Eternity/PillarsOfEternity.app/Contents/Data/Managed

The binary executable is located here (folder A) :
/Users/username/Library/Application Support/Steam/SteamApps/common/Pillars of Eternity/PillarsOfEternity.app/Contents/MacOS/

The only way to start the launcher is to direct it to folder A. However, while the launcher starts up fine like that, it then looks for the Assembly dll in the following (non-existent) folder:

/Users/username/Library/Application Support/Steam/SteamApps/common/Pillars of Eternity/PillarsOfEternity.app/Contents/MacOS/PillarsOfEternity_Data/Managed/

This gives an error as the folder does not exist. The correct Assembly DLL folder _for STEAM_ should be :

/Users/username/Library/Application Support/Steam/SteamApps/common/Pillars of Eternity/PillarsOfEternity.app/Contents/Data/Managed/

I've tried to put a symbolic link in MacOS/PillarsOfEternity_Data/Managed/, but it does not work. I guess mono does not handle those.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions