Android z-indexes changing #4560
Comments
|
Usually if things work correctly on other platforms but are broken on one, it indicates a problem with the platform, not Construct. If Construct's code was wrong, it would look wrong in Chrome too, but it looks right, suggesting Construct's code is actually correct. I suspect Android emulators may have poor quality graphics drivers which are causing the problem. Can you reproduce it on a real device? If not I would think this is a problem with the emulator, which means it would be something you'd need to report to the emulator developers. FWIW, I can't see anything in the r219 update that could be related to this; graphics driver problems can manifest unpredictably, so it may be an emulator bug that always existed but was only activated by some other innocuous change made in r219. |
|
You're right. I was able to load it up to a chromebook and android phone and the problem does not exist. |
|
OK, sounds a lot like a graphics problem with the emulator, so closing. |
Problem description
When exporting to Android/Cordova with a signed release APK, when running on Android simulators in Android Studio, the z-indexes of objects
changes only when there is a certain number of objects on a layor.
.cp3 - https://1drv.ms/u/s!AobC4q3rBlr62Ik1zIpMgzaZCakFYg?e=2SDHNV
Image on chrome browser:
Image on Android:
Steps to reproduce
Observed result
On Android the z-indexes of objects changes (but only if there are more than a specific number of objects on the layer).
Note that the barn image will go behind the ground image. Also, some of the sprites that are boxes will also go behind
the ground image. This does not happen on release r218, but will happen on all after that release.
Expected result
The z-index should not change.
More details
It seems that the z-index on Android is fine until a certain number of sprites are on a layer. Once that happens, the z-index
of some sprites change. Android Studio emulators were used. The problem occurred on all types tested.
This does not occur in iOS or on browsers (chrome and edge).
When sprites are taken away, then it seems like the z-indexes are where they should be. The problem occurs only after a certain number of sprites are on a layer.
Release: r234.4 stable (same result), Changing scripts to classic does not change outcome.
Release: r235 beta (same result)
Release: r233 beta (same result)
Release: r225 stable (same result)
Release: r222 beta (same result)
Release: r220.2 beta (same result)
Release: r220 (unable to load - get error)
Release: r219 beta - (same result)
Release: r218 stable - WORKS as it should.
It looks like it stopped working correctly on r219.
System details
The text was updated successfully, but these errors were encountered: