This topic is now archived and is closed to further replies.


OpenGL Pixel shaders in OpenGL

Recommended Posts

I am using a GeForce4 Ti 64 MB card and it certainly has programmable pixel shader capability. But most of the programs/demos floating around the net uses "GL_ARB_fragment_program" extension to do pixel shading which my driver doesn''t have. I have tried updating my drivers from but still... "GL_ARB_fragment_program" seems to be missing though i have extensions like "GL_NV_register_combiners" "GL_NV_register_combiners2" and "GL_NV_texture_shader" which i suppose are NVIDIA''s own pixel shading extensions. If that''s the case then if i write a pixel shader now using the extensions that i have in my driver then it might not run on an ATI board for the same reason the downloaded demos aren''t running on my card only because i dont have an extension (GL_ARB_fragment_program ) whereas my hardware has the capability. NOW the question is... how STANDARD is OpenGL when it comes the the question of some widely used stuffs like "Vertex Shaders" and "Pixel Shaders" ?

Share this post

Link to post
Share on other sites
Original post by browny
If that''s the case then if i write a pixel shader now using the extensions that i have in my driver then it might not run on an ATI board for the same reason the downloaded demos aren''t running on my card only because i dont have an extension (GL_ARB_fragment_program ) whereas my hardware has the capability.

The answer is easy: your card has no support for programmable pixel shaders. ARB_fragment_program is only supported by fully programmable hardware, ie. DX9-type boards: GeForce FX, Radeon 9x00.

The GeForce4 does not support that extension, because it does not have the required hardware support. In fact, a GeForce4 is not programmable, but configurable. Means, it still has a fixed function pixel pipeline, but you can route the fragments around in a multitude of ways. This is done with vendor specific extensions aka. NV_register_combiner(1,2) or NV_texture_shader(1,2,3). Your code will obviously not work on ATI cards then.

Your options:

*) Write two codepaths, one for nVidia and one for ATI. This is certainly the best choice to target a wide range of 3D cards out there, but it''s more work.

*) Get a new 3D card, and use ARB_fragment_program. Your code will only work on DX9-level cards.

*) Don''t use pixelshaders at all, but use standarized combiners, eg. ARB_texture_combine. This will work on all cards, but is technically very limited.

*) Enable NV30 emulation on your GeForce4. This will give you the ARB_fragment_program extension, but it will be 100% software emulated. It will be extremely slow. But you can at least develop for DX9 type cards without needing one.

*) Use Cg. Cg can compile into all kinds of vendor-specific or vendor-independent extensions.

Share this post

Link to post
Share on other sites
Cg is good here.

very good.

One disadvantage in Cg is that it doesn''t compile to Ati extensions (which should be obvious why)... But also, it doesn''t compile to Direct3D pixel shader 1.4... Which is a lot more useful now days than nvidia will probably admit... This makes a radeon 8500/9000/9100/9200 pretty useless in GL and no better than a Ti in D3D.. When in both it is really a lot more powerful.

Although, I havn''t looked into it, I think there might be other Cg compilers, which may solve this problem (there is a dud link on the nvidia dev site called ''open source compiler'', which gives hope)

there is also ''CGFx'' - effectivly the direct3d fx file format, but for GL and D3D, which lets you do nice material and old-school combiner stuff. Tis very good this. I wish I knew about it before I wrote my own combinery shadery materialy codey stuff in the past.

I''ve had a few issues with Cg for some small things not working right but overall it''s really nice.

It''s a lot nicer than writing (and especially converting) asm / combiners... especially if you want a bit of artistic freedom.

| - Project-X - On hold.. - | - adDeath - | - email me - |

Share this post

Link to post
Share on other sites
D3D8 has the same problems as well. While Ati can process ps < 1.4, they''re emulated thru 1.4 and thus loose some speed from what I understand. I were you I would just buy dx9 card ie. one that can do gl arb fragment/vertex programs. Rumors have it that ati''s r300 core and up can do gl2 but it has to be written into drivers first. I also understand that ati has very fast shader path compared to nv gffx. Is it still 50% behind of ati?

Share this post

Link to post
Share on other sites
Original post by silvermace
Yann, do you use Cg?
im trying to get started with it but i still havnt got round to it

Yes, I do, especially for prototyping new shaders. It''s very convenient and easy to use. Although I generally rewrite the shader in ASM once it is done (performance), it''s so much simpler to have a high-level language, when you experiment around.

I will probably switch to GLSL though, once good drivers are generally available.

Share this post

Link to post
Share on other sites

  • Announcements

  • Forum Statistics

    • Total Topics
    • Total Posts
  • Similar Content

    • By test opty
      Hi all,
      I'm starting OpenGL using a tut on the Web. But at this point I would like to know the primitives needed for creating a window using OpenGL. So on Windows and using MS VS 2017, what is the simplest code required to render a window with the title of "First Rectangle", please?
    • By DejayHextrix
      Hi, New here. 
      I need some help. My fiance and I like to play this mobile game online that goes by real time. Her and I are always working but when we have free time we like to play this game. We don't always got time throughout the day to Queue Buildings, troops, Upgrades....etc.... 
      I was told to look into DLL Injection and OpenGL/DirectX Hooking. Is this true? Is this what I need to learn? 
      How do I read the Android files, or modify the files, or get the in-game tags/variables for the game I want? 
      Any assistance on this would be most appreciated. I been everywhere and seems no one knows or is to lazy to help me out. It would be nice to have assistance for once. I don't know what I need to learn. 
      So links of topics I need to learn within the comment section would be SOOOOO.....Helpful. Anything to just get me started. 
      Dejay Hextrix 
    • By mellinoe
      Hi all,
      First time poster here, although I've been reading posts here for quite a while. This place has been invaluable for learning graphics programming -- thanks for a great resource!
      Right now, I'm working on a graphics abstraction layer for .NET which supports D3D11, Vulkan, and OpenGL at the moment. I have implemented most of my planned features already, and things are working well. Some remaining features that I am planning are Compute Shaders, and some flavor of read-write shader resources. At the moment, my shaders can just get simple read-only access to a uniform (or constant) buffer, a texture, or a sampler. Unfortunately, I'm having a tough time grasping the distinctions between all of the different kinds of read-write resources that are available. In D3D alone, there seem to be 5 or 6 different kinds of resources with similar but different characteristics. On top of that, I get the impression that some of them are more or less "obsoleted" by the newer kinds, and don't have much of a place in modern code. There seem to be a few pivots:
      The data source/destination (buffer or texture) Read-write or read-only Structured or unstructured (?) Ordered vs unordered (?) These are just my observations based on a lot of MSDN and OpenGL doc reading. For my library, I'm not interested in exposing every possibility to the user -- just trying to find a good "middle-ground" that can be represented cleanly across API's which is good enough for common scenarios.
      Can anyone give a sort of "overview" of the different options, and perhaps compare/contrast the concepts between Direct3D, OpenGL, and Vulkan? I'd also be very interested in hearing how other folks have abstracted these concepts in their libraries.
    • By aejt
      I recently started getting into graphics programming (2nd try, first try was many years ago) and I'm working on a 3d rendering engine which I hope to be able to make a 3D game with sooner or later. I have plenty of C++ experience, but not a lot when it comes to graphics, and while it's definitely going much better this time, I'm having trouble figuring out how assets are usually handled by engines.
      I'm not having trouble with handling the GPU resources, but more so with how the resources should be defined and used in the system (materials, models, etc).
      This is my plan now, I've implemented most of it except for the XML parts and factories and those are the ones I'm not sure of at all:
      I have these classes:
      For GPU resources:
      Geometry: holds and manages everything needed to render a geometry: VAO, VBO, EBO. Texture: holds and manages a texture which is loaded into the GPU. Shader: holds and manages a shader which is loaded into the GPU. For assets relying on GPU resources:
      Material: holds a shader resource, multiple texture resources, as well as uniform settings. Mesh: holds a geometry and a material. Model: holds multiple meshes, possibly in a tree structure to more easily support skinning later on? For handling GPU resources:
      ResourceCache<T>: T can be any resource loaded into the GPU. It owns these resources and only hands out handles to them on request (currently string identifiers are used when requesting handles, but all resources are stored in a vector and each handle only contains resource's index in that vector) Resource<T>: The handles given out from ResourceCache. The handles are reference counted and to get the underlying resource you simply deference like with pointers (*handle).  
      And my plan is to define everything into these XML documents to abstract away files:
      Resources.xml for ref-counted GPU resources (geometry, shaders, textures) Resources are assigned names/ids and resource files, and possibly some attributes (what vertex attributes does this geometry have? what vertex attributes does this shader expect? what uniforms does this shader use? and so on) Are reference counted using ResourceCache<T> Assets.xml for assets using the GPU resources (materials, meshes, models) Assets are not reference counted, but they hold handles to ref-counted resources. References the resources defined in Resources.xml by names/ids. The XMLs are loaded into some structure in memory which is then used for loading the resources/assets using factory classes:
      Factory classes for resources:
      For example, a texture factory could contain the texture definitions from the XML containing data about textures in the game, as well as a cache containing all loaded textures. This means it has mappings from each name/id to a file and when asked to load a texture with a name/id, it can look up its path and use a "BinaryLoader" to either load the file and create the resource directly, or asynchronously load the file's data into a queue which then can be read from later to create the resources synchronously in the GL context. These factories only return handles.
      Factory classes for assets:
      Much like for resources, these classes contain the definitions for the assets they can load. For example, with the definition the MaterialFactory will know which shader, textures and possibly uniform a certain material has, and with the help of TextureFactory and ShaderFactory, it can retrieve handles to the resources it needs (Shader + Textures), setup itself from XML data (uniform values), and return a created instance of requested material. These factories return actual instances, not handles (but the instances contain handles).
      Is this a good or commonly used approach? Is this going to bite me in the ass later on? Are there other more preferable approaches? Is this outside of the scope of a 3d renderer and should be on the engine side? I'd love to receive and kind of advice or suggestions!
    • By nedondev
      I 'm learning how to create game by using opengl with c/c++ coding, so here is my fist game. In video description also have game contain in Dropbox. May be I will make it better in future.
  • Popular Now