Sign in to follow this  

OpenGL Frustrum deprecated

Recommended Posts

Hi, I've been playing around with OpenGL 3.0 a bit since its release, trying to work my way around the deprecated features. I understand that the fixed pipeline was practically deprecated, so everything should be drawn using shaders. One thing I stumbled upon was the deprecated projection and modelview matrices, including the Frustrum and Translate/Rotate calls. What is now the best way to get the view transform matrix (modelview * projection) into the vertex shader? I know how to compute it myself, but having to do so wouldn't be very userfriendly. Regards, Ignifex

Share this post

Link to post
Share on other sites
I guess that they (khronos) did that because they're focusing on what the hardware does rather than support some functions that can be made on the application side.

May it's more efficient making some arithmetic calculations on the CPU than sending commands to GL.

Share this post

Link to post
Share on other sites
All glFrustum, glOrtho, glRotate, glTranslate, ... were likely be computed by the driver on the CPU, and only the results were pushed into the GPU.

Dropping all the predefined uniforms and attributes means to unburden GLSL and the GL API from semantics that are insufficient in some cases anyhow. E.g. what if you have to transport a 3rd color, a 2nd vertex position, or something like that? Such things happen often enough. IMHO it is a a logical step to unify the access down to generic uniforms and attributes. I'm currently implementing a graphics techniques and styles system based on shader scripts, and I would be happy if the current OpenGL would already have dropped the predefined semantics...

glRotate and friends are also mainly superflous. All projects a bit behind test projects have to implement an own co-ordinate frame system anyhow (okay, they need not really, but scan the threads here at GDnet, and you see that it is better to do that kind of stuff yourself instead of relying on OpenGL's matrix stacks). My engine currently consists of roughly 180 classes, and there is no single glTranslate or glRotate inside.

So, IMHO, it is more user friendly than user unfriendly to drop those stuff; it is just senseful to unburden the API from mainly useless stuff. That slims the API and makes it more readable and hence easier to learn. That is also a kind of user friendliness.

Just my 2 cents, of course.

EDIT: And I bet that utility libraries countervailing these "deficits" will occur in masses.

[Edited by - haegarr on August 17, 2008 10:40:40 AM]

Share this post

Link to post
Share on other sites
I agree that it will be better not to have the predefined uniforms and be able to fully define attributes.
As you said about the utility libraries, I'm mainly looking for the CPU implementation of gluPerspective and gluLookAt, which would return the matrix as a simple array, to be sent to the vertex shader. For now, I'll write my own implementation.

EDIT: Btw, as Carmack said, slimming the API is indeed the way to go.

Share this post

Link to post
Share on other sites
After a look at the source code of your library, which looks really useful, I see your glhPerspectivef function calls glFrustrum, which is now deprecated. I mean to get a 4x4 matrix in main memory, then use that as a uniform parameter for the vertex shader.

Share this post

Link to post
Share on other sites
heres what I have, beaware your matrix order might be different to mine

void MATRIX44::frustum( float l, float r, float b, float t, float n, float f )

// 2n r+l
// ---- 0 ----- 0
// r-l r-l

// 2n t+b
// 0 ---- ----- 0
// t-b t-b

// f+n 2fn
// 0 0 - ---- - ----
// f-n f-n

// 0 0 -1 0

a00 = (2.0*n) / (r-l);
a10 = 0.0;
a20 = 0.0;
a30 = 0.0;

a01 = 0.0;
a11 = (2.0*n) / (t-b);
a21 = 0.0;
a31 = 0.0;

a02 = (r+l) / (r-l);
a12 = (t+b) / (t-b);
a22 = -(f+n) / (f-n);
a32 = -1.0;

a03 = 0.0;
a13 = 0.0;
a23 = -(2.0*f*n) / (f-n);
a33 = 0.0;

if u check the opengl spec for the Frustum(...) command u can work out whats going on

Share this post

Link to post
Share on other sites
Original post by Ignifex
After a look at the source code of your library, which looks really useful, I see your glhPerspectivef function calls glFrustrum, which is now deprecated. I mean to get a 4x4 matrix in main memory, then use that as a uniform parameter for the vertex shader.

You should do
float projectionMatrix[16];
glhPerspectivef2(projectionMatrix, fovy, aspect, znear, zfar);

and upload the matrix to your shader.

glhPerspectivef and other functions will be removed in the next version which will appear in a day or 2.

Share this post

Link to post
Share on other sites

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

Sign in to follow this  

  • Announcements

  • Forum Statistics

    • Total Topics
    • Total Posts
  • Similar Content

    • By test opty
      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?
    • By DejayHextrix
      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. 
      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!
    • 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.
  • Popular Now