• 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
The Magical Pot

VBO and glIsBuffer

4 posts in this topic

Hi!

 

I'm working with VBOs and I suddenly sumbled across a very weird error. My compiler is giving me a run-time error saying that this statement can't be executed:

if ( glIsBuffer( VertexBuffer ) )

This statement can be found in this destructor:

VBOQuad::~VBOQuad()
{
	//Clear vertex buffer
	if ( glIsBuffer( VertexBuffer ) )
		glDeleteBuffers( 1, &VertexBuffer );

	//Clear index buffer
	if ( glIsBuffer( IndexBuffer ) )
		glDeleteBuffers( 1, &IndexBuffer );

	VertexBuffer = NULL;
	IndexBuffer = NULL;
}

I've tried to track this error down to find some sort of context, but I've found that the run-time error emerges before the first line of the main function is executed. The description of glIsBuffer says that the function will return true if the argument is the name of an existing buffer, and it will return false if the argument is zero or a non-zero value. The debugger says:

 

VertexBuffer CXX0030: Error: expression cannot be evaluated
IndexBuffer CXX0030: Error: expression cannot be evaluated
 
 
This would, to me, indicate that VertexBuffer doesn't exist in memory, which in turn would mean that VertexBuffer is basically NULL, which is defined as zero, so there souldn't be a problem. That's probably not right since it's crashing at that statement.
 
The main problem I'm having is that the application crashes before the main function is executed, so for all I know, the destructor hasn't even been called yet, but it's trying to execute it, by the looks of it. My question is what the problem usually is in a situation like this where the application crashes before the main function is executed.
 
Thanks!
 
EDIT: I have added a screen dump of the Stack Trace.
Edited by The Magical Pot
0

Share this post


Link to post
Share on other sites

Before the program enters the entry point of main() global variables (like 'quad' in the example) are allocated on the stack.

VBOQuad quad;
int main () { ... }

I can't say much to the error but have you checked the stack trace of you application when it crashed? This might give a clue what functions are called that lead to the destruction of this object.

Edited by Wh0p
2

Share this post


Link to post
Share on other sites

Sounds like there's no opengl context active when you try to call those opengl functions?

2

Share this post


Link to post
Share on other sites

So from the stack trace you have posted the error might found in the vector<Button>.

 

Looks like the class Button uses VBOQuad, so if there is somewhere a vector<Button> floating in your code the destructor of VBOQuad might be called while the vector is resized.

 

I don't know what State_1::State_1() is or does (static function???) but looks like that function is called and the error is caused from here by push_back which triggers the resize of the vector. I quess Sponji had the right hunch there. Also check that you are not double deleting any objects.

 

Good luck :)

0

Share this post


Link to post
Share on other sites

I managed to fix this at last. The call stack said that the error occurred after main was called and I realized that I used an incorrect method at first to check where the application crashed. When the application was to delete an object of type VBOQuad, I checked if the object existed in memory by comparing it to NULL, but I tried to print out the value of an uninitialized pointer of this type and I realized that such a pointer is not necessarily equal to NULL. In the end, an uninitialized pointer was seen as an initialized one, thus the application would try to delete an object that didn't exist in memory.

 

Thanks for your help! :)

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