HP C8000 OpenGL Implementation Guide for HP-UX 11.x - Page 40

Running OpenGL Programs, visual support for the VGL mode, special considerations

Get HP C8000 - Workstation - 0 MB RAM PDF manuals and user guides View all HP C8000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 40 highlights

running OpenGL programs virtual GLX (VGL) mode virtual GLX (VGL) mode Virtual GLX (VGL) defines a special transparent mode within hp's implementation of OpenGL that allows an hp client to render through OpenGL to X servers and/or X terminals that do not support OpenGL or the X server extension for GLX. This mode is implemented by emulating the X server extension within the OpenGL API client-side library and using the hp Virtual Memory Driver (VMD) to perform Xlib rendering. VGL provides flexibility for OpenGL users, but does not provide the same level of performance as is available to servers supporting GLX. visual support for the VGL mode In VGL mode, the visual capabilities incorporated in glXChooseVisual() and glXGetConfig() are synthesized from the list of X Visuals supported on the target X Server and the capabilities of the Virtual Memory Driver (VMD). Table 1-5 in Chapter 1 lists the X Visuals that are supported through the OpenGL Extension to the X Window System (GLX) in the Virtual GLX (VGL) mode. special considerations When you are in the VGL mode, you will notice the following differences between it and the GLX mode. • VGL deals with X servers that do not support replicated X visuals that provide extended GLX capabilities. This results in a GLX visual list that is synthesized from available X visuals. This list is assigned the maximum set of capabilities supported by the Virtual Memory Driver (VMD) for each particular visual. For example, if a visual is found to be supported by the Double-Buffered Extension (DBE), then it will be reported as having the capability of doing double-buffering. Note that there will not be a counterpart for the GLX visual with the same type and depth that is single buffered. Such visuals are locked to either single buffer or double buffer mode, based upon the first access. In VGL, to utilize one visual for both single and double buffered operation, two separate X display connections must be opened. 38 Chapter 3

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
running OpenGL programs
virtual GLX (VGL) mode
Chapter 3
38
virtual GLX (VGL) mode
Virtual GLX (VGL) defines a special transparent mode within hp's
implementation of OpenGL that allows an hp client to render through
OpenGL to X servers and/or X terminals that do not support OpenGL or
the X server extension for GLX.
This mode is implemented by emulating the X server extension within
the OpenGL API client-side library and using the hp Virtual Memory
Driver (VMD) to perform Xlib rendering.
VGL provides flexibility for OpenGL users, but does not provide the same
level of performance as is available to servers supporting GLX.
visual support for the VGL mode
In VGL mode, the visual capabilities incorporated in
glXChooseVisual()
and
glXGetConfig()
are synthesized from the list
of X Visuals supported on the target X Server and the capabilities of the
Virtual Memory Driver (VMD). Table 1-5 in Chapter 1 lists the X Visuals
that are supported through the OpenGL Extension to the X Window
System (GLX) in the Virtual GLX (VGL) mode.
special considerations
When you are in the VGL mode, you will notice the following differences
between it and the GLX mode.
•
VGL deals with X servers that do not support replicated X visuals
that provide extended GLX capabilities. This results in a GLX visual
list that is synthesized from available X visuals. This list is assigned
the maximum set of capabilities supported by the Virtual Memory
Driver (VMD) for each particular visual. For example, if a visual is
found to be supported by the Double-Buffered Extension (DBE), then
it will be reported as having the capability of doing double-buffering.
Note that there will not be a counterpart for the GLX visual with the
same type and depth that is single buffered. Such visuals are locked
to either single buffer or double buffer mode, based upon the first
access. In VGL, to utilize one visual for both single and double
buffered operation, two separate X display connections must be
opened.