OpenGL OpenGL - Render Plane equation

Recommended Posts

Hi guys, i'm trying to figure out how to render a plane. My internal plane representation consists of a normal, and distance from origin

Vector3 Normal;
float Distance;


Given this, i've tried the following to render the plane:

GL.PushMatrix();

GL.Translate(Normal.X * Distance, Normal.Y * Distance, Normal.Z * Distance);
GL.Rotate(Normal.Y * 360f, 0f, 1f, 0f);
GL.Rotate(Normal.X * 360f, 1f, 0f, 0f);
GL.Rotate(Normal.Z * 360f, 0f, 0f, 1f);

GL.Vertex3(-1, 1, 0);
GL.Vertex3(-1, -1, 0);
GL.Vertex3(1, -1, 0);
GL.Vertex3(1, 1, 0);
GL.End();

GL.PopMatrix();


While this seems to work, i have doubts that it will with all angles... (Reason being the rotation order).

So, my question, is there a better way to derive a plane to be rendered?

I'm using C# and OpenTK to render this.

Please don't comment that i should be using more modern OpenGL, that is not constructive to the question i'm asking.

Share on other sites

Your doubts are valid, but the reason is wrong. The vertices are placed onto the local x/y plane, hence the normal is along the direction of the local z axis. Putting (0,0,1) into your rotation code and considering that rotation by 360° is identical to rotation by 0°, you correctly see the front of your plane. However, just using normals along x (1,0,0) or y (0,1,0) or so with your rotation code still give you the same vertices, since all transformations are the same. Changing the order of rotation does not make any difference then.

Actually, using a normal and a distance lets several degrees of freedom in an open state. Rendering a plane with vertices need those degree of freedom to be fixed. What I mean is that you need a definition of

a) an origin of the plane, so that there is a point with local co-ordinates (0,0,0),

b) an orientation angle around the normal (think of the rolling angle of a camera; the normal gives you just 2 of the 3 angles).

You solved a) by using the point

origin := (0,0,0) + distance * normal

You solve b) by just picking an angle, i.e. so that rolling is zero.

So with these fixes you have a position and an orientation as a direction and "no rolling". Let's express "no rolling" as

up_vector := (0,1,0)
And instead of a pure direction, let's use it as difference vector from the origin to a tip point

center_point := origin + normal * 1

Now (with the origin and the center point and the up vector), what we have here are the ingredients for the gluLookAt function! Although being described as a function to compute a view matrix, the function actually just builds a transformation matrix with a translation and rotations so that the z axis points in a specific direction.

The math behind the gluLookAt function isn't complicated and leaving OpenGL's matrix stack behind is ever a Good Thing TM, but I assume you may be happy with the sketched solution. Otherwise feel free to ask :)

Edited by haegarr

Share on other sites

I think this is what you are describing:

Vector3 forward = new Vector3(Normal.X, Normal.Y, Normal.Z);
Vector3 up = new Vector3(0f, 1f, 0f);
Vector3 right = Vector3.Cross(forward, up);
up = Vector3.Cross(right, forward);

Matrix4 rot = new Matrix4(right.X, up.X, -forward.X, 0.0f,
right.Y, up.Y, -forward.Y, 0.0f,
right.Z, up.Z, -forward.Z, 0.0f,
0.0f, 0.0f, 0.0f, 1.0f);
Matrix4 trans = Matrix4.Translate(Normal * Distance);

Matrix4 result = rot * trans;

GL.PushMatrix();

GL.Vertex3(-1, 1, 0);
GL.Vertex3(-1, -1, 0);
GL.Vertex3(1, -1, 0);
GL.Vertex3(1, 1, 0);
GL.End();

GL.Begin(PrimitiveType.Points);
GL.Color3(1f, 1f, 0f);
GL.Vertex3(0f, 0f, 0f);
GL.Color3(1f, 0f, 1f);
GL.Vertex3(Normal.X * Distance, Normal.Y * Distance, Normal.Z * Distance);
GL.End();

GL.PopMatrix();


This however does not seem to work either. I can't even get the reference points rendering once i load the matrix generated above :(

Am i missing a step in this?

Share on other sites

I don't know how your framework linearizes matrices, so this code snippet
Matrix4 rot = new Matrix4(...)

may or may not be correct.

But there is a noticeable difference in transformation computation between your 1st and your 2nd post. In the 1st post you compute

Mi+1 := Mi * T * R

with M being the transformation matrix on the stack, T being the translation and R the rotation. The snippet in your 2nd post computes

Mi+1 := I * R * T

instead, where I is the identity matrix. Notice that (a) the matrix being formerly on the top of the stack is now ignored, and that (b) the order of translation and rotation is exchanged.

Hence try to change this line

Matrix4 result = rot * trans;

into

Matrix4 result = trans * rot;

Further, if the former stack matrix should play a role, instead of
use
GL.MultMatrix(result.OpenGL);

Share on other sites

Wow, GREAT CATCH! Rookie mistake on my part! You where correct in both cases, first i multiplied the matrix instead of loading; and the multiplication order did need to be reversed also. The matrix constructor was correct. Thank you so much for the help, it works flawlesly now!

For anyone who might be interested, my final code ended up being:

// Debug Normal
GL.Color3(1f, 1f, 0f);
GL.Begin(PrimitiveType.Lines);
GL.Vertex3(0f, 0f, 0f);
GL.Vertex3(Normal.X * 500, Normal.Y * 500, Normal.Y * 500);
GL.End();

GL.Color3(1f, 1f, 1f);
Vector3 forward = new Vector3(Normal.X, Normal.Y, Normal.Z);
Vector3 up = new Vector3(0f, 1f, 0f);
Vector3 right = Vector3.Cross(forward, up);
up = Vector3.Cross(right, forward);

Matrix4 rot = new Matrix4(right.X, up.X, -forward.X, 0.0f,
right.Y, up.Y, -forward.Y, 0.0f,
right.Z, up.Z, -forward.Z, 0.0f,
0.0f, 0.0f, 0.0f, 1.0f);
Matrix4 trans = Matrix4.Translate(Normal * Distance);

Matrix4 result = trans * rot;

GL.PushMatrix();
GL.MultMatrix(result.OpenGL);

// Draw Plane
GL.Vertex3(-1, -1, 0);
GL.Vertex3(-1, 1, 0);
GL.Vertex3(1, 1, 0);
GL.Vertex3(1, -1, 0);
GL.End();

// Debug Points
GL.Begin(PrimitiveType.Points);
GL.Color3(1f, 1f, 0f);
GL.Vertex3(0f, 0f, 0f);
GL.Color3(1f, 0f, 1f);
GL.Vertex3(Normal.X * Distance, Normal.Y * Distance, Normal.Z * Distance);
GL.End();

GL.PopMatrix();


Tough my math lib is a bit wonky, you might need to adjust.

Create an account

Register a new account

• Forum Statistics

• Total Topics
628384
• Total Posts
2982390
• 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
• 15
• 24
• 11