Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Different save folders used for Dark Souls II: Scholar of the First Sin on Google Drive for Windows and SteamOS #110

Open
IvanPashchenko opened this issue May 18, 2023 · 1 comment

Comments

@IvanPashchenko
Copy link

IvanPashchenko commented May 18, 2023

Describe the bug
When I upload the saves from Windows (selecting the folder manually as per #92, the save gets uploaded to Dark Souls II: Scholar of the First Sin (note the spaces). When I try to sync the saves on the Steam Deck, the empty folder Dark_Souls_II:_Scholars_of_the_First_Sin is created,

To Reproduce
Steps to reproduce the behavior:

  1. Install the v0.18.1 ee6914029a08e79946e56e21fbfbcfed795c684a version on Windows using msi installer from GH
    2, Choose Google Cloud as the provider
  2. Upload Dark Souls II: Scholar of the First Sin saves using the workaround provided in Dark Souls III (And potentially any other game using a SteamID variable in the file path) #92
  3. Install the v0.18.1 ee6914029a08e79946e56e21fbfbcfed795c684a version on SteamOS via flatpak
  4. Choose Google Cloud as the provider
  5. Try to sync Dark Souls II: Scholar of the First Sin saves
  6. An empty Dark_Souls_II:_Scholars_of_the_First_Sin is created on Google Drives, no saves are synced.

Expected behavior
The same folder is used between 2 OSes and the saves are synced

Screenshots
Windows (note that the name of the game on the first line uses spaces):
image

SteamOS (note that the name of the game on the first line uses underscores):
image

Desktop:

  • Windows 22H2 (Build 22621.1702)
  • SteamOS 3.4.6 Build 20230313.1, Kernel Version 5.13.0-valve36-1-neptune
@DavidDeSimone
Copy link
Owner

Thanks for the report - hopefully this will be addressed once #107 is released.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants