Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

glTF 2.0 draft #826

Merged
merged 458 commits into from
Jun 5, 2017
Merged

glTF 2.0 draft #826

merged 458 commits into from
Jun 5, 2017

Conversation

lexaknyazev
Copy link
Member

@lexaknyazev lexaknyazev commented Feb 2, 2017

Previous discussion was in #784.


Story so far:

  • rewritten git history of 1.0.1 and lexaknyazev/master-test branches with changed paths to specification/2.0 directory;
  • objects-to-arrays syntax change update;
  • techniques, shaders, programs were moved to KHR_technique_webgl extension;
  • updates on JSON encoding and binary data layout

Specification TODOs
General 2.0 stuff:

Binary GLB format integration:

PBR:

Skinning & Morphs:

Other:

glTF 2.0 project: #867

@pjcozzi
Copy link
Member

pjcozzi commented Feb 3, 2017

Wow, great job, @lexaknyazev! I will review this a bit today and over the weekend. Thanks for this detailed work.

@pjcozzi
Copy link
Member

pjcozzi commented Feb 3, 2017

Update wetzel to v4 schema and regenerate property reference

@lasalvavida can you please do this after your COLLADA2GLTF 2.0 updates? We also need it for 3D Tiles, CesiumGS/3d-tiles#37 (however, no need to generate that doc now).

@pjcozzi pjcozzi mentioned this pull request Feb 3, 2017
23 tasks
@pjcozzi
Copy link
Member

pjcozzi commented Feb 3, 2017

I added names to items in the above tasklist, #826 (comment), please let me know if anything is incorrect.

@lexaknyazev
Copy link
Member Author

@pjcozzi
My proposal in #742 (multi-UV) remains (with 2.0 syntax changes).
Could PBR team review it?

@pjcozzi
Copy link
Member

pjcozzi commented Feb 3, 2017

@lexaknyazev could you please review the 2.0 issues and label them resolved if they are already included in this PR?

@pjcozzi
Copy link
Member

pjcozzi commented Feb 3, 2017

My proposal in #742 (multi-UV) remains (with 2.0 syntax changes).
Could PBR team review it?

Will ask there.

@pjcozzi
Copy link
Member

pjcozzi commented Feb 3, 2017

@sbtron can any of the issues labeled PBR be closed or combined to help keep us organized?

@lexaknyazev
Copy link
Member Author

@lexaknyazev could you please review the 2.0 issues and label them resolved if they are already included in this PR?

GitHub 2.0 issues and tasklist above should be in sync now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.