Hi Michael,
can you give us an update on this one? Did taking off the GraphOps make a
difference? If so, would you be able to provide us an example model with
LINE_STRIPs so we can figure out what's wrong?
Thanks
Dirk
On 04/07/2010 09:31 AM, Carsten Neumann wrote:
>
> hm, strange. I don't see a reason why GL_LINE_STRIP would make any part of
> the sync behave different than for any of the other primitive types. Are
> these geometries "unusual" or different from the rest in your application in
> any other way? For example, do they use no index or a complicated interleaved
> index? Do they have a material that is distinct from the other materials?
> etc.
>
>> We're using the OpenSG osb loader, don't know if this is a general sync
>> problem or if the loader does something strange.
>
> Does it make a difference if you run the default graph ops or not? Using
>
> SceneFileHandler::the()->read("filename.osb", NULL);
>
> will prevent them from running (i.e. the second argument to read is a
> GraphOpSeq*, a list of graph ops to apply to the loaded model).
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
