Re: [osg-users] lighting flickering

Hello Trajce!!! LightSource may be traversed after some Drawables. This may be the problem! Try to move LightSource node upper to be traversed first. KOS 2014-02-25 0:44 GMT+04:00 Trajce Nikolov NICK trajce.nikolov.n...@gmail.com : Hi Community, I have a scene where I use light lobes

Re: [osg-users] View::setCameraManipulator

Hi Robert, I'm simply saying that setCameraManipulator should just set the camera manipulator into the view and not also set the node implicitly got from the scene data: it is not his responisibility. And that's not always a desirable behavior since in other part of the code the node should be

Re: [osg-users] lighting flickering

Thanks Kostantin! I will try to do that Nick On Wed, Mar 12, 2014 at 8:24 AM, Konstantin lalakos...@gmail.com wrote: Hello Trajce!!! LightSource may be traversed after some Drawables. This may be the problem! Try to move LightSource node upper to be traversed first. KOS 2014-02-25

Re: [osg-users] memory releasing problem by addchild and removechild

Hi Lv, On 10 March 2014 14:40, Lv Qing donlvq...@msn.com wrote: Hi, ... I have read some posts about memory releasing problem by addchild and removechild. There are no problems with memory management with addChild and removeChild. It's been working very robustly for many years.

Re: [osg-users] View::setCameraManipulator

HI Gianni, On 12 March 2014 09:07, Gianni Ambrosio ga...@vi-grade.com wrote: Hi Robert, I'm simply saying that setCameraManipulator should just set the camera manipulator into the view and not also set the node implicitly got from the scene data: it is not his responisibility. And that's

Re: [osg-users] memory releasing problem by addchild and removechild

robertosfield wrote: Hi Lv, On 10 March 2014 14:40, Lv Qing () wrote: Hi, ...     I have read some posts about memory releasing problem by addchild and removechild. There are no problems with memory management with addChild and removeChild.   It's been working very

[osg-users] vertex attribute divisor support

Hi, I’ve asked this question in the past, but re-visitng it again: given the lack of core support in Array for glVertexAttribDivisor, does anyone have any recommendations for getting per-instance data working easily? I should state that I’m aware of the ‘use a texture and gl_InstanceID to

Re: [osg-users] vertex attribute divisor support

Hi James, As far as I have seen, GL_ARB_texture_float is about as well-supported as GL_ARB_draw_instanced. The only exception I've been able to find on test hardware has been software Mesa, which supports neither. We make use of multiple floating point textures for encoding per-instance data.

[osg-users] PolytopeIntersector, LineSegmentIntersector, and PagedLOD

Hi, I'm getting unexpected behavior from PolytopeIntersector and was wondering if it might have something to do with the PagedLODs in my scene graph. I want to find all polygons in a rectilinear volume in my model, in model coordinates (not related to any view on the screen) based on two

Re: [osg-users] OSG static linking

Hi all -- Is anyone using CMake to find a static-built OSG? If so, how are you getting that to work? When building static OSG, all the library names are prefixed with osgsoversion. For example, with OSG v3.3.1, the so version is 111, so I get libs named: osg111-osg.lib, osg111-osgDB.lib,

Re: [osg-users] OSG static linking

Setting OSG_MSVC_VERSIONED_DLL to OFF appears to fix this issue, and causes the static .lib names to not contain the SO version. (After I rebuild with this set to OFF, I'm guessing the stock CMake find scripts will find my static-built OSG.) Is that correct? The CMake variable clearly says DLL,