Sign in to follow this  


Recommended Posts

Kimmen    122
Hi there, I am currently developing a 2d isometric game in c# (.net 2.0) and I am using the Tao framework. All pictures used in the game are rectangles and that is why I use GL_TEXTURE_RECTANGLE_EXT. I was just wondering if ATI has some problem with GL_TEXTURE_RECTANGLE_EXT? Because in school there's nothing wrong with the graphics and it also works correctly on a friends computer, in both cases NVidia is used. However on my own computer, with an ATI x700 graphic card, almost all graphics doesn't show up at all. Do you have some experience with GL_TEXTURE_RECTANGLE_EXT and knows what the problem could be? As a side note I can also say that on another friends computer no graphics generated by OpenGL is shown at all (the window becomes transparent and only the exit button shows (which is drawn with GDI+), any ideas there? He also use an NVidia graphic card. If you want I can post up some screenshots if you want to see the problem, both problems. thanks in advance, Kimmen

Share this post

Link to post
Share on other sites
bluntman    255
Are you checking for the existance of the extension before using it? Could be you should use just straight GL_TEXTURE_RECTANGLE or GL_TEXTURE_RECTANGLE_ARB.
You really should try and use power of 2 textures, even if you don't want a square area. Just adjust your UVs or stretch your image. You get better performance.

Share this post

Link to post
Share on other sites
Kalidor    1087
Original post by Kimmen
All pictures used in the game are rectangles and that is why I use GL_TEXTURE_RECTANGLE_EXT.
This sounds like you could be using non-square power-of-two textures (ie: 128x64). For this you don't need to use any extensions; vanilla OpenGL supports textures with power-of-two dimensions, but the dimensions don't have to be equal. I just wanted to say that because it sounds like that might be your case.

As for your problem, I don't know what might be wrong. That is pretty odd that it doesn't work on an x700 unless you are doing something else wrong that NVIDIA is silently ignoring but ATI is yelling at you for. Are you checking for OpenGL errors? What specific NVIDIA cards is this being tested on?

Share this post

Link to post
Share on other sites
Sunray    188
Try this before drawing anything with texture rectangles;


I know there is a bug with rects and the driver state/cache (ATI told me).

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 povilaslt2
      Hello. I'm Programmer who is in search of 2D game project who preferably uses OpenGL and C++. You can see my projects in GitHub. Project genre doesn't matter (except MMO's :D).
    • By ZeldaFan555
      Hello, My name is Matt. I am a programmer. I mostly use Java, but can use C++ and various other languages. I'm looking for someone to partner up with for random projects, preferably using OpenGL, though I'd be open to just about anything. If you're interested you can contact me on Skype or on here, thank you!
      Skype: Mangodoor408
    • By tyhender
      Hello, my name is Mark. I'm hobby programmer. 
      So recently,I thought that it's good idea to find people to create a full 3D engine. I'm looking for people experienced in scripting 3D shaders and implementing physics into engine(game)(we are going to use the React physics engine). 
      And,ye,no money =D I'm just looking for hobbyists that will be proud of their work. If engine(or game) will have financial succes,well,then maybe =D
      Sorry for late replies.
      I mostly give more information when people PM me,but this post is REALLY short,even for me =D
      So here's few more points:
      Engine will use openGL and SDL for graphics. It will use React3D physics library for physics simulation. Engine(most probably,atleast for the first part) won't have graphical fron-end,it will be a framework . I think final engine should be enough to set up an FPS in a couple of minutes. A bit about my self:
      I've been programming for 7 years total. I learned very slowly it as "secondary interesting thing" for like 3 years, but then began to script more seriously.  My primary language is C++,which we are going to use for the engine. Yes,I did 3D graphics with physics simulation before. No, my portfolio isn't very impressive. I'm working on that No,I wasn't employed officially. If anybody need to know more PM me. 
    • 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++.
      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.
  • Popular Now