• Advertisement
Sign in to follow this  

OpenGL ATI drivers?

This topic is 4486 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Firstly, I take it this is the right forum, since we don't have a graphics hardware forum. I have a Mac PowerBook, which the docs say has a ATI Radeon Mobility 9000, and the glGet(GL_VERSION_STRING) says I have a Radeon 9000 (not mobility), but the 'OpenGL Driver Monitor' app reports that the driver is a Radeon 8500 driver. Neither ATI nor Apple has any driver downloads for these cards on their sites, as far as I can tell. Additionaly, ATI never installed a 8500 mobility in a Mac, they went straight from 7500 to 9000, so I don't see why they have the driver for it. So I wonder if I am missing any functionality from the older driver, or whether the 9000 mobility is just a souped-up version of the desktop 8500? On another issue, my card supports ARB vertex shaders (even, it appears GLSL), but it only supports ATI_text_fragment_shaders. Is there any high-level fragment language that compiles down to ATI_text_fragment_shader (CG doesn't), as I really would prefer not learn fragment shader ASM, but pixel shaders would be nice. Thanks in advance, SwiftCoder

Share this post


Link to post
Share on other sites
Advertisement
Quote:
Original post by swiftcoder
Firstly, I take it this is the right forum, since we don't have a graphics hardware forum.
I have a Mac PowerBook, which the docs say has a ATI Radeon Mobility 9000, and the glGet(GL_VERSION_STRING) says I have a Radeon 9000 (not mobility), but the 'OpenGL Driver Monitor' app reports that the driver is a Radeon 8500 driver. Neither ATI nor Apple has any driver downloads for these cards on their sites, as far as I can tell.
Additionaly, ATI never installed a 8500 mobility in a Mac, they went straight from 7500 to 9000, so I don't see why they have the driver for it.
So I wonder if I am missing any functionality from the older driver, or whether the 9000 mobility is just a souped-up version of the desktop 8500?

On another issue, my card supports ARB vertex shaders (even, it appears GLSL), but it only supports ATI_text_fragment_shaders. Is there any high-level fragment language that compiles down to ATI_text_fragment_shader (CG doesn't), as I really would prefer not learn fragment shader ASM, but pixel shaders would be nice.

Thanks in advance,

SwiftCoder



If I remember right apple is using the 8500 driver for the 9000, and don't quote me but a 9000 is a pumped up 8500. So to answer your questions I think you can DL drivers for your mac from ATI for that laptop, but if not just make sure you have the latest OS revision from Apple they have the newest drivers for you GPU then. TO answer your shader question NO I am sorry you will have to use the ati_text_fragment shader. You don't have access to the arb_fragment shader extension. Another bad thing is you will lock your code to ATI only if you code for the ati_text_fragment_shader... Just something to think about. You need a 9600 chip or newer to do what you want to do on mac, or a fx series or newer chip. HTH...

Share this post


Link to post
Share on other sites
The radeon 9000 and the 9200 are just different versions of the 8500.
You can use ARB_vertex_program but your card doesn't support EXT or ARB fragment programming.
If you want to use fragment programming you'll have to use ATI's implementation.
It doesn't support opengl's GLSL or DX's HLSL.

Share this post


Link to post
Share on other sites
I think there is a fix available for the PC version of the standard ATI catalyst driver, which allows it to work on an 9000 Mobility. It fixed my Doom 3 normal mapping problems, and didn't cause any bad effects. There may be something similar for the Apple. I would imagine this would at least give you software implementations of shaders.

Share this post


Link to post
Share on other sites
All graphics drivers on Mac OS X are distributed in OS X updates. There are some ROM updates available from ATI's website for retail cards, but that doens't apply to you. Any other third party downloads for a particular card merely install something like a control panel (NVidia doesn't have any of this on OS X). However,

If you have OS X 10.4.3, then you have the latest graphics drivers for your card.

The Radeon 8500/9000/9200 (and their mobility variants) are all R200 class cards, and are all driven by ATIRadeon8500GLDriver. ATIRadeon9700GLDriver drives 9550 through X850XT GPUs.

Fragment programability is only accessable through ATI_text_fragment_shader on R200-class hardware. With 10.4.3, vertex shaders can be written in ARB_vertex_program or GLSL.

Share this post


Link to post
Share on other sites
Many thanks, this is what I feared.
Luckily Apple's software renderer supports ARB_fragment_shaders (therefore CG) and GLSL, so I will prototype my fragment shader code on the software renderer, and hopefully one of these days I will get a new computer ;)

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
  • Advertisement
  • Popular Tags

  • Advertisement
  • Popular Now

  • Similar Content

    • By LifeArtist
      Good Evening,
      I want to make a 2D game which involves displaying some debug information. Especially for collision, enemy sights and so on ...
      First of I was thinking about all those shapes which I need will need for debugging purposes: circles, rectangles, lines, polygons.
      I am really stucked right now because of the fundamental question:
      Where do I store my vertices positions for each line (object)? Currently I am not using a model matrix because I am using orthographic projection and set the final position within the VBO. That means that if I add a new line I would have to expand the "points" array and re-upload (recall glBufferData) it every time. The other method would be to use a model matrix and a fixed vbo for a line but it would be also messy to exactly create a line from (0,0) to (100,20) calculating the rotation and scale to make it fit.
      If I proceed with option 1 "updating the array each frame" I was thinking of having 4 draw calls every frame for the lines vao, polygons vao and so on. 
      In addition to that I am planning to use some sort of ECS based architecture. So the other question would be:
      Should I treat those debug objects as entities/components?
      For me it would make sense to treat them as entities but that's creates a new issue with the previous array approach because it would have for example a transform and render component. A special render component for debug objects (no texture etc) ... For me the transform component is also just a matrix but how would I then define a line?
      Treating them as components would'nt be a good idea in my eyes because then I would always need an entity. Well entity is just an id !? So maybe its a component?
      Regards,
      LifeArtist
    • By QQemka
      Hello. I am coding a small thingy in my spare time. All i want to achieve is to load a heightmap (as the lowest possible walking terrain), some static meshes (elements of the environment) and a dynamic character (meaning i can move, collide with heightmap/static meshes and hold a varying item in a hand ). Got a bunch of questions, or rather problems i can't find solution to myself. Nearly all are deal with graphics/gpu, not the coding part. My c++ is on high enough level.
      Let's go:
      Heightmap - i obviously want it to be textured, size is hardcoded to 256x256 squares. I can't have one huge texture stretched over entire terrain cause every pixel would be enormous. Thats why i decided to use 2 specified textures. First will be a tileset consisting of 16 square tiles (u v range from 0 to 0.25 for first tile and so on) and second a 256x256 buffer with 0-15 value representing index of the tile from tileset for every heigtmap square. Problem is, how do i blend the edges nicely and make some computationally cheap changes so its not obvious there are only 16 tiles? Is it possible to generate such terrain with some existing program?
      Collisions - i want to use bounding sphere and aabb. But should i store them for a model or entity instance? Meaning i have 20 same trees spawned using the same tree model, but every entity got its own transformation (position, scale etc). Storing collision component per instance grats faster access + is precalculated and transformed (takes additional memory, but who cares?), so i stick with this, right? What should i do if object is dynamically rotated? The aabb is no longer aligned and calculating per vertex min/max everytime object rotates/scales is pretty expensive, right?
      Drawing aabb - problem similar to above (storing aabb data per instance or model). This time in my opinion per model is enough since every instance also does not have own vertex buffer but uses the shared one (so 20 trees share reference to one tree model). So rendering aabb is about taking the model's aabb, transforming with instance matrix and voila. What about aabb vertex buffer (this is more of a cosmetic question, just curious, bumped onto it in time of writing this). Is it better to make it as 8 points and index buffer (12 lines), or only 2 vertices with min/max x/y/z and having the shaders dynamically generate 6 other vertices and draw the box? Or maybe there should be just ONE 1x1x1 cube box template moved/scaled per entity?
      What if one model got a diffuse texture and a normal map, and other has only diffuse? Should i pass some bool flag to shader with that info, or just assume that my game supports only diffuse maps without fancy stuff?
      There were several more but i forgot/solved them at time of writing
      Thanks in advance
    • By RenanRR
      Hi All,
      I'm reading the tutorials from learnOpengl site (nice site) and I'm having a question on the camera (https://learnopengl.com/Getting-started/Camera).
      I always saw the camera being manipulated with the lookat, but in tutorial I saw the camera being changed through the MVP arrays, which do not seem to be camera, but rather the scene that changes:
      Vertex Shader:
      #version 330 core layout (location = 0) in vec3 aPos; layout (location = 1) in vec2 aTexCoord; out vec2 TexCoord; uniform mat4 model; uniform mat4 view; uniform mat4 projection; void main() { gl_Position = projection * view * model * vec4(aPos, 1.0f); TexCoord = vec2(aTexCoord.x, aTexCoord.y); } then, the matrix manipulated:
      ..... glm::mat4 projection = glm::perspective(glm::radians(fov), (float)SCR_WIDTH / (float)SCR_HEIGHT, 0.1f, 100.0f); ourShader.setMat4("projection", projection); .... glm::mat4 view = glm::lookAt(cameraPos, cameraPos + cameraFront, cameraUp); ourShader.setMat4("view", view); .... model = glm::rotate(model, glm::radians(angle), glm::vec3(1.0f, 0.3f, 0.5f)); ourShader.setMat4("model", model);  
      So, some doubts:
      - Why use it like that?
      - Is it okay to manipulate the camera that way?
      -in this way, are not the vertex's positions that changes instead of the camera?
      - I need to pass MVP to all shaders of object in my scenes ?
       
      What it seems, is that the camera stands still and the scenery that changes...
      it's right?
       
       
      Thank you
       
    • By dpadam450
      Sampling a floating point texture where the alpha channel holds 4-bytes of packed data into the float. I don't know how to cast the raw memory to treat it as an integer so I can perform bit-shifting operations.

      int rgbValue = int(textureSample.w);//4 bytes of data packed as color
      // algorithm might not be correct and endianness might need switching.
      vec3 extractedData = vec3(  rgbValue & 0xFF000000,  (rgbValue << 8) & 0xFF000000, (rgbValue << 16) & 0xFF000000);
      extractedData /= 255.0f;
    • By Devashish Khandelwal
      While writing a simple renderer using OpenGL, I faced an issue with the glGetUniformLocation function. For some reason, the location is coming to be -1.
      Anyone has any idea .. what should I do?
  • Advertisement