MapStructure Optimizations: Difference between revisions

Jump to navigation Jump to search
No edit summary
Line 31: Line 31:
*  visible range (possibly constrained by a FOV,i.e. two bearing lines)
*  visible range (possibly constrained by a FOV,i.e. two bearing lines)


[[File:Navigation display MAP mode.png|thumb|right]]
[[File:Range-based-Visibility-Groups.png|thumb|Screenshot showing the [[Canvas]] [[NavDisplay]] with  visibility ranges used for  setting up dedicated Layer-specific Canvas groups]]
 
 
What this means is that we can be much smarter, and much more efficient, when updating the map - because we don't need to remove symbols, we may only need to "hide" them - because they may not be visible in the currently selected range, but they  may be visible if one of the other selectable ranges is chosen.
What this means is that we can be much smarter, and much more efficient, when updating the map - because we don't need to remove symbols, we may only need to "hide" them - because they may not be visible in the currently selected range, but they  may be visible if one of the other selectable ranges is chosen.
The point being, we can stop removing symbols like cray when toggling between ranges and simply hide stuff that is outside our current visibility volume due to the currently chosen range and/or map  mode.
The point being, we can stop removing symbols like cray when toggling between ranges and simply hide stuff that is outside our current visibility volume due to the currently chosen range and/or map  mode.

Navigation menu