Apparently, the issue was linked to the fact that the View containing the
camera for the mirror were not added as children of the main
CompositeViewer that we use.
I'm not sure why it's like that as I don't know enough of the relations
that are between the StatsHandler and everything else, but it
>
> There isn't too much others can help with because the problem is likely
> very specific to the things you've done. The best we can do is make
> general suggestions and things to try. The finding that mirrors have an
> effect is hint that either the mirrors are overdrawing the stats or leaking
On 29 March 2016 at 21:50, Alexandre Vaillancourt <
alexandre.vaillancourt.l...@gmail.com> wrote:
> It seems related to how we do our mirrors: it works well when there are no
> mirrors, but when we start the software with the mirrors, the issue
> happens. I'll keep on digging...
>
There isn't too
It seems related to how we do our mirrors: it works well when there are no
mirrors, but when we start the software with the mirrors, the issue
happens. I'll keep on digging...
--
Alexandre Vaillancourt
2016-03-29 11:22 GMT-04:00 Alexandre Vaillancourt <
alexandre.vaillancourt.l...@gmail.com>:
>
Hello!
We're normally using an in-house derived version of
osgGA::CameraManipulator to control the camera. This manipulator is placed
within a KeySwitchMatrixManipulator because we need a couple viewpoints.
We also need at some point to display viewer stats. This used to work well
in our previous
5 matches
Mail list logo
