Greetings, RetroDECK dev here, this was a known issue that was solved on 0.6.2b (15/03/2023), now we are on 0.7.5b and that bug is only a memory. Please let us know if you encounter any issue related to your config if you will decide to try RetroDECK again. Thanks a lot for your patience :)
Greetings, RetroDECK dev here, this was a known issue that was solved on 0.6.2b (15/03/2023), now we are on 0.7.5b and that bug is only a memory. Please let us know if you encounter any issue related to your config if you will decide to try RetroDECK again. Thanks a lot for your patience :)