Re: [osg-users] the new glTF format by the Kronos Group

[Erlend Sogge Heggen]

More interoperability between OSG and glTF would be wonderful. If anyone starts 
working on something, be sure to let the glTF developers by dropping a note on 
this GitHub issue:

github.../KhronosGroup/glTF/issues/456

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=65808#65808





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] the new glTF format by the Kronos Group

[Christian Buchner]

Apologies for not proofreading my initial post as much. "a interesting"
should have been "interested".

Well, there is some source code in the Khronos github repository, but it's
mostly a Collada 2 glTF converter as well as some JavaScript code for
loading such content into WebGL I suppose.

So it seems the implementation of a reader plug-in would have to be mostly
from scratch. A writer plug-in might be slightly easier to come up with,
based on parts of the Collada 2 glTF converter.

Christian


2015-10-20 23:59 GMT+02:00 Jan Ciger :

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 20/10/15 20:56, Chris Hanson wrote:
> > I could probably crank out a glTF loader in short work if anybody
> > was interested. I haven't had any clients come forth demanding one
> > yet, but it may happen. We'll see. Can't be any more complicated
> > than COLLADA! ;)
>
> Well, considering it is a part binary format, I wouldn't underestimate
> it :) It could be easily a similarly complex mess, only in a different
> way.
>
> J.
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2
>
> iD8DBQFWJrk2n11XseNj94gRArJLAJ9F85H5NayajscCXBdkzGg//A1cwgCg268J
> CsXoNZLQwWo7rfJ7vxw6WcI=
> =ucym
> -END PGP SIGNATURE-
> ___
> osg-users mailing list
> osg-users@lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

[osg-users] the new glTF format by the Kronos Group

[Christian Buchner]

Hi all,

The Khronos group has published a specification for a data exchange and
transmission format for 3D objects and scenes, it appears

https://github.com/KhronosGroup/glTF

I think the OpenScenegraph community might be a interesting in implementing
a a file format plugin, or even come up with a standaloner viewer for this
format.

So far it is hard to tell if this format will be widely adopted. But having
support in OSG from an early point in time could either make OSG more
popular, or glTF...  ;)

Christian
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] the new glTF format by the Kronos Group

[Jan Ciger]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hello,

On 20/10/15 13:51, Christian Buchner wrote:
> Hi all,
> 
> The Khronos group has published a specification for a data exchange
> and transmission format for 3D objects and scenes, it appears
> 
> https://github.com/KhronosGroup/glTF
> 
> I think the OpenScenegraph community might be a interesting in 
> implementing a a file format plugin, or even come up with a
> standaloner viewer for this format.
> 
> So far it is hard to tell if this format will be widely adopted.
> But having support in OSG from an early point in time could either
> make OSG more popular, or glTF...  ;)

Interesting, I wasn't aware of something like this being in the works.
It could be useful to support, indeed. If someone is building a new
application, this could potentially save them some work, especially if
there will be tooling available.

On the other hand, I don't see much potential for this as an
interoperability format because I don't see major game/3D engine
vendors abandoning their proprietary "baked" asset for this. There is
 too much investment in their existing tooling already and a vendor
lock-in is a major factor in their interest too. E.g. Unity wouldn't
want to make it easier for their paying customers to jump ship to
Unreal (or vice versa). The same for the various asset stores these
companies are running - vendor lock-in is a major advantage there,
because they get to be the gatekeeper and collect toll.

J.

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iD8DBQFWJom6n11XseNj94gRAob+AKC4Eln1nSCdMHpke3Xfru7j16Q8fwCfa4fw
EZ7Kjzlr5DiW6M6QODDGzs4=
=gXAU
-END PGP SIGNATURE-
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] the new glTF format by the Kronos Group

[Chris Hanson]

I could probably crank out a glTF loader in short work if anybody was
interested. I haven't had any clients come forth demanding one yet, but it
may happen. We'll see. Can't be any more complicated than COLLADA! ;)

On Tue, Oct 20, 2015 at 12:36 PM, Jan Ciger  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello,
>
> On 20/10/15 13:51, Christian Buchner wrote:
> > Hi all,
> >
> > The Khronos group has published a specification for a data exchange
> > and transmission format for 3D objects and scenes, it appears
> >
> > https://github.com/KhronosGroup/glTF
> >
> > I think the OpenScenegraph community might be a interesting in
> > implementing a a file format plugin, or even come up with a
> > standaloner viewer for this format.
> >
> > So far it is hard to tell if this format will be widely adopted.
> > But having support in OSG from an early point in time could either
> > make OSG more popular, or glTF...  ;)
>
> Interesting, I wasn't aware of something like this being in the works.
> It could be useful to support, indeed. If someone is building a new
> application, this could potentially save them some work, especially if
> there will be tooling available.
>
> On the other hand, I don't see much potential for this as an
> interoperability format because I don't see major game/3D engine
> vendors abandoning their proprietary "baked" asset for this. There is
>  too much investment in their existing tooling already and a vendor
> lock-in is a major factor in their interest too. E.g. Unity wouldn't
> want to make it easier for their paying customers to jump ship to
> Unreal (or vice versa). The same for the various asset stores these
> companies are running - vendor lock-in is a major advantage there,
> because they get to be the gatekeeper and collect toll.
>
> J.
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2
>
> iD8DBQFWJom6n11XseNj94gRAob+AKC4Eln1nSCdMHpke3Xfru7j16Q8fwCfa4fw
> EZ7Kjzlr5DiW6M6QODDGzs4=
> =gXAU
> -END PGP SIGNATURE-
> ___
> osg-users mailing list
> osg-users@lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>



-- 
Chris 'Xenon' Hanson, omo sanza lettere. xe...@alphapixel.com
http://www.alphapixel.com/
Training • Consulting • Contracting
3D • Scene Graphs (Open Scene Graph/OSG) • OpenGL 2 • OpenGL 3 • OpenGL 4 •
GLSL • OpenGL ES 1 • OpenGL ES 2 • OpenCL
Legal/IP • Code Forensics • Digital Imaging • GIS • GPS •
osgEarth • Terrain • Telemetry • Cryptography • LIDAR • Embedded • Mobile •
iPhone/iPad/iOS • Android
@alphapixel  facebook.com/alphapixel (775)
623-PIXL [7495]
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] the new glTF format by the Kronos Group

[Jan Ciger]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 20/10/15 20:56, Chris Hanson wrote:
> I could probably crank out a glTF loader in short work if anybody
> was interested. I haven't had any clients come forth demanding one
> yet, but it may happen. We'll see. Can't be any more complicated
> than COLLADA! ;)

Well, considering it is a part binary format, I wouldn't underestimate
it :) It could be easily a similarly complex mess, only in a different
way.

J.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iD8DBQFWJrk2n11XseNj94gRArJLAJ9F85H5NayajscCXBdkzGg//A1cwgCg268J
CsXoNZLQwWo7rfJ7vxw6WcI=
=ucym
-END PGP SIGNATURE-
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org