Cogs Roadmap 2H 2018

Current release 3.0

Release December 2018

Performance
Debugging
Statistics
Inspectors
Concept naming review
- E.g ondemand -> sparse etc.
Policy/strategy control
- Performance metrics
- Bounds
Hierarchical level of detail
- Using sparsely instantiated asset hierarchy
Sparse instantiation
- Asset handling
- Shorthand handling
  - Lightweight representations
  - Not 1 -> 1
- Policy based level of detail
  - Recursive/controlled from top (?)
LoD transitions
- Handle non-binary transition between levels of detail
- Dithering etc.
Hot reloading of assets
- Stability
- Dependency tracking
Progress handling
- Dependency tracking
- Reporting
- Readyness/completeness/residency queries
- Size estimate/actual queries
  - Resources
  - Entity hierarchy
  - Asset definition hierarchy
Editor expansion
- Completeness for core operations
- Export options
  - Compact/shorthand format files
Remote operation
- Bridge
- Async bridge

glTF
- Review/include
CogsBin
- Support usage across platforms/builds
- Finalize spec v1
- Move floating spec/header to v2
CAD
- Investigate other formats
OpenImageIO plugin

Scrubbing
- Remove/rework hacks and undefined behavior
- E.g relocation w/o move
- Preserve licenses/terms of 3rd parties
  - E.g OpenTK in .Net
Stability
- Defensive in core areas
- Fail early/fast where "catastrophic"
- Handle/log/continue for 99%
Physical reorganization
- Cogs.Foundation -> Core/Libraries
- Cogs.Rendering -> Core/Libraries
- Cogs.Geometry -> Core/Geometry + reorg
- TerrainExtension dll
- DrillingExtension dll
Data formats
- Specification/documentation
- Feature cleanup
  - Pipeline variables/settings etc.
  - Asset/scene shorthand
Codegen sync
Licensing review
3rd party usage scan
Hosting review
- GitHub
- Internal
- VSTS
- ...

Component reorganization
- Investigate API remapping approach to support deprecation -> removal workflow
- TransformComponent
  - Split out GeoTransform component
  - Reevaluate parenting approach
- SceneComponent
  - Investigate chaining + selective ownership (where needed) for children
  - Support child iteration without ownership
  - Perhaps move parent/child relationships to EntityData (prevSibling/nextSibling or similar)
Async resource handling
- Background loading of assets
- Multithread/core upload of buffers/textures/etc.
Multicore rendering, async compute etc.