I have a standard dual output (DVI + VGA) graphics cards, a Matrox DualHead2Go (Analogue) and 3 4:3 monitors. The DualHead2Go can take double wide screens and output half each to a separate monitor. The DualHead2Go has digital equivilants (DVI and DP) which require drivers, but the analogue one is 'dumb' and only works with a few resolutions.
Since the cards is only outputting 2 screens (albeit one twice as wide as the other), everything is nicely accelerated without having to do any special tricks.
Under Linux the screens are control by the 'xrandr' command, using Ubuntu 10.10 I didn't even need to configure any special modelines. I use a little bash script to configure the layout.
- Code: Select all
xrandr --output VGA-1 --primary
xrandr --size 2560x1024 --rate 60
xrandr --output DVI-I-1 --mode 1280x1024 --left-of VGA-1
Since SpeedDreams doesn't know about such wide screens, you have to manually edit the config files. Firstly edit '~/.speed-dreams-2/config/screen.xml' and set the width of your screen.
- Code: Select all
<params name="Screen" version="1.6">
<section name="Validated Screen Properties">
<attnum name="window width" val="3840"/>
<attnum name="window height" val="1024"/>
<attnum name="bpp" val="32"/>
<attstr name="full-screen" in="yes,no" val="yes"/>
One thing that bugged me was the fact the graphic overlay would spread across the whole screen, putting the map/etc way too far out. This can actually be controlled by editing the '~/.speed-dreams-2/config/graph.xml' file, for the appropriate driver find the 'boardwidth' parameter and set it to the percentage of the screen you want the board to cover.
- Code: Select all
<section name="0">
<attnum name="camera" val="1"/>
<attnum name="camera head list" val="0"/>
<attnum name="board width" val="33"/>
<attnum name="speedometer vertical position" val="0"/>
<attnum name="fovy-0-1" val="75.5"/>
BTW the 'speedometer vertical position' parameter causes the Speedo/Tacho to rise a number of pixels, useful if you have a cockpit setup where the wheel obscures part of the screen.
So what does it look like? See the attached files...
Simon.