On Tuesday 25 October 2005 16:45, Curtis L. Olson wrote: > We are using multiple machines, one for each display. My feeling is > that if it is a bit excessive, it is only a small bit excessive and I > can put up with it. :-) You are welcome to try running a multiheaded > machine (with support for opengl on all your displays.) I'd be > interested in hearing your results. >
I had a go at this a while back using the nvidia proprietary driver's TwinView option. TwinView can be configured to stretch the X display across 2 screens and provide acceleration on both. The nvidia driver hides the fact that the display spans two screens. So 2x 1024x768 displays are presented to the X server as a single 2048x768 wide screen. Using FlightGear across both of the displays is as simple as launching with --geometry=2048x768 and the performance is the same as you'd expect displaying the same size window on a single display. You can adjust the FOV to say 90deg to give a realistic panorama and I'd love to try it with two projectors :) Note that I tried --enable-game-mode but didn't get it working, however I'm sure this was down to my setup at the time and not the TwinView config. For displaying a panel (and avoiding the performance hit of two instances) perhaps you could configure the TwinView as 'top and bottom' monitors, the top one providing the out-the-window view and the bottom one showing the panel. The panel would probably have to be specifically designed to only fill 1/2 your display area - the 610x panel seems to scale to the longest edge in all circumstances. Personally, I'd favour the aforementioned 2 systems, one for panel, FDM, input and sound and one (or more) for the out-the-window view. (Hopefully thereby boosting the 3d display's performance a bit?) -- Dave Martin http://museum.bounce-gaming.net _______________________________________________ Flightgear-devel mailing list [email protected] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
