Why doesn’t WGL_NV_allocate_memory show up in the extension string for GEForce 256 Detonator 3 drivers? It seems to able to be used regardless…

It’s not a “real” extension. I know I’ve seen that name before, but I’m actually not entirely sure where, because it’s not in the GL_NV_vertex_array_range spec, and it’s not in our driver!

  • Matt

It appears that as long as GL_NV_vertex_array_range and GL_NV_fence are supported, the wglAllocateMemoryNV command will work. Is this also true for WGL_EXT_extensions_string and WGL_EXT_pixel_format?

wglAllocateMemoryNV must be supported by any Windows driver that supports GL_NV_vertex_array_range. Likewise, glXAllocateMemoryNV must be supported by any X driver that supports it.

If wglGetProcAddress(“wglGetExtensionsStringARB”) returns NULL, then the WGL extension string extension is not supported. If it returns a non-NULL value, you call that function to get the WGL extension string, from which you can check whether any given WGL extension is supported.

  • Matt

Thanks for the help, Matt