I noticed this a while back as well, but it mainly occurs when I try and use solid black. I've noticed that I don't get the pixelated messes when I use a few shades lighter. It's not black/black, but it's still pretty close and doesn't mess up for me. I know this is an old post, but I hope this helps.

I appreciate the input. I'll look into that. I'm not hopeful because I haven't touched many of those addons in a long while since they were all working fine. However, I will try and once again I appreciate the time.

Hey there, I'm very confused. In C3, I can preview my game and I can do the remote preview with the scanning option on my phone and it all works the way it should. If I export the game as an APK now, it will always crash.

Any thoughts?

I would like to be able to have the player pick some MP3's that the player has on their computer to listen to when the game is going. There's a fileChooser function and that loads a file or multiple files, but I'm not sure how to get it to play.

This is all done on my phone.

I've also uninstalled and reinstalled the program. I've also (because something similar happened a year ago) I've deleted the images and made new ones and the problem persists. It's like the images are reverting to a previously posted position.

The weird part is that when the 2nd to last update went live, it changed on my wife's phone, but not mine.

That makes things way easier knowing that. Thank you for replying.

On to game #2!

OK, if there this already a post on this, I couldn't find it. I would like a simple explanation on how this is going to work because Google has been terrible at responding to questions.

From Google: "This is a reminder that starting November 2, 2020, updates to apps and games on Google Play will be required to target Android 10 (API level 29) or higher. After this date, the Play Console will prevent you from submitting new app bundles and APKs with a targetSdkVersion less than 29."

Does this mean when we export we'll have to make it so that it only supports Android 10 so older Android builds are gone and you lose the people that have older devices?

If the game is fine, could we possibly just build it for compatibility for Android 5 and then not worry about updates because the game is finished?

Is there a way to build for API lv29 as a target while still maintaining compatibility with lower versions of Android in Construct 3? (I think you can do that in Visual Studio as per Microsoft's site.)

Thanks in advance... gosh I hope this gets answered lol.

I appreciate the alternative, but creating a button did not work for me either (although I agree that it should have).

Something happened to a sprite text on one of my saves so the list only shows "Lv1-0" instead of "Lv1-01". I have since fixed that and when I export the game to my phone this change shows. It shows in C3 itself, but when I do the preview layout or project, it still shows the old incorrect sprite font and doesn't reset the game proper.

The way I fixed it was to disable my load button and have it reset the defaults for when the load fails (when there is no save data).

All this to say... this process should be easier. While convoluted, I feel C2's "just delete the files on your computer" method was easier and quicker (once I found out about that answer that is).