GL_NV_vertex_array_range seems not supported
as said by glIsEnabled().
glIsEnables is used to determine whether sometine is enabled or not. Not if something is supported. For supported features, check the extension string.
i still haven’t got the drivers for agp.
But you said it isn’t important for getting that working. So, it seems not the problem.
And the allocation always fail. I tried everything but no succeed.
then, glGetString( GL_EXTENSIONS); returns a null string. However, glxinfo returns that all what’s needed is supported. what a strange thing in fact !!
I couldn’t get where is the problem.
glXAllocateMemoryNV is not null, as glXFreeMemoryNV and glVertexArrayRangeNV, but all have got the same adress (as 0x80700400 but unsure).
what an interressant thing !!!
but i don’t remember if it’s before or later.
i think it’s before glutMainLoop() and after glutCreateWindow()
and what about the difference btw glGetString() and glxinfo ?
i will try to erase all opengl and rebuilt it in a new clear way; but i’m fearly sure it’s not the source of my problem.
You said you were using glut? Why do you mention glX function then? I would advice reading either some book or at least the article on how to use extension available here at opengl.org. You’re mixing several things which shouldn’t be mixed up.
He’s using the VAR extension which needs to call some OS specific function like glXAllocateMemoryNV on XWindows or wglAllocateMemoryNV on MSWindows respectively.
It’s perfectly valid for AllocateMemoryNV to return NULL. It will do this if it can’t allocate the specific type of memory that you want. For example, if your Linux kernel or BIOS doesn’t give the driver any AGP memory, it may return NULL. If your graphics card is a PCI card, it will certainly return NULL.
Proper code to use AllocateMemoryNV and VertexArrayRangeNV looks something like:
Originally posted by kon: He’s using the VAR extension which needs to call some OS specific function like glXAllocateMemoryNV on XWindows or wglAllocateMemoryNV on MSWindows respectively.
kon
Sure, but asking about the difference between glGetString and glXInfo (or whatever it is supposed to be)? And checking extensions with glIsEnabled? This article is very good for getting things straight. Although its win32 focused, under linux its sufficient to replace wgl with glX in most cases.
Regards,
-Lev
[This message has been edited by Lev (edited 01-23-2002).]
Lev, i’ve never used glGetString before. No utilities for me. any problem with that ?
And if your source code that you are using and shown me were clear enough, i may haven’t try glIsEnabled().
I use glut because for me it’s more easier to do win32 and linux program that works on both. More, glut uses glx under linux. So, glx must be supported by glut as Kon said.
Do you know anything ? maybe, but you’re lucky, then. don’t take it bad, i don’t like that, almost i found you helpful.
Now, my problem remains the same, and it seems now only a linux problem.
Originally posted by jide:
[b]Lev, i’ve never pretended to be a star, or a god or something like that (nor you i know).
But, i though this forum is here to be helpful for everyone here. I think it already is now.
sorry if knowledge lacks are prejudicies.
JD[/b]
So where’s the problem? I just suggested you to read the article about extension and explained Kon why I suggested this. Maybe I wasn’t very polite saying that you mix up some things - sorry for that. But if you’re checking if extension is supported with glIsEnabled then its wrong - this is not a prejudice - its a fact. Everybody makes mistakes, me too, and its nothing bad in making mistakes (well, as long as nobody gets hurt) - I just tried to help you.
It wasn’t my intention to offend you, I’m sorry if I’ve done so.
Regards,
-Lev
[This message has been edited by Lev (edited 01-24-2002).]