• 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
Ender1618

glBufferData failing

4 posts in this topic

Im using OGL 4.0 core profile on Win7, with about 2gb of video card memory.

So my software is receiving an arbitrary amount of points over time that need to be visualized. The thing is i do not know in advance how many points there will be. My solution is to allocate empty VBOs of a fixed size, and copy the incoming points into the current VBO with calls to glBufferData. When a VBO fills up I allocate a new VBO and start filling it, and so on.

The problem I am having is when allocating an empty VBO, with a call like this:
[CODE]
glGenBuffers(1, &(entry.handle));
glBindBuffer(GL_ARRAY_BUFFER, entry.handle);
glBufferData(GL_ARRAY_BUFFER, entry.size, NULL, usage);
GLenum err = glCheckError();
if(err != GL_NO_ERROR)
return false;
[/CODE]

I am using interleaved arrays with a vertex of size 28 bytes, I tried letting my max VBO size to be 50k vertices, which is 1.4 mb each. After about the 5th VBO allocated like this, glBufferData fails with an invalid parameter message (from glGetError). The odd thing is if I allow the VBO max size to be 500k vertices, everything is fine, glBufferData never fails and everything renders fine.

Has anyone ever come across anything like this?

I would have thought glBufferData would have failed with a out of memory message if anything.
0

Share this post


Link to post
Share on other sites
Ugh the problem was that the error was happening before all that code, it was just being picked up when i called glGetError later.

So now my question becomes how does one use glGetError effectively? Do I actually need to call it after every gl call (that seems excessive), do I set it up to only get called in a debug build after every gl call? Is there a way to monitor any error that might be happening through piping them to the debug window (this is what DX does).
0

Share this post


Link to post
Share on other sites
You shouldn't have to call it at all unless you're trying to find an actual error in parameters or usage. Once the code base is working, you should not have to check for errors due to user input. The amount of code you need to check for actual errors in should be fairly limited, or you have speard your code out in too many places.

I believe the common OpenGL debuggers can monitor error states. However, I have never used them. The OpenGL code I use is typically very limited (only a very few selected places are actually responsible for communicating with OpenGL) and simply manually placing glGetError's in strategic places and narrowing it down in a binary search manner is quite fast.
0

Share this post


Link to post
Share on other sites
I wrap all my GL calls with a macro that, if debugging is wanted, adds a call to a function that prints a GL error.
It's not automated, but it's as close to it without going and making bindings that do it.
I would have liked having a debug version of GLEW.

On another note - do not use glBufferData to edit buffers, use glBufferSubData.
The former forces the driver to reallocate the whole buffer.
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