x4ml

The issue can be related to the Platform's theme. Here are some tips: 1. Go to the Manage Themes page -> make sure that all your themes are up-to-date 2. Try to change the theme on the Platforms page by clicking the "3 dots" icon -> Change view Let us know about the result.

It can be the theme issue. Can you make sure that you are using the latest version of it? Also, what will be the behaviour if you switch to another theme?

Thanks for letting us know. We will check them and send you the result.

Thanks for letting us know! Will be fixed in the next beta

We are working on adding these emulators to the Android app. If everything OK, they will be added to the next beta

Hello, thank you for your feedback. I’ll discuss this with the team and see if we can get it fixed by the next beta release.

What platform are you trying to change the Emulator settings for?

I assume that you have enabled the "Hide Top Status Bar" and "Hide Bottom Navigation Bar" options on the Settings page. Try to change these options and see the result. If nothing helps, then the issue is related to the Android API version.

Thanks for letting us know. Yes, we forgot to include the fix related to the improved arcade filters. It will be fixed in the next release.

Your previous Settings.xml file may be in the "LaunchBox/Data/Backups" folder. If it's not there, then it was replaced with the default one. It's happening when it was corrupted or manually changed. To avoid such situations, after you have configured all your settings, make a copy of the Settings.xml file and store it in a safe location. When you get the same issue, just replace the current Settings.xml file with the saved one.

Hi, thanks for letting us know. It would be helpful if you could record a video, so we can see where exactly it's happening.

Let us know if you are still having the same issue in version 1.19-beta-1 (1.19 Beta Thread) Thanks.

Don't use CachingEnabled and CacheValidity when you work with local images (which are stored on the device), it has zero impact. The loading.png image doesn't exist in the app, so it will not be shown. The DownsampleToViewSize property will downscale the image to the container size in memory instead of loading the full image and letting the GPU scale it at runtime. (We don't recommend using it as it can decrease the quality of the image.)

In your tests, did you use a game that has 1 additional application? Or does the game have 2 or more additional applications? So far, I haven't been able to reproduce the issue with the PlayCount property. Showing PlayTime as a zero value is already fixed and will be included in the next beta.

Is this issue still reproducible in version 1.19-beta-1? We would be grateful to receive feedback from you. P.s. In version 1.19-beta-1, we have made major behind-the-scenes optimizations on the Filter and Game pages. So far, we haven't been able to reproduce this issue.