Hi Robert,
thank you for have interest for my previous post, I'll try the latest svn
version as soon as possible.
2009/5/21 Robert Osfield
> HI Alexandre,
>
> I've now had a chance to have a look at the reproducing the problems
> using your modified example and data. The problem was due to a
HI Alexandre,
I've now had a chance to have a look at the reproducing the problems
using your modified example and data. The problem was due to a
double scaling of the projection matrices due to the unusual
combination of having an active master and slave combination, and
while the usage case in
Hello Alexandre,
What you're proposing is to copy slave camera view matrix into master
(default) camera matrix each frame, am I right ?
Isn't it another way yo avoid this copy ? isn't it a little expensive ?
No, I'm proposing to copy the slave camera's view matrix into an
osg::Uniform each
Hi Jean Sébastien,
apparently my bug is due to bad view matrix, my shader need camera view
matrix to compute it's effect.
What you're proposing is to copy slave camera view matrix into master
(default) camera matrix each frame, am I right ?
Isn't it another way yo avoid this copy ? isn't it a li
Hello Alexandre,
Well apparently I did achieve to set up my application with 2 slave
camera, but there is one last problem, I'm using a shader for my sky
sphere wich isn't working when using 2 slave cameras, has anyone already
had trouble with shaders and slave camera ?
Do you mean that (for
Well apparently I did achieve to set up my application with 2 slave camera,
but there is one last problem, I'm using a shader for my sky sphere wich
isn't working when using 2 slave cameras, has anyone already had trouble
with shaders and slave camera ?
2009/5/15 Jean-Sébastien Guay
> Hi Alexand
Hi Alexandre,
In my resize implementation I directly update the projection matrix from
the slave camera and I don't update the _projectionOffset wich for me is
useless.
Why don't you update the projection matrix of the master camera? If both
slave cameras render to the same GraphicsContext (
Hi jean-sébastien,
Your explanation is very clear.
My problem is that when I configure my application like that (2 slaves
cameras) I have a lot of weird behaviour (some of my models aren't
displayed, interraction with mouse and keyboard are odd), so I found a much
simple solution wich is to set m
Hi Alexandre,
something isn't right with the last thing I said, when creating a new
osgViewer::View a main camera is created by default, so it's not
possible to have 2 slave cameras only and no main camera, am I right ?
Of course, an osgViewer::View will always have a main camera. This is
th
Hi Alexandre,
I'm afraid others will have to pick up this thread to answer your questions.
Robert.
On Fri, May 15, 2009 at 1:51 PM, Alexandre Amalric
wrote:
> Hi robert,
>
> something isn't right with the last thing I said, when creating a new
> osgViewer::View a main camera is created by defau
Hi robert,
something isn't right with the last thing I said, when creating a new
osgViewer::View a main camera is created by default, so it's not possible to
have 2 slave cameras only and no main camera, am I right ?
My goal is to have only 2 camera not matter if they are both slaves or main
and
When using 2 slave cameras instead of 1 main calera and 1 slave camera the
resizing works perfectly.
I was thinking that the viewer had to have 1 main camera and n slave camera,
I was mistaken.
I have one last question, when we call getCameraWithFocus on a viewer set up
with 2 slaves camera and n
HI Alexandre,
On Fri, May 15, 2009 at 10:41 AM, Alexandre Amalric
wrote:
> Hi Robert,
>
> thank you for answering me but i'm confused I don't really understand what
> you want me to do on my example ?
Make it work like the original osgwindows example - use two slave
cameras rather than one maste
Hi Robert,
thank you for answering me but i'm confused I don't really understand what
you want me to do on my example ?
In fact the problem is that resizedImplementation function is called 1 time,
then there is a loop on _cameras vector (filled with 2 cameras in my
example, the main and the slave
Hi Alexandre,
On Fri, May 15, 2009 at 9:55 AM, Alexandre Amalric
wrote:
> I do not understand why we only update the projectionOffset from the slave
> camera and why we don't update the projection matrix itself.
The slave uses a relative reference frame the camera's projection
matrix is update
15 matches
Mail list logo