in the
scene, like in a video screen in the instrument panel, or
for distortion
correction in a projected or dome environment.
Open Scene Graph supports a CompositeViewer object that
supports
rendering from several widely separated viewpoints,
complete with
support for multiple terrain
, but it would be a good
project. We would have to start using a different OSG class,
CompositeViewer, to support multiple views from independent view points. Our
terrain pager would need a complete overhaul to use the PagedLOD scheme of
OSG, and the Flightgear view manager would need to be aware multiple
using the CPU is going to be
too slow, IMHO.
A moving map is a different beast. It would make sense to implement that as a
scene graph in its own right with its own pager. That would require a change in
current fg architecture to use a CompositeViewer instead of a single Viewer,
but
we're
is a different beast. It would make sense to implement
that as a
scene graph in its own right with its own pager. That would require
a change in
current fg architecture to use a CompositeViewer instead of a single
Viewer, but
we're contemplating that anyway.
Yep, I agree, moving map
.
The cameras in a camera group don't need to render directly to the
screen. They can render to a texture which can be used either in the
scene, like in a video screen in the instrument panel, or for distortion
correction in a projected or dome environment.
Open Scene Graph supports a CompositeViewer
to render directly to the
screen. They can render to a texture which can be used either in the
scene, like in a video screen in the instrument panel, or for distortion
correction in a projected or dome environment.
Open Scene Graph supports a CompositeViewer object that supports
rendering from
is to make mfd instruments with usual scenegraphs and pin that on an
object ...
Open Scene Graph supports a CompositeViewer object that supports
rendering from several widely separated viewpoints, complete with
support for multiple terrain pager threads. We could move to
CompositeViewer
Scene Graph supports a CompositeViewer object that supports
rendering from several widely separated viewpoints, complete with
support for multiple terrain pager threads. We could move to
CompositeViewer and support simultaneous views from e.g., the
tower, AI models, drones, etc.
Good thing
to a texture which can be used either in the
scene, like in a video screen in the instrument panel, or for distortion
correction in a projected or dome environment.
Open Scene Graph supports a CompositeViewer object that supports
rendering from several widely separated viewpoints, complete
2000.
A moving map is a different beast. It would make sense to implement
that as a
scene graph in its own right with its own pager. That would require
a change in
current fg architecture to use a CompositeViewer instead of a single
Viewer, but
we're contemplating that anyway.
Yep
for the tower view and a second screen for
the plane) would complicate a locked to cache flag quite a lot...
Yes, and that's not really supported by the current architecture, neither by
the tile cache nor by osgViewer::Viewer. We would need to move to a
CompositeViewer model, which supports several scene
11 matches
Mail list logo