Changes

From CCP4 wiki
Jump to navigationJump to search
513 bytes added ,  3 March
→‎Nvidia 3D Vision 2: March 2022 update
Line 15: Line 15:  
# To connect a DVI-D monitor to ar Quadro with DisplayPort 1.2, you will need a Club-3D CAC-1051 active DisplayPort/Dual-Link DVI Adapter 330MHz (110 €: do not buy the cheaper 270 MHz model, it will not work because the bandwidth is too low for 1920x1080@120hz) or for cards with miniDisplay ports, the Club-3D CAC-1151 active miniDisplayPort/Dual-Link DVI Adapter 330MHz.
 
# To connect a DVI-D monitor to ar Quadro with DisplayPort 1.2, you will need a Club-3D CAC-1051 active DisplayPort/Dual-Link DVI Adapter 330MHz (110 €: do not buy the cheaper 270 MHz model, it will not work because the bandwidth is too low for 1920x1080@120hz) or for cards with miniDisplay ports, the Club-3D CAC-1151 active miniDisplayPort/Dual-Link DVI Adapter 330MHz.
 
# specs of latest ("Maxwell") and previous ("Kepler") generation of Quadro cards are at http://www.nvidia.com/object/quadro-desktop-gpus.html . A comparison of all PCIexpress Quadro cards is at http://en.wikipedia.org/wiki/Nvidia_Quadro#PCI_Express . Latest (2014+) with prices are at http://www.heise.de/preisvergleich/?cat=gra16_512&asd=on&asuch=quadro&xf=3312_2014&sort=p . Currently (2015), the K620 is the entry system with the best price/performance ratio; in the middle range the K2200 still seems affordable.
 
# specs of latest ("Maxwell") and previous ("Kepler") generation of Quadro cards are at http://www.nvidia.com/object/quadro-desktop-gpus.html . A comparison of all PCIexpress Quadro cards is at http://en.wikipedia.org/wiki/Nvidia_Quadro#PCI_Express . Latest (2014+) with prices are at http://www.heise.de/preisvergleich/?cat=gra16_512&asd=on&asuch=quadro&xf=3312_2014&sort=p . Currently (2015), the K620 is the entry system with the best price/performance ratio; in the middle range the K2200 still seems affordable.
 +
# update March 2022: see discussion at https://www.jiscmail.ac.uk/cgi-bin/wa-jisc.exe?A1=ind2203&L=COOT
    
== Software ==
 
== Software ==
Line 69: Line 70:  
     Option        "Stereo" "10"
 
     Option        "Stereo" "10"
 
     Option        "nvidiaXineramaInfoOrder" "DFP-0"
 
     Option        "nvidiaXineramaInfoOrder" "DFP-0"
     Option        "metamodes" "DVI-I-1: 1920x1080_120 +0+0, DP-1: nvidia-auto-select
+
     Option        "metamodes" "DVI-I-1: 1920x1080_120 +0+0, DP-1: nvidia-auto-select +1920+0"
+1920+0"
   
     Option        "SLI" "Off"
 
     Option        "SLI" "Off"
 
     Option        "MultiGPU" "Off"
 
     Option        "MultiGPU" "Off"
Line 81: Line 81:     
This should be enough to get stereo working. However, note that there is a major issue on linux with window compositing causing stereo images to display improperly. This is a problem with the window display manager, and is not inherent to Xorg or NVidia. If you try to turn on stereo in Coot in a display manager that makes use of the Xorg compositing extension (e.g., Gnome3, or Unity in Ubuntu) then what you will see when you activate hardware stereo is a slight rotation of the view, but stereo remains disabled. In order to get around this problem, you must use a display manager that does not make use of compositing as part of its eye candy. This author has found the MATE desktop to work quite well for this purpose (and may in fact be one of the few that still does not use software compositing by default). Note that you ''do not'' need to disable the Compositing extension in the Xorg configuration file to make this work -- this will allow you to switch back to Gnome3, Unity, etc when you don't need stereo if you prefer! Not disabling the window compositing extension globally allows for a more flexible setup depending on your preferred workflow.
 
This should be enough to get stereo working. However, note that there is a major issue on linux with window compositing causing stereo images to display improperly. This is a problem with the window display manager, and is not inherent to Xorg or NVidia. If you try to turn on stereo in Coot in a display manager that makes use of the Xorg compositing extension (e.g., Gnome3, or Unity in Ubuntu) then what you will see when you activate hardware stereo is a slight rotation of the view, but stereo remains disabled. In order to get around this problem, you must use a display manager that does not make use of compositing as part of its eye candy. This author has found the MATE desktop to work quite well for this purpose (and may in fact be one of the few that still does not use software compositing by default). Note that you ''do not'' need to disable the Compositing extension in the Xorg configuration file to make this work -- this will allow you to switch back to Gnome3, Unity, etc when you don't need stereo if you prefer! Not disabling the window compositing extension globally allows for a more flexible setup depending on your preferred workflow.
 +
 +
The update of RHEL7 to 7.6 broke our /etc/X11/xorg.conf . It needs now
 +
        Section "Extensions"
 +
          Option    "COMPOSITE" "Off"
 +
        EndSection
 +
instead of
 +
        Section "Extensions"
 +
          Option    "Composite" "Disable"
 +
        EndSection
 +
The old version still works with KDE, but no longer with MATE. Thanks to Dirk Kostrewa for pointing this out!
    
===Mac OS X===
 
===Mac OS X===
Line 133: Line 143:     
http://pymolwiki.org/index.php/Stereo_3D_Display_Options
 
http://pymolwiki.org/index.php/Stereo_3D_Display_Options
 +
 +
https://sbgrid.org/wiki/usage/stereo
1,317

edits

Cookies help us deliver our services. By using our services, you agree to our use of cookies.

Navigation menu