10000 Migrate more logic to core · Issue #1375 · NASA-AMMOS/3DTilesRendererJS · GitHub
[go: up one dir, main page]

Skip to content

Migrate more logic to core #1375

@gkjohnson

Description

@gkjohnson

Related to #1374, #1373, initial Babylon js implementation

In order to facilitate adding the loader in to other engines more logic from the three.js TilesRenderer can be migrated to the core implementation. Some ideas:

  • Codify a dedicate field for necessary and per-engine pieces of data per tile (see the "cached" subfield in three.js version). This could require fields such as "scene" and "boundingVolume".
  • The above should allow for events to implicitly fire a "scene" object that is currently used in TilesRenderer.
  • If "boundingVolume" is required and shaped consistently then raycasting logic could be moved to core.
  • Abstract handling of the "gltfUpAxis" behavior somehow.
  • "calculateTileViewError" is probably the most complicated function to implement and could be broken up into multiple more simple functions to make this more simple.
  • Relatedly, an abstract "camera" list could be maintained so the base class can iterate over them.
  • Move more events to core.
  • Move more update() function logic to core.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0