Thanks everyone for the responses.
So far the Anders' suggestion of using screen.nas seems to have the most
promise. Torsten: I have another project I want to use the fgpanel system
for, but with this project we are trying to keep the logistics of starting
things up as simple as possible, also I'm not sure how you would keep the
fgpanel display in front of the FlightGear display if you had to click on
the flightgear display to interact with it? Hal: it's important with this
particular project to have the instrumentation attached to the screen when
the view changes or pans around, even in tower or fly-by views we want to
see the instrumentation clearly.
Regards,
Curt.
On Tue, May 31, 2011 at 2:51 PM, Hal V. Engel wrote:
> On Tuesday, May 31, 2011 11:00:58 AM Curtis Olson wrote:
>
> > I could be imagining this, but I seem to recall a while back, someone
>
> > asking if it was possible to keep a 2d panel visible all the time, even
> in
>
> > external views. I just took a quick peek at .../Cockpit/panel.cxx and it
>
> > doesn't appear that we have the ability to do this, but I just thought
> I'd
>
> > ask in case there is some other mechanism someone has added?
>
> >
>
> > I am working on a project where we are modeling a skydiver in free fall,
>
> > and we want to display some basic information on the edge of the screen
>
> > (like decent rate). But because this is not an aircraft, it makes more
>
> > sense to use external views. Also we are trying hard to avoid needing to
>
> > modify source code, and we'd like to do this in v2.0 (the most current
>
> > "release").
>
> >
>
> >
>
> > The HUD would be another alternative, but we'd like to avoid needing to
>
> > extend the HUD code to add our specific widgets.
>
> >
>
> > Perhaps we could use gui widgets and display the information numerically,
>
> > but an instrument communicates the data so much better.
>
> >
>
> > Are there any other options or ideas that I'm missing?
>
> >
>
> > Thanks,
>
> >
>
> > Curt.
>
>
> Have you thought about modeling the skydiver as an "aircraft" with the
> "cockpit" being the view out of his/her goggles? The "panel" would be
> nothing and the instruments could be just positioned about a meter in front
> of the pilots point of view. You could then keep the instruments in view as
> the "pilot" changed his view direction (IE. look up, down, left, right) by
> rotating them about the pilots head. You should be able to do all of this
> using the existing XML. Or you could create a 3D model for the skydivers
> body and possition the instruments on his/her body (IE on the top of the
> belly mounted chute pack) so that you need to look down to see them.
>
>
> Hal
>
>
>
>
> ------------------------------------------------------------------------------
> Simplify data backup and recovery for your virtual environment with
> vRanger.
> Installation's a snap, and flexible recovery options mean your data is
> safe,
> secure and there when you need it. Data protection magic?
> Nope - It's vRanger. Get your free trial download today.
> http://p.sf.net/sfu/quest-sfdev2dev
> _______________________________________________
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>
>
--
Curtis Olson:
http://www.atiak.com - http://aem.umn.edu/~uav/
http://www.flightgear.org - http://gallinazo.flightgear.org
------------------------------------------------------------------------------
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today.
http://p.sf.net/sfu/quest-sfdev2dev
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
