Lines Matching refs:multisample
24 While the OpenGL multisample extension (SGIS_multisample) provides
25 good out-of-order antialiasing via subpixel samples, multisample
32 multisample memory for every pixel in the framebuffer managed area
41 multisampling (as specified by SGIS_multisample), multisample
44 rectangle of multisample pixel state at any given time.
46 This sharing of multisample framebuffer state can result in a
50 both texture and multisample memory between the multiple channels
53 antialiasing, texture and multisample memory have to be replicated
57 area must retain multisample state because windows can be moved
64 a means to share the available multisample memory resources among
68 multisample buffer subrectangle sized smaller than the total
78 the behavior of multisample extension changes. Instead of the
79 multisample buffer memory being retained per-pixel across the
80 entire managed area, multisample memory is shared among multisample
81 windows and repositionable within a multisample window.
83 Switching windows or repositioning the multisample subrectangle
84 will make undefined the shared state within the multisample, depth,
87 When rendering into a multisample window, fragments that fall
88 outside the window's multisample subrectangle are discarded
89 (scissored). By default, the window's multisample rectangle is
97 multisample subrectangle, but otherwise would pass the pixel
101 available for copying outside the multisample subrectangle, just
102 not the multisample, depth, stencil, or accumulation buffer
117 multisample subrectangle as part of the pixel ownership test
123 multisample subrectangle, or should the accumulation buffer be
125 multisample subrectangle? If an accumulation buffer exists, it
126 should be SHARED like the multisample buffer.
129 and expensive just like multisample buffers. LBE apps still may
131 field. Like the multisample buffer, the accumulation buffer
132 should be shared and retained only within the multisample
141 multisample subrectangle, how can they guarantee reliable
146 multisample subrectangle? NO. It would justified if you had
155 * Can you clear a window using a shared multisample buffer
156 outside the multisample subrectangle? NO.
159 fragment is not within the multisample subrectangle, it cannot
160 pass the pixel ownership test when using a multisample
163 * What happens if you run a traditional (existing) multisample
165 multisample extension? VERY UNSIGHTLY FRAME BUFFER FIGHTING.
167 The app runs, but its multisample rendering will be constrained
168 to the multisample subrectangle. Multiple concurrent apps using
170 multisample rectangle.
173 server to support shared multisample mode when running a single
176 shared multisample app.
187 The advantage of overloading the existing multisample GLX
189 Optimizer) and multisample apps themselves won't have to be
190 specially tweaked to try them out using the shared multisample
194 an 8 sample shared multisample framebuffer configuration and an
195 4 sample shared multisample framebuffer configuration? YES,
198 The idea would be perhaps the 4 sample shared multisample
200 memory intensive 8 sample shared multisample configuration.
202 * Both a GLX and GL extension? YES. The multisample subrectangle
245 the multisample subrectangle. Neither the
252 fragments not within the multisample subrectangle. Otherwise, the
254 multisample subrectangle.
266 multisample, depth, stencil, and accumulation buffers retained in
267 the multisample subrectangle (but not the contents of the resolved
269 a different GL context, the multisample, depth, stencil and
270 accumulation buffer values for all pixels within the multisample
274 The multisample subrectangle can be shared between multiple
275 framebuffers (windows). Whenever the multisample subrectangle
276 becomes undefined, the contents of the multisample, depth, stencil,
278 color buffers) for all GL framebuffers sharing the multisample
281 the same multisample subrectangle (whether or not MULTISAMPLE_SGIS
285 The origin of the multisample subrectangle is defined by
287 window coordinates. The extent of the multisample subrectangle is
292 multisample subrectangle if msrx <= xw < msrx + msrwidth and msry
306 within the current multisample subrectangle are updated; in
316 ownership test does not include scissoring against the multisample
332 parameter <value> the respective multisample subrectangle width or
345 multisample rectangle. The smallest width or height of at least
347 visuals with zero multisample rectangle width or height are
351 same multisample subrectangle. There is at most one shared
352 multisample subrectangle per screen.
385 MULTISAMPLE_SUB_RECT_POSITION_SGIS GetIntegerv 2 x Z 0,0 multisample