Lines Matching refs:feedback
51 This extension provides a new mode to the GL, called transform feedback,
57 geometry program. Otherwise, transform feedback captures primitives whose
60 generated prior to clipping. Transform feedback mode is capable of
65 The vertex data recorded in transform feedback mode is stored into buffer
69 particular, transform feedback data can be used for vertex arrays (via
76 feedback mode to operate asynchronously. Query objects allow applications
77 to determine when transform feedback results are complete, as well as the
79 transform feedback mode. This extension also provides a new rasterizer
80 discard enable, which allows applications to use transform feedback to
215 supported by the GL. Transform feedback queries (section 2.Y) returns
298 In 'transform feedback' mode the vertices of transformed primitives are
306 Transform feedback is started and finished by calling
314 respectively. Transform feedback is said to be active after a call to
316 EndTransformFeedbackNV. Transform feedback is initially inactive.
317 Transform feedback is performed after color clamping, but immediately
320 that will be recorded into the buffer objects bound for transform feedback
322 that may be rendered during an instance of transform feedback. See table
334 Table X.1 Legal combinations between the transform feedback primitive
348 current transform feedback buffer state. If a geometry program or geometry
355 feedback is active. It is an invalid operation error to call
356 EndTransformFeedbackNV while transform feedback is inactive.
358 Transform feedback can operate in either INTERLEAVED_ATTRIBS_NV or
369 of buffer objects required, as given by the current transform feedback
374 Buffer objects are made to be targets of transform feedback by calling one
390 elements that can be written during transform feedback mode. This is
396 the BindBuffer* commands is called while transform feedback is active.
404 for transform feedback purposes would result in either exceeding the
412 streamed to one, or more, buffer objects in transform feedback mode. If
420 active, the set of vertex attributes recorded in transform feedback mode
427 This command sets the transform feedback state for <program> and specifies
428 which varying variables to record when transform feedback is active. The
462 TransformFeedbackVaryingsNV(). Changes to the transform feedback state
470 geometry program can be recorded in transform feedback mode. The set of
514 The TransformFeedbackAttribsNV() command sets transform feedback state
549 transform feedback buffers.
557 further tessellated into separate primitives during the transform-feedback
561 TRANSFORM_FEEDBACK_PRIMITIVES_WRITTEN_NV, the transform-feedback-
563 transform feedback primitive written query is active, the
564 transform-feedback-primitives-written count is incremented every time a
565 primitive is recorded into a buffer object. If transform feedback is not
570 been written to the bound feedback buffers; if both queries are run
588 regardless of the transform-feedback state set with the
593 can be useful in transform feedback mode if there are varying variables to
669 needs for transform feedback purposes. The set of active varying variables
679 transform feedback stage. When disabled, primitives are passed through to
816 To query which buffer objects are the target(s) when transform feedback is
825 binding used for transform feedback, call GetIntegerIndexedvEXT() with
857 used when transform feedback is active, is returned. It can be one of
942 match the allowed begin modes for the current transform feedback state
947 modes for the current transform feedback state as given by table X.1.
956 transform feedback state.
964 transform feedback is active.
967 transform feedback is inactive.
981 commands is called while transform feedback is active.
1055 TRANSFORM_FEEDBACK_ Z2 GetIntegerv INTERLEAVED_ Transform feedback mode 2.Y -
1059 feedback mode
1062 transform feedback.
1067 BUFFER_BINDING_NV IndexedvEXT each transform feedback
1071 feedback attrib. stream
1074 feedback attrib. stream
1077 transform feedback.)
1083 feedback)
1086 elapsed, feedback data amount)
1097 TRANSFORM_FEEDBACK_ Z2 GetProgramiv INTERLEAVED_ Transform feedback mode 6.1.14 -
1116 transform feedback.)
1122 transform feedback queries)
1137 feedback
1144 1. How does transform feedback differ from core GL feedback?
1146 * Transform feedback writes vertex data to buffer objects, which allows
1147 the data returned to be used directly by vertex pulling. GL feedback
1150 * Transform feedback is done after transformation, but prior to
1155 * Transform feedback supports only a single basic output primitive type
1156 (points, lines, or triangles), while core GL feedback mode supports
1159 fed back. Primitive tokens make the data returned by GL feedback mode
1166 similarities to GL feedback mode.
1168 3. What happens if you bind a buffer for transform feedback that is
1176 analogy, while a buffer is being used for transform feedback, no other
1179 source data from an active transform feedback buffer object.
1197 RESOLVED: No. A program can get the contents of the feedback buffer back
1201 initiate the transform feedback mode?
1204 a clean place to spec all of the transform-feedback-specific issues
1206 to be done at the same time as beginning and ending the feedback
1210 conjunction with transform feedback?
1214 feedback, and the contents of the buffer object are subsequently being
1217 through transform feedback, but is being consumed by the application
1225 of transform feedback, and it is deleted via DeleteBuffers?
1228 transform feedback is active.
1234 10. Should we allow feedback to buffer lists with holes (i.e. 0 and 2
1242 11. Why only one feedback primitive mode per feedback invocation?
1256 output to the feedback buffer. This is consistent with taking a
1269 15. How do the transform feedback indices, passed to the BindBuffer*
1306 valid at the start of transform feedback mode?
1315 written to the buffer. If a partial primitive enters transform feedback
1323 feedback that is active. The number of primitives that are written is
1324 only valid for transform feedback - another extension could conceivably
1329 feedback mode if non-active varying variables are specified?
1340 object in transform feedback mode are set as a property of the
1346 object in transform feedback mode are specified after the program
1352 to stream in transform feedback mode is too large.
1403 live that it needs for transform feedback purposes. The set of active
1418 25. Are primitives sent down the pipeline after transform feedback, or
1424 buffer objects bound to transform feedback. When disabled, primitives
1450 RESOLVED: Transform feedback can only record the primitive ID values
1452 primitive recorded for transform-feedback has a well-defined primitive
1453 ID, transform feedback is only capable of recording the attributes of
1456 29. Does transform feedback support the ability to capture per-vertex