Uplay location needs to be updated.

[BloodShed]

Currently the Uplay location in GSM does not work.

Game saves for Uplay games are located in (default):

64-bit Windows: %PROGRAMFILES(X86)%\Ubisoft\Ubisoft Game Launcher\savegames\<user-id>\<app id>\
32-bit Windows: %PROGRAMFILES%\Ubisoft\Ubisoft Game Launcher\savegames\<user-id>\<app id>\

The path to the Uplay launcher can be found in the registry.

Reg hive: HKEY_LOCAL_MACHINE

Reg Path: SOFTWARE\WOW6432Node\Ubisoft\Launcher

Reg Key: InstallDir

Append to path "\savegames\<user-id>"


This should make all entries that use the Uplay path work again.

[InsaneMatt]

The path you specified is already detected.
There are actually two Uplay variables, one of which is 'hidden' from the selection.

• %UPLAY% - The variable the user can select for a Custom GameSave Entry.
  This variable directs to the AppData\Local\Ubisoft Game Launcher\savegame_storage directory.
• %UPLAY_2% - The 'hidden' variable which GameSave Manager automatically switches to when save detection using %UPLAY% fails.
  This variable directs to the directory you specified in your post.

[BloodShed]

The path you specified is already detected.
There are actually two Uplay variables, one of which is 'hidden' from the selection.

• %UPLAY% - The variable the user can select for a Custom GameSave Entry.
  This variable directs to the AppData\Local\Ubisoft Game Launcher\savegame_storage directory.
• %UPLAY_2% - The 'hidden' variable which GameSave Manager automatically switches to when save detection using %UPLAY% fails.
  This variable directs to the directory you specified in your post.

It's bugged!

I made a test with Assassin's Creed: Unity.

The %UPLAY% points to C:\Users\%USER%\AppData\Local\Ubisoft Game Launcher\savegame_storage.

This is wrong.

The correct path on my system is D:\Programs\Ubisoft Game Launcher\
My system is recently reinstalled, so no orphaned files from uninstall or updates and such.

[InsaneMatt]

How are you testing it?
The "Test" button within the Custom GameSave Entries Wizard has some... issues.

The variable should be parsed correctly when actually scanning your system for supported saves (i.e a system scan).