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

glGenBuffers throwing an access violation

7 posts in this topic

Greetings, so i'm trying to use vertex buffer objects, however, glGenBuffers is throwing me an access violation

 

Checklist time:

i have glew installed.

i have freeglut installed

included in this order

 

#include <GL/glew.h>
#include <GL/wglew.h>
#include <GL/freeglut.h>
i have a linkers to the appropriate libraries, (glew32, freeglut) unless i missed something
i have run glewinit (both before and after glutinit on seperate attempts)
genbuffers is run as follows
...
GLuint VBO = 0;
void init(){    
    float temp[]={10,10,20,10,10,20};
    glGenBuffers(1,&VBO);
...
according to the utilities included in glew, my open gl version is
version string: 4.2.11931
 
 
any help?
 
i can provide more code if needed
Edited by Ussyless
0

Share this post


Link to post
Share on other sites
Have you called glewInit() once before calling glGenBuffers in your program and did it return GLEW_OK? If you did, how does the driver identify itself (name/version/possibly the extension string)?
0

Share this post


Link to post
Share on other sites
Have you called glewInit and verified its return value? Just calling glewInit won't be enough, there are plenty of things that can go wrong (most often calling it before an OpenGL context exists or when no context is current).
0

Share this post


Link to post
Share on other sites

i have tried calling it both before and after the context exists, though currently it's being called before, wasn't sure when it needed to be initialised since it's included before and DevIL is initialised before also

 

anyway, currently if i run 

 

    GLenum errr= glewInit();    
    GLenum x;
    x=GLEW_OK;
    glutInit(&argc,argv);
glewinit returns a 1, and GLEW_OK returns a 0 so i assume they are different enums
 
ah there we go, after moving it to after the context, it works fine, both enums return 0, so it's GLEW_OK, and glgenbuffers no longer send a access violation
 
i feel stupid now, i swear i did try this, but thanks for asking the right questions
 
 
perhaps a small side-question ( perhaps not ), are there any standard libraries/functions i can use to pop up a window in case of for example, a error or a specific scenario easily? (ideally something along the lines of windows::showSplashScreen() or showSplashScreen("An error!") or something like that, doesnt even need text or anything, just some external indicator that something has happened without breakpoints.)
 
edit: messagebox :P
 
thanks
Edited by Ussyless
0

Share this post


Link to post
Share on other sites

perhaps a small side-question ( perhaps not ), are there any standard libraries/functions i can use to pop up a window in case of for example, a error or a specific scenario easily? (ideally something along the lines of windows::showSplashScreen() or showSplashScreen("An error!") or something like that, doesnt even need text or anything, just some external indicator that something has happened without breakpoints.)

For any non-trivial program I would suggest having a decent logging mechanism in place (at least writing stuff to the console, better to both the console and a file). With a simple macro all logging overhead can be completely removed by #undefing a single define (like _DEBUG which is already prepared for you with MSVC default configurations).
Apart from that asserts are also extremely useful because they will reliably trigger an attached debugger in debug builds but will be completely compiled out in release builds.

That said, for something as fundamental as basic initialization, I would not hesitate to use exceptions. Wrap everything in main() inside a suitable try/catch block, place a constant breakpoint into the catch part and rigorously check all initialization steps, throwing a suitably descriptive std::runtime_error when anything fails in an unrecoverable way. Obviously a published program needs to do something smarter, but "std::cout << exc.what() << std::endl" will do during development.
0

Share this post


Link to post
Share on other sites

glewInit uses the render context that is current. So until you have OpenGL initialize and have wglMakeCurrent set up with a render context glewInit will fail

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