Sign in to follow this  
xelanoimis

OpenGL Vertex Declarations in OpenGL and DirectX ?

Recommended Posts

Hi, What is the OpenGL echivalent for DirectX9 vertex declarations ? I know that OpenGL can use vertex arrays that are echivalent for vertexbuffers. But how to set vertex declarations, and can it use multiple streams (vertex arrays) ? I want to know this for use with CG effects or vertex programs available for OpenGL. Can anyone give a small code example (not necessarly functional, just curios about the functions used). I am also interested in a platform independent approach to meshes and effects. Can vertex shaders and vertex declarations be wraped in some engine classes to use with both OpenGL and DirectX effects (eventualy CG) ? Thanks

Share this post


Link to post
Share on other sites
Moved to OpenGL

For the first part of your question you're more likely to get a better answer from the OpenGL experts - they're the guys who know the API best [wink]

AS for an API/platform independent method, yes it's probably possible - but you can't really take it any further until you know what form both API's can use (or require). From there you can either decide whether you want to take a subset approach (basic functionality that both API's can handle) or some higher-level approach that involves work-arounds/emulation for parts of the respective API's that don't natively handle what you want. For example, if you really want streams, but OpenGL can't do that you could (presumably) emulate it by creating your own Input Assembler - not necessarily efficient, but it'd probably work.

hth
Jack

Share this post


Link to post
Share on other sites
JollyJeffers,

i can't follow your explanation; so, plesae tell me, what do you mean exactly by the term "subset approach" ?

(do you mean splitting up the rendering-work into more/simple subsets by switching only the vertex-dec.format ?)

Share this post


Link to post
Share on other sites
What it comes down to in OpenGL is that you get to define vertex declarations yourself, and then you get to write the rendering backend code that translates a vertex declaration into BindBuffer and Pointer calls.

It's fairly simple to do. You define an array of structures that have all of the information about the vertex declaration -- what its usage is, what type it is, offset and stream index, etc. Then you loop through that array, calling BindBuffer and pointer as necessary.

I basically have a header that defines stuff for a declaration:

#ifndef _GEOMETRY_H
#define _GEOMETRY_H

#include "../HoverEngine.h"

#include "RendererTypes.h"
#include "VertexBuffer.h"
#include "IndexBuffer.h"

#include <vector>

//type of element, i.e. what it specifies
enum VertexElementType
{
VET_XYZ,
VET_NORMAL,
VET_DIFFUSE,
VET_SPECULAR,
VET_TEXCOORD,
};

//'format' of element, basically the data type
//it's recommended that you avoid the INT64 types, as well as long double
enum VertexElementFormat
{
VEF_SIGNED_BYTE,
VEF_UNSIGNED_BYTE,

VEF_SIGNED_SHORT,
VEF_UNSIGNED_SHORT,

VEF_UNSIGNED_INT,
VEF_SIGNED_INT,

VEF_UNSIGNED_INT64,
VEF_SIGNED_INT64,

VEF_FLOAT,
VEF_DOUBLE,
VEF_LONG_DOUBLE,
};

//FVF quick-system
#define FVF_XYZ 0x00000001
#define FVF_NORMAL 0x00000002
#define FVF_DIFFUSE 0x00000004
#define FVF_SPECULAR 0x00000008

#define FVF_TEXTURE0 0x00010000
#define FVF_TEXTURE1 0x00020000
#define FVF_TEXTURE2 0x00040000
#define FVF_TEXTURE3 0x00080000
#define FVF_TEXTURE(X) (0x00010000 << (X))

//specifies a single part of a vertex, e.g. one position, or one texcoord, etc.
struct VertexElement
{
unsigned int Stream;
unsigned int Count;
std::size_t Offset; //offset in the structure
VertexElementFormat Format;
VertexElementType Type;

//normal ctor
VertexElement() : Stream( 0 ), Count( 0 ), Format( VEF_FLOAT ),
Type( VET_XYZ ), Offset( 0 )
{ }

//inline ctor for laziness
VertexElement( unsigned int vStream, unsigned int vCount, std::size_t vOffset,
VertexElementFormat vFormat, VertexElementType vType )
: Stream( vStream ), Count( vCount ), Format( vFormat), Type( vType ),
Offset( vOffset )
{ }

static std::size_t FormatSize( VertexElementFormat vef );

//Compute the size of this element in bytes
std::size_t SizeBytes() { return FormatSize( Format ) * Count; }
};


//specifies a complete vertex, basically just a list of elements
struct VertexDeclaration
{
typedef std::vector<VertexElement> ElementList;
typedef ElementList::iterator Iterator;

ElementList Elements;

VertexDeclaration()
{
Elements.reserve( 4 );
}

static VertexDeclaration CreateFromFVF( unsigned int FVF );
};

//in D3D, streams will correspond to real streams
//in OGL, the streams will be somewhat virtualised, but effectively the same
#define MAX_VERTEX_STREAMS 8
//holds all the data for a single stream
struct StreamSource
{
VertexBuffer* Source;
std::size_t Offset;
std::size_t Stride;

StreamSource() : Source( NULL ), Offset( 0 ), Stride( 0 )
{ }
};


//holds everything geometric about an object
class Geometry
{
protected:
VertexDeclaration m_Decl;

RenderMode m_Mode;
std::size_t m_PrimitiveCount;
std::size_t m_IndexCount;

StreamSource m_Streams[MAX_VERTEX_STREAMS];
IndexBuffer* m_Indices; //if IB is NULL, use non-indexed primitive
std::size_t m_IndexOffset;

std::size_t m_FirstVertex;
std::size_t m_NumVertices;

public:
Geometry();
virtual ~Geometry();

//Sets the rendering mode and primitive count for this geom
void SetRenderMode( RenderMode Mode, std::size_t IndexCount );

//Sets the vertex buffer for the specified stream
void SetStreamSource( unsigned int Stream, VertexBuffer* Source, std::size_t Offset, std::size_t Stride );
//Sets the indices for this geom (NULL for no indexing -- Offset is used for VB)
void SetIndices( IndexBuffer* Indices, std::size_t Offset );
//Sets the range of vertex used by the indices (ignored if not using indices)
void SetRange( std::size_t First, std::size_t Count );

//used to access the vertex declaration
VertexDeclaration& Decl() { return m_Decl; }
//access the streams
StreamSource* Stream( unsigned int Idx ) { assert( Idx < MAX_VERTEX_STREAMS ); return &m_Streams[Idx]; }
//access the indices
IndexBuffer* Indices() { return m_Indices; }
//index buffer offset
std::size_t IndexOffset() const { return m_IndexOffset; }
//Primitive count
std::size_t PrimitiveCount() const { return m_PrimitiveCount; }
std::size_t IndexCount() const { return m_IndexCount; }
//render mode for this geom
RenderMode Mode() const { return m_Mode; }
//Get the index range
void GetRange( std::size_t& First, std::size_t& Count ) const { First = m_FirstVertex; Count = m_NumVertices; }

};

#endif

And then the function to parse this into OpenGL goes like this:
void OGLRenderer::BeginRender( Geometry* Geom )
{
if( m_RenderBegun )
return;
if( Geom == NULL )
return;

//keeps track of tex coord sets in use
unsigned int TexCoord = 0;

//first, get the Geom's declaration and set stuff up
VertexDeclaration::Iterator it = Geom->Decl().Elements.begin();
while( it != Geom->Decl().Elements.end() )
{
if( m_CurrentVB != Geom->Stream( it->Stream )->Source )
{
m_CurrentVB = down_cast<OGLVertexBuffer*>( Geom->Stream( it->Stream )->Source );
if( m_CurrentVB != NULL )
{
m_CurrentVB->Bind();
}
else if( GLEE_ARB_vertex_buffer_object )
{
glBindBufferARB( GL_ELEMENT_ARRAY_BUFFER_ARB, 0 );
}
}

//initialize the pointers for this element
GLsizei Stride = (GLsizei) Geom->Stream( it->Stream )->Stride;
GLsizei StreamOffset = (GLsizei) Geom->Stream( it->Stream)->Offset;
switch( it->Type )
{
case VET_XYZ:
glEnableClientState( GL_VERTEX_ARRAY );
glVertexPointer( it->Count, TranslateVertexFormat( it->Format ), Stride, m_CurrentVB->GetPointer() + it->Offset + StreamOffset );
break;
case VET_NORMAL:
glEnableClientState( GL_NORMAL_ARRAY );
glNormalPointer( TranslateVertexFormat( it->Format ), Stride, m_CurrentVB->GetPointer() + it->Offset + StreamOffset );
break;
case VET_DIFFUSE:
glEnableClientState( GL_COLOR_ARRAY );
glColorPointer( it->Count, TranslateVertexFormat( it->Format ), Stride, m_CurrentVB->GetPointer() + it->Offset + StreamOffset );
break;
case VET_SPECULAR:
glEnableClientState( GL_SECONDARY_COLOR_ARRAY );
glSecondaryColorPointer( it->Count, TranslateVertexFormat( it->Format ), Stride, m_CurrentVB->GetPointer() + it->Offset + StreamOffset );
break;
case VET_TEXCOORD:
glClientActiveTexture( GL_TEXTURE0 + TexCoord );
glEnableClientState( GL_TEXTURE_COORD_ARRAY );
glTexCoordPointer( it->Count, TranslateVertexFormat( it->Format ), Stride, m_CurrentVB->GetPointer() + it->Offset + StreamOffset );
++TexCoord;
break;
}

++it;
}

//set up indices if we have any
if( m_Indices != Geom->Indices() )
{
m_Indices = down_cast<OGLIndexBuffer*>( Geom->Indices() );
if( m_Indices != NULL )
{
m_Indices->Bind();
}
else if( GLEE_ARB_vertex_buffer_object )
{
glBindBufferARB( GL_ELEMENT_ARRAY_BUFFER_ARB, NULL );
}
}

m_RenderBegun = true;
m_CurGeom = Geom;
}

(Note: This appears to be an older version of my source. The newer version has some modifications that allow arbitrary VertexElementTypes, which is useful for shader stuff.)

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
      628308
    • Total Posts
      2981974
  • Similar Content

    • 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.
    • By Abecederia
      So I've recently started learning some GLSL and now I'm toying with a POM shader. I'm trying to optimize it and notice that it starts having issues at high texture sizes, especially with self-shadowing.
      Now I know POM is expensive either way, but would pulling the heightmap out of the normalmap alpha channel and in it's own 8bit texture make doing all those dozens of texture fetches more cheap? Or is everything in the cache aligned to 32bit anyway? I haven't implemented texture compression yet, I think that would help? But regardless, should there be a performance boost from decoupling the heightmap? I could also keep it in a lower resolution than the normalmap if that would improve performance.
      Any help is much appreciated, please keep in mind I'm somewhat of a newbie. Thanks!
    • By test opty
      Hi,
      I'm trying to learn OpenGL through a website and have proceeded until this page of it. The output is a simple triangle. The problem is the complexity.
      I have read that page several times and tried to analyse the code but I haven't understood the code properly and completely yet. This is the code:
       
      #include <glad/glad.h> #include <GLFW/glfw3.h> #include <C:\Users\Abbasi\Desktop\std_lib_facilities_4.h> using namespace std; //****************************************************************************** void framebuffer_size_callback(GLFWwindow* window, int width, int height); void processInput(GLFWwindow *window); // settings const unsigned int SCR_WIDTH = 800; const unsigned int SCR_HEIGHT = 600; const char *vertexShaderSource = "#version 330 core\n" "layout (location = 0) in vec3 aPos;\n" "void main()\n" "{\n" " gl_Position = vec4(aPos.x, aPos.y, aPos.z, 1.0);\n" "}\0"; const char *fragmentShaderSource = "#version 330 core\n" "out vec4 FragColor;\n" "void main()\n" "{\n" " FragColor = vec4(1.0f, 0.5f, 0.2f, 1.0f);\n" "}\n\0"; //******************************* int main() { // glfw: initialize and configure // ------------------------------ glfwInit(); glfwWindowHint(GLFW_CONTEXT_VERSION_MAJOR, 3); glfwWindowHint(GLFW_CONTEXT_VERSION_MINOR, 3); glfwWindowHint(GLFW_OPENGL_PROFILE, GLFW_OPENGL_CORE_PROFILE); // glfw window creation GLFWwindow* window = glfwCreateWindow(SCR_WIDTH, SCR_HEIGHT, "My First Triangle", nullptr, nullptr); if (window == nullptr) { cout << "Failed to create GLFW window" << endl; glfwTerminate(); return -1; } glfwMakeContextCurrent(window); glfwSetFramebufferSizeCallback(window, framebuffer_size_callback); // glad: load all OpenGL function pointers if (!gladLoadGLLoader((GLADloadproc)glfwGetProcAddress)) { cout << "Failed to initialize GLAD" << endl; return -1; } // build and compile our shader program // vertex shader int vertexShader = glCreateShader(GL_VERTEX_SHADER); glShaderSource(vertexShader, 1, &vertexShaderSource, nullptr); glCompileShader(vertexShader); // check for shader compile errors int success; char infoLog[512]; glGetShaderiv(vertexShader, GL_COMPILE_STATUS, &success); if (!success) { glGetShaderInfoLog(vertexShader, 512, nullptr, infoLog); cout << "ERROR::SHADER::VERTEX::COMPILATION_FAILED\n" << infoLog << endl; } // fragment shader int fragmentShader = glCreateShader(GL_FRAGMENT_SHADER); glShaderSource(fragmentShader, 1, &fragmentShaderSource, nullptr); glCompileShader(fragmentShader); // check for shader compile errors glGetShaderiv(fragmentShader, GL_COMPILE_STATUS, &success); if (!success) { glGetShaderInfoLog(fragmentShader, 512, nullptr, infoLog); cout << "ERROR::SHADER::FRAGMENT::COMPILATION_FAILED\n" << infoLog << endl; } // link shaders int shaderProgram = glCreateProgram(); glAttachShader(shaderProgram, vertexShader); glAttachShader(shaderProgram, fragmentShader); glLinkProgram(shaderProgram); // check for linking errors glGetProgramiv(shaderProgram, GL_LINK_STATUS, &success); if (!success) { glGetProgramInfoLog(shaderProgram, 512, nullptr, infoLog); cout << "ERROR::SHADER::PROGRAM::LINKING_FAILED\n" << infoLog << endl; } glDeleteShader(vertexShader); glDeleteShader(fragmentShader); // set up vertex data (and buffer(s)) and configure vertex attributes float vertices[] = { -0.5f, -0.5f, 0.0f, // left 0.5f, -0.5f, 0.0f, // right 0.0f, 0.5f, 0.0f // top }; unsigned int VBO, VAO; glGenVertexArrays(1, &VAO); glGenBuffers(1, &VBO); // bind the Vertex Array Object first, then bind and set vertex buffer(s), //and then configure vertex attributes(s). glBindVertexArray(VAO); glBindBuffer(GL_ARRAY_BUFFER, VBO); glBufferData(GL_ARRAY_BUFFER, sizeof(vertices), vertices, GL_STATIC_DRAW); glVertexAttribPointer(0, 3, GL_FLOAT, GL_FALSE, 3 * sizeof(float), (void*)0); glEnableVertexAttribArray(0); // note that this is allowed, the call to glVertexAttribPointer registered VBO // as the vertex attribute's bound vertex buffer object so afterwards we can safely unbind glBindBuffer(GL_ARRAY_BUFFER, 0); // You can unbind the VAO afterwards so other VAO calls won't accidentally // modify this VAO, but this rarely happens. Modifying other // VAOs requires a call to glBindVertexArray anyways so we generally don't unbind // VAOs (nor VBOs) when it's not directly necessary. glBindVertexArray(0); // uncomment this call to draw in wireframe polygons. //glPolygonMode(GL_FRONT_AND_BACK, GL_LINE); // render loop while (!glfwWindowShouldClose(window)) { // input // ----- processInput(window); // render // ------ glClearColor(0.2f, 0.3f, 0.3f, 1.0f); glClear(GL_COLOR_BUFFER_BIT); // draw our first triangle glUseProgram(shaderProgram); glBindVertexArray(VAO); // seeing as we only have a single VAO there's no need to // bind it every time, but we'll do so to keep things a bit more organized glDrawArrays(GL_TRIANGLES, 0, 3); // glBindVertexArray(0); // no need to unbind it every time // glfw: swap buffers and poll IO events (keys pressed/released, mouse moved etc.) glfwSwapBuffers(window); glfwPollEvents(); } // optional: de-allocate all resources once they've outlived their purpose: glDeleteVertexArrays(1, &VAO); glDeleteBuffers(1, &VBO); // glfw: terminate, clearing all previously allocated GLFW resources. glfwTerminate(); return 0; } //************************************************** // process all input: query GLFW whether relevant keys are pressed/released // this frame and react accordingly void processInput(GLFWwindow *window) { if (glfwGetKey(window, GLFW_KEY_ESCAPE) == GLFW_PRESS) glfwSetWindowShouldClose(window, true); } //******************************************************************** // glfw: whenever the window size changed (by OS or user resize) this callback function executes void framebuffer_size_callback(GLFWwindow* window, int width, int height) { // make sure the viewport matches the new window dimensions; note that width and // height will be significantly larger than specified on retina displays. glViewport(0, 0, width, height); } As you see, about 200 lines of complicated code only for a simple triangle. 
      I don't know what parts are necessary for that output. And also, what the correct order of instructions for such an output or programs is, generally. That start point is too complex for a beginner of OpenGL like me and I don't know how to make the issue solved. What are your ideas please? What is the way to figure both the code and the whole program out correctly please?
      I wish I'd read a reference that would teach me OpenGL through a step-by-step method. 
  • Popular Now