Sorry for the double post, but I have more weirdness to report: I decided to start a game, and saved normally. When I went to check file permissions for said save in Amaze, I got "rwx"! I got hopeful that I would at least be able to overwrite new saves with my old ones, even if I had to do so on a 1-by-1 basis, leaving only my custom shader. However, when I tried to do so via USB, it failed. Windows asks me if I want to overwrite the file, I click "Yes", and nothing happens.
@JosJuice any news on this? Sorry for insisting, and I understand if there isn't, I'm just checking
No, I still have no idea what's going on. Maybe I should just start adding those import and export buttons, but it'll take a little while and will definitely not be done for the next beta release.
(11-13-2021, 01:12 AM)JosJuice Wrote: [ -> ]No, I still have no idea what's going on. Maybe I should just start adding those import and export buttons, but it'll take a little while and will definitely not be done for the next beta release.
No problem, I understand. I'll just play on desktop for the time being
@JosJuice I hope I'm not being a nag, but I just saw on the progress report that you haven't even been able to verify the issue. Is there something I can do to help? Like running tests, screen recording attempts to do specific operations on my phone and/or PC through a USB cable, generating logs of any sort?... Sorry for insisting, and thanks in advance
Sorry, but I've already asked about all that I can think of that might help.
(11-14-2021, 05:08 AM)JosJuice Wrote: [ -> ]Sorry, but I've already asked about all that I can think of that might help.
No problem. I'll try and fiddle around with stuff on my own to see if I can find some sort of workaround, then. The progress report gave me an idea. If nothing works, I'll wait for you to implement the folder import/export function. Just one question: I've been using direct .apk installs, and when scoped storage was implemented, Dolphin did not import my dolphin-emu folder at all on install and behaved as if it were a fresh install, despite it being an update (even if manual). Is this the intended behavior? Would it have been any different through the Play Store? I imagine many non-savvy users will just be left in the dark if all their saves and settings are suddenly gone...
(11-14-2021, 06:03 AM)Shady Guy Jose Wrote: [ -> ]Just one question: I've been using direct .apk installs, and when scoped storage was implemented, Dolphin did not import my dolphin-emu folder at all on install and behaved as if it were a fresh install, despite it being an update (even if manual). Is this the intended behavior?
If the existing install was using the dolphin-emu folder, and you installed the new APK as an update (i.e. you did not uninstall Dolphin before installing the new APK), then it's supposed to keep using the dolphin-emu folder.
(11-14-2021, 06:24 AM)JosJuice Wrote: [ -> ]If the existing install was using the dolphin-emu folder, and you installed the new APK as an update (i.e. you did not uninstall Dolphin before installing the new APK), then it's supposed to keep using the dolphin-emu folder.
I assumed as much. That hadn't happened for me for some reason. But I uninstalled the current version, installed an older one (15260) and then reinstalled the latest version as an update and it's now working with the dolphin-emu folder. All my saves are working again. Thanks a bunch!
Well, I have no idea what's going on... But I'm glad it works, at least.