OpenSceneGraph

Files

Robert Osfield da2efd5feb From Aurelien Albert, "I get a compile error on Windows VS2008 wih new DAE plugin, here is a fix :

_document = _dae->openFromMemory(fileURI, buffer.data());

"data" method is unknow for std::vector with VS2008

I've replaced it with :

    _document = _dae->openFromMemory(fileURI, &buffer[0]);
"

2013-01-07 15:03:22 +00:00

CMakeLists.txt

From Michael Platings, "Here's the all-new, all-dancing DAE plugin, with support for reading

2010-02-26 14:41:50 +00:00

daeRAnimations.cpp

Ran script to remove trailing spaces and tabs

2012-03-21 17:36:20 +00:00

daeReader.cpp

From Aurelien Albert, "I get a compile error on Windows VS2008 wih new DAE plugin, here is a fix :

2013-01-07 15:03:22 +00:00

daeReader.h

From Oren Fromberg, ""

2012-10-08 11:54:40 +00:00

daeRGeometry.cpp

Fixed build with OSG_USE_REF_PTR_IMPLICIT_OUTPUT set to OFF.

2012-04-19 13:18:58 +00:00

daeRMaterials.cpp

From Luc Frauciel, "I've encoutered a nasty group of dae which are incompatible with dae plugins (and probably collada schema ) in 4 different ways :

2012-03-23 11:16:01 +00:00

daeRSceneObjects.cpp

Ran script to remove trailing spaces and tabs

2012-03-21 17:36:20 +00:00

daeRSkinning.cpp

From Sukender, "Added ability for writer to read from Vec3/4d/f. Plugin now warns if it finds another type of data"

2011-01-19 10:31:49 +00:00

daeRTransforms.cpp

From Chris Denham, "This is a submission to fix a problem with use of mode GL_RESCALE_NORMAL for geometries below a scaling transform which is not equal in X, Y & Z components. In this case, the 'slow' method of mode GL_NORMALIZE should be used to perform the normalization.

2012-02-09 14:11:36 +00:00

daeWAnimations.cpp

From Sukender, I wrapped my change about non-empty texture units in an off-by-default option, so that it doesn't break any existing code. But AFAIK, other readers (except OSGx) generate contiguous texture units, so I guess this option to be useful for users.

2011-05-16 10:07:20 +00:00

daeWGeometry.cpp

Ran script to remove trailing spaces and tabs

2012-03-21 17:36:20 +00:00

daeWMaterials.cpp

Ran script to remove trailing spaces and tabs

2012-03-21 17:36:20 +00:00

daeWriter.cpp

Ran script to remove trailing spaces and tabs

2012-03-21 17:36:20 +00:00

daeWriter.h

2011-05-16 10:07:20 +00:00

daeWSceneObjects.cpp

Ran script to remove trailing spaces and tabs

2012-03-21 17:36:20 +00:00

daeWTransforms.cpp

2011-05-16 10:07:20 +00:00

domSourceReader.cpp

Ran script to remove trailing spaces and tabs

2012-03-21 17:36:20 +00:00

domSourceReader.h

Ran script to remove trailing spaces and tabs

2012-03-21 17:36:20 +00:00

ReaderWriterDAE.cpp

From Oren Fromberg, ""

2012-10-08 11:54:40 +00:00

ReaderWriterDAE.h

From Oren Fromberg, ""

2012-10-08 11:54:40 +00:00

README.txt

From Jeremy Moles and Rbert Osfeild, added extra details about CMake build options.

2007-06-04 20:32:15 +00:00

scea_shared_source_license.html

From Andrew Lorino and Mike Weiblen, COLLADA 1.4.1 ReaderWriter, kindly developed and donated by Sony Computer Entertainment Inc. US R&D.

2006-08-23 13:32:03 +00:00

README.txt

osgPlugins/dae/README.txt -  Mike Weiblen http://mew.cx/

OSG reader/writer plugin for the COLLADA digital asset exchange (DAE) schema.
See http://collada.org/ and http://khronos.org/collada/ for further info.


RUNTIME USAGE EXAMPLES

    osgviewer myFile.dae
    osgconv myFile.osg myFile.dae


RUNTIME PLUGIN OPTIONS

Import Options
--------------
none

Export Options
--------------
polygon : export polygons as COLLADA polygons instead of polylists.
          This option can be used for if polylists are not supported.
          ex : osgconv -O polygon myFile.osg myFile.dae


BUILD DEPENDENCIES

- COLLADA DOM (document object model) v1.4.1
  http://collada.org/mediawiki/index.php/DOM_guide:_Setting_up

- libxml2

- iconv

A standard "ccmake ." while in the root of the OSG source will expose
two CMake variables: COLLADA_INCLUDE_DIR and COLLADA_LIBRARY. Using
these two variables correctly can be a bit tricky (especially as
the "right" and "wrong" ways to use Collada are hard to define), but
I will briefly explain them below.

  COLLADA_INCLUDE_DIR: This variable wants the path where it can
  find the COLLADA headers. On most systems this will be something
  like /usr/include or /usr/include/collada.

  COLLADA_LIBRARY: This variable is asking for the FULL PATH to the
  file libcollada_dom.a. As long as it can find this file, the
  OSG Collada ReaderWriter should build just fine.