Baggers
Baggers
We have some issues with the current approach. The lisp version isnt very lispy and the c/gpu versions don't support layout and require the creation of intermediate wrappers for basic...
This would be awesome for us as it gives the user a way to tell us that they will be requiring a certain GL version from their users. This lets...
This would let us do the persistently mapped gpu-buffer niceness. I really want to know if this can be used as a replacement for the old buffer api (on machines...
We cover the 'multiple gpu-arrays in buffer' on creation, but it isnt fun to rejiggle this later. Research current state of api and list potential issues below.
``` (defstruct-g (erosion-uvs :accesors nil) (left :vec2) (right :vec2) (top :vec2) (bottom :vec2) (top-left :vec2) (top-right :vec2) (bottom-left :vec2) (bottom-right :vec2)) ``` > ; caught WARNING: > ; The function...
It feels like a real task to switch out the array that the per instance data is taken from. Research this and see what we can do. Use play-with-verts' episode-24...
https://github.com/3b/cl-opengl/issues/10 > 23:50 borodust, Baggers: cl-opengl technically doesn't > support multiple contexts, so be careful how you use > it with them (specifically if you use immediate mode > you...
We havent really supported multiple contexts properly yet but we will do soon and so I needed a place to dump info on what I need to revisit. - `core/context/cepl-context.lisp#L6`...
https://www.khronos.org/opengl/wiki/Buffer_Object#Clearing ``` void glClearBufferData(GLenum target, GLenum internalformat, GLenum format, GLenum type, const void * data); void glClearBufferSubData(GLenum target, GLenum internalformat, GLintptr offset, GLsizeiptr size, GLenum format, GLenum type, const void...