Cloud Saves Syntax?
Hello, I noticed a few confusing things, in the address bar, and could not find anything while googling so am asking here.
This is what Moonlighter gave me:
{appdata}/../locallow/11BitStudios/Moonlighter/
What confuses me is locallow is miscapitalized, does capitalization not matter?
Also if we are playing by standard path rules, and {appdata} points to my prefixes AppData folder, then {appdata}/../ points to my prefixes user directory which of course does not contain the LocalLow folder.
Am I supposed to fix this, or does this path actually work?17 Replies
flat-fuchsia•3y ago
on window's NTFS filesystem, files and directories are case insensitive if I remember right
The path should be auto-computed by Legendary. If this is not working (as you can see by the path still having variables), something about your setup is not right (maybe your Wineprefix is set wrong, or you've selected a Wine binary that no longer exists). To know what exactly is going on there, send in a game log
The questions you've asked there are not really something you have to worry about, but just for completeness:
- Yes, paths are case-insensitive on Windows. Legendary has some special logic to handle these on Linux as well
-
{appdata} points to %APPDATA%, which on modern versions of Windows is %USERPROFILE%\AppData\Roaming (or in more simple terms, C:\Users\YourUsername\AppData\Roaming)magic-amberOP•3y ago
Ah, I see.
Here is my log: https://pastebin.com/UidNrxYb
Manually selecting the folder seems to have worked, but no matter what I do it just wants to auto generate the same {appdata} path
Pastebin
Heroic Cloud Save - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
magic-amberOP•3y ago
This is the correct path:
/home/wis/Games/Heroic/Prefixes/Moonlighter/drive_c/users/wis/AppData/LocalLow/11BitStudios/Moonlighterflat-fuchsia•3y ago
(10:03:59) ERROR: [Legendary]: Unable to compute default save path for Eagle something is preventing legendary from computing the correct pathmagic-amberOP•3y ago
Yes, the game runs by the way. Everything seems to work, it even looks like uploading saves work if I manually enter the path. As far as I can tell only computing the path is failing.
Fedora/Nobara 37, KDE
Thanks for the explanations. I can use the cloud save system now, but am willing to provide any logs or testing if you are interested in tracking down the issue.
LD_LIBRARY_PATH=/home/wis/.local/share/lutris/runners/wine/lutris-GE-Proton7-36-x86_64/lib64:/home/wis/.local/share/lutris/runners/wine/lutris-GE-Proton7-36-x86_64/lib::/opt/rocm/lib:/opt/rocm/lib64:/opt/rocm/profiler/lib:/opt/rocm/profiler/lib64:/opt/rocm/opencl/lib:/opt/rocm/hip/lib:/opt/rocm/opencl/lib64:/opt/rocm/hip/lib64
echo $LD_LIBRARY_PATH in a shell say?magic-amberOP•3y ago
~>echo $LD_LIBRARY_PATH 13:10
/opt/rocm/lib /opt/rocm/lib64 /opt/rocm/profiler/lib /opt/rocm/profiler/lib64 /opt/rocm/opencl/lib /opt/rocm/hip/lib /opt/rocm/opencl/lib64 /opt/rocm/hip/lib64Assuming your shell is adding spaces in place of :, looks like the extra : is also present at the start there
magic-amberOP•3y ago
Ah, yes fish is doing something different than bash
[wis@nobaru-x8664 ~]$ echo $LD_LIBRARY_PATH
:/opt/rocm/lib:/opt/rocm/lib64:/opt/rocm/profiler/lib:/opt/rocm/profiler/lib64:/opt/rocm/opencl/lib:/opt/rocm/hip/lib:/opt/rocm/opencl/lib64:/opt/rocm/hip/lib64:/opt/rocm/lib:/opt/rocm/lib64:/opt/rocm/profiler/lib:/opt/rocm/profiler/lib64:/opt/rocm/opencl/lib:/opt/rocm/hip/lib:/opt/rocm/opencl/lib64:/opt/rocm/hip/lib64Well, this is most likely unrelated, but you may want to find out where this is getting setup & remove that starting :
Other than that, you can try running this mouthful of a command. It's what Heroic runs to figure out the save path:
magic-amberOP•3y ago
The list seems to be doubled.
It seems to work
[Core] INFO: Trying to re-use existing login session...
[cli] INFO: Got 3 remote save game(s)
[cli] INFO: Checking "Moonlighter" (Eagle)
[cli] INFO: Cloud save for "Moonlighter" is newer:
[cli] INFO: - Cloud save date: 2023-02-05 15:51:14
[cli] INFO: - Local save date: N/A
[cli] INFO: Save game downloading is disabled, skipping...
wait, that is different. that did not work
yes, so if it is set correctly in the launcher it skipps because it is up to date
But if it it not set in the launcher it skips because it is disabled, evne tho it is enabled but has the wrong pathRight, if you already ran save sync, the path will be stored in legendarys metadata
I'll get back to you in ~half an hour
magic-amberOP•3y ago
hmm, might be hard to track down what is setting it, I am seeing things like firefox modifying that variable in some random binary file.
Alright, so
- First of all, close Heroic if it's still open
- Head to
~/.config/legendary and open up installed.json. Find the entry for your game & delete the save_path key
- After that, run the above command again
If it's set in your shell, check your (I assume) ~/.config/fish/config.fish or other scripts that run on login
Firefox may change that variable, but unless you actually run it (and it then launches other programs), that's not gonna affect your general sessionmagic-amberOP•3y ago
Ah, I see what you mean. But nothing in I am doing is touching LD_LIBRARY. It looks like
/etc/profile.d/rocm-meta.sh is running export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/rocm/lib:/opt/rocm/lib64:/opt/rocm/profiler/lib:/opt/rocm/profiler/lib64:/opt/rocm/opencl/lib:/opt/rocm/hip/lib:/opt/rocm/opencl/lib64:/opt/rocm/hip/lib64 Maybe this file gets called twice?
That seemed to fix it
[cli] INFO: Computed save path: "/home/wis/Games/Heroic/Prefixes/Moonlighter/drive_c/users/wis/AppData/LocalLow/11BitStudios/Moonlighter"
But I am a little confused their, as I played around with just deleting the entry in teh gui as well, that that seemed to delete the entire moonligher entry in that file, and that also worked, but it did not work before. Maybe the running version of heroic was just bugged, ands shutting it down and restarting it fixed it.
Well, I did some scripting so the next time I restart if it is this rocm file causes a weird library path it should be fixed. Then I just have to figure out where the bug report goes.Well, it being called twice shouldn't be an issue, but that leading : might be (since
LD_LIBRARY_PATH is empty before this runs)