Hi Akos,

I get this message(s) when loading "cube.osg" in the osgViewer! Apart from
that my materials are always NULL even if I add it manually. 
So it seems i have to include a simple viewer on top of my converter. At the
moment I simply do the following:
- open the CAD file in my converter.
- depending Nurbs activation triangulate it or generate Nurbs
- save the OpenSg graph.

thats all.

Thanks for the fast answer,

Patrik
 

-----Ursprüngliche Nachricht-----
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Im Auftrag von Akos Balazs
Gesendet: Donnerstag, 2. Dezember 2004 23:50
An: opensg-users@lists.sourceforge.net
Betreff: Re: [Opensg-users] Nurbs again

Hi Patrik,

On Thu, 2 Dec 2004, [iso-8859-1] Patrik Müller wrote:

> I'm implementing the Nurbs interface for OCC using 
> testSurfaceRender.cpp as example. But I always get the following error 
> message for each of my Nurbs surfaces:
>
> "FATAL: Invalid geoPtr->getPositions() in createSharedIndex()"

When do you get this error actually? createSharedIndex() I believe is a
GraphOp, that's called by some loaders and possibly by other things, and as
a first thought I believe it gets confused by the fact that the OSG::Surface
doesn't actually contain Geometry yet (only the NURBS data) since it's not
tessellated yet.

Depending on your application you might be able to work around this issue by
calling OSGSurface::forceTessellate() once for each surface when your
surfacedata is in place, but you will lose the ability to do automatic
retessellation when the FieldContainers change.

Hope this helps,
        Akos



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Opensg-users mailing list
Opensg-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensg-users

Reply via email to