-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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 and SRC #364
Comments
These changes would help open up a whole range of applications. One example is fast isosurface renderings from atmospheric and oceanographic forecast models. |
FWIW, although not using SRC, this are demos illustrate the kind of streaming capabilities we are currently missing in glTF: |
Thanks - just send me an email if you have a free spot for a short call, should not take too much time. |
|
Closing now that we are collaborating on extensions. 👍 |
Hi all,
maybe you have already heard about the SRC (Shape Resource Container) format, especially if you're involved in the X3D(OM) community.
It's something we have designed last year, partially deriving it from glTF, we also published a paper about that on Web3D 2014 (see project page: http://x3dom.org/src).
The paper provides a comparison between glTF and SRC, discussing the reasons for not taking the current state of glTF as-is.
So, an interesting question is:
Are there any chances the the changes proposed by SRC could, at some point, find their way into glTF?
It could be useful for us to refer to SRC as a subset of glTF, and it could also be useful if glTF would provide the benefits of SRC (like progressive streaming).
Thanks in advance.
Regards,
Max
P.S.: If you prefer discussion via email instead of the issue tracker, you can also write me to
max dot limper at igd dot fraunhofer dot de
P.P.S.: Just for completeness, there was another interesting paper at last Web3D which also proposed a format for streaming binary data (entitled Blast), and it also includes a brief discussion about glTF (http://dl.acm.org/citation.cfm?doid=2628588.2628599&CFID=626140191&CFTOKEN=41679963). So, it seems there's a need for streaming and efficient handling of binary data.
The text was updated successfully, but these errors were encountered: