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 LayerMasker only takes a number of layers, not a starting layer. This means that, if you pass uint.MaxValue to LayerMasker.Layers(), it will return layers below a minimum layer, if you are using one.
LayeredSpatialMap gets around this by using a couple layer maskers and also doing bit-shifts on values incoming. However, a simple mask >> startingLayer << startingLayer would remove them entirely from the mask.
In order to gain more intuitive behavior, it may be useful to have LayerMasker implement support for a starting (minimum) layer specifically.
The text was updated successfully, but these errors were encountered:
Currently, the
LayerMasker
only takes a number of layers, not a starting layer. This means that, if you passuint.MaxValue
toLayerMasker.Layers()
, it will return layers below a minimum layer, if you are using one.LayeredSpatialMap
gets around this by using a couple layer maskers and also doing bit-shifts on values incoming. However, a simplemask >> startingLayer << startingLayer
would remove them entirely from the mask.In order to gain more intuitive behavior, it may be useful to have
LayerMasker
implement support for a starting (minimum) layer specifically.The text was updated successfully, but these errors were encountered: