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.

Sign up for GitHub

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

Jump to bottom

Port Issue: Balatro savedata missing when using HDMI output #287

Open
2 of 20 tasks
michebble opened this issue Apr 14, 2024 · 0 comments
Open
2 of 20 tasks

Port Issue: Balatro savedata missing when using HDMI output #287

michebble opened this issue Apr 14, 2024 · 0 comments

Comments

@michebble
Copy link

Device Type

  • RG351P/M
  • RG351V
  • RG351MP
  • RG353M/V/P
  • RG503
  • RG552
  • RGB10
  • RGB30
  • RK2023
  • X55
  • Other device (device name here)
  • All of the above

Firmware

  • ArkOS
  • ArkOS Wummle
  • AmberELEC
  • JelOS
  • RockNix
  • uOS
  • RetroOZ
  • TheRA

Port: Balatro

Description

When connecting the the RGB30 to a screen via HDMI Balatro does not read previously saved data.

I believe data is usually saved in saves/loveBalatro_1x1. When running via HDMI I think that Balatro instead read/writes saves from saves/love/Balatro.

It would be great to be able to use the same same save data when either playing connected to a screen via HDMI or not.

Reproduction Steps

  • Power on the RGB30 without connecting to an external screen
  • Launch Balatro skip through tutorial and progress through the game to create some save data.
  • Connect RGB30 to a screen via HDMI
  • Power on the device
  • Launch Balatro
  • Saved data will not be recognised
@michebble michebble changed the title Port Issue: Port Issue: Balatro Apr 14, 2024
@JeodC JeodC changed the title Port Issue: Balatro Port Issue: Balatro savedata missing when using HDMI output Sep 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@michebble