Hi Sukender, On Thu, Aug 20, 2009 at 3:57 PM, Sukender<[email protected]> wrote: > Good news! I've sync'd the 3DS reader with lib3DS 2.0.0-rc1 (well, I need to > modify the CMakeList now). I'm not 100% sure that the one I used ( > http://www.lib3ds.org/ ) is the same as the one used in OSG... Am I wrong ? > If not, is it a problem ?
I believe it's probaby the same lib3ds, it's quite a few years since I reviewed the original source though. You should be able to spot similarities with the existing code base. Just adopting lib3ds won't carry the modifications that have been made by members of the OSG community so support reading for istreams etc, so I don't think a straight adoption of lib3ds will be possible without modifications of lib3ds or our plugin. I'm opposed to adopting any new code that drops existing functionality, the existing functionality is being actively used by members of the community. While 3ds write hasn't been up to now a requirement. > Should the lib3DS files be in osgPlugins/3ds, or osgPlugins/3ds/lib3DS, or > simply oustide as an external dependency to make sync easier? I've original put lib3ds into the 3ds plugin directory just to enable easy build for OSG users. These days with CMake building against 3rd party dependencies is less onerous, so potentially would could spin it out. The bottom line is the ability to support all that is supported by the existing plugin. > Once cleaned and submitted, I'll work on the 3DS writer, as told in another > thread. So are you porting the existing plugin across to use the external lib3ds, writing a new plugin from scratch, adapting the new lib3ds to be closer to what we have? I'm curious as to why writing to .3ds is a goal, as a exchange format it's pretty poor. Robert. _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
