Hi Christian,
I would think that modifying the reader might be easier than
processing its generated output.
I would say the opposite - creating a NodeVisitor that you run over the
loaded graph, which will massage the data to suit your needs, would be
easier than modifying the reader plugin.
Hello.
Is there any Sample/Example for this ?
Thank you again.
On 26 March 2012 15:00, Christian Buchner wrote:
> I'd say you would have to modify the DAE reader according to your
> shader's needs, or alternatively you'd need to do some postprocessing
> on the returned geometry.
>
> I would thi
I'd say you would have to modify the DAE reader according to your
shader's needs, or alternatively you'd need to do some postprocessing
on the returned geometry.
I would think that modifying the reader might be easier than
processing its generated output.
Christian
___
Hello.
Is there any way using the dae plugin in osg, to pass the vertices in
shader code as attributes?
What i do now for simple geometry shapes (lets assume we have a quad), is
to use
setAttributeValues( ... ); passing the vertices' positions, colors normals
etc.
How can i get this information f
4 matches
Mail list logo