Recently upgraded to Starling 1.8 and ran into a problem. Note: not 100% the 1.8 update causes the issue, but we started noticing after the upgrade.
With the ATF tools from AIRSDK 19:
If I make an ATF with no mips and ECT only, it loads on my older android tablet. (WORKS)
-c e -r -n 0,0"
If I make an ATF with no mips and ECT2 only, it doesn't load: no errors, but the textures don't show up.
-c e2 -r -n 0,0"
Also, if I make an ATF with "all types", it also doesn't load: no errors, but the textures don't show up.
-c -r -n 0,0"
It seems as though ETC2 is being preferred or defaulted to when it's actually incompatible on this older tablet -> LG GPad 7"
I have a feeling this has to do with Context3DProfiles. I'm currently using "baseline" for this device, but probably should do some detection logic to run as something else like baseline constrained ?
Thanks in advance for any tips.