Sign in to follow this  
Mercenarey

OpenGL Shader API - which should I choose? HLSL, Cg or GLSL?

Recommended Posts

Mercenarey    103
As I understand it from reading some, HLSL is DX-specific, GLSL is OpenGL, while NVidia's Cg is above both HLSL and GLSL, making use of them both, making Cg kindof technology independent - and platformindependent too since it can use GLSL. Cg looks very tempting, since it bridges the gap between DX and OpenGL - on the other hand, is it here to stay? I kindof fear that it could go down the road of 3DFX, that suddenly goes out of business, and all programs using 3DFX's API are suddenly no longer possible to use in the future. And then again, Cg is said to be as good as identical with HLSL, so maybe there is no need for the concern? What are your thoughts on this matter? [Edited by - Mercenarey on July 19, 2005 8:44:19 PM]

Share this post


Link to post
Share on other sites
_the_phantom_    11250
Quote:
Original post by Mercenarey
...and platformindependent too since it can use GLSL.


But does it? I know it can target NV's assembler interface and the ARB assembler interface, have they added support for GLSL targets as well?
heh, if they have then a game on an NV driver could end up going Cg=>GLSL=>Cg [grin]

Share this post


Link to post
Share on other sites
ajas95    767
IIRC, Sony announced at GDC 05 they're using Cg for PS3... (duh, they're using an nvidia chip...) So PS3 success portends Cg's (i.e. I wouldn't worry :)

But as Mr Teh_Phantom suggests, whenever you go 1-layer-up, you rely more on someone supporting the ground under your feet...

(My opinion: Cg, one good language among several, here to stay).

Share this post


Link to post
Share on other sites
python_regious    929
Personally, I'd say go with GLSL - as when ATi bring out a SM3 based card, they're not going to update the asm interfaces. Therefore, with Cg, you won't be able to get anything more than SM2 on non-vidia cards.

EDIT: or HLSL for that matter, I thought I was in the OpenGL forum for a minute there.

Share this post


Link to post
Share on other sites
Mercenarey    103
Thanx for the answers. I think I will go with Ajas95.

If Cg is here to stay (and it certainly sounds like it will, if Sony is gonna use it), it is alot better than using GLSL or HLSL. I want to make it easy to port my program to other platforms, so I don't want to tie myself to HLSL. And I can't tie myself to GLSL atm, since my graphics layer uses DX at the moment :)

If Cg is an umbrella over all the shader technologies, I think that is the right way to go. Especially if it is here to stay.

Share this post


Link to post
Share on other sites
Toji    535
Quote:
Original post by LarsMiddendorf
NVidia could create a GLSL backend for ATI SM3.0 cards.


Why exactly would they do that? GLSL isn't tied to one vendor or the other, it's a part of OpenGL. It's up to ATI to build a working GLSL implementation for a SM 3.0 card. At that point, if you "compile" a CG program to GLSL it should work on any card.

Share this post


Link to post
Share on other sites
BlackBox    150
I recommend you use:
GLSL -> if you are programming in OpenGL
HLSL -> if you are programming in DirectX
CG -> if you are poor and cant buy a book because the docomentation is great.

I would not worry too much about this, from personal experience, learning the concepts is more important than the language itself. Once you learnt the concepts, changing from one language to another is extreamly easy and intuitive.

Good luck.

Share this post


Link to post
Share on other sites
stroma    218
i agree with blackbox, do not worry about the language so much, all of them same in lots of ways. some syntax differences at all.
after learnt the shaders' concept, it is not a big deal to change the language.
but personally, i do not recommend CG because of portability. (but yes, its documentetion is quite well)

Share this post


Link to post
Share on other sites
THACO    234
I alwyas thought CG = HLSL? they just change the name for directx? I can't remember where I heard that so im probably mistaken

-THACO

Share this post


Link to post
Share on other sites
python_regious    929
Quote:
Original post by stroma
Quote:
Original post by Mercenarey
why isn't it portable?
the easiest answer is: because belonts to nvidia.


It is perfectly portable across API's, OS's, and graphics cards. As I said earlier though, portability across the SM3 range of cards will probably suffer in the future as the asm interfaces won't be updated. Just because it's created and managed by nVidia is totally irrelevant.

Share this post


Link to post
Share on other sites
Twixn    188
Cg is more like HLSL for OpenGL...nVidia actually recommend HLSL over Cg for DX apps. For OpenGL apps its upto you, GLSL is just a new face to Cg on NV drivers.

But, i use Cg :D ... its more consistant atm, but i will change to GLSL/HLSL later, GLSL is just too inconsistant between graphics cards atm, probably in its major release (like 1.2 or something) i will convert back.

-Twixn-

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  

  • Similar Content

    • By Zaphyk
      I am developing my engine using the OpenGL 3.3 compatibility profile. It runs as expected on my NVIDIA card and on my Intel Card however when I tried it on an AMD setup it ran 3 times worse than on the other setups. Could this be a AMD driver thing or is this probably a problem with my OGL code? Could a different code standard create such bad performance?
    • By Kjell Andersson
      I'm trying to get some legacy OpenGL code to run with a shader pipeline,
      The legacy code uses glVertexPointer(), glColorPointer(), glNormalPointer() and glTexCoordPointer() to supply the vertex information.
      I know that it should be using setVertexAttribPointer() etc to clearly define the layout but that is not an option right now since the legacy code can't be modified to that extent.
      I've got a version 330 vertex shader to somewhat work:
      #version 330 uniform mat4 osg_ModelViewProjectionMatrix; uniform mat4 osg_ModelViewMatrix; layout(location = 0) in vec4 Vertex; layout(location = 2) in vec4 Normal; // Velocity layout(location = 3) in vec3 TexCoord; // TODO: is this the right layout location? out VertexData { vec4 color; vec3 velocity; float size; } VertexOut; void main(void) { vec4 p0 = Vertex; vec4 p1 = Vertex + vec4(Normal.x, Normal.y, Normal.z, 0.0f); vec3 velocity = (osg_ModelViewProjectionMatrix * p1 - osg_ModelViewProjectionMatrix * p0).xyz; VertexOut.velocity = velocity; VertexOut.size = TexCoord.y; gl_Position = osg_ModelViewMatrix * Vertex; } What works is the Vertex and Normal information that the legacy C++ OpenGL code seem to provide in layout location 0 and 2. This is fine.
      What I'm not getting to work is the TexCoord information that is supplied by a glTexCoordPointer() call in C++.
      Question:
      What layout location is the old standard pipeline using for glTexCoordPointer()? Or is this undefined?
       
      Side note: I'm trying to get an OpenSceneGraph 3.4.0 particle system to use custom vertex, geometry and fragment shaders for rendering the particles.
    • By markshaw001
      Hi i am new to this forum  i wanted to ask for help from all of you i want to generate real time terrain using a 32 bit heightmap i am good at c++ and have started learning Opengl as i am very interested in making landscapes in opengl i have looked around the internet for help about this topic but i am not getting the hang of the concepts and what they are doing can some here suggests me some good resources for making terrain engine please for example like tutorials,books etc so that i can understand the whole concept of terrain generation.
       
    • By KarimIO
      Hey guys. I'm trying to get my application to work on my Nvidia GTX 970 desktop. It currently works on my Intel HD 3000 laptop, but on the desktop, every bind textures specifically from framebuffers, I get half a second of lag. This is done 4 times as I have three RGBA textures and one depth 32F buffer. I tried to use debugging software for the first time - RenderDoc only shows SwapBuffers() and no OGL calls, while Nvidia Nsight crashes upon execution, so neither are helpful. Without binding it runs regularly. This does not happen with non-framebuffer binds.
      GLFramebuffer::GLFramebuffer(FramebufferCreateInfo createInfo) { glGenFramebuffers(1, &fbo); glBindFramebuffer(GL_FRAMEBUFFER, fbo); textures = new GLuint[createInfo.numColorTargets]; glGenTextures(createInfo.numColorTargets, textures); GLenum *DrawBuffers = new GLenum[createInfo.numColorTargets]; for (uint32_t i = 0; i < createInfo.numColorTargets; i++) { glBindTexture(GL_TEXTURE_2D, textures[i]); GLint internalFormat; GLenum format; TranslateFormats(createInfo.colorFormats[i], format, internalFormat); // returns GL_RGBA and GL_RGBA glTexImage2D(GL_TEXTURE_2D, 0, internalFormat, createInfo.width, createInfo.height, 0, format, GL_FLOAT, 0); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_NEAREST); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_NEAREST); DrawBuffers[i] = GL_COLOR_ATTACHMENT0 + i; glBindTexture(GL_TEXTURE_2D, 0); glFramebufferTexture(GL_FRAMEBUFFER, GL_COLOR_ATTACHMENT0 + i, textures[i], 0); } if (createInfo.depthFormat != FORMAT_DEPTH_NONE) { GLenum depthFormat; switch (createInfo.depthFormat) { case FORMAT_DEPTH_16: depthFormat = GL_DEPTH_COMPONENT16; break; case FORMAT_DEPTH_24: depthFormat = GL_DEPTH_COMPONENT24; break; case FORMAT_DEPTH_32: depthFormat = GL_DEPTH_COMPONENT32; break; case FORMAT_DEPTH_24_STENCIL_8: depthFormat = GL_DEPTH24_STENCIL8; break; case FORMAT_DEPTH_32_STENCIL_8: depthFormat = GL_DEPTH32F_STENCIL8; break; } glGenTextures(1, &depthrenderbuffer); glBindTexture(GL_TEXTURE_2D, depthrenderbuffer); glTexImage2D(GL_TEXTURE_2D, 0, depthFormat, createInfo.width, createInfo.height, 0, GL_DEPTH_COMPONENT, GL_FLOAT, 0); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_NEAREST); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_NEAREST); glBindTexture(GL_TEXTURE_2D, 0); glFramebufferTexture(GL_FRAMEBUFFER, GL_DEPTH_ATTACHMENT, depthrenderbuffer, 0); } if (createInfo.numColorTargets > 0) glDrawBuffers(createInfo.numColorTargets, DrawBuffers); else glDrawBuffer(GL_NONE); if (glCheckFramebufferStatus(GL_FRAMEBUFFER) != GL_FRAMEBUFFER_COMPLETE) std::cout << "Framebuffer Incomplete\n"; glBindFramebuffer(GL_FRAMEBUFFER, 0); width = createInfo.width; height = createInfo.height; } // ... // FBO Creation FramebufferCreateInfo gbufferCI; gbufferCI.colorFormats = gbufferCFs.data(); gbufferCI.depthFormat = FORMAT_DEPTH_32; gbufferCI.numColorTargets = gbufferCFs.size(); gbufferCI.width = engine.settings.resolutionX; gbufferCI.height = engine.settings.resolutionY; gbufferCI.renderPass = nullptr; gbuffer = graphicsWrapper->CreateFramebuffer(gbufferCI); // Bind glBindFramebuffer(GL_DRAW_FRAMEBUFFER, fbo); // Draw here... // Bind to textures glActiveTexture(GL_TEXTURE0); glBindTexture(GL_TEXTURE_2D, textures[0]); glActiveTexture(GL_TEXTURE1); glBindTexture(GL_TEXTURE_2D, textures[1]); glActiveTexture(GL_TEXTURE2); glBindTexture(GL_TEXTURE_2D, textures[2]); glActiveTexture(GL_TEXTURE3); glBindTexture(GL_TEXTURE_2D, depthrenderbuffer); Here is an extract of my code. I can't think of anything else to include. I've really been butting my head into a wall trying to think of a reason but I can think of none and all my research yields nothing. Thanks in advance!
    • By Adrianensis
      Hi everyone, I've shared my 2D Game Engine source code. It's the result of 4 years working on it (and I still continue improving features ) and I want to share with the community. You can see some videos on youtube and some demo gifs on my twitter account.
      This Engine has been developed as End-of-Degree Project and it is coded in Javascript, WebGL and GLSL. The engine is written from scratch.
      This is not a professional engine but it's for learning purposes, so anyone can review the code an learn basis about graphics, physics or game engine architecture. Source code on this GitHub repository.
      I'm available for a good conversation about Game Engine / Graphics Programming
  • Popular Now