Re: [Flightgear-devel] Panel question

[John W. <ca...@mm...>]

----- Original Message -----
From: "David Megginson" <da...@me...>
To: <fli...@li...>
Sent: Monday, August 27, 2001 6:22 AM
Subject: re: [Flightgear-devel] Panel question


> Roman Grigoriev writes:
>
>  > Nice to fly with panel but nothing to see but the panel :-((
>
> You can scroll the panel up and down to see more of the outside or
> more of the panel.  Personally, I bind the scrolling to two joystick
> buttons so that I can scroll fast, but you can also use Shift-F5 and
> Shift-F6.
>
>
> All the best,
>
>
> DAvid
>
> --
> David Megginson
> da...@me...
>
>
> _______________________________________________
> Flightgear-devel mailing list
> Fli...@li...
> http://lists.sourceforge.net/lists/listinfo/flightgear-devel
>
You can always disable the panel with --disable-panel and fly with the HUD.
Also there is a full screen default option in the preferences.xml. If you
can get sockets i/o (see documentation in DOCS) to work you might consider
running the second machine with all panel/HUD displays off and "fiddle" with
the view on the "server" machine via the left mouse.

Perhaps a better long term solution would be a multicast capability on
192.168.x.x or whatever other numbers you want to use
for private LAN. if you can afford all the hardware, you could then run the
fgfs "server" and send packets to the other client machines
which could be configured as desired to display peripheral views, panels, or
whatever. Or have the primary fgfs broadcast the aircraft
state vector and each client can do as it sees fit.

Regards
Jack W.
and a full screen
file or as an option