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
Right now, with 4 cameras we get 15 tiles. That's overkill, as most will be empty. It's better to have 9 tiles (8 compass directions, and one "other" that combines the rest of the tiles).
The "other" tile could have a direction of "up" or "down" that should work fine with the selection algorithm.
Integrating the tilemapper turns out to be more work, because we have to recompute the new tileconfig and this is not trivial.
Also, it should ideally be done at the source, so in the native code and when we create the tiled point clouds (so we don't pay an extra performance penalty).
Right now, with 4 cameras we get 15 tiles. That's overkill, as most will be empty. It's better to have 9 tiles (8 compass directions, and one "other" that combines the rest of the tiles).
The "other" tile could have a direction of "up" or "down" that should work fine with the selection algorithm.
Linked to https://github.com/jvdrhoof/mmsys_2025/issues/19
The text was updated successfully, but these errors were encountered: