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

After update Arcade roms are unplayable #918

Open
TISupe opened this issue Jul 8, 2024 · 4 comments
Open

After update Arcade roms are unplayable #918

TISupe opened this issue Jul 8, 2024 · 4 comments

Comments

@TISupe
Copy link

TISupe commented Jul 8, 2024

I recently updated to the recent update and tried playing few arcade games but none work now. which worked before the update. There were no chages made to roms or roms directory.

this is what it show now:
Screenshot_20240709_014259_Lemuroid

Working Version: 1.15.0
Games tried: All my Arcade library

Addtional Request: Please just stick with older UI its snappiness and simplicity will be missed╥﹏╥. Ingame Side UI is a good idea tho(✿╹◡╹) keep it please with older menu UÌ̗( ˶'ᵕ'˶)

@mimvahedi
Copy link

mimvahedi commented Jul 9, 2024

Try factory reset in Lemuroid advanced settings

@TISupe
Copy link
Author

TISupe commented Jul 9, 2024

Try factory reset in Lemuroid advanced settings

im just sticking with the older ver for now till i find something worthwhile in the update

@master1274
Copy link

Попробуйте выполнить сброс настроек в расширенных настройках Lemuroid.

я пока просто придерживаюсь старой версии, пока не найду что-нибудь стоящее в обновлении

A little strange. Report a problem. Get the correct answer to solve it (reset settings). Then refuse to solve the problem.

@TISupe
Copy link
Author

TISupe commented Jul 10, 2024

Попробуйте выполнить сброс настроек в расширенных настройках Lemuroid.

я пока просто придерживаюсь старой версии, пока не найду что-нибудь стоящее в обновлении

A little strange. Report a problem. Get the correct answer to solve it (reset settings). Then refuse to solve the problem.

Strange...?.. I just wanted to report it so it could be fixed in later updates. I have solved the problem by not updating.

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

3 participants