Hello Carsten,
On Thu, Jan 29, 2009 at 2:48 PM, Carsten Neumann <[email protected]>wrote:
> > WARNING: SharePtrGraphOp::setIncludes: Unrecognized type [Material].
> > WARNING: SharePtrGraphOp::setIncludes: Unrecognized type
> [StateChunk].
>
> hm, those two should have been fixed in r1686.
Yes, I redid the test with r1706, thanks!
> WARNING: OSBCommonElement::readFieldContent: Skipping unknown field
> > [vbo] [SFBool].
> >
> > WARNING: OSBCommonElement::readFieldContent: Skipping unknown field
> > [vbo] [SFBool].
> > WARNING: OSBCommonElement::readFieldContent: Skipping unknown field
> > [vbo] [SFBool].
>
> this one is essentially harmless, it just means that a field was removed
> from Geometry in 2.0. I'll see if I can silence it or maybe lower it
> from warning to info.
OK. By the way, would it do any good if we load the old OSB models in OSG2
and re-save them?
Would it fix anything or load faster?
> > ... (repeated 2k times)
>
> are these all about [vbo] or other fields as well?
Yes, the same exact message.
> yes, and it looks essentially like just one material being off, the one
> making up most of the walkable surface, or are there more being off?
I examined the three most important models we have. In all occasions, the
geometry seems OK (same # of triangles drawn) and as far as I could tell
only one texture is 'missing' per model. In all cases, it happens to be the
texture covering the largest area.
However I'm not sure if other textures as missing, since the 1.8 statistics
don't mention how many textures are in use.
NEW_OSB_IO enables a new implementation of the OSB loader/writer, it is
> essentially the default for 2 and I've not built the previous one in ages.
> OSGCOMPAT enables some compatibility interfaces that may reduce the
> porting effort, but do not change the features of the OSB loader.
Thanks for the explanation! (mostly confirmed what we thought)
hm, debugging a loader is tricky from a distance, do you have a model
> that shows the problem that you can share?
I'll see what I can do. I'll send whatever I can find to your email.
PS: now every time I run cmake it prints the values of
"COLLADA_DAE_INCLUDE_DIR" (and DOM) in red. Did you forget to remove
something? :-)
Thanks!
Regards,
Thiago
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users