Yeah that's pretty weird. I doubt this is a result of upgrading to DOM
2.1. The Collada plugin has probably always had these problems, though I
could be mistaken.
Robert Osfield wrote:
2008/5/13 [EMAIL PROTECTED]:
I submitted a fix to osg-submissions. Diff (against trunk) is below for
I just tried this and I didn't have any problems. I'm on Ubuntu Gutsy.
Here's (roughly) what I did.
# DOM setup
sudo aptitude install libxml2-dev libpcre3-dev libboost-filesystem-dev
svn co dom
make
sudo make install
# OSG setup
sudo aptitude install cmake
svn co osg-trunk
svn co
Actually I can reproduce this now. I just wasn't calling it the same way
you guys were. I was giving the output file a full path, and in that
case the conversion works.
This is likely a simple error in the way the plugin converts URIs to
file paths (which, incidentally, doesn't need to be
I submitted a fix to osg-submissions. Diff (against trunk) is below for
anyone who wants it now.
Steve
===
--- src/osgPlugins/dae/ReaderWriterDAE.cpp(revision 8313)
+++ src/osgPlugins/dae/ReaderWriterDAE.cpp(working copy)
Hi.
For your information writer plugin for dae doesn't work at all:
osgconv cessna.osg cessna.dae
I/O error : Permission denied
I/O error : Permission denied
error : xmlNewTextWriterFilename : out of memory!
Error: daeLIBXMLPlugin::write(file://cessna.dae) failed
Warning: Error in writing to
HI Valery,
On Sat, May 10, 2008 at 12:48 PM, Валерий Быков [EMAIL PROTECTED] wrote:
For your information writer plugin for dae doesn't work at all:
osgconv cessna.osg cessna.dae
I/O error : Permission denied
I/O error : Permission denied
error : xmlNewTextWriterFilename : out of memory!
Hi Guys,
I've now merged Garrett's changes to get the dae plugin source code
compiling against colladadom 2.x, and have moved on to getting
colladadom 2.1 built and installed, but alas am struggling a bit.
For those trying to follow this path - the requirements for external
dependencies is looks
Hi All,
I've now manually copied collada libs into /usr/local/lib, a bit of
hack, but at least I've got things on the OSG compiling. Along with
my changes to the OSG's CMake files, and Garrett's changes to the
source things are compiling once more. I've checked in the changes
into SVN. The
Hello Robert:
The only ones I have been testing against are the Google models that
can be found:
this is the big hoard,
http://sketchup.google.com/3dwarehouse/
This model is pretty good:
View in Google Earth
and here is the main link for it:
Now I've got the dom built, but now the install apears to be playing up.
Sorry, there's a bug in the make install rule that causes it to not work on Linux unless
you're running from an svn checkout. I fixed the bug in the trunk and it'll go in the
next release, but for now you can comment out
On Tue, May 6, 2008 at 6:38 PM, [EMAIL PROTECTED] wrote:
Was waiting to see if Steve had any anomalies show up on his end.
Sorry, I know I said I'd look at this over the weekend but I didn't get a
chance. I'll definitely test this sometime this week.
Robert, I would move forward with
Hello Robert:
Not sure if Steve made additional changes but I did a submission of
the dae plugin to the osg- submission with title
here is the tar gz up of the dae module.
There were no core OSG interface modifications to the dae plugin so it
should be binary compatible at that level.
Was waiting to see if Steve had any anomalies show up on his end.
Sorry, I know I said I'd look at this over the weekend but I didn't get
a chance. I'll definitely test this sometime this week.
Robert, I would move forward with merging Garrett's patch into the OSG
trunk. If I have changes
Hello Steve:
Tried the models I use on the Mac and Windows and everything is
running ok on my end.
Take care
Garrett
On Apr 30, 2008, at 3:32 PM, [EMAIL PROTECTED] wrote:
Thanks Garrett. Might not get around to this until the weekend, but
I'll let you know how the testing goes or If I
To: OpenSceneGraph Users
Subject: Re: [osg-users] Robert, collada dae2 maybe?
Hello Steve:
Was just curious. You mentioned that you were doing another release
shortly for collada DOM 2.1 from the current 2.0 because of some
issues with 2.0. Were these issues show stoppers for using
Were these issues show stoppers for using the current 2.0?
Kind of depends on the platform you're using. The Visual Studio libraries were
a little screwed up. The VS 2008 lib just wasn't right and the debug build of
the VS 2005 lib wouldn't work if you didn't have VS 2005 SP 1 or something
Hello Robert:
I wanted to tar up the dae and call it maybe dae2 for the collada 2.0
tag release they have. Do you want me to send to you or send to the
osg-submissions?
Take care
Garrett
___
osg-users mailing list
Hello Robert
may want the collada expert who maintains the current dae plugin to
take a look at the modifications. There were just a couple of files
modified and the modifications were minimal. Could probably just
conditionally compile the current dae plugin to allow support for the
new
Hey Garrett, thanks a ton for this work. I'd been planning to bring OSG
up to DOM 2.0 myself at some point, but it looks like that's taken care
of with your patch. Thanks!
Does your patch bring platforms other than Mac up to DOM 2.0 also? I
vaguely recall that the OSG Collada plugin had
Hello Steve:
Glad I can help some :).
I plan on doing the windows build as well but have only done the MAC.
I have also only tested with a few Google Collada models so I don't
think I hit everything. Would need others to pound it to see if we
missed anything. For instance, the texture
I have not tested writing so we may have to add a nativeToUri utility call(
found in daeUtil.h) for encoding to a URI any files with spaces and special
symbols.
In DOM 2.0 the DAE methods that work with document names (like DAE::open/load,
DAE::write/save, etc) work with file paths just
Hello Steve:
Thank you for the comments. I'll pound the ingest side of things as
much as I can. I will start windows build this week after I finish
some OSG 2.4 upgrades on MAC and test the dae some more. I don't have
any other OS's than that at my disposal. I do know some who use
I'll see if they can also give it a whirl for you.
That's probably not necessary. If you and I each do our best to test the
platforms we have access to that should be enough. If someone's having a
problem on a different platform they can contribute a patch.
I think the daeRMaterial that I
Hello Steve:
I was just saying writing a document with an OS file path containing
spaces or whatever should work fine, since the DAE class methods
pass all document names through nativePathToUri first.
Ah, ok gotcha. Thank you for the help!
Take care
Garrett
24 matches
Mail list logo
