Upgrading to 5.1.1 from 4.27.2 messes textures ASTC Android GLS3.2

Development Rendering
, , ,
1

When I upgrade game from 4.27.2 to 5.1 everything looks great in editor but on device textures are messed in ASTC Android GLS but VULKAN looks fine.
Model: One mesh + 1 texture

2
2839Ă—1799 313 KB

1
1839Ă—1799 259 KB

Please Help. I would really appreciate any ideas to solve this issue or it is bug. Thanks

2

Hey there @Nire2020! That does seem like it could be a bug, though determining if it’s changes to the renderer between the versions or a bug in the migration system. Is the material simple enough to be able to recreate the material under a new material? It would give some good information on what may have caused it.

3

Thanks for respond. Material is simple. In Editor works fine, but on devices messed built with 5.1. while built with 4.27.2 its ok same as in Editor.

mat
mat1518Ă—876 107 KB

alpha
alpha1842Ă—888 245 KB

Im just changing colors of characters by alpha

I would leave in 4.27 but need TARGET SDK 33.

Thanks

4

This is from editor and built with 4.27.2:

1
1510Ă—984 123 KB

2
2484Ă—952 132 KB

5

Interesting! It kind of looks like compression artifacting, though that shouldn’t be the case purely from migration. Also if Vulkan is working correctly for it that’s even weirder. I know there were some changes to the between the versions but I couldn’t find much information on it. If a fresh shader rebuild doesn’t help, and the compression isn’t the case, this will be a bit of an odd one.

Could you try adjusting the scalability up and down in the standalone? (This shouldn’t fix it but depending on the changes it might give us some insight, specifically testing LODs/Mips and draw failure at once).

6

I have tried adjust scalability texture quality (all), material , shading quality in device profiles but still “dirty” textures and yes vulkan is working great but earlier in 4.27.2 we used GLS.

The point is that everything works great built with 4.27.2 But we need TARGET API 33 as Google requires but have issues with that also. Because of permissions. BTW We should edit manifest, but it is not possible without c++. We should add :

<manifest …>

<uses-permission android:name="android.permission.READ_MEDIA_IMAGES" />

<!-- Required to maintain app compatibility. -->
<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE"
                 android:maxSdkVersion="32" />

but it is not possible with Project settings Android permissions and tags because it is limited

BTW If you have any idea how to implement this in Project settings - > Android please share

Thank you very much for your support

7

I work mostly PC side so mobile deployment isn’t my specialty, so I can’t help much with the manifest question, especially android side, so I’d hate to give misinformation there!

That said, material wise this is quite strange. In editor, does the ES3 display preview do this as well? I’ve been attempting to find more information on similar issues, but this one seems unique!

1 Like