The FBO Saga - Week 1#
This Past Week#
As mentioned in the last week’s blogpost, the goal for that week was to investigate VTK’s Framebuffer Object framework. An update on that is that indeed, VTK has one more low-level working FBO class that can be used inside FURY, however, they come with some issues that I will explain further below.
My Current Problems#
The problems I am having with these FBO implementations are first something related to how a FBO works, and second related to how VTK works. In OpenGL, a custom user’s FBO needs some things to be complete (usable):
At least one buffer should be attached. This buffer can be the color, depth or stencil buffer.
If no color buffer will be attached then OpenGL needs to be warned no draw or read operations will be done to that buffer. Otherwise, there should be at least one color attachment.
All attachments should have their memory allocated.
Each buffer should have the same number of samples.
My first problem relies on the third requirement. VTK’s implementation of FBO requires a vtkTextureObject as a texture attachment. I figured out how to work with this class, however, I cannot allocate memory for it, as its methods for it, Allocate2D, Create2D and Create2DFromRaw does not seem to work. Every time I try to use them, my program stops with no error message nor nothing. For anyone interested in what is happening exactly, below is how I my tests are implemented:
| color_texture = vtk.vtkTextureObject() # color texture declaration
| color_texture.Bind() # binding of the texture for operations
| color_texture.SetDataType(vtk.VTK_UNSIGNED_CHAR) # setting the datatype for unsigned char
| color_texture.SetInternalFormat(vtk.VTK_RGBA) # setting the format as RGBA
| color_texture.SetMinificationFilter(0) # setting the minfilter as linear
| color_texture.SetMagnificationFilter(0) # setting the magfilter as linear
| color_texture.Allocate2D(width, height, 4, vtk.VTK_UNSIGNED_CHAR) # here is where the code stops
In contrast, for some reason, the methods for 3D textures, Allocate3D works just fine. I could use it as a workaround, but I do not wish to, as this just does not make sense.
My second problem relies on VTK. As VTK is a library that encapsulates some OpenGL functions in more palatable forms, it comes with some costs. Working with FBOs is a more low-level work, that requires strict control of some OpenGL states and specific functions that would be simpler if it was the main API here. However, some of this states and functions are all spread and implicit through VTK’s complex classes and methods, which doubles the time expended to make some otherwise simple instructions, as I first need to dig in lines and lines of VTK’s documentation, and worse, the code itself.
What About Next Week?#
For this next week, I plan to investigate further on why the first problem is happening. If that is accomplished, then things will be more simple, as it will be a lot easier for my project to move forward as I will finally be able to implement the more pythonic functions needed to finally render some kernel distributions onto my screen.
Wish me luck!