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

0.9.8 creates unnecessary subfolder for save states. #442

Closed
Tasosgemah opened this issue Dec 10, 2023 · 6 comments
Closed

0.9.8 creates unnecessary subfolder for save states. #442

Tasosgemah opened this issue Dec 10, 2023 · 6 comments

Comments

@Tasosgemah
Copy link

Tasosgemah commented Dec 10, 2023

I use the option for each core to save inside their own core-named folder.

With 0.9.7, the save states were stored in "states/DOSbox-pure"

With 0.9.8, the save states are stored in "states/DOSbox-pure/DOSbox-pure"

Is this an intentional change? Not sure how it helps.

@Massouille78
Copy link

Massouille78 commented Dec 19, 2023

Hello,

I also agree that save state and saves aren't be in subfolder.

0.9.7 was best choice.

Thanks in advance

@schellingb
Copy link
Owner

Looks like this is an issue with RetroArch when using a new libretro interface we use for enabling Netplay for DOS games. So until this is fixed in RetroArch we are kinda stuck... We maybe need to disable Netplay support until the fix is common in a stable release of RetroArch :-(

schellingb added a commit that referenced this issue Dec 23, 2023
…ng its "Sort Save States into Folders" option (#442)

Netplay is now only available with nightly builds of RetroArch (and once version 1.17 gets released)
@schellingb
Copy link
Owner

Please try the newly released 0.9.9.
It should be fixed with any stable RetroArch version (up to latest 1.16) and recent nightly builds of RetroArch. If you use an older nightly build of RetroArch (between 2 and 6 weeks old) it might still be broken.

@Tasosgemah
Copy link
Author

Yeah, it works on the latest nightly. On the previous one i used it's still broken like you said (it's from 15 Nov).

@Massouille78
Copy link

Hello, It is ok now for me on the last version 0.9.9,

Thanks very much

@PoloniumRain
Copy link
Contributor

I can also confirm that this issue is now fixed in both RA 1.16 and the latest nightly.

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

4 participants