# OpenGL GPU voxelization - Conservative rasterization issue.

## Recommended Posts

While implementing the technique outlined in Crassins / Greens work found in OpenGL insights I've run into some issues.

To get proper voxel coverage I need to dilate the triangles before they are sent off to rasterization. As written in the article they are using an older technique found in GPU Gems 2 on conservative rasterization.

My issue is that the my geometry shader projects the triangles using orthographic projections where the conservative rasterization technique only works when using perspective. As far as I can tell.

Anyone here had any experience with implementing the technique? And if so please help me out here.

#### Share this post

##### Share on other sites

I don't see why you shouldn't be able to use conservative rasterization with an orthographic projection - the only difference is that you accept all pixels which are ever-so-slightly covered by a triangle (conservative estimate) instead of discarding those with less than 50% coverage. Though obviously the math will be different. In fact, it will probably be simpler since the projection is not as complicated, for instance I would start by getting the triangle's screen-space dimensions. Since this is an orthographic projection, this is trivial and you can just use the post-transformation (x, y) coordinates of each vertex.

At this point you have all the information you need to apply the corrective algorithms (42.2) in the GPU Gems article, obtain the new optimal vertex coordinates, and invert the transformation to get your corrected vertices back into world space (if you need this for rendering - the rasterization step doesn't care and just wants clip space coordinates).

Most of the math at the end of this article concerns how to correct depth as well, since this is important in perspective rendering. However, that's not the case for orthographic projections, as there is no depth to worry about then, so it seems to me that you can ignore all of that.

At least that's my take on it - I've never implemented any of this, just going on mathematical principles and logic here.

#### Share this post

##### Share on other sites

First of all - Thank you for your answer.

I agree that having orthographic projects makes alot of stuff easiere as I can just extend the clipspace vertices directly. The problem lies in HOW much to extend. The article outlines that you'll need to extend along the worst-case semidiagonal. The author uses the fact that a line in clipspace can be represented as a plane through the camera (0,0,0) in projected space and then dilutes along the plane normal - Then to find the new vertex positions they do a plane - plane intersection using a cross product.

I just don't think this works for orthographic projects as all points on a direction vector from the origin doesn't project to a single point.

For reference here my geometry code for the impl.

	// Triangle bounding box.
vec4 f4AABB;

// Compute v0.
vec4 f4CSV0 = m4ViewProj * RF_WORLD * gl_in[0].gl_Position;
f4AABB.xy = f4CSV0.xy;
f4AABB.zw = f4CSV0.xy;

// Compute v1.
vec4 f4CSV1 = m4ViewProj * RF_WORLD * gl_in[1].gl_Position;
f4AABB.xy = min(f4AABB.xy, f4CSV1.xy);
f4AABB.zw = max(f4AABB.zw, f4CSV1.xy);

// Compute v2.
vec4 f4CSV2 = m4ViewProj * RF_WORLD * gl_in[2].gl_Position;
f4AABB.xy = min(f4AABB.xy, f4CSV2.xy);
f4AABB.zw = max(f4AABB.zw, f4CSV2.xy);

// Extend and set AABB.
f4AABB.xy -= vec2(fHalfPixel);
f4AABB.zw += vec2(fHalfPixel);
OUT.f4AABB = f4AABB;

// Compute dialated edges.
vec3 f3Plane[3];
f3Plane[0] = cross(f4CSV0.xyw - f4CSV2.xyw, f4CSV2.xyw);
f3Plane[1] = cross(f4CSV1.xyw - f4CSV0.xyw, f4CSV0.xyw);
f3Plane[2] = cross(f4CSV2.xyw - f4CSV1.xyw, f4CSV1.xyw);
f3Plane[0].z -= dot(vec2(fHalfPixel), abs(f3Plane[0].xy));
f3Plane[1].z -= dot(vec2(fHalfPixel), abs(f3Plane[1].xy));
f3Plane[2].z -= dot(vec2(fHalfPixel), abs(f3Plane[2].xy));

// Compute plane intersections.
f4CSV0.xyw = cross(f3Plane[0], f3Plane[1]);
f4CSV1.xyw = cross(f3Plane[1], f3Plane[2]);
f4CSV2.xyw = cross(f3Plane[2], f3Plane[0]);

// Emit vertex data.
OUT.f3CSPosition = m3Rotation * (f4CSV0.xyz / f4CSV0.w);
OUT.f3Color = f3Color;
gl_Position = f4CSV0;
EmitVertex();

OUT.f3CSPosition = m3Rotation * (f4CSV1.xyz / f4CSV1.w);
OUT.f3Color = f3Color;
gl_Position = f4CSV1;
EmitVertex();

OUT.f3CSPosition = m3Rotation * (f4CSV2.xyz / f4CSV2.w);
OUT.f3Color = f3Color;
gl_Position = f4CSV2;
EmitVertex();

EndPrimitive();

## Create an account or sign in to comment

You need to be a member in order to leave a comment

## Create an account

Sign up for a new account in our community. It's easy!

Register a new account

## Sign in

Already have an account? Sign in here.

Sign In Now

• ### Forum Statistics

• Total Topics
628354
• Total Posts
2982230
• ### Similar Content

• Hi all,

I'm starting OpenGL using a tut on the Web. But at this point I would like to know the primitives needed for creating a window using OpenGL. So on Windows and using MS VS 2017, what is the simplest code required to render a window with the title of "First Rectangle", please?

• Hi, New here.
I need some help. My fiance and I like to play this mobile game online that goes by real time. Her and I are always working but when we have free time we like to play this game. We don't always got time throughout the day to Queue Buildings, troops, Upgrades....etc....
I was told to look into DLL Injection and OpenGL/DirectX Hooking. Is this true? Is this what I need to learn?
How do I read the Android files, or modify the files, or get the in-game tags/variables for the game I want?
Any assistance on this would be most appreciated. I been everywhere and seems no one knows or is to lazy to help me out. It would be nice to have assistance for once. I don't know what I need to learn.
So links of topics I need to learn within the comment section would be SOOOOO.....Helpful. Anything to just get me started.
Thanks,
Dejay Hextrix
• By mellinoe
Hi all,
First time poster here, although I've been reading posts here for quite a while. This place has been invaluable for learning graphics programming -- thanks for a great resource!
Right now, I'm working on a graphics abstraction layer for .NET which supports D3D11, Vulkan, and OpenGL at the moment. I have implemented most of my planned features already, and things are working well. Some remaining features that I am planning are Compute Shaders, and some flavor of read-write shader resources. At the moment, my shaders can just get simple read-only access to a uniform (or constant) buffer, a texture, or a sampler. Unfortunately, I'm having a tough time grasping the distinctions between all of the different kinds of read-write resources that are available. In D3D alone, there seem to be 5 or 6 different kinds of resources with similar but different characteristics. On top of that, I get the impression that some of them are more or less "obsoleted" by the newer kinds, and don't have much of a place in modern code. There seem to be a few pivots:
The data source/destination (buffer or texture) Read-write or read-only Structured or unstructured (?) Ordered vs unordered (?) These are just my observations based on a lot of MSDN and OpenGL doc reading. For my library, I'm not interested in exposing every possibility to the user -- just trying to find a good "middle-ground" that can be represented cleanly across API's which is good enough for common scenarios.
Can anyone give a sort of "overview" of the different options, and perhaps compare/contrast the concepts between Direct3D, OpenGL, and Vulkan? I'd also be very interested in hearing how other folks have abstracted these concepts in their libraries.
• By aejt
I recently started getting into graphics programming (2nd try, first try was many years ago) and I'm working on a 3d rendering engine which I hope to be able to make a 3D game with sooner or later. I have plenty of C++ experience, but not a lot when it comes to graphics, and while it's definitely going much better this time, I'm having trouble figuring out how assets are usually handled by engines.
I'm not having trouble with handling the GPU resources, but more so with how the resources should be defined and used in the system (materials, models, etc).
This is my plan now, I've implemented most of it except for the XML parts and factories and those are the ones I'm not sure of at all:
I have these classes:
For GPU resources:
Geometry: holds and manages everything needed to render a geometry: VAO, VBO, EBO. Texture: holds and manages a texture which is loaded into the GPU. Shader: holds and manages a shader which is loaded into the GPU. For assets relying on GPU resources:
Material: holds a shader resource, multiple texture resources, as well as uniform settings. Mesh: holds a geometry and a material. Model: holds multiple meshes, possibly in a tree structure to more easily support skinning later on? For handling GPU resources:
ResourceCache<T>: T can be any resource loaded into the GPU. It owns these resources and only hands out handles to them on request (currently string identifiers are used when requesting handles, but all resources are stored in a vector and each handle only contains resource's index in that vector) Resource<T>: The handles given out from ResourceCache. The handles are reference counted and to get the underlying resource you simply deference like with pointers (*handle).
And my plan is to define everything into these XML documents to abstract away files:
Resources.xml for ref-counted GPU resources (geometry, shaders, textures) Resources are assigned names/ids and resource files, and possibly some attributes (what vertex attributes does this geometry have? what vertex attributes does this shader expect? what uniforms does this shader use? and so on) Are reference counted using ResourceCache<T> Assets.xml for assets using the GPU resources (materials, meshes, models) Assets are not reference counted, but they hold handles to ref-counted resources. References the resources defined in Resources.xml by names/ids. The XMLs are loaded into some structure in memory which is then used for loading the resources/assets using factory classes:
Factory classes for resources:
For example, a texture factory could contain the texture definitions from the XML containing data about textures in the game, as well as a cache containing all loaded textures. This means it has mappings from each name/id to a file and when asked to load a texture with a name/id, it can look up its path and use a "BinaryLoader" to either load the file and create the resource directly, or asynchronously load the file's data into a queue which then can be read from later to create the resources synchronously in the GL context. These factories only return handles.
Factory classes for assets:
Much like for resources, these classes contain the definitions for the assets they can load. For example, with the definition the MaterialFactory will know which shader, textures and possibly uniform a certain material has, and with the help of TextureFactory and ShaderFactory, it can retrieve handles to the resources it needs (Shader + Textures), setup itself from XML data (uniform values), and return a created instance of requested material. These factories return actual instances, not handles (but the instances contain handles).

Is this a good or commonly used approach? Is this going to bite me in the ass later on? Are there other more preferable approaches? Is this outside of the scope of a 3d renderer and should be on the engine side? I'd love to receive and kind of advice or suggestions!
Thanks!
• By nedondev
I 'm learning how to create game by using opengl with c/c++ coding, so here is my fist game. In video description also have game contain in Dropbox. May be I will make it better in future.
Thanks.

• 10
• 9
• 11
• 24
• 11