Call threshold prevents all atlas-based images from rendering about haxepunk HOT 2 CLOSED

It should be greater than. This checks to see if the layer data has passed a certain threshold. If it passes the threshold the atlas is drawn immediately. Haxe/NME was slowing down due to too many draw calls being processed at once so I added this in.

You can bypass it by setting Atlas.drawCallThreshold to a very high value. There is still a draw call later in render() so it shouldn't prevent any rendering.

from haxepunk.

Ah, okay, I get it now. I don't know why flipping the operator corrected my issue. I have some objects that just don't want to display in conjunction with the map, which is driven by HaxePunk-Tiled. The map is obviously obscuring the objects, but they show up under some conditions. If I push the map layer (which is at 100) back to 123 the objects show. 122 they don't. Mind you the nearest object is at layer 90, so this makes no sense to me. Or if I adjust the layer by 1 at runtime the objects appear at that point. The what where? Who what? Huh?!

from haxepunk.