Objects within YSort disappear/appear randomly in editor with GLES3

stuck_in_a_maze

I have a project with nested YSorts for different types of objects in my world, including the player. While using GLES3, these objects appear sporadically, changing their visibility depending on where I move the editor veiwport. This problem showed up when I added lots of scenes to the YSort, but removing them works only sometimes. When I switch to GLES2, the problem resolves, but I don't wanna use GLES2. I really have no idea what's happening.

I have integrated graphics on a laptop - Intel(R) UHD Graphics 620

Things I have tried:

Moving objects into the parent YSort node, so they aren't nested as much
Deleting some things - this only kinda worked.

cybereality

Could be a driver issue. Intel has really poor drivers. You may be able to work around this by putting in z-index overrides. It's kind of a hack, but it can work in some situations. I also found that the Image/Texture import settings are sometimes bugged on low-end devices / web / or mobile. There are sometimes several compression methods available (if you click the image on the lower left and then the Import on the upper left). You can filter all the images by typing ".jpg" or ".png" in the lower FileSystem dock and then using Control + Shift to select them all. Then click the Import tab and look on the image compression. Usually "lossy" works the most compatible. A setting on "0.7" or above should look good.

stuck_in_a_maze

cybereality I tried compressing my images like that, but sadly it didn't work. I think you're right about it being Intel, because I found someone with a similar issue who also had intel integrated graphics. Could you elaborate on what you mean by "z index overrides"? Thanks

cybereality

Any object that extends Node2D has a Z Index property. You can see this in the Inspector after you click on the object (it will be under where the position is). You can use this to manually set the order of Sprites and other 2D objects. They are relative (to the parent object) so you can nest a bunch of objects under one node if they are all on the same layer. This can be annoying if you have a lot of objects, and sometimes there are issues, but it's something to try if nothing else works. Higher Z values will be on top.