I surely understand that...
So Would there any test set that could ensure removal of this code doesn't
break anything?
(I would like to submit changes I made for BufferObject and TransformFeedBack
serialization but i'd rather lever any doubts about its integration first)
robertosfield wrote:
>
On 23 May 2016 at 12:08, Julien Valentin wrote:
> Searching posts at this period -oct 2010- i found this post
> http://forum.openscenegraph.org/viewtopic.php?t=6826
> does it recall anything?
This does look relevant, I have a vague recollection, but not yet
enough of
Searching posts at this period -oct 2010- i found this post
http://forum.openscenegraph.org/viewtopic.php?t=6826
does it recall anything?
robertosfield wrote:
> Hi Julian,
>
> Thanks for tracking down the commit. I did a quick search for related
> discussions on osg-users but haven't spotted
Hi Julian,
Thanks for tracking down the commit. I did a quick search for related
discussions on osg-users but haven't spotted anything around the right
time frame (late October 2010). There is probably something in
osg-submissions and osg-users that discusses this as I don't think
it'll be
Thanks Robert
According to the git log:
> commit 57a0065d08b3aa5b06da54a7b78ea2ae36cb2c9a
> Author: Robert OSFIELD <>
> Date: Thu Oct 28 14:04:57 2010 +
>
> Added use ObjectWrapper's FinishObjectReadCallback to fix
> VertexBufferObject handling in osg::Geometry
> and a call to the
Hi,all
I would like to provide osg TransformFeedback serialization feature but
something weird forbid BufferObject serialization:
This callback calls setUseVertexBufferObjects(false) and just kill all
BufferObject attached the geometry's BufferDatas
Code:
struct
6 matches
Mail list logo