# OpenGL OpenGL's glDrawRangeElements not working on Windows/freeglut?

## Recommended Posts

Hello everyone, still pretty new feeling for opengl here. Using freeglut for Windows, I've been getting an error for code that was working in my Linux build. My makefile code includes the following for importing webgl stuff:

[CODE]
ifeq ($(shell uname), Linux) Graphics = -I/usr/X11R6/include -L/usr/X11R6/bin -lglut -lGL -lGLU else ifeq ($(shell uname), Darwin) # Darwin = Mac
Graphics = -framework OpenGL -framework GLUT
else
Graphics = -I ".\include" -L ".\lib" -lglut -lGLU -lGL -lfreeglut -lglu32 -lopengl32 -Wl,--subsystem,windows -static
endif
[/CODE]

where .\include and .\lib are just the folders from freeglut-MinGW-2.8.0-1.mp.zip, and my src folder has the freeglut dll inside. So, that said, this is the error I'm getting:

[CODE]
error: 'glDrawRangeElements' was not declared in this scope
[/CODE]

due to this call:

[CODE]glDrawRangeElements(GL_TRIANGLES, 0, 3, 6, GL_UNSIGNED_BYTE, indices+6*i);[/CODE]

So, Googling the error only gives [url="http://www.gamedev.net/topic/498052-gldrawrangeelements-was-not-declared-in-this-scope/"]one good Google result[/url], and it's a cryptic dead link reply along with, using glext.h, the following:

[CODE]
PFNGLDRAWRANGEELEMENTSPROC glDrawRangeElements = NULL;
[/CODE]

So I tried #include glext.h with the file in my src folder, and it tells me glDrawRangeElements doesn't have a type.

[CODE]error: 'glDrawRangeElements' does not name a type[/CODE]

Surprisingly, tweaking the above code makes the error go away by removing the middle step:
[CODE]
[/CODE]

But when it finally gets to the display of the game, if any instances of glDrawRangeElements are left, it just gives a blank white screen. Commenting out those instances of glDrawRangeElements makes everything except for that work, but trying to include them breaks everything.

Another, unrelated Google result brought this code up:

[CODE]
#ifdef _WIN32
// function pointer to OpenGL extensions
// glDrawRangeElements() defined in OpenGL v1.2 or greater
PFNGLDRAWRANGEELEMENTSPROC pglDrawRangeElements = 0;
#define glDrawRangeElements pglDrawRangeElements
#endif
[/CODE]

along with

[CODE]
#ifdef _WIN32
// get function pointer to glDrawRangeElements
#endif
[/CODE]

But I'm basically getting the same errors. If I assign anything to glDrawRangeElements, it says pglDrawRangeElements does not name a type. I have glext.h included too, so this comes off as especially strange. So, any thoughts? I'm on a Windows 7 64-bit OS using OpenGL, GLU, and freeglut as far as I can tell.

##### Share on other sites
Well, at the least, I found that this works with similar results:

[CODE]glDrawRangeElements(GL_TRIANGLES, 6, GL_UNSIGNED_BYTE, indices+6*i);[/CODE]

Might be a bit laggier, not sure yet, but definitely runs on Windows and Linux both. Anyways, just posting this in case someone comes across this same issue!

##### Share on other sites
Two things:

Windows's native OpenGL support is for an old version. To use the newer APIs you need to use wglGetProcAddress. Most people use an extension loading library for this and I notice that you are not linking with any. Details of extension loading libraries can be found [url="http://www.opengl.org/wiki/OpenGL_Loading_Library"]here[/url]. They work on other platforms as well so you don't have to write conditional code.

The other thing is you are linking with the -static flag which will prevent linking with dynamic libraries - this might also cause problems.

## Create an account

Register a new account

• ### Forum Statistics

• Total Topics
627764
• Total Posts
2978976
• ### Similar Content

• Hello! As an exercise for delving into modern OpenGL, I'm creating a simple .obj renderer. I want to support things like varying degrees of specularity, geometry opacity, things like that, on a per-material basis. Different materials can also have different textures. Basic .obj necessities. I've done this in old school OpenGL, but modern OpenGL has its own thing going on, and I'd like to conform as closely to the standards as possible so as to keep the program running correctly, and I'm hoping to avoid picking up bad habits this early on.
Reading around on the OpenGL Wiki, one tip in particular really stands out to me on this page:
For something like a renderer for .obj files, this sort of thing seems almost ideal, but according to the wiki, it's a bad idea. Interesting to note!
So, here's what the plan is so far as far as loading goes:
Set up a type for materials so that materials can be created and destroyed. They will contain things like diffuse color, diffuse texture, geometry opacity, and so on, for each material in the .mtl file. Since .obj files are conveniently split up by material, I can load different groups of vertices/normals/UVs and triangles into different blocks of data for different models. When it comes to the rendering, I get a bit lost. I can either:
Between drawing triangle groups, call glUseProgram to use a different shader for that particular geometry (so a unique shader just for the material that is shared by this triangle group). or
Between drawing triangle groups, call glUniform a few times to adjust different parameters within the "master shader", such as specularity, diffuse color, and geometry opacity. In both cases, I still have to call glBindTexture between drawing triangle groups in order to bind the diffuse texture used by the material, so there doesn't seem to be a way around having the CPU do *something* during the rendering process instead of letting the GPU do everything all at once.
The second option here seems less cluttered, however. There are less shaders to keep up with while one "master shader" handles it all. I don't have to duplicate any code or compile multiple shaders. Arguably, I could always have the shader program for each material be embedded in the material itself, and be auto-generated upon loading the material from the .mtl file. But this still leads to constantly calling glUseProgram, much more than is probably necessary in order to properly render the .obj. There seem to be a number of differing opinions on if it's okay to use hundreds of shaders or if it's best to just use tens of shaders.
So, ultimately, what is the "right" way to do this? Does using a "master shader" (or a few variants of one) bog down the system compared to using hundreds of shader programs each dedicated to their own corresponding materials? Keeping in mind that the "master shaders" would have to track these additional uniforms and potentially have numerous branches of ifs, it may be possible that the ifs will lead to additional and unnecessary processing. But would that more expensive than constantly calling glUseProgram to switch shaders, or storing the shaders to begin with?
With all these angles to consider, it's difficult to come to a conclusion. Both possible methods work, and both seem rather convenient for their own reasons, but which is the most performant? Please help this beginner/dummy understand. Thank you!

• I want to make professional java 3d game with server program and database,packet handling for multiplayer and client-server communicating,maps rendering,models,and stuffs Which aspect of java can I learn and where can I learn java Lwjgl OpenGL rendering Like minecraft and world of tanks

• A friend of mine and I are making a 2D game engine as a learning experience and to hopefully build upon the experience in the long run.

-What I'm using:
C++;. Since im learning this language while in college and its one of the popular language to make games with why not.     Visual Studios; Im using a windows so yea.     SDL or GLFW; was thinking about SDL since i do some research on it where it is catching my interest but i hear SDL is a huge package compared to GLFW, so i may do GLFW to start with as learning since i may get overwhelmed with SDL.
-Questions
Knowing what we want in the engine what should our main focus be in terms of learning. File managements, with headers, functions ect. How can i properly manage files with out confusing myself and my friend when sharing code. Alternative to Visual studios: My friend has a mac and cant properly use Vis studios, is there another alternative to it?

• Both functions are available since 3.0, and I'm currently using glMapBuffer(), which works fine.
But, I was wondering if anyone has experienced advantage in using glMapBufferRange(), which allows to specify the range of the mapped buffer. Could this be only a safety measure or does it improve performance?
Note: I'm not asking about glBufferSubData()/glBufferData. Those two are irrelevant in this case.
• By xhcao
Before using void glBindImageTexture(    GLuint unit, GLuint texture, GLint level, GLboolean layered, GLint layer, GLenum access, GLenum format), does need to make sure that texture is completeness.

• 11
• 10
• 10
• 23
• 14