Supported Display Options

Virtually any screen/monitor connected to the HDMI port on your Pi will work. Additionally, the following displays have been successfully tested:
Note 1: The type and model of your monitor will affect the latency since response time, picture enhancement, and refresh rate will add latency. The best latency can be achieved with low response time, gaming monitors with a refresh rate of more than 120Hz.

DSI Displays

On the Raspberry Pi, we're using the FKMS driver to enable low latency decoding. Some of the newer monitors require the KMS driver, which does not work with OpenHD. Only Official Raspberry Pi DSI monitors can use FKMS.

Zeiss Cinemizer OLED

Please note that the monitor has to be connected and powered before the Pi is powered on because the auto-detection only works at start-up. You can define your (custom) monitor resolution in config.txt statically to connect the monitor after the Pi is already running. Also, make sure to uncomment hdmi_force_hotplug=1 to enable "hotplugging" for your HDMI monitor/goggles.

Using a Phone or Tablet

Regardless of the monitor attached directly to the Ground SBC, you can use a phone or tablet running the official QOpenHD App.
Note 2: When using your phone or tablet, dual video doesn't work, and the latency might be slightly higher.
Warning 1: When using your phone/tablet as the only display (connected to the ground station), the viewing experience is less than ideal, and there might be stutters and lost frames.

Using a Laptop Combined with the X86 Releases

In Evo, we added the possibility to use your existing laptop as a ground station. For this to work, you either need the USB-Image and boot from it or install OpenHD using the OpenHD X86 installer.
Warning 2: When using your X86 device, your experience (latency, framerate, etc.) depends on the power of your device. On more powerful devices, the latency is much less than on the Pi. On older/less powerful devices, it may be higher.

Dual Display Setup

Note 3: Dual display setup isn't working because of the low latency video decode we use. On X86, it will work without issues. On the Pi, there is no capability to do so without adding a lot of latency.