Hi Richard and Robert
I just want to confirm that the problem exists here as well. Several
machines all running winXP and nVidia cards all show this issue.
A standard osgdem-generated database will behave this way when run in
osgviewer at our computers with two monitors. The monitors are conected
to one single graphics card with two outputs using nVidias
nView-Display-Setting "dualview".
If I switch to use the setting called "Horizontal Span" the problem no
longer occurs.
In "dualview" the fullscreen mode of osgviewer covers only one display
(the one set as primary) while in "Horizontal Span" fullscreen covers
all displays.
/Sebastian
Robert Osfield wrote:
Hi Richard,
I don't really have any clues to what might be wrong, could be one of
many things so we'll need to work through isolating the problem.
Does the problem existing when running osgviewer on the same databases?
Is the second display on the same graphics context/graphics card?
Robert.
On 11/13/06, Schmidt, Richard, SDGE1 <[EMAIL PROTECTED]> wrote:
I am just dragging the window onto the second screen using the mouse.
No scene graph manipulation or anything like that. The error is
reproducible on multiple machines (desktops and laptops) all using
nvidia hardware. The window handle is coming from a .NET custom
control. We do not experience the bug with other nodes, or pagedLOD
nodes which are already loaded. They keep drawing like supposed.
Richard
-----Ursprüngliche Nachricht-----
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Im Auftrag von Robert
Osfield
Gesendet: Montag, 13. November 2006 10:44
An: osg users
Betreff: Re: [osg-users] Choosing correct PagedLOD child
Hi Richard,
When you say "move the producer window onto the second monitor" do you
dragging it across using a mouse, or opening up a new window on the
new monitor and if so at what point in the app are you setting this
new window up?
Robert.
On 11/13/06, Schmidt, Richard, SDGE1 <[EMAIL PROTECTED]> wrote:
> I am observing the similar problem, however it seems to happen in a
multimonitor environment only.
>
> When creating a globe using osgDem everything runs fine until we
move the producer window onto the second monitor. Doing that seems to
stop osg from loading further nodes. Nodes which are loaded on the
first monitor get still displayed correctly.
>
> Any ideas?
> Richard
>
>
> -----Ursprüngliche Nachricht-----
> Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Im Auftrag von Chris Hanson
> Gesendet: Samstag, 11. November 2006 00:34
> An: osg users
> Betreff: Re: [osg-users] Choosing correct PagedLOD child
>
> Weitz, Andrew C. wrote:
> > I just got around to trying your PagedLOD class. It seems like it is
> > only partially working. When I load an OSG file with a PagedLOD, it
> > jumps immediately to the correct LOD, like it's supposed to.
However,
> > it will never display any intermediate LODs when I zoom in/out. It
> > seems to only display the highest or lowest LOD.
> > Have you experienced this behavior?
>
> Umm, no. It works well for me.
>
> > Thank you,
> > Andrew
>
> --
> Chris 'Xenon' Hanson aka Eric Hammil | http://www.3DNature.com/ eric
at logrus
> "I set the wheels in motion, turn up all the machines, activate
the programs,
> and run behind the scenes. I set the clouds in motion, turn up
light and sound,
> activate the window, and watch the world go 'round." -Prime
Mover, Rush.
_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
