> The Triangle Iterator loops through all triangle primitives (triangles,
> fans, strips) stored in the geometry. It does _not_ loop through
> non-triangles, as this would be very confusing in other cases.
>
> To do what you want, you do need to search for missing faces. Doing that
> in general
Simon Haegler wrote:
> osgHello
>
> i have a a geometry core with a box which is open on one side. i try to write
> a
> function which "regenerates" cores, i.e fills the holes. i tried to use the
> triangle iterator to loop through _all_ triangles (implicit triangluation),
> but
> somehow the hol
osgHello
i have a a geometry core with a box which is open on one side. i try to write a
function which "regenerates" cores, i.e fills the holes. i tried to use the
triangle iterator to loop through _all_ triangles (implicit triangluation), but
somehow the hole is still there. do i need to explici
Hi,
On Sun, 2007-03-25 at 09:18 -0500, Allen Bierbaum wrote:
> Andreas Zieringer wrote:
> > Hi Allen,
> >
> >
> >> I have been trying to track down some memory leaks in my application
> >> today and I noticed that the _changedStore and _createdStore vectors in
> >> OSG::ChangeList seem to gr
Hello,
I am attaching a small snippet of code showing one of the probable usage
of FieldContainer that is taken from the starter guide.
But i am getting error
Could you point out my mistake as the error script saying as follows:
firstOSG.cpp: In function ‘int main(int, char**)’:
firstOSG.cpp:
>
Hi,
> I don't want to switch it to a map, as that would penalize the 99%
> of models
> that use the positions as expected. The solution would be to find
> the lowest
> index actually used and use that as an offset for the vector, but
> that's too big
> of a change for me, I'll leave that
Hello,
my name is Sebastian Knödel. I'm a PhD student at the University of
Bordeaux.
In our Research Group (http://iparla.labri.fr/) we are working in the
area of Rendering and Interaction with mobile devices but also with
immersive Technologies like stereo projections. We use OpenSG a lot in
Hello Mathias,
the basic idea is to apply the modifications recorded in the changelist
so it can be cleared and does not grow too much.
Mathias Otto wrote:
> Thanks for your response, but I am using clustering and I don't know how this
> should work for the remote Aspect.
In that case y
Thanks for your response, but I am using clustering and I don't know how this should work for the remote Aspect. Nevertheless it makes me wondering, that the changelist is smaller, when I do load all objects, than I share the objects. Because now shareing the geometries works too. Mathias
Hello Mathias,
Mathias Otto wrote:
> I have got a problem concening shareing a geometry core on a lower level. So
> I
> have some scenarios with many objects, all stored in obj files. Therefor I
> wrote
> my own loader that shares materials amd merges geometries really fast. Those
> g
10 matches
Mail list logo
