You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the mapnodes are sorted by a Z-index. which works fairly well for 1x1 tiles.
For multitile buildings, it's not possible to calculate a Z-index that will work. Instead, mapNodes should be sorted by a depth search.
I think it's safe to assume, that only the BUILDINGS layer will inhabit multitile buildings. We will still need a basic Z-Order for the overlapping terrain tiles.
Worst case, we'll have two containers (with mapnode*) in two orders, and move the rendering to Map to render each layer.
Hi, I'd like to help with this issue. But I found that current implementation doesn't use Z-index. Is it ture? And why there will has multiple buildings in one node?
Currently the mapnodes are sorted by a Z-index. which works fairly well for 1x1 tiles.
For multitile buildings, it's not possible to calculate a Z-index that will work. Instead, mapNodes should be sorted by a depth search.
I think it's safe to assume, that only the BUILDINGS layer will inhabit multitile buildings. We will still need a basic Z-Order for the overlapping terrain tiles.
Worst case, we'll have two containers (with mapnode*) in two orders, and move the rendering to Map to render each layer.
I found this article:
http://shaunlebron.github.io/IsometricBlocks/
Source Code:
https://github.com/shaunlebron/IsometricBlocks
The text was updated successfully, but these errors were encountered: