HI Yefei,
I can tell you how I'd set things up under Linux, but under windows
I'm afraid I can't help you.
Since you are generate just one view you should be able to set up one
card with TwinView, i.e. one graphics context spanning two outputs,
and the other just normal one context to one windows.
On my linux box I have driven 4 monitors from two cards using two
TwinView setups, Producer just treats this as two contexts/two
cameras. Perhaps is great, no strange increases in cull or draw.
Driving three monitors should just be a matter of one of the cards not
using TwinView.
TripleHead2Go is also a useful box, modern cards can handle the
resolution suprisingly well, even from just one card. TripleHead2Go
is only a couple of hundred dollars.
Robert
On 10/24/06, Yefei He <[EMAIL PROTECTED]> wrote:
Hi, Robert,
> The configuration files I use for testing are from the
> Producer distibution, under the
> Producer/doc/Tutorial/SourceCode directory.
My configure files are derived from the files under the
Producer directory you mentioned as well.
>
> If you set up things with one camera per render surface,
> you'll need one render surface per card. For you two outputs
> from one card stretching one camera to work over the two
> outputs may be work for you. It'll all depends on what
> exactly you are trying to do to.
>
I have two video cards in my computer, one connected
with two displays and another with one. I just want to render
one view across three full screens. Simple enough.
I just took another dab at reconfiguring the Windows display
properties. I changed the nvidia settings on the card with
two monitors from DualView to Horizontal Span. So Windows
thought there was one 1280x1024 display and one 2560x1024
display, instead of three 1280x1024 displays. Turned out this
worked well with my application, which recognized two displays
and thus created two render surfaces and two cameras. There
were two curiosities, however:
1. osgviewer with two render surface configuration still
didn't work. There must be something in the viewer code that's
different from my implementation. 300ms for draw time on the
camera using the render surface across two displays connected
to the same card is not normal. It's as if there's no hardware
acceleration on the card. But, running osgviewer without using
configure file works fine across the two displays on the same
card.
2. Does Producer::lens recognize the wide span and does
correction automatically? I set the lens for the camera covering
the single display render surface to a horizontal AOV of 40
degrees, and did the same for the lens of the other camera
covering the two-display render surface. But somehow the FOV
matched on all three displays. I would thought with 2560x1024
against 1280x1024, I'd need to use a wider horizontal AOV on the
former?
>
> Even if you whole app can't be ported to windows, try
> modifying one of the OSG examples to have the camera setup
> you require then try it under Linux and windows and see how
> you get on.
>
> As for trying out linux, its free, easy to download and
> install as dual boot. If you care about performance you
> shoud try it straight away.
>
I agree, I think should try it again when I have time. A year
ago I tried and Linux could not recognize the hard drive on my
computer at home. I remember it was a PATA/SATA issue. That
really put me off. Maybe it's solved now.
>
> Robert.
>
Yefei
_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
