3D Engine Module

Target Use case

The lack of centralization of 3D functionality makes it impossible to make optimizations based on global state, and tight coupling between the APIs of deck.gl and luma.gl that makes it hard to update luma.gl and have a clear idea of what parts of deck.gl might be affected. A proper 3D engine in deck.gl responsible for 3D asset management and drawing operations would enable optimizations such as asset reuse and operation batching, and generally make both codebases easier to maintain.

Proposed feature

RFC: #2989

To Do List

• Add label and assign to milestone
• Coding
• Doc update
• What’s new update
• Test