• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
Clancy

converting to VBOs with glDrawElements from immediate mode

7 posts in this topic

This draws a box.

 

     glBegin ( GL_LINE_STRIP );
        glVertex2i ( x0, y0 );
        glVertex2i ( x1, y0 );
        glVertex2i ( x1, y1 );
        glVertex2i ( x0, y1 );
        glVertex2i ( x0, y0 );
    glEnd ();
 

Now, to convert it to use VBO I have done

 

 

    GLint vertices[] = {x0,y0,x1,y0,x1,y1,x0,y1,x0,y0 };
    unsigned int indices[] = {0, 1, 2, 3,0};

    glBindBuffer(GL_ARRAY_BUFFER, buffers[0]);
    glBufferData(GL_ARRAY_BUFFER, sizeof(vertices), vertices, GL_DYNAMIC_DRAW);

    glEnableClientState(GL_VERTEX_ARRAY);
    glVertexPointer(2, GL_INT, 0, NULL);
    glDrawElements(GL_LINE_STRIP, 5, GL_UNSIGNED_INT, indices);
    glDisableClientState(GL_VERTEX_ARRAY);
 

 

I must be doing something stupid, since it isn't working.  Instead of a box, it isn't drawing anything visable.

Not getting any GL errors either.

I can toggle the code above to go back to old code, and it works as it should.

 

 

 

Where did I mess up ?

Edited by Clancy
0

Share this post


Link to post
Share on other sites

vertices is a pointer which means that sizeof(vertices) will always be 4 or 8, what you want is something like 4*sizeof(GLint).

0

Share this post


Link to post
Share on other sites

vertices is a pointer which means that sizeof(vertices) will always be 4 or 8, what you want is something like 4*sizeof(GLint).

No, vertices is an array and sizeof(vertices) correctly returns its size.

1

Share this post


Link to post
Share on other sites

No, vertices is an array and sizeof(vertices) correctly returns its size.

If you do something like this: GLint vertices[] = {x0y0x1y0x1y1x0y1x0y0};

the value of "vertices" will be the address of the first element and the [index] operator does not do anything else but some pointer arithmetic to access the elements. You can access the first element as *vertices. vertices should have the type GLint* and sizeof should return the according size.

If I am wrong, I will of course accept that, but that would kinda destroy everything I thought understood about programming...

 

Edit: Okay, I googled and tried it myself and actually sizeof returns the correct array size :)

Edited by _Slin_
0

Share this post


Link to post
Share on other sites

No, vertices is an array and sizeof(vertices) correctly returns its size.

If you do something like this: GLint vertices[] = {x0y0x1y0x1y1x0y1x0y0};

the value of "vertices" will be the address of the first element and the [index] operator does not do anything else but some pointer arithmetic to access the elements. You can access the first element as *vertices. vertices should have the type GLint* and sizeof should return the according size.

If I am wrong, I will of course accept that, but that would kinda destroy everything I thought understood about programming...

 

Why not printf sizeof (vertices) and find out?  But Brother Bob is right; if it was *vertices it would be different of course.

 

The OP's code looks correct to me, assuming that buffers[0] is a valid buffer object name created via glGenBuffers (if that's not the case then there's the problem).  An outside possibility is a driver bug causing problems with a GL_INT vertex type; maybe try changing that to floats and see if the problem reproduces?  Another test might be to use:

 

glBegin (GL_LINE_STRIP);
glArrayElement (0);
glArrayElement (1);
glArrayElement (2);
glArrayElement (3);
glArrayElement (0);
glEnd ();

That's functionally equivalent tothe glDrawElements call but - just using it as a test - may help to shed some light on what's happening here.

0

Share this post


Link to post
Share on other sites

vertices is the array itself, not a pointer to the first element. There are many places where the array can decay into a pointer, which is the primary source of confusion in situations like this. But in the end, an array is not a pointer, nor is a pointer an array. Both can be subscripted, both can be used in a pointer contexts (such as passing an array to a function that expects a pointer, in which the pointer-decay I mentioned takes place), but they are distinct types.

 

Try this for example:

int main()
{
    int foo1[] = {1, 2, 3};
    int *foo2 = foo1;

    std::cout << "type=" << typeid(foo1).name() << ", size=" << sizeof(foo1) << std::endl;
    std::cout << "type=" << typeid(foo2).name() << ", size=" << sizeof(foo2) << std::endl;
}

This is what VS2012 for x64 shows for me:

type=int [3], size=12
type=int * __ptr64, size=8

It shows that the array has the type of three integers and the size of three integers, and that the pointer is of pointer type and is the size of a pointer. The assignment of foo1 to foo2 demonstrates how the array decays into a pointer and is thus a valid assignment.

0

Share this post


Link to post
Share on other sites

The OP's code looks correct to me, assuming that buffers[0] is a valid buffer object name created via glGenBuffers (if that's not the case then there's the problem). An outside possibility is a driver bug causing problems with a GL_INT vertex type; maybe try changing that to floats and see if the problem reproduces? Another test might be to use:



glBegin (GL_LINE_STRIP);
glArrayElement (0);
glArrayElement (1);
glArrayElement (2);
glArrayElement (3);
glArrayElement (0);
glEnd ();

That's functionally equivalent tothe glDrawElements call but - just using it as a test - may help to shed some light on what's happening here.

glGenBuffers I use is correct, not really sure how anyone can screw that up. ;)

 

However, using your little example with glArrayElement  *does* work.

 

So, I guess I am chasing a driver issue of some kind... though, I need to get back to my main machine to test, instead of this crappy laptop that has intel HD3000 in it.

0

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  
Followers 0