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

Size/performance comparison to COLLADA #28

Closed
pjcozzi opened this issue Mar 21, 2013 · 7 comments
Closed

Size/performance comparison to COLLADA #28

pjcozzi opened this issue Mar 21, 2013 · 7 comments
Labels

Comments

@pjcozzi
Copy link
Member

pjcozzi commented Mar 21, 2013

This is a new github label for developer outreach ideas, e.g., demos, publications, presentations, etc. Anyway...

When glTF stabilizes, it would be good to show some size and speed comparisons to COLLADA or even other formats to help motivate glTF. Even compare amount of code needed to write a renderer. Perhaps we can use Three.js, which already supports other formats for the load speed comparisons.

@RemiArnaud
Copy link
Contributor

I'm writing a collada.js loader - did not like the ones I've seen so far..

On Wed, Mar 20, 2013 at 5:52 PM, Patrick Cozzi notifications@gh.neting.ccwrote:

This is a new github label for developer outreach ideas, e.g., demos,
publications, presentations, etc. Anyway...

When glTF stabilizes, it would be good to show some size and speed
comparisons to COLLADA or even other formats to help motivate glTF. Even
compare amount of code needed to write a renderer. Perhaps we can use
Three.js, which already supports other formats for the load speed
comparisons.


Reply to this email directly or view it on GitHubhttps://github.com//issues/28
.

@fabrobinet
Copy link
Contributor

as a side note, feeding three.js with glTF works as the example shows, but not the best case scenario.
It looks that Three.js doesn't take arraybuffer as input for the vertex attribute so the loading will likely be sub optimal here.

@tparisi
Copy link
Contributor

tparisi commented Mar 21, 2013

There are MANY issues with Three.js. The COLLADA loader is not good. I have fixed several serious bugs in there, including ahem lights were never even implemented. So anything people do in this area would be great. FYI at some point, soon, I will put in a pull request with Ricardo to get these changes pushed back into the mainline.

@pjcozzi
Copy link
Member Author

pjcozzi commented Apr 5, 2013

If we can find someone to code it, it would also be interesting to show loading performance of glTF vs. a completely binary format. Depending on packaging, glTF is most likely a tad slower, but probably not significant enough to turn folks off.

@fabrobinet
Copy link
Contributor

IMO depends mostly if you have very big node hierarchy...

@pjcozzi
Copy link
Member Author

pjcozzi commented Jul 7, 2015

We can use some of the numbers in #395

@pjcozzi
Copy link
Member Author

pjcozzi commented Oct 19, 2015

Now part of #456.

@pjcozzi pjcozzi closed this as completed Oct 19, 2015
donmccurdy pushed a commit to donmccurdy/glTF that referenced this issue Oct 15, 2021
JSON schema cleanup for EXT_mesh_features
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants