Lines Matching +full:hollow +full:- +full:knight

2 -----------------------
23 .. code-block:: text
42 the ``glDraw*()`` calls (a common behavior for non-tiled GPUs, particularly those with
57 .. code-block:: text
89 This suggests that, for non-blitting drivers, resetting your "might be used on
96 .. code-block:: text
117 .. code-block:: text
145 .. code-block:: text
186 frame n-1 as the CPU starts the current frame. The first map is ``offset = 0,
194 vertex array -- you can't effectively use it as a hint for any buffer placement
202 .. code-block:: text
240 the :ext:`GL_ARB_sync` fence has ensured that the GPU has started frame n-1.
243 of the VBO -- it is important that a blitting driver make use of the flush
249 .. code-block:: text
279 .. code-block:: text
303 fence ensures that frame n-1 has started on the GPU before CPU work starts on
306 Hollow Knight
309 .. code-block:: text
341 start of the previous frame before we go unsynchronized writing over the n-2
347 .. code-block:: text
366 The :ext:`GL_ARB_sync` fence ensures that the GPU has started frame n-1 before the CPU
371 reallocate if the buffer is GPU-busy (it wasn't in this trace capture) to avoid
372 stalls on the n-1 frame completing.
379 --------------------------
381 * Non-blitting drivers must track the valid range of a freshly allocated buffer
386 * Non-blitting drivers must reallocate storage on ``glBufferData(NULL)`` so that
399 * Buffer valid range tracking in non-blitting drivers must use the