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
{{ message }}
This repository has been archived by the owner on Oct 19, 2020. It is now read-only.
The scene structure is the JSON representation of a scene where the models are either expressed in parameters or linked in as gz.data3d.buffer
Before the models can be processed (e.g. exported as some format), they need to be converted to a 3d model in the data3d format, which looks something like this:
The materials may need to be resolved using the default materials library
It's currently not possible to use the 3dio-js API in a meaningful standalone fashion
Behaviour
Method in 3dio-js where i can put in scene structure JSON and get data3d JSON
Implications
No breaking changes to existing stuff necessary
Steps
Separate param model resolver from aframe param model components (so called "architectural toolkit")
Call param model resolvers
Strategy for supporting "custom meshes", meaning objects that data3d meshes that are linked into the scene structure by path on S3 (update this issue when finished) Update: It turns out 3dio-js has functions for loading the sceneStructure from s3 bucket paths (aka "keys"). Added calls to storage.get to recursive scenestructure-to-data3d for now (scene/structure/to-data3d.js)
Scope
gz.data3d.buffer
Behaviour
Implications
Steps
Update: It turns out
3dio-js
has functions for loading the sceneStructure from s3 bucket paths (aka "keys"). Added calls tostorage.get
to recursive scenestructure-to-data3d for now (scene/structure/to-data3d.js
)storage.get
to not only work for files withdata3d.buffer/json
extension and file format Make storage.get work for getting any data out of s3 storage #140 ?utils/data3d/encode-binary
The text was updated successfully, but these errors were encountered: