Matrox orion HD, Инструкция по установке и эксплуатации оборудования

Страница: 12 / 68

12 Chapter 1: Introduction
Second, all functionality on the Matrox Orion HD board is controlled by a
Matrox-designed GPU and uses MIL GPU services. For the Matrox Orion HD
board to work, the GPU must drive the output of the Windows desktop.
Otherwise, you will not be able to allocate the board as a MIL system; calling
MsysAlloc() with M_SYSTEM_ORION_HD will fail.
Third, the Matrox Orion HD board has the same limitations as any other
DirectX-capable display board or display device. To work properly,
Matrox Orion HD requires the underlying Direct3D engine (GPU) to be in an
operational state. Some events can cause all Direct3D devices (for example,
Matrox Orion HD and other display boards) to transition to a lost device state.
While these devices are in a lost device state, some of their on-board capabilities
will not be available. For example, you cannot initiate grab or display operations
until Matrox Orion HD recovers from the lost device state.
Some well-known events that can cause a Direct3D device to transition into a lost
device state are:
• Changing the display resolution and desktop settings.
• Connecting to the computer using RemoteDesktop.
• Viewing the desktop from a remote client (such as, VNC).
❖
Note that, in most cases, if Matrox Orion HD is in the process of grabbing
images, the current grab will continue. The grab will only be interrupted if you
initiate a remote connection to the computer.
To recover gracefully from a lost device state, MIL and Matrox Orion HD will
wait for the event to be over before trying to transition back to an operational state.
❖
Note that Matrox Orion HD only supports DirectX version 9.