Horde3D

Next-Generation Graphics Engine
It is currently 01.11.2024, 00:55

All times are UTC + 1 hour




Post new topic Reply to topic  [ 6 posts ] 
Author Message
 Post subject: utOpenGL.h
PostPosted: 15.02.2009, 07:51 
Offline

Joined: 19.11.2007, 19:35
Posts: 218
I'm curious how the function bindings were determined in utOpenGL.

I'm getting ready to transfer in geometry shaders from my sandboxes and require adding ProgramParameteriEXT(). I'll also end up needing to add others to deal with transform feedback, texture arrays, and draw instanced. Adding the variables is obvious since the extension documentation gives the hex addresses.

Also, is there a better way to handle the checking than adding a "SM4_Capable" var to the Modules::config() and setting it based on extension queries then looking it up for SM4/newer regions?


Top
 Profile  
Reply with quote  
 Post subject: Re: utOpenGL.h
PostPosted: 15.02.2009, 09:08 
Offline
Tool Developer

Joined: 13.11.2007, 11:07
Posts: 1150
Location: Germany
Good question. That's something we have to discuss regarding a port to OpenGL ES and DX anyway.


Top
 Profile  
Reply with quote  
 Post subject: Re: utOpenGL.h
PostPosted: 15.02.2009, 13:17 
Offline
Engine Developer

Joined: 10.09.2006, 15:52
Posts: 1217
There are official spec files that list all function declarations and tokens. You can assemble your C-header from those and the public documentation.
http://www.opengl.org/registry/#specfiles

AcidFaucet wrote:
Also, is there a better way to handle the checking than adding a "SM4_Capable" var to the Modules::config() and setting it based on extension queries then looking it up for SM4/newer regions?

Unfortunately OpenGL does not have a good mechanism for querying hardware capabilities so a lot of tricking will be necessary. It would be nice to have a more abstracted internal hardware capability class that can be accessed from the renderer. This is something that we plan to address some time after Beta3.


Top
 Profile  
Reply with quote  
 Post subject: Re: utOpenGL.h
PostPosted: 16.02.2009, 02:47 
Offline

Joined: 19.11.2007, 19:35
Posts: 218
Thanks! Kind of figured that was how it was being done, but wanted to be certain, it's a pain digging through the extension documents.

On the capabilities issue, a caps class had crossed my mind. On a side note, does anyone have a recent ATI card that could do an supported recent extensions check for me?


Top
 Profile  
Reply with quote  
 Post subject: Re: utOpenGL.h
PostPosted: 16.02.2009, 04:16 
Offline

Joined: 22.11.2007, 17:05
Posts: 707
Location: Boston, MA
AcidFaucet wrote:
Thanks! Kind of figured that was how it was being done, but wanted to be certain, it's a pain digging through the extension documents.
I suggested replacing utOpenGL with GLee a while ago, but if there is some reason not to, you could still use the XML files GLee is generated from, and write a custom generator.

Quote:
On the capabilities issue, a caps class had crossed my mind. On a side note, does anyone have a recent ATI card that could do an supported recent extensions check for me?
I have a Radeon 4870 HD, running catalyst 9.1 (I believe it is the latest).

_________________
Tristam MacDonald - [swiftcoding]


Top
 Profile  
Reply with quote  
 Post subject: Re: utOpenGL.h
PostPosted: 16.02.2009, 04:34 
Offline

Joined: 19.11.2007, 19:35
Posts: 218
That would certainly simplify things quite a bit. I'll have to take a look at it.


Top
 Profile  
Reply with quote  
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 6 posts ] 

All times are UTC + 1 hour


Who is online

Users browsing this forum: No registered users and 15 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group