Hello Thiago,
Thiago Bastos wrote:
> AFAIK there's no Max exporter for OSG2. I've tried using most, if not
> all other formats that Max is able to export (and OSG2 is able to read)
> and things never get right. Either the Max exporters don't export
> everything (mostly materials) or OpenSG doesn't read everything, I don't
> know.
probably a bit of both ;)
> Naturally, we tried to load the old OSBs. The first thing we noticed is
> that it takes *much* more time to load the same OSB, and it prints a lot
> of warnings:
the longer load times are probably caused by the warnings.
> WARNING: SharePtrGraphOp::setIncludes: Unrecognized type [Material].
> WARNING: SharePtrGraphOp::setIncludes: Unrecognized type [StateChunk].
hm, those two should have been fixed in r1686.
> 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.
> ... (repeated 2k times)
are these all about [vbo] or other fields as well?
> LOG: Found no object named 'Scene'.
> LOG: Found no object named 'TF_DETAIL' (did you load the tie?).
ahh, 10loading.cpp :) -- these do not indicate a problem, just that you
loaded a different model than the tutorial expected (these programs go
together with the tutorial text and it contains instructions to load the
tie.wrl model).
> Then, when the model loads, it looks a bit different. I've attached two
> screenshots to illustrate.
> AFAICT the geometry is OK, but it's messing with some materials.
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?
> We're using the latest svn revision with NEW_OSB_IO enabled and
> OSGCOMPAT disabled.
which revision is it you have? The SharePtrGraphOp warnings should not
be there in the latest, but if you still see them I'd like to find out
what causes them.
> Could this be the problem? We're not completely sure of the implications
> of these two options.
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.
hm, debugging a loader is tricky from a distance, do you have a model
that shows the problem that you can share?
Thanks,
Carsten
------------------------------------------------------------------------------
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
